Develop Bugs

HTC Evo 4G 0004 camera problem

I have searched around looking for a fix for this, but everything I find seems to be related to people who are rooted and running custom roms/kernels. The handset in question here is a completely stock Evo.
One of my users has a Evo HW version 0004
Somehow his kid was playing with it and messed up the settings for his google account associated with the phone, and in his attempt to fix it, he ended up deleting the actual google account. This left the handset with a stranded google account that it couldn't log into...
I did a factory reset on the phone, added a newly created google account, and got everything back in working order... or so I thought.
This morning he comes back with a complaint that the camera won't work.
When you launch the camera app, you get the white camera logo for a second, then the screen just goes black and the only way to get out is to press the home key. Same thing for the camcorder app.
What I have noticed after going into Settings -> Applications is that the camera app is not generating any data. I figured that it may have something cached that just needed to be cleared, but with 0.00k of data, the button is just greyed out. I checked this against my Evo, and mine shows 4.00k of data, so I know there is supposed to be at least something there.
I also tried to boot into recovery to clear cache that way, but when I choose the recovery option I just get a picture of a phone with a red exclamation mark logo on the screen.
I also have tested the theory that this camera issue can be caused by unreadable data on the microSD card. I removed his card and installed a freshly formatted card with 0 information on it and had the same results.
I have tried rebooting the handset, reinstalling the camera app, force quitting the app and restarting, and even as a member here suggested in another thread smacking it around a bit to assert dominance... No dice.
Hopefully someone has run into this issue on a non-rooted, completely stock phone before.

You will need to run the latest official ruu from sprint. Also you could go to settings and try firmware update and see if the fixes it. Your camera driver is probably missing. Did you restore an old ruu? If you need the link ill try to find it since I'm on my phone and at lunch. Ill update this post with it!
Just grab the full update and run the ruu it should fix the camera.
http://forum.xda-developers.com/showthread.php?t=740319
Most likely their kid didn't do that maybe they did that to get a new evo!(possibility) Lol Was the phone wiped before you got hold of it?

I'd run an RUU on the phone to get everything cleaned out, and if it's still not working, take it in to Sprint. Maybe they'll replace it for such a glitch?

dirkyd3rk said:
You will need to run the latest official ruu from sprint. Also you could go to settings and try firmware update and see if the fixes it. Your camera driver is probably missing. Did you restore an old ruu? If you need the link ill try to find it since I'm on my phone and at lunch. Ill update this post with it!
Just grab the full update and run the ruu it should fix the camera.
http://forum.xda-developers.com/showthread.php?t=740319
Most likely their kid didn't do that maybe they did that to get a new evo!(possibility) Lol Was the phone wiped before you got hold of it?
Click to expand...
Click to collapse
3.26.651.3 is most current? This is what it went back to after Factory Reset, and I ran the OTA 3.70.651.1 today and nothing changed. Is there a full 3.70 anywhere that you know of?
Edit: drmacinyasha, you must have snuck in with the 3.70 while I was typing

netstat_EVO said:
3.26.651.3 is most current? This is what it went back to after Factory Reset, and I ran the OTA 3.70.651.1 today and nothing changed. Is there a full 3.70 anywhere that you know of?
Click to expand...
Click to collapse
You could run that one, then to the HTC firmware update from the phone. But let me find the 3.70 ruu gimmie few mins.
Here's the 3.70, good luck.
http://forum.xda-developers.com/showthread.php?t=877438

getting this from adb
Code:
error: insufficient permissions for device
Stupid question, but do I have to root the broken phone to fix it?

netstat_EVO said:
getting this from adb
Code:
error: insufficient permissions for device
Stupid question, but do I have to root the broken phone to fix it?
Click to expand...
Click to collapse
No you shouldn't have to root! Do you have htc sync installed on the comp that might be the prob. Make sure the comp is picking up the phone. Head over to HTC.com to get HTC sync or Google search would take you there.

dirkyd3rk said:
No you shouldn't have to root! Do you have htc sync installed on the comp that might be the prob. Make sure the comp is picking up the phone. Head over to HTC.com to get HTC sync or Google search would take you there.
Click to expand...
Click to collapse
HTC Sync doesn't play with unix/linux

netstat_EVO said:
HTC Sync doesn't play with unix/linux
Click to expand...
Click to collapse
Ohh then there's your problem right there. You will need HTC for adb to pick up correctly meaning you need a windows machine. I'm sures there's long ways around it but I'm not sure of them. Maybe if someone else can chime in to help. As far as I know that ruu is for win and won't run unless HTC sync is installed and picking up the phone. :-( You could root then flash a stock(3.70) rom and get it back on that way for 0004 which would be faster.

got it working, pushing zips now.
trick was just to restart adb
What it was doing:
Code:
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb push ./unrevoked-forever-son.zip /sdcard/
error: insufficient permissions for device
and
Code:
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb devices
List of devices attached
???????????? no permissions
So I just restarted adb
Code:
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb kill-server
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb devices
List of devices attached
[serialNumber] device
And all seems to be right with the world ... so far, we'll see after this flash process is done

netstat_EVO said:
got it working, pushing zips now.
trick was just to restart adb
What it was doing:
Code:
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb push ./unrevoked-forever-son.zip /sdcard/
error: insufficient permissions for device
and
Code:
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb devices
List of devices attached
???????????? no permissions
So I just restarted adb
Code:
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb kill-server
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/android-sdk-linux_x86/platform-tools# ./adb devices
List of devices attached
[serialNumber] device
And all seems to be right with the world ... so far, we'll see after this flash process is done
Click to expand...
Click to collapse
Wow great man, lets us know how it goes. I don't use linux so I don't know much. I use Mac and do adb in boot camp windows 7 lol. You seem to be on the right track.

Getting (e) can't open PC36IMG.zip
(bad)
from phone... MD5 checks out. I don't get it.

netstat_EVO said:
Getting (e) can't open PC36IMG.zip
(bad)
from phone... MD5 checks out. I don't get it.
Click to expand...
Click to collapse
Continued with steps regardless of error, and recovery seems to be loading it ... fingers crossed.

Well ... something good came out of this. I now know how to RUU a phone...
But, the camera is still dead. Can it just die like that? It worked before Factory Reset, and was not dropped after, so I really doubt there is any physical damage.

netstat_EVO said:
Well ... something good came out of this. I now know how to RUU a phone...
But, the camera is still dead. Can it just die like that? It worked before Factory Reset, and was not dropped after, so I really doubt there is any physical damage.
Click to expand...
Click to collapse
Wow that blows, maybe it actually just went out. You seem to have done everything correct I'm out of ideas :-( its possible that it could have just died I've heard of people's cameras dying. I can't explain it dying after the reboot though. Maybe something went down that you're unaware of? I wish I could help more....

for anyone who may have some insight as to actually make heads or tails out of what logcat generates... This is what I can find that seems to be related when I open the camera app on this device.
Code:
I/ActivityManager( 97): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.CameraEntry bnds=[365,586][475,704] }
D/AK8973 ( 69): Compass Start
D/Sensors ( 97): open_akm, fd=116
I/WindowManager( 97): Setting rotation to 1, animFlags=1
I/ActivityManager( 97): Config changed: { scale=1.0 imsi=310/120 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=10}
W/HTCCamera( 1612): onNewIntent: com.android.camera.CameraEntry
W/HTCCamera( 1612): need to do create, not to initate mode onNewIntent!!
W/HTCCamera( 1612): onRestart() - start
W/HTCCamera( 1612): onRestart() - end
W/HTCCamera( 1612): onStart() - start
W/HTCCamera( 1612): onStart() - end
W/HTCCamera( 1612): onResume() - start
W/HTCCamera( 1612): !!!! @@@@ broadcastStopVoiceRecording() - start
W/HTCCamera( 1612): !!!! @@@@ broadcastStopVoiceRecording() - end
W/HTCCamera( 1612): Initial Display Orientation is landscape
W/HTCCamera( 1612): mIsInitOrientation = false, mIsWaitOrientation = false
W/HTCCamera( 1612): OnResume - reset UI, immediately set mMainLayout invisible
W/########## HtcSettingsReceiver ##########( 1612): 2011-04-06 04:29:15 861(ms) onReceive-start
W/HTCCamera( 1612): Block Capture UI - onResume(), and unblock after start preview
W/HTCCamera( 1612): onResume() - mFocusingState = NO_FOCUSING
W/HTCCamera( 1612): keyguard is not shown !!!!!
W/HTCCamera( 1612): onResume() - end
W/HTCCamera( 1612): $$$$$$$$$$$$$$$$$$$$$$$$$$$$$ surfaceCreated [email protected]
W/HTCCamera( 1612): $$$$$$$$$$$$$$$$$$$$$$$$$$$$$ surfaceCreated $$$$$$$$$$$$$$$$$$$$$$$$$$$ start preview
W/HTCCamera( 1612): $$$$$$$$$$$$$$$$$$$$$$$$$$$$$ surfaceChanged $$$$$$$$$$$$$$$$$$$$$$$$$$$ w=800 h=480
W/IInputConnectionWrapper( 219): showStatusIcon on inactive InputConnection
D/PowerManagerService( 97): New lightsensor value:160, lcdValue:164
D/dalvikvm( 97): GC_EXPLICIT freed 7778 objects / 367488 bytes in 106ms
D/dalvikvm( 615): GC_EXPLICIT freed 948 objects / 46040 bytes in 52ms
I/ActivityManager( 97): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.htc.launcher/.Launcher }
W/HTCCamera( 1612): onPause() - start
W/HTCCamera( 1612): onPause() - mIsUIReady = false
W/########## HtcSettingsReceiver ##########( 1612): 2011-04-06 04:29:21 988(ms) onReceive-start
W/HTCCamera( 1612): AudioManager.STREAM_SYSTEM_ENFORCED, to fix volume ,mOriginalVolume = -1
W/HTCCamera( 1612): onPause() - mFocusingState = NO_FOCUSING
W/HTCCamera( 1612): OnPause - set mWaitResetSettings to false
W/HTCCamera( 1612): releaseFaceDetection()
W/HTCCamera( 1612): onPause mIdle is false
W/HTCCamera( 1612): onPause() - end
D/Sensors ( 97): close_akm, fd=116
I/WindowManager( 97): Setting rotation to 0, animFlags=1
D/PowerManagerService( 97): New lightsensor value:160, lcdValue:164
I/ActivityManager( 97): Config changed: { scale=1.0 imsi=310/120 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=11}
D/AK8973 ( 69): Compass CLOSE
W/HTCCamera( 1612): doOnPause() - start
W/HTCCamera( 1612): OnPause - hide UI, set mMainLayout invisible
W/HTCCamera( 1612): doOnPause() - end
W/HTCCamera( 1612): $$$$$$$$$$$$$$$$$$$$$$$$$$$$$ surfaceDestroyed $$$$$$$$$$$$$$$$$$$$$$$$$$$
W/HTCCamera( 1612): onStop() - start
W/HTCCamera( 1612): onStop() - end
D/dalvikvm( 97): GC_EXPLICIT freed 2571 objects / 112000 bytes in 104ms
The handset is most likely being replaced at Sprint tomorrow morning, but I am still curious as to what the root problem actually is.

solution
hey, im new here as a member but ive been browsing these forums for quite a while. the solution to your camera problem is to format the sdcard, i had the same prob almost... the camera would work but the camcorder would go black and i would have to end the process through a task killer or restart the phone. after a complete format of the sdcard it worked again just fine. just thought id throw in my 2 cents i hope this helps.

hate138 said:
hey, im new here as a member but ive been browsing these forums for quite a while. the solution to your camera problem is to format the sdcard, i had the same prob almost... the camera would work but the camcorder would go black and i would have to end the process through a task killer or restart the phone. after a complete format of the sdcard it worked again just fine. just thought id throw in my 2 cents i hope this helps.
Click to expand...
Click to collapse
How do u format the sd card? I tried using as card reader but now the sd card keep forever to open, tried other computers and still the same, seems its been as partition that's why can't open now using as card reader, am I correct?

tony888 said:
How do u format the sd card? I tried using as card reader but now the sd card keep forever to open, tried other computers and still the same, seems its been as partition that's why can't open now using as card reader, am I correct?
Click to expand...
Click to collapse
Well if you are rooted and have a custom recovery loaded, you can select the wipe then sdcard option. Then it would be best to partition to 1024 ext and 0 swap then go ext2 to ext3 and ext3 to ext4. Since the OP is not rooted they can mount the card via USB to a PC, right click on the drive and select format.
From what I get, seems like a write issue with the hardware to the SD. They already tried a different SD so that is out. Has to be a write issue that is hw related regardless what ruu is used. Try to download something such as a jpg or test doc directly to the phone to see if it writes and saves.
Sent from my PC36100 using xda premium

[Q] "Cannot connect to camera" in all AOSP based aftermarket ROMs

I finally got the chance to purchase a Galaxy S III yesterday and so far it's proving to be a gorgeous device. Not being a huge fan of TouchWiz, I decided to go the CM route, and decided to be brave and use the 10.1 nightlies. Everything works except the camera, which upon being started, displays "Camera error: Cannot connect to camera" and the app exits.
This is not just a bug with CM Nightly. (Otherwise I wouldn't be asking for support.) This symptom has been observed with the following ROMs:
CyanogenMod 10.1 nightly (2013-01-16) - flashed via CWM and TWRP
CyanogenMod 10.0 stable - flashed via TWRP
LiquidSmooth JB v2.1 beta 2 (based on 4.2.1) - flashed via CWM
It appears that only one other person has had this issue with d2tmo. My device is brand new, as in purchased 18 hours ago new. Date on the box is December 31, 2012. It's a 16GB Titanium Grey T-Mobile model, if that is of any relevance.
I have not yet encountered any AOSP based ROM in which the camera works. I have already attempted the following troubleshooting steps, with no luck:
Wipe dalvik cache/cache partition
Fix permissions (via the option in both TWRP and CWM)
Manually shelling in and chmodding /dev/video* to 0666. They were owned previously by root/camera with mode 0660.
I did an adb logcat and found the Java traceback where the camera open fails:
Code:
I/ActivityManager( 643): Displayed com.android.gallery3d/com.android.camera.CameraLauncher: +390ms
D/dalvikvm( 4160): GC_CONCURRENT freed 1410K, 6% free 18148K/19252K, paused 3ms+4ms, total 32ms
D/dalvikvm( 4160): WAIT_FOR_CONCURRENT_GC blocked 17ms
D/qdoverlay( 237): Unset pipe=RGB1 dpy=0;
E/Sensors ( 643): accelHandler 3.133883 2.830913 8.935818
D/qdoverlay( 237): Set pipe=RGB1 dpy=0;
E/mm-camera( 240): mm_camera_open: ctrl_fd = -1
E/mm-camera( 240): Errno:5
E/MP-Decision( 1326): DOWN Ld:34 Ns:1.100000 Ts:190 rq:0.100000 seq:196.000000
E/mm-camera( 240): mm_camera_open: ctrl_fd = -1
E/mm-camera( 240): Errno:5
E/mm-camera( 240): mm_camera_open: opened, break out while loop
E/mm-camera( 240): mm_camera_open: after while loop
E/QCameraHWI( 240): startCamera: cam_ops_open failed: id = 0
W/QualcommCamera2( 240): int android::camera_device_open(const hw_module_t*, char const*, hw_device_t**): end
E/CameraClient( 240): Could not open camera 0: -1
E/CameraClient( 240): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
I/CameraClient( 240): Destroying camera 0
E/CameraHolder( 4160): fail to connect Camera
E/CameraHolder( 4160): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 4160): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 4160): at android.hardware.Camera.<init>(Camera.java:340)
E/CameraHolder( 4160): at android.hardware.Camera.open(Camera.java:302)
E/CameraHolder( 4160): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
E/CameraHolder( 4160): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/CameraHolder( 4160): at com.android.camera.Util.openCamera(Util.java:358)
E/CameraHolder( 4160): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:327)
D/qdoverlay( 237): Unset pipe=RGB1 dpy=0;
So my theory is a permissions issue. I poked around for anything in /dev that was owned by the "camera" group and chmodded it to 0666, just to temporarily see if it'd work... no dice.
I'm certainly no Linux noob, though I don't hack on android much and I don't know all the terrible things they've done to the kernel, but if anyone has more advanced troubleshooting suggestions, throw 'em at me.
Any help would be much appreciated. Thanks!

Seen it happen to my wife's S2 running CM10 stable.. but I simply clicked the camera icon again, and it connected. Never had an issue again.. weird.

*bump*
I found that starting the camera produces some rather extensive dmesg output:
Code:
<3>[ 1072.801739] store_afe_cal: offset 1089687720 is > mem_len 344064
<6>[ 1072.821150] msm_pcm_routing_process_audio: reg 0 val 0 set 1
<6>[ 1072.821364] msm8960_i2s_startup
<6>[ 1072.826399] msm8660_i2s_hw_params Codec Clock 0xc0c372bc ; Rx Bit Clock c0c37228
<6>[ 1072.826399] tabla_hw_params: DAI-ID 1 rate : 48000
<6>[ 1072.826430] msm_pcm_routing_hw_params : channel = 2
<6>[ 1072.831313] msm_pcm_routing_prepare : be_id = 0
<6>[ 1072.842606] afe_q6_interface_prepare:
<6>[ 1072.854387] msm8960_enable_codec_ext_clk: enable = 1
<6>[ 1072.908866] msm_dai_q6_trigger:port:0 cmd:1 dai_data->status_mask = 0
<6>[ 1072.908866] afe_send_cal
<6>[ 1072.927636] mdp_bus_scale_update_request: handle=-460495872 index=2 ab=1610612736 ib=1744830464
<4>[ 1072.942804] CPU1: Booted secondary processor
<7>[ 1072.947138] [cam_ldo_power_on : 1816] REAR CAMERA POWER ON!!
<7>[ 1072.947138] [s5c73m3] rear camera on 1
<7>[ 1072.947169] [s5c73m3] check GPIO_CAM_FLASH_SW : 1
<7>[ 1072.951747] [s5c73m3] check vddCore : 1150000
<6>[ 1072.952906] CAM_ISP_CORE voltage is enabled to 1150 mV by selector value [38]
<7>[ 1072.954158] [s5c73m3] check GPIO_CAM_A_EN : 1
<7>[ 1072.956111] [s5c73m3] check GPIO_CAM_SENSOR_EN : 1
<7>[ 1072.958461] [cam_ldo_power_on : 1816] REAR CAMERA POWER ON!!
<7>[ 1072.958461] [s5c73m3] rear camera on 2
<7>[ 1072.958492] [s5c73m3] check CAM_AF_EN : 1
<6>[ 1072.960475] mdp_bus_scale_update_request: handle=-460495872 index=1 ab=805306368 ib=872415232
<7>[ 1072.962276] [s5c73m3] check CAM_MIPI_EN : 1
<7>[ 1072.964382] [s5c73m3] check ISP_RESET : 1
<6>[ 1072.981565] TIMERIRQ_START : period=200
<6>[ 1072.981657] Sensors set: 70
<6>[ 1072.984526] <6>MPL-accmpu6050_set_odr:199
<6>[ 1072.984648] <6>MPL-accODR : 5000 (199)mHz
<3>[ 1073.006622] [s5c73m3_sensor_init:3410] Entered
<3>[ 1073.010285] [s5c73m3_sensor_init_probe:3358] Entered
<3>[ 1073.022188] [s5c73m3_check_fw:3124] Enter
<3>[ 1073.064428] [s5c73m3_get_sensor_fw_version : 2768] sensor_fw = ZHFJ02
<3>[ 1073.070318] [s5c73m3_get_phone_fw_version:2844] Entered
<3>[ 1073.086586] [s5c73m3_get_phone_fw_version:2957] can't open ZHFJ02. download from F-ROM
<3>[ 1073.095131] [s5c73m3_reset_module:424] E
<7>[ 1073.098550] [cam_ldo_power_off : 1987] REAR CAMERA POWER OFF!!
<7>[ 1073.115122] [s5c73m3] check GPIO_CAM_FLASH_SW : 0
<7>[ 1073.116740] [cam_ldo_power_on : 1816] REAR CAMERA POWER ON!!
<7>[ 1073.116740] [s5c73m3] rear camera on 1
<7>[ 1073.116770] [s5c73m3] check GPIO_CAM_FLASH_SW : 1
<7>[ 1073.119304] [s5c73m3] check vddCore : 1150000
<6>[ 1073.133373] CAM_ISP_CORE voltage is enabled to 1150 mV by selector value [38]
<7>[ 1073.135937] [s5c73m3] check GPIO_CAM_A_EN : 1
<7>[ 1073.137890] [s5c73m3] check GPIO_CAM_SENSOR_EN : 1
<7>[ 1073.141431] [cam_ldo_power_on : 1816] REAR CAMERA POWER ON!!
<7>[ 1073.141461] [s5c73m3] rear camera on 2
<7>[ 1073.141461] [s5c73m3] check CAM_AF_EN : 1
<7>[ 1073.148084] [s5c73m3] check CAM_MIPI_EN : 1
<7>[ 1073.152937] [s5c73m3] check ISP_RESET : 1
<3>[ 1073.155562] [s5c73m3_reset_module:441] X
<3>[ 1073.170028] [s5c73m3_get_sensor_fw_binary:2453] Entered
<6>[ 1073.308438] mdp_bus_scale_update_request: handle=-460495872 index=2 ab=1543503872 ib=1677721600
<3>[ 1073.583732] [s5c73m3_get_sensor_fw_binary:2549] sent SPI ready CMD
<3>[ 1074.108438] [s5c73m3_get_sensor_fw_binary:2578] made CSC value by S/W = 0x563c77e
<3>[ 1074.115153] [s5c73m3_get_sensor_fw_binary:2584] Original CRC Int = 0x563c77e
<3>[ 1074.126018] [s5c73m3_get_sensor_fw_binary : 2593] failed to open /data/SlimISP_ZH.bin, err -13
<3>[ 1074.133831] [s5c73m3_get_sensor_fw_binary:2622] Exit
<3>[ 1074.138776] [s5c73m3_get_phone_fw_version : 2962] i2c failed, err -22
<3>[ 1074.146406] [s5c73m3_check_fw : 3137] failed s5c73m3_get_phone_fw_version!!
<3>[ 1074.152601] [s5c73m3_sensor_init_probe : 3376] failed s5c73m3_check_fw!!
<3>[ 1074.159957] [s5c73m3_sensor_init : 3428] s5c73m3_sensor_init failed!
<3>[ 1074.165786] msm_mctl_open_init: isp init failed: -5
<7>[ 1074.178147] [cam_ldo_power_off : 1987] REAR CAMERA POWER OFF!!
<7>[ 1074.188615] [s5c73m3] check GPIO_CAM_FLASH_SW : 0
<3>[ 1074.189714] msm_open_init: HW open failed rc = 0xfffffffb
<7>[ 1074.214527] [cam_ldo_power_on : 1816] REAR CAMERA POWER ON!!
<7>[ 1074.214527] [s5c73m3] rear camera on 1
<7>[ 1074.214558] [s5c73m3] check GPIO_CAM_FLASH_SW : 1
<7>[ 1074.216602] [s5c73m3] check vddCore : 1150000
<6>[ 1074.217854] CAM_ISP_CORE voltage is enabled to 1150 mV by selector value [38]
<7>[ 1074.219105] [s5c73m3] check GPIO_CAM_A_EN : 1
<7>[ 1074.220143] [s5c73m3] check GPIO_CAM_SENSOR_EN : 1
<7>[ 1074.222218] [cam_ldo_power_on : 1816] REAR CAMERA POWER ON!!
<7>[ 1074.222249] [s5c73m3] rear camera on 2
<7>[ 1074.222249] [s5c73m3] check CAM_AF_EN : 1
<7>[ 1074.225759] [s5c73m3] check CAM_MIPI_EN : 1
<7>[ 1074.227803] [s5c73m3] check ISP_RESET : 1
<3>[ 1074.255546] [s5c73m3_sensor_init:3410] Entered
<3>[ 1074.259026] [s5c73m3_sensor_init_probe:3358] Entered
<3>[ 1074.272729] [s5c73m3_check_fw:3124] Enter
<3>[ 1074.284877] [s5c73m3_get_sensor_fw_version : 2768] sensor_fw = ZHFJ02
<3>[ 1074.291255] [s5c73m3_get_phone_fw_version:2844] Entered
<3>[ 1074.295742] [s5c73m3_get_phone_fw_version:2957] can't open ZHFJ02. download from F-ROM
<3>[ 1074.303647] [s5c73m3_reset_module:424] E
<7>[ 1074.307462] [cam_ldo_power_off : 1987] REAR CAMERA POWER OFF!!
<7>[ 1074.317442] [s5c73m3] check GPIO_CAM_FLASH_SW : 0
<7>[ 1074.318479] [cam_ldo_power_on : 1816] REAR CAMERA POWER ON!!
<7>[ 1074.318510] [s5c73m3] rear camera on 1
<7>[ 1074.318510] [s5c73m3] check GPIO_CAM_FLASH_SW : 1
<7>[ 1074.320921] [s5c73m3] check vddCore : 1150000
<6>[ 1074.322050] CAM_ISP_CORE voltage is enabled to 1150 mV by selector value [38]
<7>[ 1074.323271] [s5c73m3] check GPIO_CAM_A_EN : 1
<7>[ 1074.324309] [s5c73m3] check GPIO_CAM_SENSOR_EN : 1
<7>[ 1074.325347] [cam_ldo_power_on : 1816] REAR CAMERA POWER ON!!
<7>[ 1074.325377] [s5c73m3] rear camera on 2
<7>[ 1074.325377] [s5c73m3] check CAM_AF_EN : 1
<7>[ 1074.328856] [s5c73m3] check CAM_MIPI_EN : 1
<7>[ 1074.330932] [s5c73m3] check ISP_RESET : 1
<3>[ 1074.333373] [s5c73m3_reset_module:441] X
<3>[ 1074.336303] [s5c73m3_get_sensor_fw_binary:2453] Entered
<3>[ 1074.759072] [s5c73m3_get_sensor_fw_binary:2549] sent SPI ready CMD
<3>[ 1075.295376] [s5c73m3_get_sensor_fw_binary:2578] made CSC value by S/W = 0x563c77e
<3>[ 1075.302121] [s5c73m3_get_sensor_fw_binary:2584] Original CRC Int = 0x563c77e
<3>[ 1075.309018] [s5c73m3_get_sensor_fw_binary : 2593] failed to open /data/SlimISP_ZH.bin, err -13
<3>[ 1075.317808] [s5c73m3_get_sensor_fw_binary:2622] Exit
<3>[ 1075.322752] [s5c73m3_get_phone_fw_version : 2962] i2c failed, err -22
<3>[ 1075.329314] [s5c73m3_check_fw : 3137] failed s5c73m3_get_phone_fw_version!!
<3>[ 1075.336273] [s5c73m3_sensor_init_probe : 3376] failed s5c73m3_check_fw!!
<3>[ 1075.343384] [s5c73m3_sensor_init : 3428] s5c73m3_sensor_init failed!
<3>[ 1075.349427] msm_mctl_open_init: isp init failed: -5
<7>[ 1075.362185] [cam_ldo_power_off : 1987] REAR CAMERA POWER OFF!!
<7>[ 1075.373355] [s5c73m3] check GPIO_CAM_FLASH_SW : 0
<3>[ 1075.376071] msm_open_init: HW open failed rc = 0xfffffffb
<6>[ 1075.591179] mdp_bus_scale_update_request: handle=-460495872 index=1 ab=805306368 ib=872415232
Per the last couple of lines, I tried copying several of the /system/cameradata/SlimISP_Z*.bin files to /data/SlimISP_ZH.bin. No luck, even the same error code (-EACCES)... and permissions are sufficient for anyone to open the file for reading.
[edit] I also verified (using Skype) that the front camera works. Some interesting information from sysfs:
Code:
[email protected]:/sys/class/camera # cat rear/rear_camtype
S5C73M3
[email protected]:/sys/class/camera # cat rear/rear_camfw ; echo
ZHFJ02 ZCFC13
[email protected]:/sys/class/camera # cat front/front_camtype ; echo
SLSI_S5K6A3YX
[email protected]:/sys/class/camera # cat front/front_camfw ; echo
S5K6A3 S5K6A3
I'm lost.

Got it!
For those who will inevitably encounter this problem later and find this thread via Google/etc.: (possibly myself included)
I restored the stock firmware, which (through some process I have yet to understand) dropped that file (SlimISP_ZH.bin) into /data/. I pulled that file out of my stock /data/ and dropped it into the same directory under CyanogenMod and - voilá! - the camera instantly began to work.
I'm unsure whether I can legally stick this file up on the web at the moment, but it should be pretty easy to obtain - try looking in the backup you took before you flashed your custom ROM or just spend half an hour backing up, flashing to stock, pulling the file down, flashing back to CM, and pushing that file to /data/ (you may need to restart adbd as root on the phone).

