[Q] GPS won't lock if rear camera is in use, otherwise GPS works great - Verizon Samsung Galaxy S III

I've searched high and low, but haven't been able to find a solution to this issue, hopefully somebody here has a good answer for this one.
I'm trying to run Waze in the foreground and DailyRoads Voyager in the background while driving, but any time DRV is running, Waze can't get a GPS lock. If I shut down DRV, I get a GPS lock quickly and without issue. The issue doesn't appear to be app related, as I can generate the same symptoms using other camera apps and 'gps status'.
I've seen a few references on other forums where people with S3's are having the same issue, but I haven't found a resolution yet. I'm running the current OTA build, never rooted/tweaked.
Any ideas?

PDXKris said:
I've searched high and low, but haven't been able to find a solution to this issue, hopefully somebody here has a good answer for this one.
I'm trying to run Waze in the foreground and DailyRoads Voyager in the background while driving, but any time DRV is running, Waze can't get a GPS lock. If I shut down DRV, I get a GPS lock quickly and without issue. The issue doesn't appear to be app related, as I can generate the same symptoms using other camera apps and 'gps status'.
I've seen a few references on other forums where people with S3's are having the same issue, but I haven't found a resolution yet. I'm running the current OTA build, never rooted/tweaked.
Any ideas?
Click to expand...
Click to collapse
This is a seriously random suggestion, but did you try turning off geotagging in the main camera app?

aooga said:
This is a seriously random suggestion, but did you try turning off geotagging in the main camera app?
Click to expand...
Click to collapse
I just double-checked, and GPS tagging was already turned off in the stock camera app. Thanks for the idea though!

Can anybody else confirm if they see this behavior as well?
Since my first post I've tried rooted OTA, ran numerous CM10.1 builds (doing full wipes in between), leanKernel, testing along the way all without any real success. It seems a little hit and miss, on occasion (maybe 10% of the time) it seems to work, but in those times GPS still takes 5-10min to get a lock usually has less accuracy than when using GPS apps alone w/o the camera on.
When the camera isn't in use, I typically get a GPS lock in <30 sec (sometimes in just a few seconds).

Related

Is your camera locking up (No pre-view picture)?

Is your camera locking up (No pre-view picture)?
When I select the camera icon, I see the camera menu in the lower part of the screen and I can even take pictures, however I see a black image instead of the pre-view photo on the screen. This issue goes away by soft resetting the phone; however it usually comes back after few days and the only way to see the pre-view image is by resetting the phone. The strange part is that the camera can actually take pictures but I cannot see the photo before taking it. Have you heard of this issue? The phone works just fine otherwise and I like it a lot.
Thanks,
z_zk_z said:
Is your camera locking up (No pre-view picture)?
When I select the camera icon, I see the camera menu in the lower part of the screen and I can even take pictures, however I see a black image instead of the pre-view photo on the screen. This issue goes away by soft resetting the phone; however it usually comes back after few days and the only way to see the pre-view image is by resetting the phone. The strange part is that the camera can actually take pictures but I cannot see the photo before taking it. Have you heard of this issue? The phone works just fine otherwise and I like it a lot.
Thanks,
Click to expand...
Click to collapse
Are you running stock?
I can't speak for whatever potential issues might be caused by any of the custom roms in circulation, but on a stock phone, obviously it shouldn't be doing that.
I can't imagine what hardware issue would produce intermittent preview-ability that's temporarily remedied by a soft reset, yet still manages to capture the photo itself, but there's a first time for everything.
Sent from my Inspire using XDA Premium
My stock camera application (and Camera360) and camcorder applications both exhibit this behavior. A soft-reset of the device usually temporarily resolves the issue (i.e. allows me to use the camera for a short period of time). However, after my phone has been on for a while any app that uses the camera just locks up (eventually have to force close or soft-reset).
It is rather annoying. The only information I found seems to indicate that there may be an issue with the API within FroYo itself. Hopefully when we get the update to GingerBread the problem will resolve itself.
I also read something else about something to do with an LED widget that caused someone problems but I'm not using any LED widgets, so I'm not sure what that's referring to.
Hopefully there's a fix out there somewhere or we get the 2.3 update soonish.
ryguy25 said:
My stock camera application (and Camera360) and camcorder applications both exhibit this behavior. A soft-reset of the device usually temporarily resolves the issue (i.e. allows me to use the camera for a short period of time). However, after my phone has been on for a while any app that uses the camera just locks up (eventually have to force close or soft-reset).
It is rather annoying. The only information I found seems to indicate that there may be an issue with the API within FroYo itself. Hopefully when we get the update to GingerBread the problem will resolve itself.
I also read something else about something to do with an LED widget that caused someone problems but I'm not using any LED widgets, so I'm not sure what that's referring to.
Hopefully there's a fix out there somewhere or we get the 2.3 update soonish.
Click to expand...
Click to collapse
Hmmm...
This is the first thread I've come across that brings up this problem.
My stock (rooted) phone, my mom's stock phone, and my dad's stock phone have never encountered an issue like this, but then again, maybe we were the three lucky ones...
EDIT:
That's not to say you guys are crazy... maybe we just haven't had the right combo of circumstances to expose the problem/bug on our phones.
Now that I think more about it, I did have an issue when I ran barcode scanner once, about a month ago. That of course uses the camera. As soon as it identified the barcode, and I pressed the 'search web' button, it just froze (image still visible), but the back key/screen input was unresponsive. The only thing that worked was the home button, which, instead of going to the home screen, displayed the screen you see when you are about to end a call with someone on your phone. Thing is, I hadn't made a single call that day. That screen was also unresponsive, but when I pushed the home button again, it finally got to the home screen.
I then went into manage apps in settings and FC'd barcode scanner and the dialer/phone, just in case. I even uninstalled barcode scanner because I thought it might have a phone-specific bug that I didn't want to deal with.
I don't know if there's any correlation between the yours/OP's issue, but it sounds like it's ****ed up in a similar way. FWIW.
Sent from my Inspire using XDA Premium
I think I managed to fix mine by wiping my dalvik cache. On the downside, my current drain used to be around 5 when my phone was in standby and now it is around 45. On the upside, I haven't had a problem with the camera or camcorder since then.
Sent from my Desire HD using XDA App
Mine ended up being a hardware issue. Phone was exchanged with at&t. Haven't had an issue with the camera since.
Just wanted to update for the OP.
Sent from my Inspire using XDA App

GPS application crashing hangs the GPS sensor

Hello
I have a HTC HD2 flashed with ParanoidAndroid 1.5b. I was trying to run the Sygic GPS navigator but it crashes after a while with ICS. This is not a problem with the ROM but with the application. So far so good. However, I found out that since the application opened the GPS to try to get a fix, when it crashed it left the GPS "on" (although the icon on the status bar disappeared after a while). I tried another GPS navigation program but it couldn't get a fix. I thought it was the GPS configuration, so I changed it to reflect my region (Europe, Greece). But to no avail. Whatever I tried, I couldn't get a fix. I rebooted the device and tried GPS status, it got a fix after a minute or so. If I run Sygic (which crashes) again, it is impossible to get a GPS fix afterwards. If an application that uses the GPS crashes while the GPS is on, it leaves the sensor working. However, there is no indication that there is a problem, as the icon disappears after a while, and gets back on when another app tries to use the sensor. It just can't get a fix. What's more, the battery starts to drain after that (easy to spot with Current Widget, since the draw goes from 6-7mAh to 105-107mAh)
Switching the GPS on and off (from the notification drawer) does not fix the problem. The only solution is to reset the device.
My question (finally) is: is there another solution to "resetting" the sensor to its original (after the boot) state?
Best regards
George

[Q] Nexus 5 sensors stop working at random no output until restart

