i did the update over the lg tool, all good except everytime i go into the stock camera app and try to do anything it force closes :/ camera apps from the market work wtf i miss froyo....
try clearing Camera app data
My camera does the same thing. It first happened at a concert I was at on Sunday, when I needed it the most. I cleared the Camera data and it kept on happening. After it force closed, when I open it, the camera does not work at all. The camera app opens, but all I see is a black screen. Only fix I've found is a reboot.
ok so ive cleared the camera app data and rebooted it still force closes, apps from the market work just not the stock o and oi rooted it today etc and am using the rooted stock ginger rom and the camera app still f/c
south69_dallas said:
i did the update over the lg tool, all good except everytime i go into the stock camera app and try to do anything it force closes :/ camera apps from the market work wtf i miss froyo....
Click to expand...
Click to collapse
If all else fails, do a factory reset. Yeah I know, you won't like it, but you already don't like the force Close...so what can you lose?
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?
Since greenifying my camera app (stock one), when i go to take pictures, it often either opens with an error, or it will open and appear to be working, but it wont take any pictures. this makes things difficult when trying to capture a moment.
So what im wondering is, if its a bad idea to hibernate the camera (doesnt seem like it should be...) or, if ive hibernated something else i shouldnt have which makes the camera run properly??
Im running samsung stock 4.0.4 UCLJ3
I just tried a 3rd party app too, and that one opens in a frozen state too ("a better camera")
Pawprints1986 said:
Since greenifying my camera app (stock one), when i go to take pictures, it often either opens with an error, or it will open and appear to be working, but it wont take any pictures. this makes things difficult when trying to capture a moment.
So what im wondering is, if its a bad idea to hibernate the camera (doesnt seem like it should be...) or, if ive hibernated something else i shouldnt have which makes the camera run properly??
Im running samsung stock 4.0.4 UCLJ3
I just tried a 3rd party app too, and that one opens in a frozen state too ("a better camera")
Click to expand...
Click to collapse
i hibernated my camera app and it's working fine....it's not a problem cuz when you open the hibernated app it will start normally .....so make sure to wipe cache and data of the camera app and see what happen
good luck :good:
I'm using a Pixel, still on Android 9, and my orientation sensor (and accelerometer) have suddenly stopped working. However, it appears that it's a software issue as the auto-rotation still works when in Safe Mode. I've uninstalled every app that's been updated in the past two days (roughly when I think this problem began) but it's still a no-go. I've also installed a sensor test app and I find the sensors do work initially on boot, but freeze after 5 seconds or so.
Any ideas of how I might fix this?
Clear system cache.
You update, install or uninstall any apps recently?
I tried clearing the cache but it didn't change anything. I also uninstalled all the apps that had recently updated, restarting the phone each time, but the sensor is still frozen unfortunately.
ppuzzlerr said:
I tried clearing the cache but it didn't change anything. I also uninstalled all the apps that had recently updated, restarting the phone each time, but the sensor is still frozen unfortunately.
Click to expand...
Click to collapse
Factory reset time...
I have the same problem also with Pixel 1 and it happened on the same day (Oct 20)! The difference is I'm on Android 10.
After factory reset and backup restore it works.
After updating all apps, it still works.
After restart once all apps are updated... No work.
R
BHZero said:
I have the same problem also with Pixel 1 and it happened on the same day (Oct 20)! The difference is I'm on Android 10.
After factory reset and backup restore it works.
After updating all apps, it still works.
After restart once all apps are updated... No work.
Click to expand...
Click to collapse
Roll back to factory settings, one by one and find the culprit(s). Sounds like a rogue 3rd party app.
Once I have a device running well I almost never update anything. I'll run on the factory loaded versions for years many times. Result, no issues.
blackhawk said:
R
Roll back to factory settings, one by one and find the culprit(s). Sounds like a rogue 3rd party app.
Once I have a device running well I almost never update anything. I'll run on the factory loaded versions for years many times. Result, no issues.
Click to expand...
Click to collapse
Thanks for the help! How do I do this?
The return to factory settings is in the app under settings.
You can try uninstalling it otherwise.
I don't see that option all the time and you may have to hit uninstall for it to appear.
A forced stop might be enough for troubleshooting.
Typically I use my package disabler for things like this.
So I've done a factory reset with no restore (to keep it clean). Updated every app individually and restarted the device each time.
Updated GOOGLE MAPS. Rebooted.
Presto! All sensors are now locking up and battery starts burning away.
Disabled Google Maps, cleared cache + data, and rebooted. Problem did NOT go away. Now I'm doing one more (hopefully last) restore and will disable Google Maps right away.
Wow... did not expect it to be Maps...
BHZero said:
So I've done a factory reset with no restore (to keep it clean). Updated every app individually and restarted the device each time.
Updated GOOGLE MAPS. Rebooted.
Presto! All sensors are now locking up and battery starts burning away.
Disabled Google Maps, cleared cache + data, and rebooted. Problem did NOT go away. Now I'm doing one more (hopefully last) restore and will disable Google Maps right away.
Wow... did not expect it to be Maps...
Click to expand...
Click to collapse
I'm not, Gmaps updates are a back street abortion.
So it was the update that trashed it?
I always keep gmail and maps on the factory load version. Invariably updates make them less user friendly on a Samsung
I set Playstore settings for auto updates by wifi only.
I always keep wifi disabled, effectively preventing any auto updating. I also firewall block and disable Playstore unless I need it. It's a background pocket hog.
Updates generally cause more harm than good if the app is already running well...
I have the same issue, and after guessing which app was causing the problem I found out it's the Google app. I disabled it and all the sensors started working back and also automatic brightness. Also I tried leaving the beta updates of the Google app and whenever the Google app is active the sensors stops working. Probably Google trying to kill the pixel 1 or a new function conflicting with the sensors
Oh my god! I have the same issue! Stock Android 10.
Sensors work fine on Safe Mode, but on normal mode they sometimes don't work.
Same problem here, since a couple of days ago, some sensors (gyro, light, accelerometer, compas) stop working after a couple of seconds after reboot. I factory reset my pixel, I tried uninstalling GMaps, I tried deactivating Wifi and Bluetooth,... but nothing is working.
Proximity sensor still work though.
gmsalomao2 said:
Oh my god! I have the same issue! Stock Android 10.
Sensors work fine on Safe Mode, but on normal mode they sometimes don't work.
Click to expand...
Click to collapse
Have you tried disabling Google app as mentioned by cristejeda33 above?
I have the same issues, it happens when one or more apps get updated, don't now which one is causing it exactly, but the issue goes away after the next update, and comes back at the next update and so on ..., features like, adaptive brightness, tap to wake, lift to wake, display rotation os and in camera, youtube video rotation....... stopped working and the battery is draining a lot faster. thinking of getting rid of the good old pixel ..
blackhawk said:
Have you tried disabling Google app as mentioned by cristejeda33 above?
Click to expand...
Click to collapse
I stopped the services from the Google app and the sensors started working. And kept on working for some time after that. They keep stopping and coming back.
gmsalomao2 said:
I stopped the services from the Google app and the sensors started working. And kept on working for some time after that. They keep stopping and coming back.
Click to expand...
Click to collapse
Try disabling Google play Services... just a wild guess.
It's a dependency or a parent app of Google App that's maybe causing the trouble. These can be hard to ferret out... play with it.
You could just go shotgun and revert all Google apps to factory load version -if- it wasn't a system wide firmware update that triggered it.
I've experienced this too many times, updates break things.
On my N10+ I lock down all updates, especially firmware. I'm rarely updated anything because it causes trouble. Result is a very fast and stable operating platform with minimum maintenance required. When there is an issue it's much easier to track down as the system is a known and familiar quantity. My current load is over a year and a half old... still running strong.
Wife and I are using OG Pixels and a couple of weeks ago we both noticed massive battery degradation. Then we both realized that auto rotate is extremely slow as are a bunch of sensors. Skymap doesn't track anymore. Both our phones also get extremely hot.
Google brought us here and we see that stopping the Google app makes the sensors work normally again. Lots of issues being reported in the playstore for this app also. Would love to hear if anyone has made any headway working around this or are we screwed until an update comes out?
What's the best way we can report this to Google publicly? And put the link here
All accelerometer, compass, gyroscope and proximity sensors turned off a few days ago on my og pixel and after disabling the google app all the sensors are working again.
I had a look on the play store and the last update for the google app was on the 21st October, which is exactly when it broke.
I disabled google maps first, then the google app, then sensors worked, so i re-enabled the maps app, I then cleared the cache on the google app and re-enabled that too, and all is still working.
Thank you very, very much for finding the cause of this, I was about to factory reset the phone and then have to reload everything which may or may not have worked anyway. Your efforts are much appreciated, long may your technology function correctly.
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