Develop Bugs

[Q] Random reboots and frustrating boot loops

Hey all,
I've been having boot-loop problems for almost a month now. The phone just abruptly reboots and goes into a boot loop with just the HTC screen. The problem is fixed temporarily if I remove the battery for a while and then power it back up. If I start having too many things going on, such as several tabs in DolphinHD, downloading several updates, etc. [no gaming at all] it'll do the same thing and just reboot.
I was running Cyanogen 6 [stable] with Kingxkernel #2. I was not overclocked, but did have a few setcpu profiles active. I've tried everything imaginable since they began:
-Tried a different kernel [SNAP], didn't work
-Truned off setcpu, didn't work
Today, I got fed up with everything and then decided to flash a Sense ROM hoping that that would fix everything. I flashed the latest Fresh and after the install, even before I could skip all the set-up stuff, the phone started to reboot again.
As for the Fresh installation, I wiped fully including dalvik and cache all in RA.
I'm about to go crazy. I wan't my fully functioning phone back. Please help
EDIT: Also, I forgot to mention that around the same time the random reboots and bootloops began I got a new battery. It was the one from Best Buy made by Seido. Idk if that would affect anything seeing as I get the same problems with both batteries.

if i was you i would do all the following:
1. titanium backup all your apps...
2. flash clockwork recovery
3. nandroid backup everything
4. wipe /system
5. wipe /data
6. wipe /boot
7. wipe /cache
8. wipe /dalvik
9. install rom of your choice
10. run it for a few hours and push it as hard as you can to cause a reboot
- if it reboots -> plug into computer load up terminal/command prompt do adb logcat (copy and paste where and why it reboots)
- if it doesn't reboot -> start reinstalling your apps one at a time or in batches until you find the culprit (unlikely since most installed apps should only cause a force close rather than a reboot but still worth a shot)
11. post back with your findings... ?
fyi the nightly builds seem more stable than the stable build ever was... at least to me on my evo it was...

Thanks for the reply.
I'm going to try that to see what happens. I'll post asap.

Alright, I flashed Clockwork as you said and wiped/formatted everything you mentioned. After that, I flashed Fresh. Everything went well until it went through it's first routine reboot after flash; I didn't even get to pull down the lockscreen into activation before it randomly rebooted. I did a logcat on the first reboot. This is a little piece of the last part of that:
V/libgps ( 292): DeferredActionThread pthread_cond_wait returned
V/libgps ( 292): PA event: 0x00000040
V/libgps ( 292): PDSM_PA_EVENT_GPS_LOCK 0
D/dalvikvm( 292): GC_FOR_MALLOC freed 618 objects / 115992 bytes in 145ms
I/ActivityThread( 674): Publishing provider com.htc.dcs.provider.utility: com.htc.dcs.service.utility.UtilityProvider
D/dalvikvm( 292): GC_FOR_MALLOC freed 55 objects / 177104 bytes in 74ms
D/dalvikvm( 292): GC_FOR_MALLOC freed 296 objects / 253256 bytes in 86ms
I/ActivityThread( 674): Publishing provider com.htc.sync.provider.weather: com.htc.sync.provider.weather.Provider
D/ConnectivityService( 292): getMobileDataEnabled returning true
I/ActivityThread( 674): Publishing provider com.htc.socialnetwork.snprovider: com.htc.socialnetwork.provider.SocialNetworkProvider
horiveira:tools stgomez91$
Click to expand...
Click to collapse
It rebooted after the second to the last line. This is my first time using logcat, so I don't know too much about what any of that stuff is, except for the last line obviously.
Can anybody tell the reason why I get these problems by looking at that?
Here's a copy of the logcat file: http://www.sendspace.com/file/kt3lj1
I was hoping this would work, but alas...it did not. What do I do now??

Had the same problem.
For me the solution was to reset the GPS and after that all the random reboots stopped.
Dial : ##GPSCLRX#
Enter your MSL Code
let the phone reboot.
I hope this works for you.

How do you get your MSL code?

Gonna try that now, I hope it works...
How did you figure out it was the GPS?
EDIT: Just tried what you suggested. Didn't seem to work: after it rebooted and got past the Fresh screen, it rebooted without me touching it.

jthurs said:
How do you get your MSL code?
Click to expand...
Click to collapse
Use MSL reader, it's in the Market (and free).

Alright, after doing what aj74 mentioned and it not working, I left the battery out for a bit then powered it back on. That was at 3pm. At around 4, it had yet to reboot so I decided to restore all of my apps with Titanium Backup. I have yet to have a random reboot, though I highly doubt it's fixed.
I'm afraid to use my phone :-/

same problem. looks like this is becoming more and more frequent. i have tried unrooted, and a bunch of rooted roms. this is a problem that needs solving fast.

lo' and behold, as I was getting confident and rearranging things on the phone the loops began again.

I guess I feel better
Well, I feel better since it isn't just me. It has been working fine, then I took the phone on my first trip and as soon as I got off the plane on Wednesday, the random restarts started.
I'm guess some type of app update caused it, but god only knows which one. I did a factory reset, the gps reset, restored a nandroid backup from late september, and turned off all synching. Still get the reboot loop.
I seem to be able to make it stop for a little while by putting the phone in the freezer, but I can't believe we would all start having this problem at about the same thing if it was simply a overheating issue.
Update:
I was roaming when all of this happened, and now that I'm home, I haven't been able to get the phone to mess up. This will make it tough to take in for service. It still may be a heating issue, however, since it is not hot where I live, but it was hot where I was visiting.
Update 2:
I have now been able to get the problem to happen in my home area. The battery temp was > 100 F when it happened.

[Q] Warning: Camera Failed , HELP!

Ok I've switched from Evo to the Epic, and got it from a friend that had dropped it and shattered the screen. I replaced the screen, and it had EB13 on it. I test everything out and it was all good, camera/screen/gps etc.. So then I did the OTA to EC05, and now my camera doesnt work.
What I have tried:
Odin back to EB13 = fail
Wipe data/back to factory = fail
Wipe camera data via menu->settings->applications->manage applications->All->Camera-> Clear Data = fail
menu->Settings->about phone->system updates->update firmware fails also.
Replace launcher with Launcher Pro, create short->activity->CameraFirmware->com.sec.android.app.camerafirmware.cameraFirmware_user , and started it via there, selected "phone to cam FW write" it goes to about 10% and says failed, try again.
Also I've wiped the SD card to ensure files there are not messing with it.
I'm bone stock, no root, no custom recovery etc..
What do you guys think I should do?

Try different camera app
If that doesn't work your camera is messed up and you should go to a sprint store
Sent from my SPH-D700 using XDA Premium App

Sounds like you're rather screwed, unforunately - one last thing to try: a completely different SD card.

A different camera app didnt work either. I will try a different camera as soon as a retailer online has one in stock.

A different camera app didnt work either. I will try a different camera as soon as a retailer online has one in stock.
03-31 02:25:47.349: INFO/camerafirmwarejni native.cpp(7055): JNI_OnLoad
03-31 02:25:47.357: ERROR/camerafirmwarejni native.cpp(7055): Native registration unable to find class 'com/sec/android/app/camerafirmware_SE/Native'
03-31 02:25:47.357: ERROR/camerafirmwarejni native.cpp(7055): ERROR: registerNatives failed
03-31 02:25:47.357: WARN/dalvikvm(7055): JNI_OnLoad returned bad version (-1) in /system/lib/libcamerafirmwarejni.so 0x47c874d8
03-31 02:25:47.357: WARN/dalvikvm(7055): Exception Ljava/lang/NoClassDefFoundError; thrown during Lcom/sec/android/app/camerafirmware/Native;.<clinit>
03-31 02:25:47.357: WARN/dalvikvm(7055): threadid=7: thread exiting with uncaught exception (group=0x4001d7f0)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): FATAL EXCEPTION: Thread-8
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): java.lang.ExceptionInInitializerError
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at com.sec.android.app.camerafirmware.CameraFirmware_user$1$2$1.run(CameraFirmware_user.java:137)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at java.lang.Thread.run(Thread.java:1096)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): Caused by: java.lang.NoClassDefFoundError: com.sec.android.app.camerafirmware_SE.Native
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at java.lang.Runtime.nativeLoad(Native Method)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at java.lang.Runtime.loadLibrary(Runtime.java:448)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at java.lang.System.loadLibrary(System.java:557)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at com.sec.android.app.camerafirmware.Native.<clinit>(CameraFirmware.java:578)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): ... 2 more
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): Caused by: java.lang.ClassNotFoundException: com.sec.android.app.camerafirmware_SE.Native in loader dalvik.system.PathClassLoader[/system/app/CameraFirmware.apk]
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at dalvik.system.PathClassLoader.findClass(PathClassLoader.java:243)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): at java.lang.ClassLoader.loadClass(ClassLoader.java:532)
03-31 02:25:47.365: ERROR/AndroidRuntime(7055): ... 6 more
Click to expand...
Click to collapse
and
03-31 02:23:13.986: ERROR/camerafirmwarejni native.cpp(6894): Native registration unable to find class 'com/sec/android/app/camerafirmware_SE/Native'
03-31 02:23:13.986: ERROR/camerafirmwarejni native.cpp(6894): ERROR: registerNatives failed
03-31 02:23:13.986: WARN/dalvikvm(6894): JNI_OnLoad returned bad version (-1) in /system/lib/libcamerafirmwarejni.so 0x47c87418
03-31 02:23:13.986: WARN/dalvikvm(6894): Exception Ljava/lang/NoClassDefFoundError; thrown during Lcom/sec/android/app/camerafirmware/Native;.<clinit>
03-31 02:23:13.986: WARN/dalvikvm(6894): threadid=7: thread exiting with uncaught exception (group=0x4001d7f0)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): FATAL EXCEPTION: Thread-8
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): java.lang.ExceptionInInitializerError
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at com.sec.android.app.camerafirmware.CameraFirmware_user$1$2$1.run(CameraFirmware_user.java:137)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at java.lang.Thread.run(Thread.java:1096)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): Caused by: java.lang.NoClassDefFoundError: com.sec.android.app.camerafirmware_SE.Native
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at java.lang.Runtime.nativeLoad(Native Method)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at java.lang.Runtime.loadLibrary(Runtime.java:448)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at java.lang.System.loadLibrary(System.java:557)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at com.sec.android.app.camerafirmware.Native.<clinit>(CameraFirmware.java:578)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): ... 2 more
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): Caused by: java.lang.ClassNotFoundException: com.sec.android.app.camerafirmware_SE.Native in loader dalvik.system.PathClassLoader[/system/app/CameraFirmware.apk]
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at dalvik.system.PathClassLoader.findClass(PathClassLoader.java:243)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): at java.lang.ClassLoader.loadClass(ClassLoader.java:532)
03-31 02:23:13.998: ERROR/AndroidRuntime(6894): ... 6 more
03-31 02:23:14.005: WARN/ActivityManager(2454): Force finishing activity com.sec.android.app.camerafirmware/.CameraFirmware_user
03-31 02:23:14.009: INFO/(2454): dumpmesg > "/data/log/dumpstate_app_error.log"
03-31 02:23:14.052: INFO/dumpstate(6903): begin
03-31 02:23:14.091: DEBUG/BatteryService(2454): update start
03-31 02:23:14.091: DEBUG/BatteryService(2454): updateBattery level:81 scale:100 status:2 health:2 present:true voltage: 4060 temperature: 310 technology: Li-ion AC powered:false USB powered:true icon:17302172
03-31 02:23:17.712: DEBUG/VoldCmdListener(2347): asec list
03-31 02:23:17.712: DEBUG/VoldCmdListener(2347): CommandListener::AsecCmd::runCommand -> com.rovio.angrybirds-1
03-31 02:23:18.941: INFO/dumpstate(6903): done
03-31 02:23:19.193: DEBUG/BatteryService(2454): update start
03-31 02:23:19.251: DEBUG/BatteryService(2454): updateBattery level:81 scale:100 status:2 health:2 present:true voltage: 4057 temperature: 310 technology: Li-ion AC powered:false USB powered:true icon:17302172
03-31 02:23:19.271: VERBOSE/NotificationService(2454): notification manager receiver action = android.intent.action.BATTERY_CHANGED
03-31 02:23:19.271: INFO/StatusBarPolicy(2454): BAT. status:2 health:2
03-31 02:23:19.275: DEBUG/SyncmlService(2537): mBatteryReceiver: action - android.intent.action.BATTERY_CHANGED
03-31 02:23:19.275: DEBUG/WifiService(2454): ACTION_BATTERY_CHANGED pluggedType: 2
03-31 02:23:19.290: DEBUG/BatteryService(2454): update start
03-31 02:23:19.326: VERBOSE/NotificationService(2454): notification manager receiver action = android.intent.action.BATTERY_CHANGED
03-31 02:23:19.326: INFO/StatusBarPolicy(2454): BAT. status:2 health:2
03-31 02:23:19.330: DEBUG/SyncmlService(2537): mBatteryReceiver: action - android.intent.action.BATTERY_CHANGED
03-31 02:23:19.330: DEBUG/WifiService(2454): ACTION_BATTERY_CHANGED pluggedType: 2
03-31 02:23:19.333: INFO/dalvikvm(6894): Rejecting re-init on previously-failed class
Click to expand...
Click to collapse

TpyoKnig said:
A different camera app didnt work either. I will try a different camera as soon as a retailer online has one in stock.
Click to expand...
Click to collapse
Maybe try flash back to di18/ota to ec05?
Sent from my SPH-D700 using Tapatalk

lafronz said:
Maybe try flash back to di18/ota to ec05?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Didn't work either

Did you try a different SD card yet?

k0nane said:
Did you try a different SD card yet?
Click to expand...
Click to collapse
No I dont have another, will try later in the day.

k0nane said:
Did you try a different SD card yet?
Click to expand...
Click to collapse
New SD card didnt fix it either. However I did managed to check the firmware, and compared it to whats on phone for the camera, and it reports all 00's for the firmware on the camera. Now how can I update it? any suggestions?

I would say that you may have no other option than to head to a Sprint Store and have them check it out then order you a refurb, it will cost you nothing if you have TEP and probably won't cost you anything if you don't and are polite to the Rep you get.

My Phone/Cam FW Ver check:
[[email protected]:NONE] , can someone else post theirs? thanks

Try flashing a custom Rom or stock rom.
TpyoKnig said:
My Phone/Cam FW Ver check:
[[email protected]:NONE] , can someone else post theirs? thanks
Click to expand...
Click to collapse
Why don't you reflash to stock Rom. That is the best way to get the firmware back on the camera. If this does not work you have no choice but to go back to the sprint store.

jamice4u said:
Why don't you reflash to stock Rom. That is the best way to get the firmware back on the camera. If this does not work you have no choice but to go back to the sprint store.
Click to expand...
Click to collapse
I've flashed back to stock and that didn't fix it either. I'ma buy a replacement camera I guess. To ebay I go!
PS I CANT take the phone back to sprint, as I'm not with sprint, I use my phone with Verizon.

TpyoKnig said:
I've flashed back to stock and that didn't fix it either. I'ma buy a replacement camera I guess. To ebay I go!
PS I CANT take the phone back to sprint, as I'm not with sprint, I use my phone with Verizon.
Click to expand...
Click to collapse
You must know someone high up to have them put your esn in the device management database. Unless you're talking about one of the prepaid carriers that use Verizon's network.
Sent from my SPH-D700 using Tapatalk

Verizon does have an open network policy..

One last suggestion: Take the sd card out, then try the camera and see if the app opens.
When my sd card was borked, I couldn't open the app at all with the card in, but when I took it out, the camera opened fine, but gave the error that it couldn't save without an sd card. After replacing sd card, worked fine.

mis3 said:
One last suggestion: Take the sd card out, then try the camera and see if the app opens.
When my sd card was borked, I couldn't open the app at all with the card in, but when I took it out, the camera opened fine, but gave the error that it couldn't save without an sd card. After replacing sd card, worked fine.
Click to expand...
Click to collapse
I've tried with a new SD card, same thing, browsing the SGS 1900 forum, it appears they have the EXACT same camera in the I9000, now to get the firmware to work. http://forum.xda-developers.com/showthread.php?t=829482
a few there reported they got it fixed. gotta figure out how they did it. Can someone send me the latest files in /system/firmware/ for their device? Thanks!

