Database Info

Camera Force Closes

Any app that uses the camera seems to force close on me. Examples include the amazon.com, droidshooting, layar, etc. After the force close, the camera app itself reports that is cannot connect to the camera. The native camera app, google googles, and barcode scanner app seem to be immune to the initial crash. The amazon app worked before I updated to 2.3.2, have not tried it since. Is this a common issue, or should I exchange my phone. I am running stock, pushed OTA 2.3.3 manually. I have had no other issues with this phone.

Kah-Neth said:
Any app that uses the camera seems to force close on me. Examples include the amazon.com, droidshooting, layar, etc. After the force close, the camera app itself reports that is cannot connect to the camera. The native camera app, google googles, and barcode scanner app seem to be immune to the initial crash. The amazon app worked before I updated to 2.3.2, have not tried it since. Is this a common issue, or should I exchange my phone. I am running stock, pushed OTA 2.3.3 manually. I have had no other issues with this phone.
Click to expand...
Click to collapse
go to the main settings, applications, manage applications, all, camera, then press the clear data button. check and see if that fixes the problem for you

simms22 said:
go to the main settings, applications, manage applications, all, camera, then press the clear data button. check and see if that fixes the problem for you
Click to expand...
Click to collapse
It did not. The camera app itself works, until some other app trying to use the camera forcecloses.

Kah-Neth said:
It did not. The camera app itself works, until some other app trying to use the camera forcecloses.
Click to expand...
Click to collapse
try clearing the data on one of those apps that force make the camera force close.

simms22 said:
try clearing the data on one of those apps that force make the camera force close.
Click to expand...
Click to collapse
Still force closes. I am thinking it may be something changed in the way the phone handles having two cameras.

Has anybody else had this problem with amazon app?

I have the problem with the bar code scanner part of the Android app. The take a picture part works fine for me. i tried wiping, different roms, 2.3.2, 2.3.3...even restoring back to an older nandroid backup. I don't use the bar code scanner often so I don't remember if the older version of 2.3 worked previously
Glad to see someone else is seeing it and not just my phone. I asked a similar question a few days ago and the replies were basically don't use amazon.. use something else... blah blah..

ScotchtapeLoser said:
I have the problem with the bar code scanner part of the Android app. The take a picture part works fine for me. i tried wiping, different roms, 2.3.2, 2.3.3...even restoring back to an older nandroid backup. I don't use the bar code scanner often so I don't remember if the older version of 2.3 worked previously
Glad to see someone else is seeing it and not just my phone. I asked a similar question a few days ago and the replies were basically don't use amazon.. use something else... blah blah..
Click to expand...
Click to collapse
Does the camera stop working for other apps after you do this? When I try certain apps, they forceclose, then the camera will not at all until i reboot.

Yes. If I try to use the amazon bar code scanner, it kills the camera and no other camera app will work until I reboot.

bumping.... the way the camera is called in 2.3.3 is different. Amazon corrected the problem with their app in the recent update. The other programs will have to do that eventually as well.

Camera sometimes doesn't work

Hello.
I'm on franco kernel r33 and stock rom. Sometimes the camera doesn't work, it says it "can't connect to device" or something like that. I don't know what's going on and I have to reboot to make it work. Here's the log. Thanks in advance.

Forgot to attach the log -.-

Well I'm not gonna look through you logcat right now(might circle back to that, even if it may not contain anything relevant) but I've found that I can make this error message appear by having the camera used by another app(e.g. one that works like a flashlight) and then opening the camera.
So do you use any third party app that make use of the camera? It could be snapchat or Skype for example. If they fail to release the camera when you press the home button, they may be able to cause this problem. If you have such a third party app, try quitting it properly by use of the back button or maybe even force close it.
edit: I'm actually not sure that killing the app will fix the problem, so you may have to try not using it for a while to see if it makes the problem not appear. My bet is that it is caused by skype not releasing the camera properly, since that seems to be the only app accessing it prior to the error.
It can of course also be a hw problem or a low level(kernel) problem. And after looking through the log it doesnt look like the same error i get when the camera is simply occupied. Does it work in a third party camera app after you get the error?

ColdFire InOx said:
Hello.
I'm on franco kernel r33 and stock rom. Sometimes the camera doesn't work, it says it "can't connect to device" or something like that. I don't know what's going on and I have to reboot to make it work. Here's the log. Thanks in advance.
Click to expand...
Click to collapse
Snapchat has been borking the Camera on my phone and a Galaxy S3 with Beanstalk.

Snapchat or other 3rd party camera app probably.
Sent from my Nexus 5 using Tapatalk

mortenmhp said:
It can of course also be a hw problem or a low level(kernel) problem. And after looking through the log it doesnt look like the same error i get when the camera is simply occupied. Does it work in a third party camera app after you get the error?
Click to expand...
Click to collapse
I believe it doesn't...
Enviado do meu Nexus 5 através de Tapatalk

Well that rules out problems with the camera app itself, so it is either because the camera is not being released by Skype or something similar, or it is a problem with the phone or os.
Try to avoid using Skype or any other third party app that uses the camera, after a reboot and see if the problem still appear. Maybe even try safe mode (also without running those apps).
If that doesn't fix it, you should do a factory reset.

It seems to be Instagram causing the issue. Is there any way to fix it?

Camera freezes?

Am I the only one with stock 4.4.2 whose camera freezes?
I've been battling the problem that if I use the camera on the Nexus 5 it will sometimes freeze the phone. It may happen after a variable amount of pictures are taken. Suddenly the phone freezes and only a reboot will get it back to normal. I've asked in this forum without success and then found this
http://stackoverflow.com/questions/5880096/problem-using-camera-api-on-android?rq=1
Any solutions anyone?

Anderson2 said:
Am I the only one with stock 4.4.2 whose camera freezes?
I've been battling the problem that if I use the camera on the Nexus 5 it will sometimes freeze the phone. It may happen after a variable amount of pictures are taken. Suddenly the phone freezes and only a reboot will get it back to normal. I've asked in this forum without success and then found this
http://stackoverflow.com/questions/5880096/problem-using-camera-api-on-android?rq=1
Any solutions anyone?
Click to expand...
Click to collapse
What's your phone setup? Are you rooted with a custom ROM?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Rooted, stock 4.4.2 ROM.
Nova prime launcher.
No syncing on anything.
Use xprivacy, AFWall+, gravitybox. (but all 3 disabled with no improvement).
Camera is essentially unusable because of need to reboot every few pictures. Screenshots in my other thread.
http://forum.xda-developers.com/showthread.php?t=2761146
http://forum.xda-developers.com/showthread.php?t=2761146

Anderson2 said:
Rooted, stock 4.4.2 ROM.
Nova prime launcher.
No syncing on anything.
Use xprivacy, AFWall+, gravitybox. (but all 3 disabled with no improvement).
Camera is essentially unusable because of need to reboot every few pictures. Screenshots in my other thread.
http://forum.xda-developers.com/showthread.php?t=2761146
http://forum.xda-developers.com/showthread.php?t=2761146
Click to expand...
Click to collapse
dont disable the exposed, delete it(remove everything xposed completely), reboot, then try your camera

I would hate to do that because I really like xposed. But I'll make a nandroid backup, and then do as you say. If it's no better, I could always restore the nandroid. But nobody else has noticed any connection between xposed and Google camera. I "believe" the problems started when I updated to the latest camera update. Wish I could find the pre update camera app.

Anderson2 said:
I would hate to do that because I really like xposed. But I'll make a nandroid backup, and then do as you say. If it's no better, I could always restore the nandroid. But nobody else has noticed any connection between xposed and Google camera. I "believe" the problems started when I updated to the latest camera update. Wish I could find the pre update camera app.
Click to expand...
Click to collapse
xposed causes many many random issues that are undocumented. for many not a single issue, for others its like a phone full of gremlins.

Well, tis done. I'll see if the camera behaves. It takes time for it to act up....
Fwiw, I've used xposed for quite a while and the camera freezing only started about 4-6 weeks ago. Maybe it was a recent update.
I uninstalled xposed. Where should I look for files to delete to ensure a good test?

Anderson2 said:
Well, tis done. I'll see if the camera behaves. It takes time for it to act up....
Fwiw, I've used xposed for quite a while and the camera freezing only started about 4-6 weeks ago. Maybe it was a recent update.
I uninstalled xposed. Where should I look for files to delete to ensure a good test?
Click to expand...
Click to collapse
honestly, i dont know. i have never needed or been willing to use xposed. an uninstall and a reboot should be fine(dirty flashing your rom again would be best, but i think it will be fine without). just give it some time to test. if its not xposed, restore your backup and we will look further.

I'm afraid to say anything, but I think uninstalling Xposed did it. Will wait longer before breathing a sigh.....
Thank you.

Trying to debloat

I was wondering if someone could shed some light on this. I've been playing with what's safe to debloat but I'm only just starting. I used titanium backup, after making a full nandroid backup, to remove some things I thought were basic safe bloat. Like hangouts, Facebook, gmail, ant + hal stuff.
But when I restart it, the flashlight doesn't work anymore, says it's already being used and the toggle is sort of greyed out. It seemed to be part of "smart things' which I didn't touch, to look in greenify that starts running when I turned on the torch after hibernating a bunch of things. This was true on both nougat and Oreo, the error happened on both after only some very basic debloat.
... So is debloat not possible? I used the same caution as my s5 neo currently on lollipop. The torch there works just fine with the ant hal stuff removed so I figured that was safe. This was the only true system app set I removed.
So.... What broke the flashlight? To go back to my backup it works again so not a hardware issue... I'm at a loss
Sent from my [device_name] using XDA-Developers Legacy app

Could you please specify exactly what apps you've removed?

