natekc
commented
7 years ago Open natekc opened 7 years ago
natekc
commented
7 years ago natekc
commented
7 years ago According to vampirefo, the camera libs depend on lib3a.so and libdpframework.so, which somehow makes it incompatible with libc.so and libandroidruntime.so.. (this is totally irrelevant)
zhaofengli
commented
7 years ago danielhk's camera wrapper could be of use. Also see his changes to the vendor makefiles.
natekc
commented
7 years ago Looks like our libs don't crash at the same place that danielhk's did..
Somehow we get the wrong PID for the media process when trying to connect to the camera service from cameraManagerGlobal.
natekc
commented
7 years ago It really is a mystery why the libs aren't working. According to DeckerSu who had very similar error (or lack of) message to us, camera can be fixed by adding all the missing libs. Unfortunately that didn't work.. I used ndk-depends to show all deps for the camera hal. I even dlopen each individual camera related library and they were all fine.
natekc
commented
7 years ago Confirmed that danielhk's camera wrapper would be useless for us. getResolution() works correctly for our HAL because I can see the calls completing successfully in kernel space.
Zombie-Ryushu
commented
6 years ago Has anyone attempted to use a Kernel driver from another similar BLU Device that runs Nougat?
natekc
commented
6 years ago No that won't fix anything. The problem isn't in the kernel.
rob-3
commented
6 years ago Just a shot in the dark... mrmazak has improved the stability of his camera on his LineageOS 13 port and Slim6 port by substituting Open Camera instead of the default app. Any chance this would help us here?
natekc
commented
6 years ago Sorry, open camera won't help us here if our camera isn't working at all. The problem is at the library level (probably libcamera_client.so or libcameraservice.so). My current guess is that MTK modified something there that is needed for the camera to work.
Zombie-Ryushu
commented
6 years ago Exactly. The most sensible solution I see is for one of the team members to buy a Nougat MediaTek device, figure out what was done, then build what we learn into all subsequent MediaTek Roms.
rob-3
commented
6 years ago Do we just need to get some MediaTek nougat camera libraries from some device?
Zombie-Ryushu
commented
6 years ago Some additional new stuff has been learned from the BLU R2, but, as far as I know. The Nougat Rom is still broken with regard to Bluetooth, and the Camera. You can still use Bluetooth and the Camera with the LineageOS 13.1 Marshmellow Rom, but you'll be vulnerable to KRACK
Zombie-Ryushu
commented
6 years ago Has anyone worked on this?
aaronbooker
commented
6 years ago I would donate my R1 HD for the duration of figuring this out and pay shipping both ways... :-)
I really appreciate what you guys are doing. Thank you! Would love to get Lineage OS on it with a working camera.
Zombie-Ryushu
commented
6 years ago That exists, the LineageOS 13 Rom has a working Camera. Its LineageOS 14 thats a problem.
aaronbooker
commented
6 years ago Sorry - I realized that. I meant a working camera without security exploits. In reading the thread, it sounded like a device could be useful for the devs?
On Feb 1, 2018, at 2:46 PM, Zombie-Ryushu notifications@github.com wrote:
That exists, the LineageOS 13 Rom has a working Camera. Its LineageOS 14 thats a problem.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/blumonks/android_device_blu_p6601/issues/1#issuecomment-362427843, or mute the thread https://github.com/notifications/unsubscribe-auth/AiYrJzRSmqCr9A0vXHvcq7QGU9hTTzOqks5tQj7cgaJpZM4NvKCl.
Zombie-Ryushu
commented
6 years ago Not another R1 HD. The issue is this. BLU Either doesn't have the Drivers, or won't because it threatens BLU's Business model, produce a fully working Nougat Rom for the R1 HD. The WPA Supplicant Krack issue can be fixed in the Marshmellow rom by recompiling WPA Supplicant independently. That would require either a system loaded Zip (Loaded from TWRP) or a completely new Marshmellow Rom. Remember, KRACK is in WPA Suppplicant. Not the Kernel.
Its very unusual for BLU to update their devices an Android version. When they do,its usually the high end models with Qualcomm chips rarther than MediaTek. This is why they don't sell Phones with Oreo.
Either they don't have the drivers, or they are holding them back to use as a carrot and stick to get consumers to Purchase new devices.
What was being was attempted to get the R1 HD to use Drivers from the BLU R2 LTE.
rob-3
commented
6 years ago @aaronbooker Kazudante on XDA only stopped development due to lack of a device. Maybe you could get in touch with him?
Zombie-Ryushu
commented
6 years ago I own one. But am using it. Can't he just buy a used one?
Mohammadalin
commented
5 months ago can i change this two file form andoid 5.1 to 7.1 will it work ?