actually. our firmware files are stored in /system/sem/ so if someone could provide me with the latest ones, I would GREATLY appreciate it the wave_firmware files from another post for the SGS I9000 goes a bit furthur, it goes to 8% 19/253 then fails at (in logcat) VIDIOC_S_CTRL failed, then whole thing fails to flash. I'm almost positive this is a firmware issue.

TpyoKnig said:
actually. our firmware files are stored in /system/sem/ so if someone could provide me with the latest ones, I would GREATLY appreciate it the wave_firmware files from another post for the SGS I9000 goes a bit furthur, it goes to 8% 19/253 then fails at (in logcat) VIDIOC_S_CTRL failed, then whole thing fails to flash. I'm almost positive this is a firmware issue.
Click to expand...
Click to collapse
There seems to be two copies - /system/seh and /system/sem - on EC05. Both are in the attached zip.

[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

static phone calls and kernels not working

I hope someone can help me figure out what the problem is with my phone because I am out of ideas. I've been using the peoples ROM with stock kernel and occasionally my phone calls would be very staticy , but toggling speaker phone removed that issue. Now any ROM I use that doesn't use the stock kernel causes that same issue except I can't toggle it off anymore. Also many kernels I use besides stock causes apps to force close and system process to force close, unless the kernel came with the ROM. I've tried wiping my internal storage, formatting everything, installing any kernel I can find, fixing permissions, clear long cache 100's of times, flashing kernelcleaner, and I really don't know what to do next. Any advice? I really don't want to be stuck on 4.1.2.

Can I get any help on this?
Sent from my SPH-L710 using xda app-developers app

dokosatchii said:
Can I get any help on this?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Maybe try a clean install. You could always take a logcat to see if it is phone related. May also be a defective earpiece

lvpre said:
Maybe try a clean install. You could always take a logcat to see if it is phone related. May also be a defective earpiece
Click to expand...
Click to collapse
Do you mean wipe internal/system/factory reset and the install a ROM? I've done that but no improvements. I'll try a logcat but have no idea how to decipher it.
Normally I'd agree with you about it being a faulty earpiece, but the same issue pops up if I connect headphones or bluetooth headset during a phone call, still the same static noise. Could it cause all these issues?

I created a logcat but not sure what I should be looking for. I ran a logcat while making a phone call, does someone have a similar logcat so I can compare against? If it turns out the same I guess its just a hardware problem and that I should replace the earpiece? Any advice would be great.

dokosatchii said:
I created a logcat but not sure what I should be looking for. I ran a logcat while making a phone call, does someone have a similar logcat so I can compare against? If it turns out the same I guess its just a hardware problem and that I should replace the earpiece? Any advice would be great.
Click to expand...
Click to collapse
What rom are you using? Sometimes a logcat with have an /e or /f if a file or service is causing the issue. Start the logcat then try to make a call. If you are still having issues, use odin, unified toolkit, or something similar and make your phone completely stock again. Since you did a full wipe (system, data, caches, factory reset), maybe the rom you flashed has a custom kernel that has voltage settings not compatible with your phone. But try the stock rooted rom and then go back to completely unrooted, out-of-the-box stock if that doesn't work.

lvpre said:
What rom are you using? Sometimes a logcat with have an /e or /f if a file or service is causing the issue. Start the logcat then try to make a call. If you are still having issues, use odin, unified toolkit, or something similar and make your phone completely stock again. Since you did a full wipe (system, data, caches, factory reset), maybe the rom you flashed has a custom kernel that has voltage settings not compatible with your phone. But try the stock rooted rom and then go back to completely unrooted, out-of-the-box stock if that doesn't work.
Click to expand...
Click to collapse
I reset the phone to stock using odin, and I still get the issue(sometimes), but it goes away when I toggle speaker phone once. I am starting to think either the speaker is bad or my phone is just faulty.
I have tried every rom possible, MIUI, Paranoid Android, Slimbean, the only one that works is the rom that uses stock kernel like FreeGS3 and The Peoples Rom and even then I still have to toggle the speaker phone to get it working.(not all the time)
ASIDE: When I flash other kernels to test whether it'll work just as ktoonz, etc. the phone just goes through a bootloop or process start to fail, could be related?
EDIT: I created a logcat while placing a phone call while on stock and while using slimbean and I see the following discrepancies:
Stock: 4.1.2
--------------------------------------------------------------------------------------------
[ 08-21 09:50:38.359 170: 170 D/AudioHardwareALSA ]
setParameters() realcall=on
[ 08-21 09:50:38.359 170: 170 D/AudioHardwareALSA ]
>>>> realcall start!!!!
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
setPhoneState() state 2
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
Entering call in setPhoneState()
[ 08-21 09:50:38.369 170:13648 E/AudioPolicyManagerBase ]
unknown stream type
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
getNewDevice() selected device 1
Slimbean ROM 4.3/4.2.2
--------------------------------------------------------------------------------------------
[ 08-21 10:07:52.803 343: 817 D/AudioHardwareInterface ]
setMode(IN_CALL)
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
Any idea's on how to get this AudioPolicyManager to run properly?
EDIT: After endless searching, guidance and effort, I am chalking this up to hardware problems. If anyone is experiencing this issue, I recommended returning the phone to sprint and getting it replaced.

Sound dies after waking

This will be a long post to explain my problem and I hope somebody could enlighten me on what's happening and if it's fixable
Sound Problem
Bought an used T-Mobile S4 (SGH-M919), came with stock 4.3 (MK2), not rooted, not KNOX warranty voided, everything working perfectly including sound, 2 days of constant use, then I wanted to upgrade to 4.4.4 (NK2), I tried through system update on Android and it only said "Failed to register" or something similar, however with Kies3 I was able to upgrade, then the nightmare started.
Being a stock firmware I thought, what could go wrong, update went smoothly, everything was working but after 10 minutes and here comes the important part, the SOUND GETS STUCK/DOESN'T RESUME/DIES AFTER THE SYSTEM GOES TO SLEEP, it always happens when I leave the screen turn off for like 5-10 minutes, the longer it stays off, less chances sound returns, not through ear piece, speaker or headphones, weird part it's that if I turn the phone off and on it works normally again until sleep, everything works normally, except for the part that if the screen goes off, hell begins, the longer it stays off, less chances sound resumes, and I say that because sometimes sound resumes but after like 5-15 seconds of waking, AND IT REPRODUCES EVERY SOUND IT SHOULD HAVE DONE WHEN IT WENT AWAKE (like button presses, volume change, sound systems, etc), like if something was stuck or in large queue, I can almost say it's 100% something related to software and not hardware since it reproduces the animation sound at the boot every time.
After the sound dies, weird stuff happens, Youtube videos get reproduced at like 0.5x speed, trying to play music with the default player says "Not supported" (varying mp3's from 128 to 320kbps), sometimes if I reboot from Android it gets stuck in a restart loop, not always, sound only seems to return again when it's restarted through shutdown/manually (that doesn't seem to happen with custom ROMs), sometimes Android gets weird, like laggy, no background on the home screen, stuck and with only the shutdown menu working, not even volume bar showing up or very laggy (this was something very rare in custom ROMs or it didn't happen at all).
I had to void the KNOX warranty to install a custom recovery (TWRP) and flash custom roms, I already tried stock 4.4.4 roms debloated/deodexed/rooted and even a 5.0.1 rom, tried 2 different kernels + stock, different modems varying from MK2 to NK2 again (flashed like 5 times each one), hell even I tried to flash the LTE modem (NON-HLOS.bin) from MK2, however I didn't get any sound (WiFi was working, weird) since I read that it has to match the bootloader version.
At this moment I'm downloading a 4.3 custom ROM to do another test and probably the last one, I'm running out of options.
Little Facts:
-Already went to complete stock through Kies3 and tried flashing the full firmware with Odin too.
-Volume bar changes normally, I really assured it wasn't muted in any way.
-I f*ckd up IMEI, too much wipes, kernel switches, rom flashing, I did an EFS backup just to find it was at 0 already, however problem started way before that, one problem at the time.
-Light/RGB sensor doesn't work, headphone jack do (I even dissassembled and reassembled without headphone jack to test, didn't work).
-Tried plugin headphones and removing them multiple times.
-Tried with and without a SD card/SIM/WiFi.
-No warranty.
Sorry for the long post, I can create a thread if the mods prefer.

I think I remember seeing something like this and I'm not sure on this but I think it was a third party app causing it. Have you factory reset and installed no apps to see if it still happened, or reboot into safe mode? If you have, can you upload bootloader and modem info using this app https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo when you say you flashed the LTE modem and got no sound, that shouldn't happen if you did indeed flash the matching LTE modem. Could be firmwares never got flashed correctly. Could also be why your imei is 0

I did multiple factory resets, and when I flashed the LTE modem I didn't get sound because the LTE modem was MK2 (just trying stuff) and bootloader NK2, however I reflashed the full stock firmware, I'm currently at NK2 modem, LTE and bootloader.
The only thing I haven't done is reboot in safe mode, will try later and post results.
Edit:
About the IMEI, I'm pretty sure that when I made the EFS backup with TWRP it wasn't 0, since I made it because I was going to try stuff that could go wrong and I wanted a backup, I still have the full system backup with EFS partition included, however, not even restoring the backup bring it back.

New info
-Safe-mode didn't work
-Did multiple full wipes and back to stock through Kies3/Odin, nothing
Trying to find more info found this through ' adb logcat *:E ' (Stock ROM, NK2, 4.4.4)
Code:
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/ACDB-LOADER( 300): Error: ACDB AudProc vol returned = -8
E/alsa_pcm( 300): cannot prepare channel: errno =-22
If the sound was lost, as soon as I click the screen it produces those errors like 100 times, even if it's on vibration only.
Some other errors from *#7353# testing (SPEAKER TEST)
Code:
E/AudioSessionOutALSA( 300): PCM Prepare failed - playback err = 0
E/AudioSessionOutALSA( 300): Failed to open LPA/Tunnel Session
E/AudioTrack( 300): Could not get audio output for stream type 3
E/AudioSink( 300): Unable to create audio track
E/TunnelPlayer( 300): Opening a routing session failed
E/MediaPlayer( 8834): error (1, -19)
E/MediaPlayer( 8834): error (-19, 0)
E/MediaPlayer( 8834): Should have subtitle controller already set
E/MediaPlayer( 8834): Error (1,-19)
E/MediaPlayer( 8834): Error (-19,0)
And from MELODY TEST
Code:
E/MediaPlayer( 8834): stop called in state 0
E/MediaPlayer( 8834): error (-38, 0)
E/MediaPlayerService( 300): WFD client is not created
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
And those 2 lines repeats themselves like 100 times
It could be an hardware problem, sadly, I hate that it works, but it stops working for no reason.
And found multiple threads about the same issue across different models:
http://forum.xda-developers.com/showthread.php?t=2333222
http://forum.xda-developers.com/showthread.php?t=2386070
http://forum.xda-developers.com/showthread.php?t=2333222
http://forum.xda-developers.com/showthread.php?t=2718326
http://forum.xda-developers.com/showthread.php?t=2612167&page=6 Post #51

My problem may be similar to yours. I have a completely stock S4. I have done no rooting to it. About a month ago I noticed the same sound problem you have. I noticed my phone would lose sound ability the longer it was on. Similar problems with YouTube playback slow, and I can't play media files like music or video (I get process errors).
I have factory reset a few times and the problems return. I'm getting tired of having to reset my phone every 1/2 hour. I've missed phone calls and alarms I've set.

I had this problem on an ATT S4. It was a hardware issue. Phone was under warranty and fixed by Samsung.
Sent from my SGH-M919 using Tapatalk

I guess I have to do a insurance claim. My current phone is my 1st replacement of my original GS4. The first phone was insurance replaced because it was passed the factory warranty and it stopped charging any battery put into it. Now my current one has started hanging at the T-mobile logo when resetting and just plain random resets.
My GS4 was reliable for a while. Maybe time for a Nexus 6.

I literally did the same thing last week with a refurbished phone from T-Mobile. Buyer be ware
Sent from my SGH-M919 using XDA Free mobile app