Pawprints1986 said:
I was wondering if someone could shed some light on this. I've been playing with what's safe to debloat but I'm only just starting. I used titanium backup, after making a full nandroid backup, to remove some things I thought were basic safe bloat. Like hangouts, Facebook, gmail, ant + hal stuff.
But when I restart it, the flashlight doesn't work anymore, says it's already being used and the toggle is sort of greyed out. It seemed to be part of "smart things' which I didn't touch, to look in greenify that starts running when I turned on the torch after hibernating a bunch of things. This was true on both nougat and Oreo, the error happened on both after only some very basic debloat.
... So is debloat not possible? I used the same caution as my s5 neo currently on lollipop. The torch there works just fine with the ant hal stuff removed so I figured that was safe. This was the only true system app set I removed.
So.... What broke the flashlight? To go back to my backup it works again so not a hardware issue... I'm at a loss
Click to expand...
Click to collapse
You want to keep ant+ as that deals with low power Bluetooth devices, and you want to keep anything Hal related since that deals with Hardware Access Layer.

BurnedDrake said:
You want to keep ant+ as that deals with low power Bluetooth devices, and you want to keep anything Hal related since that deals with Hardware Access Layer.
Click to expand...
Click to collapse
The weird part is though, I can hibernate those things with greenify, and to turn on the flashlight with those hibernated, they don't come out from hibernation but the flashlight does work, the only thing actually that does come out of hibernation is"smart things" so I thought that was the thing to not remove... That's why I thought they were safe to kill off completely. On my s5 neo I did kill those off and nothing stopped working.... Hmm. Odd indeed.
Sent from my [device_name] using XDA-Developers Legacy app

Pawprints1986 said:
The weird part is though, I can hibernate those things with greenify, and to turn on the flashlight with those hibernated, they don't come out from hibernation but the flashlight does work, the only thing actually that does come out of hibernation is"smart things" so I thought that was the thing to not remove... That's why I thought they were safe to kill off completely. On my s5 neo I did kill those off and nothing stopped working.... Hmm. Odd indeed.
Click to expand...
Click to collapse
I may be incorrect about hal being the actual cause of flashlight not working I was really only using that as an example, but freezing things makes the system see it as not existing and greenifying things just hibernates them,but still allows for apps/system to call them when needed. The safest bet for debloating is just removing apps that you know a hundred percent what they are and leave the rest for greenify if need be. I've also seen a lot of people get overzealous with greenify, Android does a great job of managing memory when it needs to. For example you don't want to greenify everything when those things get woken up all the time for things like phone calls text messages and whatnot, it is detrimental to battery life.

Question HELP! Front camer showing "Camera Failed" warning in all apps

Hi. I've had the S22 Ultra for 3 days and this morning I noticed that when I tried to unlock with Face Recognition it says "Couldn't open camera. Try again."
I then tried opening the camera app, all rear sensors work. But when I switch to the front camera, the app crashes with a warning "Camera failed". I also can't open the front cam in third party apps like messenger and Instagram.
What I did so far:
1. Deleted cache and data for camera app. Still same error when switching to front cam.
2. Removed permissions for All apps except the default camera app. Same error.
3. Uninstalled all apps I have installed since it was last working, still no dice.
4. Booted in safe mode, front cam works fine.
Since it's working in safe mode, I guess this isn't any serious hardware issue, I hope.
I have the Snapdragon version with 512gb storage model SM-S908E/DS.
Anybody have an idea what may be causing this and how to fix it?
Thanks in advance!

It's a 3rd party app. Look at which ones have or request cam permissions to start.
A package disabler is helpful as you can disable apps one by one until you find it.

blackhawk said:
It's a 3rd party app. Look at which ones have or request cam permissions to start.
A package disabler is helpful as you can disable apps one by one until you find it.
Click to expand...
Click to collapse
Got it to work eventually by doing force restart (holding down power button + volume up key). Turned it back on and front cam started working again.
I also then re-allowed the app permissions when I was diagnosing it and front cam still works fine.
Yeah might have been a third party app though it's weird that it didn't work even when I removed all camera permissions for all the apps.
Glad it's working again though, and thankfully I did not need to do factory reset and it's not a hardware issue so I avoid the trouble of returning the unit.
Thanks!

Unless you find the root cause it likely will return.
This is why one should use factory reset as a last ditch measure. It can be tedious but rewarding.
Many times issues are inadvertently caused by the user, many times by installing buggy 3rd party apps. I tend not to experiment with new apps unless I need them because of the trouble they can cause... like 2 back to back factory resets because of boot looping. Android's should run fast and stable if not the cause(s) should be tracked down.
Malware, boot loops*, major firmware upgrades, apps changing hidden user settings and corruption of the user data partition are the only exceptions.
*if app caused you'll still need to track it down

The only recent apps that I remember installing was an app called Nice Lock (an alternative to good lock since we don't have it in my region) and the Keys Cafe module, as well as the "Write on PDF" app from Samsung. I uninstalled these when I was having the front camera problem but removing them did not solve it even after a few regular restarts and cache/data clearing. It only started working when I did the force restart. I reinstalled "Write on PDF" back and so far, so good.

Hard reboot is the solution sometimes.
If you need to continuously use it though it can indicate a hardware issue.
Run it through it's paces while still within the window of return.

Yeah I might need to keep an eye on the issue.
Thanks!

hard reset and start installing apps 1-by-1 and test camera