I spent the better part of yesterday flashing many aokp/cm10.x/miui roms only to inevitably go back on a TW based rom so that I had a working camera.
Thanks for your findings. I will try this out in a bit and will post that it hopefully worked for me too

metalfingers_ said:
dropped that file (SlimISP_ZH.bin) into /data/. I pulled that file out of my stock /data/ and dropped it into the same directory under CyanogenMod and - voilá! - the camera instantly began to work.
Click to expand...
Click to collapse
so you're saying that the stock image will contain this SlimISP_ZH.bin file in /data ? it was a little bit hard to understand from your post.
i'm going to check this out and see what i can do. it would be great if you could post that file up somewhere, so that others don't have to restore and fart around and on and on and on. maybe i'll post it somewhere when i try this.
so, you are NOT alone in this problem. i have been banging my head into this issue for days now since i bought my brand new S3 (same as you, Titanium gray, attempting to run CM10)
UPDATE: i've reloaded ICS stock rom using ODIN and now the phone won't boot. it just sits at the Samsung logo. i've tried wiping cache, dalvik cache, fixing permissions, etc. no joy.
what a ****ing day.

progress!
i think i might have things working for me! wow... what a day this was.
the SlimISP file seemed to be at issue. someone recovered a version from a stock Galaxy S III. (that file is posted here, btw)
interestingly, this person's version of the file was SlimISP_GC and not _ZH
i moved the file over to my /data directory and the camera did not work.
then this person also told me that they found the file in their /system/cameradata folder. interesting, i though... and i looked in that folder on my phone. there were about a half dozen SlimISP bin files there!
taking a bit of a shotgun approach, i just copied them ALL over to my /data directory. and while i was at it, i fixed permissions to make these files all readable, writeable, and executable. 777 perms for testing.
lo and behold, my camera suddenly worked! no reboots necessary, etc.
so, i do not know if this was the result of the SlimISP_GC.bin file, or any of the files i copied, or if permissions were also a factor. i hope to whittle it down a little and do some more testing to see exactly what's what.
for now i'm going to reboot a few times, test the camera a few times, and so forth. then once i have a solid TWRP backup image, i'll tinker with some of these files and see which one might be the keystone in this whole affair.
either way, so thankful that it's working. major props to @wimremes and especially to @badger32d for the missing file help (Badger switched his S III back to stock just to dig around since my phone wasn't liking the ODIN process for some reason today)
a slight boo and hiss to someone in #CyanogenMod on freenode who had the gall to just spew hate and profanity at people who would dare to question why a non-working camera would not be considered a key feature of a phone.
most of all, HUGE thanks to the whole CyanogenMod community for all the tireless effort that they put into porting this most awesome of roms to so many devices and to their ceaseless quest to always keep improving the whole experience for the users.
EDIT: i never did figure out why my phone wouldn't boot when i rolled it back to ICS stock via ODIN. bad cable or bad download simply perhaps? i am not sure. i have successfully used ODIN to push all sorts of things to the phone in the past.
i may tinker with it in the future some more... but for now, i'm just endlessly thrilled that this last item is working. phone feels "complete" now

For those of you still looking (including the 2 people that PMed me... sorry, I didn't notice until now):
So it turns out that noobnl, one of the maintainers for Cyanogen for the S III, goes to the same university as me, and we're both members of the same student organization. We actually sat down the other night and fast-tracked this firmware file into CyanogenMod's blobs repo. Thanks Shareef!
The blob file you're probably looking for:
I don't have the requisite 10 posts yet so I can't post outside links. It's at goo dot gl slash ANigI.

here's the link that metalfingers_ couldn't post....
goo.gl/ANigI

Same problem here - Liquid Smooth and Slim Bean
Thank you all for the information in this thread. My mother already told me I was an idiot years ago. I have tmo sg3 and now have Liquid-JB-v2.1-Beta2 running on it. I do like it, but have no camera. I had no camera under Slim Bean too. I have the files you folks have mentioned, but don't really see a data directory other than /android/data. Unfortunately at this point, I'm using Windows to connect to the phone instead of a linux box.
I guess my question is what is the most effective way to copy this file to the correct directory? I was guessing I need to go into CWM and copy through there, but I have little experience so far. I got the phone about 2 weeks ago, and couldn't stand the stock rom, but everything did work. So I went ahead and took a dive.
Thanks in advance, and if I am looking for answers that have already been posted, I missed them so please excuse me.

sgibney said:
Thank you all for the information in this thread. My mother already told me I was an idiot years ago.
Click to expand...
Click to collapse
don't worry... you're surely not an idiot. i don't know what kind of person it takes to run the Galaxy S III as stock, but i surely couldn't ever be content with that bloated, awful environment. I nearly puked when i first started mine up, and i immediately shut the phone off and couldn't wait to get home to start modding it.
sgibney said:
I have tmo sg3 and now have Liquid-JB-v2.1-Beta2 running on it. I do like it, but have no camera. I had no camera under Slim Bean too.
Click to expand...
Click to collapse
yes, the non-working camera seems to be one of the biggest problems that people have when running non-stock Android on the Galaxy S III.
sgibney said:
I have the files you folks have mentioned, but don't really see a data directory other than /android/data. Unfortunately at this point, I'm using Windows to connect to the phone instead of a linux box. I guess my question is what is the most effective way to copy this file to the correct directory?
Click to expand...
Click to collapse
ah, so i presume that you are browsing the file system either from your windows box or by using a "typical" file manager app on the phone. in either case, you are not seeing the whole picture.
here's a brief overview of a few details...
When Android devices have an SD card or microSD card present, the file system will often treat this as an /sdcard directory (that's right off the root of the whole filesystem)
even devices that do not take any removable media often still allocate a partition of their internal memory to this purpose, and thus on something like the Nexus 7 tablet you'll have an /sdcard directory even when there is no card slot
some devices, like our Galaxy S III phones, actually do both. there is an internal partition for users to access and also a microSD card slot
in that case, the root of the file system will have a /storage directory and within that there will be /sdcard0 (internal partition) and /sdcard1 (microSD card, if present)
... in ALL of these cases, when you plug your Android phone into a computer or even when you browse the device with a "typical" file manager app, all you can view are the /sdcard directories. What you need is a way to "break out" of those directories and go "deeper" into the file system (or, technically, one would really call that "higher up" in the directories) so that you can start by viewing just the root directory (simply the "/" and nothing else) and then see utterly the whole device directory tree.
To do that, most power users like to rely on better file manager apps. Two of the most popular are: Root Explorer and ES File Explorer
I think you'll find that most folk here (or at least i can say "most folk whom i know") prefer Root Explorer. Its interface is clean and it allows very fast toggling between Read-Only and Read/Write mounting. (that's also an issue that comes up, i'll explain) ES File Explorer does all the same tasks (and i think comes as part of some ROM packages i've seen) but just doesn't pop for me in the same way. ES File Explorer is totally free, however. Root Explorer used to be (and you can still surely find links to the old versions or just email me and i'll send it to you) but the current version now costs a dollar or something.
If you have full root access on your phone, you can easily use an app like one of those file managers to view the WHOLE file system, from the root directory on down. You will see that there is a /data directory (a directory named "data" just within the "/" root directory of the device) and THIS data directory is where you'll need to place those SlimISP files. If you're running a custom Android rom you should already have root access on your phone so this should work.
When people do NOT have root access of their phone, they run into problems copying/moving files in some ways. The /system directory, for example, is often mounted as Read-Only and therefore you can't push things into there. But with root-enabled file manager apps like the ones mentioned above, that's not a problem.
Your /data directory should not have any such restrictions. You should be able to move the SlimISP files into there (from your /sdcard directory or wherever they are right now) but once you do, you will have to set the permissions properly.
If you've never worked within a UNIX environment, the concept of permissions is a little different from how an O/S like Windows treats it, but it's not a totally foreign notion. Essentially, there are three kinds of permissions and three categories to which they can be applied...
Permissions: Read, Write, Execute
Categories: Owner, Group, All
... the details of all this get a little weighty for our discussion here, but suffice it to say that when you view a UNIX-based file system, it's typical to see strings of letters next to file names. Like this: rw-rw-r-x or rwxr--r-- etc etc. These are triplets of letters, representing whether the Read, Write, or Execute permission exists for people in the three categories. The letters (and hyphens, if the permission does not exist) are all mashed together in a long string.
So in our two examples in the above paragraph, in the first case (rw-rw-r-x ... maybe you can try to visualize it this way: rw- rw- r-x) the Owner of the file has Read and Write but not Execute perms. Others in the same group as the owner have these same permissions. And the "all" group has Read and Execute permissions but Write is not set. (which is a pretty odd permission set overall, hah). In the second example i posted (rwxr--r-- ... visualize it this way: rwx r-- r--) the owner has full Read/Write/Execute but others in the owner's group and also the "all" group only have Read permissions. Is that a little clear?
Overall, we don't have to get into details like that too deeply. Just know that when you copy or move the SlimISP files into your /data directory, there is a chance they will arrive with unhelpful permissions. While i myself have never narrowed down exactly which permissions are necessary to make the camera work, you can't go wrong (in this case*) by just setting them all. My SlimISP files all are set to rwxrwxrwx and the camera works for me. One day i'll drill into the file system and actually start revoking permissions and renaming files to see EXACTLY which file and what permissions worked for me. For now, just setting them all is fine.
So, hopefully that will help you out! Sorry the post was long-winded. It just seemed like you really wanted to learn.
* NOTE - While setting full permissions on a random camera driver file is fine on a phone that doesn't get used by other people, this is NOT a healthy attitude or wise course of action to ever take if, say, you're administrating a computer or running a network or something. Getting frustrated that something isn't working can be rough, but it's basically never a good idea to solve the problem by throwing up your hands and saying, "screw it... give EVERYONE and ALL PROCESSES permissions on this damn resource because I don't know why the hell it's failing."
That's a recipe for trouble and for security breaches. Can't count the number of times i've seen a firewall config with an "any any" rule thrown in there because some dumb sysadmin couldn't be bothered to actually troubleshoot why some oddball service wasn't working correctly. Heh, and i've usually seen these firewall configs when called in on post-intrusion audit jobs.

