Yeah, too much time to spend, when the results will be the same no camera, no gps.
Sent from my LineageOS (R1HD) using Tapatalk
(Discontinued) Lineage OS For R1HD (Discontinued)
- Thread starter vampirefo
- Start date
Sent from my LineageOS (R1HD) using Tapatalk
@vampirefo i was just looking into something and came to realie that the file_context.bin is our first major downfall regarding the camera and the gps......use a hex editor and compare both stock file_contexts and LineageOS file_contexts.bin file and you will see the big difference in them , just search for camera and youl see.....i don't think this devellopment is nearly over.....plus simply switching out filecontexts with stock does not boot
@vampirefo looking deeper into the file contexts file the devices that are set for the camera,gps are totally different from the ones in our device's file_context....i think we may have found the reason why.
this way you can look at without hexeditor
https://github.com/vampirefo/android_device_blu_p6601/blob/master/sepolicy/file_contexts
You may be on to something, I see several things different , tomorrow will make changes and recompile.
Last edited:
true but the one from stock has way more compared to that one alot more refrences that are missing . example : (picture)
Edit : theres more 2nd pic and after it come gyro refrences and so on , im not sure if its the key but its worth the try
Last edited:
@vampirefo in the source for device i see that mtk_SMI is linked to camera but in stock these are the only 2 : u
bject_r:mtk_sched_device:s0
/dev/MTK_SMI(/.*)? ubject_r:MTK_SMI_device:s0 /dev/mtk_rrc(/.*)?
where the smily face popped up was supposed to be an o for object....idk why this always happen when i post codes. is there a way to turn that off?
bject_r:mtk_sched_device:s0/dev/MTK_SMI(/.*)? u
bject_r:MTK_SMI_device:s0 /dev/mtk_rrc(/.*)?where the smily face popped up was supposed to be an o for object....idk why this always happen when i post codes. is there a way to turn that off?
Last edited:
Use Pastebin to copy/paste code and share a link here. Cleans up the thread a little..@vampirefo in the source for device i see that mtk_SMI is linked to camera but in stock these are the only 2 : u
/dev/MTK_SMI(/.*)? u
where the smily face popped up was supposed to be an o for object....idk why this always happen when i post codes. is there a way to turn that off?
The thing that sticks out to me is IMX258_CAM_CAL_DRV@vampirefo in the source for device i see that mtk_SMI is linked to camera but in stock these are the only 2 : u
/dev/MTK_SMI(/.*)? u
where the smily face popped up was supposed to be an o for object....idk why this always happen when i post codes. is there a way to turn that off?
This camera driver might be an answer.
Sent from my BLU R1 HD using Tapatalk
Last edited:
I don't have this device on me anymore, but it's always so exciting to see your work progress!
Yes that why i quickly posted about the file_context issue.
This is why I love open development, be it open source or just the dev. It really shows how real work is done.
At least for things like this, it is almost never a steady amount of dev. Its work, till you hit a roadblock. Suddenly everything stops, and people try and find some way through. Sometimes you can't find a way, some times you find a shortcut, and sometimes you have to trudge through the mud to get by.
Being able to see this helps you understand how hard this work really, and be that much more thankfull for the work people do for free.
So thanks to all y'all throwing time in in an effort to get this phone even more awesome. Hats off.
At least for things like this, it is almost never a steady amount of dev. Its work, till you hit a roadblock. Suddenly everything stops, and people try and find some way through. Sometimes you can't find a way, some times you find a shortcut, and sometimes you have to trudge through the mud to get by.
Being able to see this helps you understand how hard this work really, and be that much more thankfull for the work people do for free.
So thanks to all y'all throwing time in in an effort to get this phone even more awesome. Hats off.
Last edited:
It looks good, but I don't see how it helps, now if it gave the location of the files, or said what files needed to be loaded.
None the less the info looks nice.
Sent from my BLU R1 HD using Tapatalk
Not sure what is happening. I found the files in the /dev/ folder but size is listed as 0 and when I try to copy them the phone reboots.
Guessing here....
The way linux works, the drivers are a part of the kernel. Also "everything" is a file. Thus what you see in /dev is likely just a reference to the kernel.
What I think is needed is the "blobs" (which I believe is in /system/lib/hw/). Think of this as bios, that are loaded by the kernel on boot. These are closed source, and just released as a built file. Without these "bios", the kernel cant talk with the hardware. However, since they are closed, they often only work with the kernel they were released on.
Our issue is that this phones official rom is Android 6, but for some reason cyanogenmod/lineage for android 6 didn't boot. Cyan/Lineage for android 7 does boot, and seems to work fine/ish. However, the blobs are for Android 6, and are not working.
Again, just guessing here, but what we need is either for Blu to release Android 7 to this phone (doesn't seem likely), or for a phone using the same cpu, and camera/gps to release Android 7 (in 32bit, as issues with 64bit too). Might happen, might not.
Also, someone might find a clever hack to get it working, who knows.
I hav eseen that they are all 0sized and just like you said , they are refrenced files, mostlikely is due to the fact that when you are not using the camera they are not being used since the modules are in the kernel and not external.....so most likely when those files are about to be used or being used they are inflated by the kernel itself and @vampirefo the screenshot that he posted is to tell you the name of the drivers that are needed and the location is always /dev/(drivername) the ones he refered to be the size of 0 , even in the file_context you see that the location is /dev/(drivername) as their location.Guessing here....
The way linux works, the drivers are a part of the kernel. Also "everything" is a file. Thus what you see in /dev is likely just a reference to the kernel.
What I think is needed is the "blobs" (which I believe is in /system/lib/hw/). Think of this as bios, that are loaded by the kernel on boot. These are closed source, and just released as a built file. Without these "bios", the kernel cant talk with the hardware. However, since they are closed, they often only work with the kernel they were released on.
Our issue is that this phones official rom is Android 6, but for some reason cyanogenmod/lineage for android 6 didn't boot. Cyan/Lineage for android 7 does boot, and seems to work fine/ish. However, the blobs are for Android 6, and are not working.
Again, just guessing here, but what we need is either for Blu to release Android 7 to this phone (doesn't seem likely), or for a phone using the same cpu, and camera/gps to release Android 7 (in 32bit, as issues with 64bit too). Might happen, might not.
Also, someone might find a clever hack to get it working, who knows.
I know they are in the kernel, that's not my not my question, I know some are in dev others are not, no matter I am done.
My github is up those that want to continue to try and get it to work are welcome to try.
As I said before blu needs to release 7 or someone else does.
I am looking to get another phone.
Sent from my NS-P08A7100 using Tapatalk
Last edited:
ok, may i suggest, this tablet as your next one.
https://www.walmart.com/ip/RCA-Voya...oid-6.0-Marshmallow-Operating-System/53990885
lol, that way you might be working on the project then..
:good:
That looks like an Intel, can't do much with Intel, root is about it, Intel is harder to work with than mtk.ok, may i suggest, this tablet as your next one.
https://www.walmart.com/ip/RCA-Voya...oid-6.0-Marshmallow-Operating-System/53990885
lol, that way you might be working on the project then..
:good:
Sent from my BLU R1 HD using Tapatalk
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone