Motorola Z2 Force (nash) camera does not work (any AOSP 10 up to v209)

[lisandrocarmona]

I'm using Motorola Z2 Force (nash) with system-quack-arm64-ab-vanilla.img (AOSP 10.0 v209). While opening camera, I got a black empty screen and nothing happens.

I've tested twice, rebooting in between, so the two sets of logs should show the same error/issue. I've tested also on Havoc 3.0 (Android 10) and camera did not work either.

logs.zip logs2.zip Thank you

[phhusson]

That's not an OEM treble device, you'll need to ask your treble developer.

Le mar. 14 janv. 2020 à 19:13, Technical notifications@github.com a écrit :

I'm using Motorola Z2 Force (nash) with system-quack-arm64-ab-vanilla.img (AOSP 10.0 v209). While opening camera, I got a black empty screen and nothing happens.

I've tested twice, rebooting in between, so the two sets of logs should show the same error/issue. I've tested also on Havoc 3.0 (Android 10) and camera did not work either.

logs.zip https://github.com/phhusson/treble_experimentations/files/4060663/logs.zip logs2.zip https://github.com/phhusson/treble_experimentations/files/4060664/logs2.zip Thank you

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1069?email_source=notifications&email_token=AAAA4OT6M4G7KRNHS3Z4BYLQ5X6DFA5CNFSM4KGXLOI2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IGEI4JQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OS55F4ZQXXEAAPJ24LQ5X6DFANCNFSM4KGXLOIQ .

[lisandrocarmona]

Thank you. Does it make any difference that all pie treble versions work? I'm using a pie vendor.

[ModHatter6811]

Thank you. Does it make any difference that all pie treble versions work? I'm using a pie vendor.

Your device only supports up to EGL 1.4 and Android 10 uses EGL 1.5 (Khronos). Your vendor libs are out of date. There's no fixing that buddy. That's 100% an OEM issue.

E/libEGL (4573): Driver indicates EGL 1.5 support, but does not have a critical API 01-14 14:47:49.360 W/ActivityTaskManager(1111): Activity stop timeout for ActivityRecord{b9cb759 u0 com.android.camera2/com.android.camera.CameraLauncher t13}

[phhusson]

This doesn't seem to be a critical issue

Le mer. 15 janv. 2020 à 12:24, ModHatter6811 notifications@github.com a écrit :

Thank you. Does it make any difference that all pie treble versions work? I'm using a pie vendor.

Your device only supports up to EGL 1.4 and Android 10 uses EGL 1.5 (Khronos). Your vendor libs are out of date. There's no fixing that buddy. That's 100% an OEM issue.

E/libEGL (4573): Driver indicates EGL 1.5 support, but does not have a critical API 01-14 14:47:49.360 W/ActivityTaskManager(1111): Activity stop timeout for ActivityRecord{b9cb759 u0 com.android.camera2/com.android.camera.CameraLauncher t13}

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1069?email_source=notifications&email_token=AAAA4OVNWZR644N7BOMGMRDQ53W5FA5CNFSM4KGXLOI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI77Q4I#issuecomment-574617713, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OTK6MUYBPP2DCIBMFTQ53W5FANCNFSM4KGXLOIQ .

[ModHatter6811]

This doesn't seem to be a critical issue Le mer. 15 janv. 2020 à 12:24, ModHatter6811 notifications@github.com a écrit : … Thank you. Does it make any difference that all pie treble versions work? I'm using a pie vendor. Your device only supports up to EGL 1.4 and Android 10 uses EGL 1.5 (Khronos). Your vendor libs are out of date. There's no fixing that buddy. That's 100% an OEM issue. E/libEGL (4573): Driver indicates EGL 1.5 support, but does not have a critical API 01-14 14:47:49.360 W/ActivityTaskManager(1111): Activity stop timeout for ActivityRecord{b9cb759 u0 com.android.camera2/com.android.camera.CameraLauncher t13} — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1069?email_source=notifications&email_token=AAAA4OVNWZR644N7BOMGMRDQ53W5FA5CNFSM4KGXLOI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI77Q4I#issuecomment-574617713>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OTK6MUYBPP2DCIBMFTQ53W5FANCNFSM4KGXLOIQ .

It's not. It looks like there's no mapper in vendor, and that's really not your problem. Their dev might be able to fix it by defining the camera hal at, /vendor/etc/vintf/manifest.xml with

<manifest version="1.0" type="device" target-level="1"> <hal format="hidl"> <name>android.hardware.camera.provider</name> <transport>hwbinder</transport> <version>2.4</version> <interface> <name>ICameraProvider</name> <instance>legacy/0</instance> </interface> <fqname>@2.4::ICameraProvider/legacy/0</fqname> </hal> <hal format="hidl"> <name>android.hardware.graphics.mapper</name> <transport arch="32+64">passthrough</transport> <version>2.0</version> <interface> <name>IMapper</name> <instance>default</instance> </interface> <fqname>@2.0::IMapper/default</fqname> </hal> </manifest>

manifest.xml.txt

This also assumes that /vendor/lib/hw/android.hardware.camera.provider@2.4-impl.so & /vendor/lib/hw/android.hardware.graphics.mapper@2.0-impl.so exist, and there's no guarantee it'll work. They might need to delete the "32+" after "arch=" as well.