I got same problem, but found a different solution:
http://forum.xda-developers.com/showthread.php?p=37328191

Thank you Deviant
Thank you for the information. I found another Rom from ktmdave7 [ROM] JB 4.1.1 STOCK Slim 01-18-2013 (3rd Release) which I decided to try. I concur with your assessment of the device with stock software. I like this ROM, but I have no GPS now. I'd rather have no GPS than no camera, but damn if it hasn't had me looking around for a fix. At this point, what I found was says it is a stock t-mobile sgh-t999 rom T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar that I will try to go back to stock and see if the GPS works. This is about the only solution I've seen replicated to some success. I do not know why I'm letting the GPS crap bother me... I will keep you folks informed.
Thank you again for taking the time to go over the steps you added. I will do what you suggest if I still have problems. I sure would like to use some more ROMs and these are so much more functional than stock Samsung/T-Mobile.

You are not the only one
I have the same exact firmware zhfj02 on my g3 and it was just purchased 3 weeks ago. No working camera on any non stock based roms. I had no GPS with all non stock roms until I went to 4.2.1 but then again no camera. Going back to stock before would never get the GPS working again. I just went back to stock again to check the cam firmware and suddenly the gps is working again. Going to try ktmdave7's rom again as it is basically stock slimmed.
So, you are not the only one. I have a shg-t999 from t-mobile and experience the same problem. I was able to take one pic using Deviant's method, but then right back to "can't connect to camera" or whatever the message was. I would have to reboot, then I could take one picture. This prompted back to stock, then discovered gps working again, now going back to ktmdave7's rom.

I've been experiencing this error for the past month.. normally it would fix itself after a reboot/clear cache, but not this time. I've messed with it countless times, wiped it, flashed different roms, nothing worked... So just now I ODIN'd back to stock...and it STILL DOESN'T WORK.. Is there any reason why using ODIN to return to stock from an AOSP rom, wouldn't fix this problem?
I attempted to go thru the steps here.. http://forum.xda-developers.com/showthread.php?t=2113526 but for some reason I'm unable to pull up that camera firmware menu though, the screen goes black then closes and "factory test" FC's every damn time.....
So at this point, I've been searching around and I can't get any of the Factory Test USSD codes to work, most fail or just FC. I can't check my firmware version and even if I knew what it was, I still wouldn't be able to flash an updated fw. What options do I have left? Is it possible to manually flash the drivers..?
I've tried both the stock JB rom and the prerooted stock JB rom and neither will pull up the menu...

civicvx94 said:
I've been experiencing this error for the past month.. normally it would fix itself after a reboot/clear cache, but not this time. I've messed with it countless times, wiped it, flashed different roms, nothing worked... So just now I ODIN'd back to stock...and it STILL DOESN'T WORK.
Click to expand...
Click to collapse
i am not familiar with whether ODIN return to stock flashing would fail to flash, say, the boot partition (and thus if you have some other kernel somehow, say) but overall that is genuinely weird.
some questions...
1. what is the exact way in which this error manifests itself? when you launch the camera app does it give you "cannot connect to camera" error or something else?
2. does EITHER camera work for you? for example, using Skype with the camera facing the user... can that camera operate properly?
overall, this may just be odd and academic. if you are running stock Galaxy S III and it looks factory-normal, etc... you could likely just go into the store where you purchased this and attempt a warranty exchange. explain that the camera worked fine until the other day, and now it's erroring.
tell them that trouble shooting forums (or even reps on the phone) informed you that this is a sign of a faulty camera lens or something else you choose to make up. let them proceed with the warranty swap.

