Guest fattymcdirty Posted September 24, 2011 Report Share Posted September 24, 2011 I've got a ZTE Libra which "should" be hardware-wise the same as the ZTE Blade - now I installed Ginger Stir Fry Beta 26 and the connection through the Camera-App doesn't work on my Libra - this seems to be a bug? Or an hardware-issue? Maybe different camera-hardware? And if yes - how do I get that camera drivers integrated into my ROM? :/ Any fast help is appreciated! Link to comment Share on other sites More sharing options...
Guest t0mm13b Posted September 24, 2011 Report Share Posted September 24, 2011 Find out by inspecting what drivers are used for the camera by digging around in /sys/devices or dmesg. Get the latest kernel sources from github (mentioned elsewhere). Find the appropriate driver for said hardware and and recompile the kernel. Fastboot flash the boot.img with new kernel, and reboot, cross fingers and see what what happens. It would help for the benefit of this community for you to disclose the information on what drivers/hardware etc.... as we're playing blind here.... :) Link to comment Share on other sites More sharing options...
Guest fattymcdirty Posted September 24, 2011 Report Share Posted September 24, 2011 well............ since i don'T have the stock rom (2.2) anymore.. there's nothing listed under the devices section with this ROM now... so.. what to do...? and: i can't find any stock LIBRA rom on the net ANYWHERE... is any1 able to help? Link to comment Share on other sites More sharing options...
Guest t0mm13b Posted September 24, 2011 Report Share Posted September 24, 2011 I've got a ZTE Libra which "should" be hardware-wise the same as the ZTE Blade - now I installed Ginger Stir Fry Beta 26 and the connection through the Camera-App doesn't work on my Libra - this seems to be a bug? Or an hardware-issue? Maybe different camera-hardware? And if yes - how do I get that camera drivers integrated into my ROM? :/ Any fast help is appreciated! Since you say you have installed GSF b26, you should be able to find out via way of using usb cable plugged in and using adb shell and look in the dmesg output for the type of camera and ask on the GSF thread about it :) Link to comment Share on other sites More sharing options...
Guest fattymcdirty Posted September 24, 2011 Report Share Posted September 24, 2011 this is all dmesg gives me http://pastebin.com/UbcsU0YX Link to comment Share on other sites More sharing options...
Guest fattymcdirty Posted September 24, 2011 Report Share Posted September 24, 2011 in /sys/devices/platform i see: msm_camera_mt9t11x.0 msm_camera_ov5642.0 Link to comment Share on other sites More sharing options...
Guest t0mm13b Posted September 24, 2011 Report Share Posted September 24, 2011 this is all dmesg gives me http://pastebin.com/UbcsU0YX Please stop double posting elsewhere at the same time.... cross posting is not a nice thing to do :) looks like you'll have to reboot again and capture all of the dmesg from there and then, from kernel initialization right up to android's home screen :) Link to comment Share on other sites More sharing options...
Guest t0mm13b Posted September 24, 2011 Report Share Posted September 24, 2011 in /sys/devices/platform i see: msm_camera_mt9t11x.0 msm_camera_ov5642.0 That's generic and is already built into the kernel. BTW IIRC, there was a issue with GSF b26 (I don't use it myself - use CM7) Check in the GSF thread and read it from page to page to find out if there's any issue... Other than that I cannot help you... :) Link to comment Share on other sites More sharing options...
Guest fattymcdirty Posted September 24, 2011 Report Share Posted September 24, 2011 and that'S what adb logcat says while booting: I/CameraService( 650): CameraService started (pid=650) I/QualcommCameraHardware( 650): getCameraInfo: IN I/QualcommCameraHardware( 650): getCameraInfo: loading libqcamera at 0x7000dc88 E/mm-camera( 650): mm_camera_get_camera_info: controlfd is invalid No such file or directory I/QualcommCameraHardware( 650): getCameraInfo: numOfCameras = 0 E/QualcommCameraHardware( 650): getCameraInfo: dlclose(libqcamera) I/QualcommCameraHardware( 650): getCameraInfo: OUT so how do i get a working stock rom back on my libra since i don't have a backup? or how do i get a working driver into that rom? i can't compile it on my own since i'm not into deep into this.. :/ Link to comment Share on other sites More sharing options...
Guest fattymcdirty Posted September 25, 2011 Report Share Posted September 25, 2011 is any1 able to provide a stock 2.2 rom for the libra? i stupidly didn't do a backup of it... and how it seems i don't have any chance to get this camera running under 2.3 without the help of some1 of you :/ Link to comment Share on other sites More sharing options...
Guest fattymcdirty Posted September 25, 2011 Report Share Posted September 25, 2011 when i run adb shell dmesg > dmesg.txt from the startup on, i always get the same output, which is quite short: that's all... i it doesn't seem to be the full boot log... any1 able to help? _wait_for_batt_chg_event:1195:ret = 0 <4>[09-25 09:22:13.320005] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1196:msm_batt_wait_for_batt_chg_event: 1196 <4>[09-25 09:22:13.320005] [79: msm_battery] <4>[09-25 09:22:13.320005] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1220: <4>[09-25 09:22:13.320005] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:784:status read ok!base: 105 size: 11 <4>[09-25 09:22:13.320005] [79: msm_battery] <4>[09-25 09:22:13.320005] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:796: <6>[09-25 09:22:13.320005] [79: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 3752, batt_cap = 3 4, batt_temp = 30, chg_fulled = 0 <6>[09-25 09:22:13.320005] [79: msm_battery] <4>[09-25 09:22:13.320005] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:820: <4>[09-25 09:22:13.320005] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:844: <5>[09-25 09:22:13.320005] [79: msm_battery]msm_batt_update_psy_status_v1() : Go t unnecessary event from Modem PMIC VBATT driver. Nothing changed in Battery or charger status <5>[09-25 09:22:13.320005] [79: msm_battery] <4>[09-25 09:22:15.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1195:ret = 0 <4>[09-25 09:22:15.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1196:msm_batt_wait_for_batt_chg_event: 1196 <4>[09-25 09:22:15.320004] [79: msm_battery] <4>[09-25 09:22:15.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1220: <4>[09-25 09:22:15.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:784:status read ok!base: 105 size: 11 <4>[09-25 09:22:15.320004] [79: msm_battery] <4>[09-25 09:22:15.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:796: <6>[09-25 09:22:15.320004] [79: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 3752, batt_cap = 3 4, batt_temp = 30, chg_fulled = 0 <6>[09-25 09:22:15.320004] [79: msm_battery] <4>[09-25 09:22:15.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:820: <4>[09-25 09:22:15.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:844: <5>[09-25 09:22:15.320004] [79: msm_battery]msm_batt_update_psy_status_v1() : Go t unnecessary event from Modem PMIC VBATT driver. Nothing changed in Battery or charger status <5>[09-25 09:22:15.320004] [79: msm_battery] <4>[09-25 09:22:17.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1195:ret = 0 <4>[09-25 09:22:17.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1196:msm_batt_wait_for_batt_chg_event: 1196 <4>[09-25 09:22:17.320004] [79: msm_battery] <4>[09-25 09:22:17.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1220: <4>[09-25 09:22:17.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:784:status read ok!base: 105 size: 11 <4>[09-25 09:22:17.320004] [79: msm_battery] <4>[09-25 09:22:17.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:796: <6>[09-25 09:22:17.320004] [79: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 3752, batt_cap = 3 4, batt_temp = 30, chg_fulled = 0 <6>[09-25 09:22:17.320004] [79: msm_battery] <4>[09-25 09:22:17.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:820: <4>[09-25 09:22:17.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:844: <5>[09-25 09:22:17.320004] [79: msm_battery]msm_batt_update_psy_status_v1() : Go t unnecessary event from Modem PMIC VBATT driver. Nothing changed in Battery or charger status <5>[09-25 09:22:17.320004] [79: msm_battery] sh-4.1# dmesg dmesg <4>[09-25 09:22:19.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1195:ret = 0 <4>[09-25 09:22:19.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1196:msm_batt_wait_for_batt_chg_event: 1196 <4>[09-25 09:22:19.320004] [79: msm_battery] <4>[09-25 09:22:19.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1220: <4>[09-25 09:22:19.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:784:status read ok!base: 105 size: 11 <4>[09-25 09:22:19.320004] [79: msm_battery] <4>[09-25 09:22:19.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:796: <6>[09-25 09:22:19.320004] [79: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 3752, batt_cap = 3 4, batt_temp = 30, chg_fulled = 0 <6>[09-25 09:22:19.320004] [79: msm_battery] <4>[09-25 09:22:19.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:820: <4>[09-25 09:22:19.320004] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:844: <5>[09-25 09:22:19.320004] [79: msm_battery]msm_batt_update_psy_status_v1() : Go t unnecessary event from Modem PMIC VBATT driver. Nothing changed in Battery or charger status <5>[09-25 09:22:19.320004] [79: msm_battery] <4>[09-25 09:22:21.320006] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1195:ret = 0 <4>[09-25 09:22:21.320006] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1196:msm_batt_wait_for_batt_chg_event: 1196 <4>[09-25 09:22:21.320006] [79: msm_battery] <4>[09-25 09:22:21.320006] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _wait_for_batt_chg_event:1220: <4>[09-25 09:22:21.320006] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:784:status read ok!base: 105 size: 11 <4>[09-25 09:22:21.320006] [79: msm_battery] <4>[09-25 09:22:21.320006] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _get_batt_chg_status_v1:796: <6>[09-25 09:22:21.320006] [79: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 3752, batt_cap = 3 4, batt_temp = 30, chg_fulled = 0 <6>[09-25 09:22:21.320006] [79: msm_battery] <4>[09-25 09:22:21.320006] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:820: <4>[09-25 09:22:21.320006] [79: msm_battery]drivers/power/msm_battery.c:msm_batt _update_psy_status_v1:844: <5>[09-25 09:22:21.320006] [79: msm_battery]msm_batt_update_psy_status_v1() : Go t unnecessary event from Modem PMIC VBATT driver. Nothing changed in Battery or charger status <5>[09-25 09:22:21.320006] [79: msm_battery] Link to comment Share on other sites More sharing options...
Guest atlantix Posted September 27, 2011 Report Share Posted September 27, 2011 I've been following this forum for some time but this is my first post since I've got exactly the same problem. Thanks to all the devs and members contributing and helping here at MoDaCo! So I bought a device called Wayteq-ZTE Libra in Germany, read here about flashing custom roms, flashed - worked like a charme - BUT stupidly didn't make a backup of my stock rom. Well, Libra is Blade, isn't it? Unfortenately my Libra is not. Camera hardware seems different and not supported by all the 2.3-roms (new kernel) and many custom 2.2-roms out there. That's why when flashing roms such as GSF or CM - both great roms by the way! - the camera won't work. The driver can't be loaded I guess, and that's why no connection to the camera can be established. But there's a rom which works perfectly with my Libra: The Triple Two Project's rom (see threat here at MoDaCo). It's based on the latest(?) official froyo rom, so no overclocking or overscroll glow. But everything works. And when you change some standard apps (for example the launcher) it runs quite smooth. By the way: when I take a look at /sys/devices/platforms there is beside the above mentioned camera hardware msm_camera_mt9p111.0 msm_camera_s5k5cagx.0 msm_camera_s5k5cagx_mcnex_qtech.0 Hope that helps, cheers. Link to comment Share on other sites More sharing options...
Guest fattymcdirty Posted September 27, 2011 Report Share Posted September 27, 2011 I've been following this forum for some time but this is my first post since I've got exactly the same problem. Thanks to all the devs and members contributing and helping here at MoDaCo! So I bought a device called Wayteq-ZTE Libra in Germany, read here about flashing custom roms, flashed - worked like a charme - BUT stupidly didn't make a backup of my stock rom. Well, Libra is Blade, isn't it? Unfortenately my Libra is not. Camera hardware seems different and not supported by all the 2.3-roms (new kernel) and many custom 2.2-roms out there. That's why when flashing roms such as GSF or CM - both great roms by the way! - the camera won't work. The driver can't be loaded I guess, and that's why no connection to the camera can be established. But there's a rom which works perfectly with my Libra: The Triple Two Project's rom (see threat here at MoDaCo). It's based on the latest(?) official froyo rom, so no overclocking or overscroll glow. But everything works. And when you change some standard apps (for example the launcher) it runs quite smooth. By the way: when I take a look at /sys/devices/platforms there is beside the above mentioned camera hardware msm_camera_mt9p111.0 msm_camera_s5k5cagx.0 msm_camera_s5k5cagx_mcnex_qtech.0 Hope that helps, cheers. nice one! with that info, some1 should be able to implement those drivers into the 2.3 roms? Link to comment Share on other sites More sharing options...
Guest Maxsas360 Posted September 27, 2011 Report Share Posted September 27, 2011 Is it 5mpx? Link to comment Share on other sites More sharing options...
Guest atlantix Posted September 27, 2011 Report Share Posted September 27, 2011 Is it 5mpx? Sorry, forgot to mention: it's 3,2mpx. The model is also sold in Hungary (Wayteq is an hungarian company) in cooperation with ZTE. I've read about all the confusion concerning the new Blade II, Blade+ and the Libra, and as this model is sold here and in Hungary for about two months I think it's not the blade which is announced in the UK. But as mentioned, ZTE's model labelling is quite confusing... Link to comment Share on other sites More sharing options...
Guest wbaw Posted September 27, 2011 Report Share Posted September 27, 2011 (edited) These kernel config options should fix it CONFIG_MT9P111=y # CONFIG_MT9P111_MCNEX is not set CONFIG_MT9P111_SAMSUNG_FPC=y # CONFIG_MT9P111_SAMSUNG_SOCKET is not set CONFIG_S5K5CAGX=y CONFIG_S5K5CAGX_SAMSUNG_FPC=y CONFIG_S5K5CAGX_MCNEX_QTECH=y CONFIG_S5K5CAGX_MCNEX_QTECH_FPC=y I posted a new kernel for gsf in the gsf thread on xda, it'd be appreciated if anybody can test it, see if it does solve the zte libra camera problem & report back. Edited September 27, 2011 by wbaw Link to comment Share on other sites More sharing options...
Guest atlantix Posted September 27, 2011 Report Share Posted September 27, 2011 (edited) These kernel config options should fix it CONFIG_MT9P111=y # CONFIG_MT9P111_MCNEX is not set CONFIG_MT9P111_SAMSUNG_FPC=y # CONFIG_MT9P111_SAMSUNG_SOCKET is not set CONFIG_S5K5CAGX=y CONFIG_S5K5CAGX_SAMSUNG_FPC=y CONFIG_S5K5CAGX_MCNEX_QTECH=y CONFIG_S5K5CAGX_MCNEX_QTECH_FPC=y I posted a new kernel for gsf in the gsf thread on xda, it'd be appreciated if anybody can test it, see if it does solve the zte libra camera problem & report back. Thank You so much for you refforts, wbaw!!! Still no luck here... Looking at /sys/devices/platform there's no directory for msm_camera_s5k5cagx.0 and msm_camera_s5k5cagx_mcnex_qtech.0 as it is with the roms where the camera is working (as I said, Tripple Two Project, for example). May be the reason? However mt9p111 is there. But anyway, thanks! ... and I'm sorry, I don't have my stock rom anymore. Could just dump the boot.img from Tripple Two. Would that help? Edited September 27, 2011 by atlantix Link to comment Share on other sites More sharing options...
Guest KonstaT Posted September 27, 2011 Report Share Posted September 27, 2011 Thank You so much for you refforts, wbaw!!! Still no luck here... Looking at /sys/devices/platform there's no directory for msm_camera_s5k5cagx.0 and msm_camera_s5k5cagx_mcnex_qtech.0 as it is with the roms where the camera is working (as I said, Tripple Two Project, for example). May be the reason? However mt9p111 is there. But anyway, thanks! ... and I'm sorry, I don't have my stock rom anymore. Could just dump the boot.img from Tripple Two. Would that help? Did you ever try the Triple Two Project with the optional Telenor kernel to see if it kills the camera. Only difference in those two kernel configs was that the original chinese one has: CONFIG_S5K5CAGX=y CONFIG_S5K5CAGX_SAMSUNG_FPC=y CONFIG_S5K5CAGX_MCNEX_QTECH=y CONFIG_S5K5CAGX_MCNEX_QTECH_FPC=y [/code] If I have to guess, I'd say that ZTE has released incomplete source code once again. Link to comment Share on other sites More sharing options...
Guest atlantix Posted September 27, 2011 Report Share Posted September 27, 2011 Did you ever try the Triple Two Project with the optional Telenor kernel to see if it kills the camera. Only difference in those two kernel configs was that the original chinese one has: CONFIG_S5K5CAGX=y CONFIG_S5K5CAGX_SAMSUNG_FPC=y CONFIG_S5K5CAGX_MCNEX_QTECH=y CONFIG_S5K5CAGX_MCNEX_QTECH_FPC=y If I have to guess, I'd say that ZTE has released incomplete source code once again. Yes, I did.. forgot to mention, sorry! And... indeed, the Telenor kernel breaks the camera! Link to comment Share on other sites More sharing options...
Guest fattymcdirty Posted October 3, 2011 Report Share Posted October 3, 2011 so what does that mean? is it still somehow possible to get the libra camera working with the zte blade stock roms? and if yes - what would be necessary for it? or do we have to stick to 2.2 now forever with our libra..? Link to comment Share on other sites More sharing options...
Guest Tom G Posted October 8, 2011 Report Share Posted October 8, 2011 Could you try this rom. I doubt your camera will work, but it will hopefully provide some more information. cm-7.1.0-cam-test.zip md5 a4e5c95f6a7393097893e686e3f04682 Please provide logs. dmesg and logcat. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now