That worked, the camera works now, but now android.process.media fails on boot. But it seems to have not serious side-effects, so i will just have to wait untill it is resolved.
Thanks for your help. On Friday, June 6, 2014 7:47:55 PM UTC+1, Eino-Ville Talvala wrote: > > This is due to some additional validation added to a system library in > AOSP; unfortunately the latest available camera binaries fail this > validation. > > You can probably restore functionality if you revert commit > https://android.googlesource.com/platform/system/media/+/9c51a070d0379637a3bddcee89d16273352a6564 > > > > On Friday, June 6, 2014 11:27:57 AM UTC-7, Glenn Kasten wrote: >> >> AOSP master is under active development right now, so it is very likely to >> have occasional build breaks or regressions. If you do find the root >> cause, >> please update here. Or even better if you find a fix, please upload a >> patch using the procedure at >> http://source.android.com/source/submit-patches.html >> AOSP can't accept patches here, either inline or as attachments. >> >> On Friday, June 6, 2014 10:58:17 AM UTC-7, Owain Davies wrote: >>> >>> Hello porters, >>> >>> This about an issue I have found with the on the latest master branch >>> aosp built for the Nexus 5 with the camera. >>> >>> I have today downloaded the latest aosp master branch. I applied the >>> latest proprietary drivers for hammerhead and and built the >>> full_hammerhead_userdebug build. >>> It builds and flashes fine. It starts but when I try to use the camera >>> It fails with "Unfortunately, Camera has stopped.". See attachment >>> LaunchCamera-logcat.log. >>> >>> In summary: >>> >>> At around line 149, bad things start to happen, >>> >>> E/mm-camera( 199): mct_stream_metadata_bus_msg:Failed to do buf_done >>> F/libc ( 3110): system/media/camera/src/camera_metadata.c:497: >>> clone_camera_metadata: assertion "validate_camera_metadata_structure(clone, >>> NULL) == OK" failed >>> F/libc ( 3110): Fatal signal 6 (SIGABRT), code -6 in tid 3273 >>> (cam_stream_proc) >>> I/DEBUG ( 2095): *** *** *** *** *** *** *** *** *** *** *** *** *** >>> *** *** *** >>> There then follows a crash report that idicates that the media server >>> crashed and fingers the "/system/bin/mediaserver" as the victim and >>> consequentially all the related services died. >>> With the media server dead the Camera application throws a fatal >>> exception and dies. >>> There then appear to be many problem in mm_camera running in t PID199, >>> >>> PID199 in this case is /system/bin/mm-qcamera-daemon and is started as a >>> service by init. >>> >>> So, I ran the following command to get adb logcat from boot. >>> adb reboot ; adb logcat > boot-logcat.log >>> >>> Output attached, slightly abbreviated. I have noted the following >>> problems: >>> >>> around line 34: >>> E/mm-camera-img( 199): cac_comp_load:679] Error opening CAC library >>> E/mm-camera( 199): module_cac_init:1027] Error rc -6 >>> >>> But I can track down what the CAC library is or what a reutnr code of -6 >>> means. >>> >>> @46: >>> D/mm-camera-intf( 186): mm_camera_open: dev name = /dev/video1, cam_idx >>> = 1 >>> D/mm-camera-intf( 186): mm_camera_open:failed with I/O error retrying >>> after 20 milli-seconds >>> >>> @435: it fails to open the camera with errors in libsensor and mm-camera >>> >>> Eventually the camera opens @449 but can not get a data stream from the >>> camera @452 >>> >>> It then tries again with the second camera and fails similarly. >>> >>> I have checkd the camera was working on the stock factory image, and if >>> I build clean from the release tag android-4.4.3-r1.1. So something has >>> happened between then and now. I though it might be the tightening up of >>> the sepolicy, but I changed the kernel command line to start with selinux >>> in permissive mode, also I am not seeing any particularly relevant denials. >>> >>> Thanks, >>> >>> Owain >>> >>> P.S. I don't know if this is the right group for this as the Nexus 5 is >>> already supported, and the problems appear to manifest in a proprietary >>> binary, but these are the same drivers that work fine in >>> android-4.4.3-r1.1, so I think it is some thing that changed in the the >>> open source. I hope somebody can point me in the right direction. >>> >> -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