Deviant Ollam said:
i am not familiar with whether ODIN return to stock flashing would fail to flash, say, the boot partition (and thus if you have some other kernel somehow, say) but overall that is genuinely weird.
some questions...
1. what is the exact way in which this error manifests itself? when you launch the camera app does it give you "cannot connect to camera" error or something else?
2. does EITHER camera work for you? for example, using Skype with the camera facing the user... can that camera operate properly?
overall, this may just be odd and academic. if you are running stock Galaxy S III and it looks factory-normal, etc... you could likely just go into the store where you purchased this and attempt a warranty exchange. explain that the camera worked fine until the other day, and now it's erroring.
tell them that trouble shooting forums (or even reps on the phone) informed you that this is a sign of a faulty camera lens or something else you choose to make up. let them proceed with the warranty swap.
Click to expand...
Click to collapse
Yes, if I'm on an AOSP rom and open the camera it says "cannot connect to camera" and closes.. when I'm on a stock rom it says "camera failed" and closes.
The FFC does work, but i can't access it. The only way I was able to find this out was by running a USSD code to get to the hardware test menu. The rear camera fails and closes, but the front works fine. However, in apps like Instagram for example, when I attempt to use it, it defaults to the rear camera and closes before I can switch to the FFC.
All issues are consistant no matter the rom or the firmware.. I've flashed 3 roms, 2 different stock firmwares and 1 stock rooted one today alone.. Same on each.
I'm going to try to get it replaced I guess.. It just seems crazy to me that its stuck like this.

have you tried adding the .bin files that we have added to make it work?
I am running CM10 and it worked when i dropped in the SlimISP_ZH.bin file.

Deviant Ollam said:
have you tried adding the .bin files that we have added to make it work?
I am running CM10 and it worked when i dropped in the SlimISP_ZH.bin file.
Click to expand...
Click to collapse
Yeah... I extracted those all of those files and pasted them all in /data/ and set permissions to 777.. but still nothing.

Any other ideas or should I try to get a warranty replacement?
Sent from my SGH-T999 using xda app-developers app

[Q] Camera quit working, says Gallery has stopped - logcat

I have the GSM i9250 and love the phone. Got the 4.3 OTA update on Wednesday afternoon. It was updating while driving to a golf match and all seemed well.
During the golf match, a small amount of beer was dripped on my phone (it was in the cubby hole and my team mate tossed a crumpled empty beer can in there). I didn't think anything of it, but when done, there was enough beer to line the inside of my diztronic case and render the power button nonfunctional.
I took it apart, cleaned it all up, cleaned up the power button and all is well again. The next day I went to fire up my camera and got "Unfortunately, Gallery has stopped." I popped everything apart, cleaned it all again, checked connections, etc, same problem. I flashed the official 4.2.2 image (bootloader, radio, system, data, user), same problem. It got the 4.3 OTA again, so I upgraded. I also borrowed the camera out of a co-worker's phone and same problem.
It seems like a software issue, but if something is toast due to the beer spillage, it may not even be able to fire up the camera.
I flashed CWM and ran fix permissions, same problem.
This is the most pertinent info here:
Code:
E/CameraHAL( 127): Couldn't get camera properties
W/dalvikvm( 4634): threadid=18: thread exiting with uncaught exception (group=0x418e4700)
E/AndroidRuntime( 4634): FATAL EXCEPTION: Thread-404
E/AndroidRuntime( 4634): java.lang.RuntimeException: Fail to get camera info
E/AndroidRuntime( 4634): at android.hardware.Camera._getCameraInfo(Native Method)
E/AndroidRuntime( 4634): at android.hardware.Camera.getCameraInfo(Camera.java:202)
E/AndroidRuntime( 4634): at com.android.camera.CameraHolder.<init>(CameraHolder.java:169)
E/AndroidRuntime( 4634): at com.android.camera.CameraHolder.instance(CameraHolder.java:123)
E/AndroidRuntime( 4634): at com.android.camera.Util.openCamera(Util.java:316)
E/AndroidRuntime( 4634): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:294)
W/ActivityManager( 375): Force finishing activity com.google.android.gallery3d/com.android.camera.Camera
Since it says CameraHAL, I'm assuming that's an actual hardware failure.
Anyone have some insight?

I'm with my Galaxy Nexus in the same situation, after install JB update (4.2.1), the camera stopped work as well playing videos on youtube too, I already have made the installation of 4.3 version but I still get the same error, I'm planning to clean my motheboard and check if it's evertything correct.
Anyway, please, let me know about your results too.
Regards.

I'm still having issues with it, but now I can't even open Gallery.

