[Updated]
I recently put CM 11 on my Verizon S4. Everything was working fine. I decided to update to a more recent nightly (likely last weekend). After the update, my camera doesn't work any more. When I go in to the camera it shows a blank screen for the camera image, freezes for a while and then a popup says that the Camera Failed! After googling, I tried restoring the previous CM 11 image that worked previously. I tried wiping the cache, force closing the app and clearing cache and data, I re-flashed the original Samsung image, I did a factory reset. Nothing worked to restore the camera. I went in today to a phone repair shop and they replaced the camera module. That didn't help - it still didn't work. Thankfully they didn't charge me anything for their time which was really nice of them. I get home and restored the CM 11 backup of the working image. The camera still doesn't work and now the external speakers don't work for media files. I was afraid that it was something forgotten to be reconnected by the repair shop, but I can hear the phone ring when I make a call. (I haven't received a call yet so I don't know if it is only on outgoing calls).
Can anyone point me to help or resources for how I can diagnose and hopefully fix these problems? My phone is falling apart and I don't know what to do!
Peter
[Update] I solved the camera problem by restoring a backup of the original TW rom. This seems similar to a problem I had with dubbsy's rom where the GPS wouldn't work some times after a flash and required restoring the touchwiz rom to get it to work and then re-flashing the custom rom. Once the camera started working again with the original rom it continues to work with the OctOS rom. Strange but at least it works.
The external speaker was resolved by taking it back to the repair shop. He switched the external speaker module with one from another S4. Putting it back together it worked, but when he put back in all the screws and closed things up it didn't work again. Finally loosening a few screws, getting it to work and then retightening solved it. I don't think it was the original speaker module, but something about opening it up and closing it back up caused the speaker not to work at all. Now it does and I can hear the ringer and notifications agin.
Related
My camera all of the sudden stopped working the other day. Whenever I try to use it, the screen goes black then force closes after a few minutes. I tried to download a few other camera apps and nothing happened. Currently running with no root and I don't want to root it until the camera is fixed, unless that would help fix it.
MSK01 said:
My camera all of the sudden stopped working the other day. Whenever I try to use it, the screen goes black then force closes after a few minutes. I tried to download a few other camera apps and nothing happened. Currently running with no root and I don't want to root it until the camera is fixed, unless that would help fix it.
Click to expand...
Click to collapse
If you're on a 100% stock ROM with no changes and no root access with a camera that stopped working, there are very few things which can be done.
The only real solution would be to clear out the specific stock camera application's data directory. Not sure if this is possible w/o having to clear all the data.
I'd suggest the following steps in this order:
1) Manage applications under settings is where to look to clear out the specific Camera application data in hopes that only something was corrupted. Reboot and test.
2) Wipe all data on the device. Reboot and test.
3) If none of these worked, personally, I would return/exchange the stock device for another one as at this point, it would definitely seem to be hardware related.
An alternative route would be to gain root access and look into switch kernels/ROMs, but this could end up being a dead end if the issue is hardware related.
The only good/not so bad news is I've never seen the camera completely stop working on any of these devices .. at least not yet. So hopefully this issue is not hardware related! Good luck!
I cleared out the camera information and it worked the second I restarted my phone. Thank you!
That happened to me to, nothing I tried worked. Was good that I had ESRP. The Sprint store replacement the phone in lieu of just fixing the camera
dgr581 said:
That happened to me to, nothing I tried worked. Was good that I had ESRP. The Sprint store replacement the phone in lieu of just fixing the camera
Click to expand...
Click to collapse
Sometimes it's nice for them to just fix your phone and not give you a refurb. My sprint store seems to screw ur phone up when they fix it lol.
In the past when I was on the evo they swapped my screen out and broke my volume buttons. Then they just gave me a refurb.
Same thing happened to me. Suddenly, it doesn't work. Oddly enough, the Front Face camera does work by using the Mirror app. But the Rear camera does not respond when launching the Camera app.
I already tried switching ROMs, switching kernels, factory defaults, and nothing worked. Might be a hardware issue. I just hope it can be fixed without replacing my phone. It would suck having a replacement phone with HBOOT v1.50...
3 days ago I started experiencing weird phone behaviour. I tried calling someone but i didn't hear the "calling" beeping sound nor i could hear if there was any answer on the other end. Then i couldn't hear anything when i was getting calls. It didn't matter if i use the "loud" speaker or the "on-ear" speaker, the result was the same - no in-call volume. Microphone and "loud" speaker seem to work fine as i could use them as usual with other apps. Mobile data was working, so antenna was also OK, SIM card seemed to function properly as well. Other people who I tried speaking to did hear me fine, just i couldn't hear anything.
I tried freezing, then uninstalling all the non system apps that i thought could have impact on this matter, but that didn't help. I was using AOKP Rom and i had nand backup of Omega Rom 5.2 with stock samsung touchwiz, I tried restoring back to it, but for my surprise the in-call sound was still quiet. I didn't know what else could be and let it alone for an hour or so. Suddenly, the next time I tried it again, it WORKED!. After 2 hours of it working, i got back to my AOKP as i have it backed up right before switching to Omega Rom backup. I defrosted the apps and reinstalled the uninstalled ones. Nothing was influencing the in-call sound of the phone, everything worked fine.
The next day this problem popped up all of a sudden again. I got mad, i tried everything i did before except restoring the stock rom. Nothing helped. I then booted into CWM and set to fix permissions, to wipe Dalvik cache and i flashed the latest modem. Rebooted. The in-call sound was OK again. Something of these actions fixed it.
Today i got this NO IN-CALL SOUND bug once again. Seems like it wasn't the new modem that helped me. I booted to CWM and wiped Dalvik cache, rebooted, the in-call sound was working fine again. So, wiping Dalvik cache does fix the problem so far.
I'm keen to understand what exactly could cause this weird behaviour of disappearing in-call sound. Do you have any ideas?
I have the same problem.
If you find any sollutions, let me know.
You may delete some system apps.the solution is that you can just flash a rom and don't delete the apps you don't know
I've experienced something similar. I think in my case the MIC wasn't working either, but not entirely sure about that.
This thread seems to be about the same issue:
http://forum.xda-developers.com/showthread.php?t=1721604
Also while browsing the developer forum, I bumped into something interesting:
http://forum.xda-developers.com/showthread.php?t=1745974
This is for a ROM I don't use, but if the it's the same issue, and affects other ROMs too, I'd be very interested in knowing what exactly was fixed here.
Experienced this problem for the first time today, the volume actually disappeared during a call. Read through the posts suggested above and cleared cache and dalvik, but it didn't make any difference. Finally, I removed the battery, re-fitted and re-booted and it's currently working again. There does seem to be an issue with Omega/Siyah 1.2.6 combinations which is what I'm currently running
Hi all,
I'm really hoping someone will be able to help me. My Nexus 10 has been working fine up til now. I just tried to take some photos, the first two were fine, the flash worked and they came out ok.. then I tried to take another but the flash didn't work. I figured it might just be a bug so I restarted the nexus, it still wouldn't work. then after a few mins the flash just came on and stayed on. so I went back to the camera app, the flash turned off and the app told me "cannot connect to camera". Another reboot and the camera is fine again but still no flash. Any suggestions? or is it RMA time... which I'm reluctant to do as other than this the tablet is perfect.
Thanks
The flash by-default is automatic, depending on lighting. May want to try going to the camera app, and making sure flash is actually on, and not automatic, and then giving it a shot.
Tried setting the flash from auto, no luck. Was in a fairly dark room anyway so auto should have caused the flash to go anyway. Thanks for the suggestion though
EDIT
------------
UPDATE - I tried flashing the factory image to check if it was some kind of corruption or software bug. Didn't work, still no flash. So I started reinstalling all my apps and setting everything back up and, while installing some humble bundle games, I accidentally started the camera app... and guess what, the flash came on and then went off again after it had focused. Took a few photos and the flash was working. Tried again 2 mins later (without changing anything on the device) and the flash has stopped working again...>.<
I have a stock rooted G3 running ZV8. One day last week, my rear facing camera stopped working. No warnings or anything like that beforehand, just no longer working. I get a black screen with only a back button and the last pic taken icon, but nothing else. When I try to access the camera from another camera app I get the message that the camera can't be started or is in use by another application.
The front facing camera seems to still be functional, but can only be accessed by a camera app that goes directly to it, like Camera360. I'm at a complete loss as to ideas about whether this is a software issue, or a hardware issue. If anyone else has had issues with their camera no longer working, any info you can give would be greatly appreciated.
Thanks!
I am having the same problem, and it just appeared out of nowhere as well... I have tried clearing the camera apps cache and data and have wiped davlick from twrp but to no avail. Going to try wiping and reinstalling the rom and will get back to you if it works.
I am running the stock rooted rom :S
My calls are always on speakerphone, doesn't matter if the speakerphone button is on or not, I don't believe this is a hardware problem even though my screen was replaced a few days ago, I mean how could it possibly be. I can't be the only one with this problem, I have searched everywhere, seems like I am. I'm running stock (rooted) so I don't believe it is a software problem either, I have tried rebooting and clearing cache so far.
Details: Stock E2303 MM Rooted. Only thing that could be screwing with audio is Viper4Android, and I uninstalled its drivers already. Also the headphone jack is dead if it matters.
Sorry for creating thread ahead of time, but the problem has been fixed by flashing stock using Flashtool, incase someone has the same problem.