Hi all, I'm a little worried as I love my Nexus 5 coming from a Desire Z but I'd say from as little as 30 mins to up to 8 hours or so I have to reset my phone as all the sensors stop working. Installing a sensor monitoring app it says the output is blank on them all.
Screen rotation, compass, maps and the barometer all stop working.
Anyone else getting this?
I don't think its hardware as a reboot fixes it for a while.
Thanks
Edit:
It also seems to have resolved itself after a while, when I installed a step counting app I checked and the sensors and they were all working again.
A bit odd...
I am having the same problem. Which step counting app did you install to keep it working?
brandnamebob said:
I am having the same problem. Which step counting app did you install to keep it working?
Click to expand...
Click to collapse
Hi
It was an app called Moves - but it ate an absolute load of battery life so I uninstalled it rather quick, it was also pretty crap.
I have this issue very rarely now, I just wish I knew what the problem was caused by.
Have you in the past enabled the ART library?
LaurenceGough said:
Hi
It was an app called Moves - but it ate an absolute load of battery life so I uninstalled it rather quick, it was also pretty crap.
I have this issue very rarely now, I just wish I knew what the problem was caused by.
Have you in the past enabled the ART library?
Click to expand...
Click to collapse
I have not used the ART library yet.
The app I noticed the problem in is 'Reddit is Fun' but It is most likely a background app that is causing the issues.
I uninstalled a bunch of them, including Elixer and PressureNet, just to see if I continue to have the issue.
Ahh OK. I installed an app called barometer+ so I could make use of the pressure sensor. I think it has background logging as well. Perhaps it is this causing it.
I'm having the same issue. Right now I'm just restarting my phone whenever I notice it.
smalovic said:
I'm having the same issue. Right now I'm just restarting my phone whenever I notice it.
Click to expand...
Click to collapse
smalovic do you have any weather apps or pressure sensor apps (or anything like that)?
Have you tried the ART libary at all?
Thanks
LaurenceGough said:
smalovic do you have any weather apps or pressure sensor apps (or anything like that)?
Have you tried the ART libary at all?
Thanks
Click to expand...
Click to collapse
I have PressureNet installed. I switched to the ART library but I'm getting the same problem.
Hi all,
Same issue here. I'm using syspressure app for background pressure logging. I switched to a every 5 mins sample rate instead of 1. Now I will try to see if it's happening again.
Sent from my Nexus 5 using xda app-developers app
My Barometer+ app was set to hour updates...
I guess we can all relate to a pressure app, probably the cause...
Setting SyPressure sample rate to 5 minutes has done nothing.
After about 30 mins of standby all sensors stopped working again.
Now I have disabled the widget of SyPressure that means no background logging anymore.
I will update the status.
---------- Post added at 09:16 AM ---------- Previous post was at 08:54 AM ----------
UPDATE:
After about 30 mins of standby all sensors still WORKING.
Now I will try to wait much more than 30 minutes
I will update!!
UPDATE 2:
After more than 1 hour, sensors still OK!
I will try overnight and check it out.
Anyway also battery perfomence seems to be better, 1 hour ago charge was at 33% and now is still alt 33%
PS. Sorry for my english
I uninstalled PressureNet yesterday and left it overnight. Everything's still working this morning!
It must be some glitch with the barometer apps.
Same problem here. I also have sypressure on my phone. I've uninstalled sypressure a day ago, and for now everything work fine
I have the same infuriating issue.
My device: Nexus 5
Build: KRT16M
Unlocked, TWRP Recovery, Root, Chainfire's SuperSU
I also have "pressureNET" app installed for logging pressure readings.
After reboot all sensors work fine. Installed app "Sensor Sense" confirms this. Then randomly at some point in time, 2 or 5 or 8 hours later most sensors stop working and it is always the same ones.
Battery, Location, Light, and Proximity all continue to work fine indefinitely.
Pressure, Accelerometer, Gravity, Gyroscope, Linear Acceleration, Rotation, and Magnetic Field all fail and no apps can make a call on these sensors as part of their function.
This is most readily and frequently apparent in (i) the "Gallery" in which rotating the screen no longer results in auto-rotation of images, (ii) orientation of recorded images and videos with "Camera" in which the capture is locked into one orientation and videos shot in landscape (for example) end up with an on-their-side portrait orientation when viewed, and (iii) YouTube videos can no longer orientate when playing and the screen is changed to a different orientation e.g. load video in portrait mode, flip horizontal, and video no change or adaptation occurs, (iv) going into a PhotoSphere results in a black screen of nothing, (v) "Compass" doesn't work, (vi) "Skymap" doesn't work, etc. etc.
Would love to see a resolution to this issue; this is the first forum or instance of discussing the problem on the Web that I have found.
Robooting the device resets everything and all sensors (and apps) work fine as normal.
markbruce said:
My device: Nexus 5
Build: KRT16M
Unlocked, TWRP Recovery, Root, Chainfire's SuperSU
I also have "pressureNET" app installed for logging pressure readings.
After reboot all sensors work fine. Installed app "Sensor Sense" confirms this. Then randomly at some point in time, 2 or 5 or 8 hours later most sensors stop working and it is always the same ones.
Battery, Location, Light, and Proximity all continue to work fine indefinitely.
Pressure, Accelerometer, Gravity, Gyroscope, Linear Acceleration, Rotation, and Magnetic Field all fail and no apps can make a call on these sensors as part of their function.
This is most readily and frequently apparent in (i) the "Gallery" in which rotating the screen no longer results in auto-rotation of images, (ii) orientation of recorded images and videos with "Camera" in which the capture is locked into one orientation and videos shot in landscape (for example) end up with an on-their-side portrait orientation when viewed, and (iii) YouTube videos can no longer orientate when playing and the screen is changed to a different orientation e.g. load video in portrait mode, flip horizontal, and video no change or adaptation occurs, (iv) going into a PhotoSphere results in a black screen of nothing, (v) "Compass" doesn't work, (vi) "Skymap" doesn't work, etc. etc.
Would love to see a resolution to this issue; this is the first forum or instance of discussing the problem on the Web that I have found.
Click to expand...
Click to collapse
Uninstall pressureNET, reboot, and you should be all set.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Resolved
I confirm that "pressureNET" was the app causing the other sensors to crash.
50 hours after uninstalling and rebooting there has been no recurrence of the problem; all sensors and the handset have worked flawlessly throughout.
markbruce said:
I confirm that "pressureNET" was the app causing the other sensors to crash.
50 hours after uninstalling and rebooting there has been no recurrence of the problem; all sensors and the handset have worked flawlessly throughout.
Click to expand...
Click to collapse
Reading the other replies, it seems as though any barometer app causes the issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app
smalovic said:
Reading the other replies, it seems as though any barometer app causes the issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Damn, I'm having the same issue intermittently. Might have to uninstall the app until they get this sorted out, which is a shame because the sample size for reading in my region is probably very small.
Looks like the pressureNET dev is working on a fix. He posted on Reddit: http://www.reddit.com/r/Android/comments/1qzg0n/nexus_5_sensor_issues_whats_going_on/
Sent from my Nexus 5 using XDA Premium 4 mobile app