I got it fixed, so far anyway.
Used fastboot to erase boot, system, userdata, cache, and recovery. Then ran fastboot format on all as well (won't format boot). When that was done, I fastboot flashed the 4.2.2 bootloader, rebooted into bootloader, then flashed boot, recovery, system, and userdata for 4.2.2.
After reboot, my camera works again.
**EDIT**
Got the 4.3 OTA and camera still works.

cougar694u said:
I got it fixed, so far anyway.
Used fastboot to erase boot, system, userdata, cache, and recovery. Then ran fastboot format on all as well (won't format boot). When that was done, I fastboot flashed the 4.2.2 bootloader, rebooted into bootloader, then flashed boot, recovery, system, and userdata for 4.2.2.
After reboot, my camera works again.
**EDIT**
Got the 4.3 OTA and camera still works.
Click to expand...
Click to collapse
Oh, I'm gonna give it a try, well, it might be the same issue that I'm having. My phone stop camera working with the 4.2.1 update, I have flashed 4.3 and still the same error. But the back camera works on apps like Facebook or Lomo Cam, when I select front camera it gives me a error such as a crash or even a information saying that the app wasn't able to connect to the front camera. I'll first clean the front camera contact and later I'll try your solution.

Clear the logcat, run logcat and force the error message. It may be a faulty front camera.

I have tried it, but, it didn't work. :/

From your description, I didn't think it would. Does the proximity sensor work?

Yeah, all these stuff work except for the camera, actually, only the front camera. I have installed some other camera apps such as Lomo Cam and Night Vision, I those apps I can take a photo or even record with the rear camera but when I select front camera or even camera configurations, its crashes. I already have opened my phone and cleaned the things there but no sucess. Is there a way to use stock camera app? Because I want photosphere but it seems like that everytime it opens, it tries to get camera info from both cameras and when it doesn't get the front one, it crashes.
PS: my log is just like yours, crashing in getting camera info

Wifi not working after upgrading to 7.0 - ideas?

Hi everyone,
I downloaded and installed the OTA manually using the instructions here. Everything went fine, but after restarting the Wifi does not work. If I go to settings and flip the switch, it flips, but soon moves back into the off position.
Any ideas what I can check, what could be causing this? Thanks!

Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
strophy said:
Hi everyone,
I downloaded and installed the OTA manually using the instructions here. Everything went fine, but after restarting the Wifi does not work. If I go to settings and flip the switch, it flips, but soon moves back into the off position.
Any ideas what I can check, what could be causing this? Thanks!
Click to expand...
Click to collapse

You could try flashing the vendor.img, system.img, and boot.img from the factory image through fastboot
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
You could try flashing the vendor.img, system.img, and boot.img from the factory image through fastboot
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks SlimSnoopOS, will that preserve all my user data? Isn't that done already during the normal OTA process? Should I get the .img files from the OTA or from the full factory image?
I did a little more research on this by viewing the log over adb. The following status/error messages appear when I try to enable Wifi:
08-31 15:07:29.997 859 7849 D WifiService: setWifiEnabled: true pid=11646, uid=1000
08-31 15:07:35.069 522 857 E WifiHW : Failed to write wlan fw path param (No such device)
08-31 15:07:35.075 859 3272 E WifiStateMachine: Failed to reload STA firmware java.lang.IllegalStateException: command '2325 softap fwreload wlan0 STA' failed with '400 2325 SoftAP command has failed'
08-31 15:07:35.078 859 859 E WifiController: WifiControllerWifi turn on failed
I've been unable to find anything related online, but a lot of other people over at the Nexus product forums have this problem after upgrading. Can someone identify the error from these messages?
Thanks!

strophy said:
Thanks SlimSnoopOS, will that preserve all my user data? Isn't that done already during the normal OTA process? Should I get the .img files from the OTA or from the full factory image?
I did a little more research on this by viewing the log over adb. The following status/error messages appear when I try to enable Wifi:
08-31 15:07:29.997 859 7849 D WifiService: setWifiEnabled: true pid=11646, uid=1000
08-31 15:07:35.069 522 857 E WifiHW : Failed to write wlan fw path param (No such device)
08-31 15:07:35.075 859 3272 E WifiStateMachine: Failed to reload STA firmware java.lang.IllegalStateException: command '2325 softap fwreload wlan0 STA' failed with '400 2325 SoftAP command has failed'
08-31 15:07:35.078 859 859 E WifiController: WifiControllerWifi turn on failed
I've been unable to find anything related online, but a lot of other people over at the Nexus product forums have this problem after upgrading. Can someone identify the error from these messages?
Thanks!
Click to expand...
Click to collapse
Yes to both of your first two questions. When flashing factory image files one by one, only userdata.img affects that. Use the factory image.
Sent from my Nexus 5X using Tapatalk

strophy said:
Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
Click to expand...
Click to collapse
I am having same problem with MAC address = 02:00:00:00:00:00
---------- Post added at 11:09 AM ---------- Previous post was at 10:21 AM ----------
SlimSnoopOS said:
Yes to both of your first two questions. When flashing factory image files one by one, only userdata.img affects that. Use the factory image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Flash factory image (boot.img, vendor.img, system.img) does not help my Nexus 5x (WiFi wrong MAC address)

xbing6 said:
I am having same problem with MAC address = 02:00:00:00:00:00
---------- Post added at 11:09 AM ---------- Previous post was at 10:21 AM ----------
Flash factory image (boot.img, vendor.img, system.img) does not help my Nexus 5x (WiFi wrong MAC address)
Click to expand...
Click to collapse
Thanks for trying that xbing6. My phone is still OEM locked so I'd like to try and fix this without removing the lock if possible. Unlikely, I know. I found a post where someone has resolved the problem by gaining root and doing a strange series of flashes and setting modifications:
http://chromloop.com/2016/08/how-to-fix-wifi-problem-updating-android-7-0-nougat/
Does anyone more knowledgeable care to theorize about how this happened and if there is anything we can do, beyond the root method or waiting for Google?

probably a hardware issue...
Hi there!
Does your WiFi keep flashing/blinking and showing "Turning on..."?
For example, like in this video: http://www.dailymotion.com/video/x2cuyjt_nexus-5-turning-wifi-on-frozen-problem_tech
I had a very similar problem on my G2 and I believe that these WiFi/BT problems are common to all LG devices, probably due to poor quality WiFi/BT chips used.
Did you drop your device? Did you leave it charging over a longer period, for example, during the night, and observed it getting very warm, or even hot, during the process?
I believe the root cause of your problem is a hardware issue. Someone in the forums suggested that replacing the battery may solve the problem; I can't confirm nor deny this, you might want to try it out.
Also, you might want to check out a detailed summary I've written about this issue here: http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
Let us know if you managed to fix the problem!
Good luck!

NimbleWeasel said:
Hi there!
Does your WiFi keep flashing/blinking and showing "Turning on..."?
For example, like in this video: http://www.dailymotion.com/video/x2cuyjt_nexus-5-turning-wifi-on-frozen-problem_tech
I had a very similar problem on my G2 and I believe that these WiFi/BT problems are common to all LG devices, probably due to poor quality WiFi/BT chips used.
Did you drop your device? Did you leave it charging over a longer period, for example, during the night, and observed it getting very warm, or even hot, during the process?
I believe the root cause of your problem is a hardware issue. Someone in the forums suggested that replacing the battery may solve the problem; I can't confirm nor deny this, you might want to try it out.
Also, you might want to check out a detailed summary I've written about this issue here: http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
Let us know if you managed to fix the problem!
Good luck!
Click to expand...
Click to collapse
Thanks for the ideas NimbleWeasel. I doubt it though - the wifi went from functioning perfectly to non-functional immediately after applying the update. Never been dropped, less than 2 months old, and doesn't get excessively hot. Google has now reached out to me for a bug report so I'll hopefully hear more from them soon and update this thread.

keep us posted!
Hi strophy,
What about the link, did you watch the video? Does your phone show the effect as in the video?
After reading through the posts again, I think that you might indeed be experiencing a different problem.
I am curious to see what Google will reply!

NimbleWeasel said:
Hi strophy,
What about the link, did you watch the video? Does your phone show the effect as in the video?
After reading through the posts again, I think that you might indeed be experiencing a different problem.
I am curious to see what Google will reply!
Click to expand...
Click to collapse
Hey mate, no my problem is quite different. Firstly, that video is a Nexus 5 running Android 4.x I think? I'm on Nexus 5X running Android 7.0. The wifi switch slides into the on position, stays there for 5 seconds, then slides back by itself. No hotspots are shown at any time. The MAC address also looks like the photo in this post: http://chromloop.com/2016/08/how-to-fix-wifi-problem-updating-android-7-0-nougat/
I don't think my problem is a hardware problem. Let's see what Google says...

My Wifi drops and reconnects whenever I take the phone out of my pocket and open an app that uses data. My data usage has gone up significantly with the Wifi drops. Appears there's others having problems on google product forums with no workaround at this time.
Any help would be appreciated!
ETA: My MAC address appears normal, not the one posted in other forums.

strophy said:
Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
Click to expand...
Click to collapse
I am facing the same issue. Hope Google finds a solution for this

[HELP] D855 Doesn't show download mode & Doesn't flash

Greetings
So now I have completed two months of trials trying to fix this thing. I figured it's time to post something.
I have an LG G3 D855 32GB GCC (As it says on the box). The device was not booting so I tried removing the battery for a couple of minutes and putting it back. It worked for a while but now it's dead. I changed the battery and it's still the same thing.
I searched around and found people suggesting flashing the TOT file. So I went to download mode (it used to go there ) tried flashing and I got an error. I don't recall the error to be honest.
Now the device won't boot and won't show the download mode screen. However, it gets recognized as "LGE AndroidNet USB Serial Port".
I tried the KDZ method and it doesn't work. The TOT method gives me the errors below:
When I use LGUP8974.dll
PID: NULL
IMEI: NULL
[ 9: 2:27] CrossDL [] to [D855]. SWersion[]
000000064
Error: [ 9: 2:27] CrossDL [] to [D855]. SWersion
When I use LGD855_20140526_LGFLASHv160.dll
PID: NULL
IMEI: NULL
Model :
DLL : D855
SWV :
SWOV :
Model Information Check FAIL !
I'm not sure how bad the situation is or what exactly I'm doing wrong. I tried searching and trying everything and none is working.
Notes:
I'm not sure if I'm using a proper TOT the one I'm using says (LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+0.tot)
Searching using my IMEI in a website resulted with the SW (D85530D_00)

have u resolved the issue ?