Compass issues after upgrading to Lollipop

Hey guys,
New smartphone user here. I've had Nexus 5 for a few months now.
Lollipop is really well made and the new visuals are great. Everything seems to be working well so far, except for my compass. It does not work either in my Compass app or in Google Maps. I've seen a few threads where people lost some of their sensors, so I downloaded Sensor Box to see what it would find.
The magnetic sensor works properly, but there isn't a "compass" sensor in it. Are they different or is the compass position determined using the magnetic sensor? The GPS Essentials compass does work, but it feels very slow and it's all over the place.
Additionally, when I start my Compass app, it does not activate Location like GPS Essentials would, although, it fetches my current address properly on top of the compass itself. (see attachment)
Could it be just that the compass works in a different way in Lollipop and apps have to be updated for it? I'm completely lost. Any help would be appreciated, guys.
Cheers,
I am experiencing the same issue.
I'm also having this issue, only app I did get it to work with was Compass 360. But I really only would need it for Google Maps, so this is still very annoying.
Did anyone come up with a solution, or at least an explanation yet?
Or does anyone know where to file a bug report about such an issue?
Are you sure the APIs just didn't change with Lollipop? If one app works and not another, it may not be a Lollipop bug.
Kompass is dead on for me, no issues whatsoever. Try moving the phone in a horizontal figure 8 to calibrate the kompass and watch for electrical/magnetic interferences.

Bug in nexus 5 accelerometer?

Is there a bug in the nexus 5 accelerometer?
I've been trying various pedometer apps. None seem particularly accurate but what bothers me is how the built in accelerometer they are based on seems to abruptly stop working every now and then and the steps stop counting until I reboot. Happens simultaneously to all 2-3 apps I have installed which suggests the accelerometer is the common factor.
Is this a known bug? Is there a way to fix it or test it?
Try downloading a game that relies on the accelerometer and see how it works, is everything works fine in the game, then I'd say it's not because of your accelerometer. If it is the accelerometer, try recalibrating it. Old HTC phones had a built in tool for that iirc, but for now, there must be some apps on Play Store which are capable of doing just that.
You are not alone...My accelerometer cuts out in my sleep tracking app intermittently since the May update for 6.0.1 on a nexus 5.
maybeme2 said:
Is there a bug in the nexus 5 accelerometer?
I've been trying various pedometer apps. None seem particularly accurate but what bothers me is how the built in accelerometer they are based on seems to abruptly stop working every now and then and the steps stop counting until I reboot. Happens simultaneously to all 2-3 apps I have installed which suggests the accelerometer is the common factor.
Is this a known bug? Is there a way to fix it or test it?
Click to expand...
Click to collapse

Categories

Resources