Hello, you can get the GPS to work with the phone in standby?
There 'a registry key to change?
I have a ROM-based T-Mobile 2.10.
Thanks
Your battery would be dead in about 2 hours. Why do you need that?
Just one example ... you're using google maps and want to put away your phone for a minute (inside your pocket or whatever, in order to use both of your hands) ...
you could just turn the screen off and safe battery instead of having to lock it and touch it every once in a while to keep the display from turning off (you may put it in your pocket for more than one minute at times )
if gps is turned off, google maps often needs an awful amount of time to find the satelites ... you could just save precius navigation time by doing this small change.
For my part, I use google maps quite often for maybe ... 20 minutes a day, but having to keep the phone in my hand and touch the display just to stop it from losing all gps connection is quite a bummer ... this small battery drain would definitely be worth the time saving feature of this change - if it is possible.
TL;DR version:
1)Start Google Navigation, pick destination, start driving. Result: Sporatic or no lock and definitely no turn by turn working.
2)Start Google Navigation, pick destination, start GPSTest, start driving. Result: Almost constant lock and turn by turn works astonishingly well.
What gives?
Alright, please read this whole post, try it out, then comment on whether there is something to this or maybe I'm just crazy (a very definitely possibility). I was playing around with the GPS today and tried the Vibrant GPS hardware fix (pulling up the contact so that the GPS antenna is making better contact with the metal back). There wasn't much of a difference, so I decided to take the back off and run the GPS without the metal backing. I found that interestingly enough I was getting a better SNR with the back off than with the back on it was 8/8 at about 25-30 with the back on (using GPSTest) while with the back off it was 8/8 with 30-35.
Now comes the really interesting bit. On my drive home today I decided to see how well I could hold a moving lock. I turned on Google Navigation, pointed to my house, and started driving. Needless to say I was not able to hold a lock for very long. However, if I left the navigation app running and started GPSTest, all of a sudden I was getting the turn by turn voice pretty accurately. I then exited GPSTest and probably 10 seconds later lost my lock again. Open GPSTest, BOOM lock back on and turn by turn working again. Am I just hitting a really lucky coincidence or is GPSTest doing something we're not aware of? Please post here if you can either a) replicate what I'm seeing or b)think I'm blowing smoke cuz you aren't seeing a lick of difference.
smoking blow/10
anyways I'll try it out
comdei said:
smoking blow/10
anyways I'll try it out
Click to expand...
Click to collapse
BTW... this is GPS Test by Chartcross Limited, NOT the one by Mike Lockwood. You're welcome to try both however.
Previous GPS threads have repeatedly documented the positive effect of moving your nav app to the background. Theories on it center around backlight, temperature, or CPU/GPU. My own myTracks tests seem to point towards CPU/GPU. Or, at least, they seemed to rule out temperature or backlight as a factor.
So did you have GPS Test in the foreground during this test? This will pretty consistently give you improved performance over having Navigation up. If you turn the screen OFF altogether, it almost works as well as a real GPS! Check out the difference by recording a few drives in MyTracks -- it's night and day, on my phone at least.
My personal, uninformed theory (guess) is that the CPU/GPU and screen during Navigation are starving the GPS subsystem of power, causing either reception issues or causing the clock to desync and lose the position of the satellites it's tracking.
Ah well, such is life.
Perception 10.2 | SpeedMod K13D | I9000XXJQ1
I noticed this as well with my old setup (phone bought in August 2010 running Cognition & JK4 radio firmware). I got one of the refurbs from the random power off fiasco and GPS seemed to be just as unreliable. I've recently flashed the JL2 radio firmware, and GPS locks on within seconds and stays locked around town - as it should. I think a lot of people's issue would be completely resolved if they played around with radio firmwares...
Ikonomi said:
So did you have GPS Test in the foreground during this test? This will pretty consistently give you improved performance over having Navigation up. If you turn the screen OFF altogether, it almost works as well as a real GPS! Check out the difference by recording a few drives in MyTracks -- it's night and day, on my phone at least.
Click to expand...
Click to collapse
Yeah, GPS Test was in the foreground, navigation in the background. I get the feeling however its more to do with the application than the hardware. I say this because having other apps in the foreground doesn't quite have the same effect for me. Is that the case for everyone else as well?
knyghtryda said:
TL;DR version:
1)Start Google Navigation, pick destination, start driving. Result: Sporatic or no lock and definitely no turn by turn working.
2)Start Google Navigation, pick destination, start GPSTest, start driving. Result: Almost constant lock and turn by turn works astonishingly well.
What gives?
Alright, please read this whole post, try it out, then comment on whether there is something to this or maybe I'm just crazy (a very definitely possibility). I was playing around with the GPS today and tried the Vibrant GPS hardware fix (pulling up the contact so that the GPS antenna is making better contact with the metal back). There wasn't much of a difference, so I decided to take the back off and run the GPS without the metal backing. I found that interestingly enough I was getting a better SNR with the back off than with the back on it was 8/8 at about 25-30 with the back on (using GPSTest) while with the back off it was 8/8 with 30-35.
Now comes the really interesting bit. On my drive home today I decided to see how well I could hold a moving lock. I turned on Google Navigation, pointed to my house, and started driving. Needless to say I was not able to hold a lock for very long. However, if I left the navigation app running and started GPSTest, all of a sudden I was getting the turn by turn voice pretty accurately. I then exited GPSTest and probably 10 seconds later lost my lock again. Open GPSTest, BOOM lock back on and turn by turn working again. Am I just hitting a really lucky coincidence or is GPSTest doing something we're not aware of? Please post here if you can either a) replicate what I'm seeing or b)think I'm blowing smoke cuz you aren't seeing a lick of difference.
Click to expand...
Click to collapse
this worked really well for me. am on andromeda 3. but was getting on locks without staying on continuously. with the approach. gps was spot on.!! a BIG Thanks
I've noticed this for some time when running the GPS Application Test in lbstestmode. Run the GPS test first and then move it to the background and launch your normal GPS program and you'll usually be better off. Needless to say, I'm doing another warranty exchange in hopes of getting one with better GPS hardware soon.
Try this:
Get a mobile hotspot (or someone who has wifi tethering enabled on their phone). Put your phone into flight mode, then turn WIFI on and connect to that mobile hotspot. Fire up navigation, and go for a drive. You'll be amazed at how accurate your GPS is.
That leads me to believe that there is an interference issue in the GSM/GPS antennas. Part of the reason why putting navigation in the background helps improve the GPS performance is because it stops refreshing the map, which means it's not trying to use the GSM radio. But if you fire up Pandora, even with Navigation in the background, the GPS will start going nuts again.
I'm pretty sure AT&T is aware of this, and I even think they have a... well, not a fix, but a way to mitigate the problem.
A friend of mine did a warranty exchange on his Captivate last Monday for a problem with his USB port. The Captivate he got in exchange has been getting much better performance with it's GPS. And since his worked just fine all week, I exchanged mine yesterday. Now, quite often after flashing a new ROM, the GPS will work fine for a day or three. So I'm not going to be convinced mine is working as well just yet. But there are some notable differences from what I've seen before... When I'm tracking my position on Google Maps, my actual position now stays within what the GPS reports as it's error, even when I'm driving around. Previously, my phone might report a 10m error, but my actual position might be 200m or more from where it thought I was. In addition to that, I'm seeing that my phone is locking into more satellites, and holding that lock even as the SNRs drop due to obstructions. And finally, my GPS works just as good while it's in the car dock, whereas before it would only intermittently get enough signal to fix a position. Overall, while my GPS still isn't as good as other phones I've had in the past, it is now actually good enough to use and trust.
I think that AT&T isn't advertising this because it's not something that they can push out over the air or through a Kies update. I'm guessing that either they modified the antennas slightly, or that they installed a new firmware to the GPS chip (at a lower level than the driver)... or maybe both.
Either way, my friend's GPS has been working great all week long, and mine appears to be doing so as well. I'll not say that it's permanently fixed yet, but I'm cautiously optimistic. We'll see how it's doing after another few days go by.
UPDATE 3/28:
Two more days of testing have passed. So far, the GPS is holding up nicely. The only issues are with the car dock. When the phone is in the car dock, the GPS will occasionally drift 5~10 meters off of my position. This doesn't really surprise me, as the electronics in the car dock are right up against the GPS antenna, and simply putting the phone in the dock will drop the reported SNRs by more than 25% - usually a lot more.
Still, even with the car dock, the GPS is perfectly usable. And without the car dock, the GPS is now exactly what it should have been from the get-go.
I've also found that if I run either gps status or gps test to get the fix, then start whatever app I need to use, the performance is much better. Recently I just use lbs test to get the fix, then proceed with whatever app i need to use. Seems to work better, as lbs test continues to work in the background
i have seen this in the past but trying to prove that it is not random has been a problem as i cant repeat the results.
also i dont thing i have ever observed the phenomenon while using control plane mode.
maybe another coincidence, i cant tell but i have been using the control plane version of da_g's fix for a couple months now in combination with the jl3 modem and have gps that many smart phones would envy. i find jl3 to have the most stable positioning and tracking, less blue circles ect. i also find agps settings to hinder tracking. i only set agps mode to standalone. not sure how supl works or if controlplane supl setting is actually doing anything because i was under the impression that supl was part of agps but it is a combination that started working for me and i am sticking to it.
I'm running 4.2.2 Jellybean on the new Droid Ultra. Motorola Smartactions are now gone and I can no longer have GPS come on automatically when connected to my car's bluetooth.
It looks like the only option now is to have my GPS constantly on. I wanted to know if Google Now constantly uses my GPS location and will drain my battery.
I've tweaked the settings on my other apps not to use GPS based location. I don't see this setting on Google Now.
Sent from my XT1080 using Tapatalk 4
For some reason. After enabling google now and with that, enabling google to use anonomys location data, Maps seems to be running in the background sometimes. Google analatics is also a culprit, it's running in the background too.
Google now doesn't use your location data(gps) 24/7, but it does tend to gather info based on your location now and then.
It does this so it can suggest more relevant location info via Google Now.
Not to good for battery I've experienced.
Google Now only uses GPS when you activate it.
Sent from my YP-G1 using xda app-developers app
it uses it as needed, but not every instant
Google Now definitely does *not* constantly use GPS. Right now my phone shows 4 minutes GPS use in the last 4 hours (a short walk home from work).
Google is keenly aware of the tradeoff between location accuracy and power. That's why they created the new Location APIs: see developer.android.com/google/play-services/location.html (sorry no links).
The idea is to use the least power-consuming sensor to get the desired information. For example, the phone can use the accelerometer (which takes almost no power) to see if the phone's moving. If it's not, then there's no need to update the location. If it can figure out roughly where you are from WiFi (at Starbucks again!) or the cell network then it may not need GPS. Even when the GPS is used, it needs fewer readings when you're walking than when you're driving.
Between readings, Android will try to put the GPS in a low power idle state to avoid a 2 minute cold start. Whether it can or not depends on the phone's chipset and the manufacturer's firmware.
Google Now wants to track your location so it can guess where you're going. I think it's cute, but then it doesn't use much power on my Galaxy Nexus.
The power-vampire is more likely to be a 3rd party application. As an Android developer, I know it's way way easier to just fire up the GPS when the app starts, or even before it starts, and leave it running at high speed (i.e. high power) even when I'm not using it. It takes much more effort to use GPS sparingly and to throttle it as a appropriate.
Suggestion: Leave GPS turned on for a day, and check the power usage under Settings / Battery. Then turn it off for a day and compare. You can tap the Google Services line for details, including GPS usage time.
ehartwell said:
Google Now definitely does *not* constantly use GPS. Right now my phone shows 4 minutes GPS use in the last 4 hours (a short walk home from work).
Google is keenly aware of the tradeoff between location accuracy and power. That's why they created the new Location APIs: see developer.android.com/google/play-services/location.html (sorry no links).
The idea is to use the least power-consuming sensor to get the desired information. For example, the phone can use the accelerometer (which takes almost no power) to see if the phone's moving. If it's not, then there's no need to update the location. If it can figure out roughly where you are from WiFi (at Starbucks again!) or the cell network then it may not need GPS. Even when the GPS is used, it needs fewer readings when you're walking than when you're driving.
Between readings, Android will try to put the GPS in a low power idle state to avoid a 2 minute cold start. Whether it can or not depends on the phone's chipset and the manufacturer's firmware.
Google Now wants to track your location so it can guess where you're going. I think it's cute, but then it doesn't use much power on my Galaxy Nexus.
The power-vampire is more likely to be a 3rd party application. As an Android developer, I know it's way way easier to just fire up the GPS when the app starts, or even before it starts, and leave it running at high speed (i.e. high power) even when I'm not using it. It takes much more effort to use GPS sparingly and to throttle it as a appropriate.
Suggestion: Leave GPS turned on for a day, and check the power usage under Settings / Battery. Then turn it off for a day and compare. You can tap the Google Services line for details, including GPS usage time.
Click to expand...
Click to collapse
Very informative. Thank you! I'm actually using the MAXX version of the new Droid Ultra. Has the 3,500 mAh battery. This phone lasts a LONG time.
Sent from my Droid MAXX
I just noticed under Battery usage there is a Battery Saver on/off toggle. How does that work?
Sent from my Droid MAXX
I've been leaving the gps constantly on without using navigation for one day. At the end of 24 hours the gps had only been on for a total of 3 minutes 27 seconds. From now on I'm leaving the gps on and never turning it off. No worries on draining the battery.
Sent from my Droid MAXX
Great info in this thread guys. Actually came to this forum to ask a couple questions, and this thread already answered one!
Hi guys, maybe you could help me out. I was thinking whether I could use this phone when riding a bike (on normal terrain, 90% roads) to track my position (via MyTracks, Strava etc.). Does anyone know how the battery behaves (I would like to see the map on the phone all the time) in such a regime? Or, could you make a test for me? No WiFi, data or anything, just GPS and position recording.
Thanks a lot!
Just gonna give my two cents here.
I think you can theoretically and I'm saying just that because you can test GPS from the service tests. But from exp it is significantly slower to get GPS coordinates than with data or WiFi. Now regarding battery if you have the location service on or at high accuracy it will drain the battery more than with the service off or limited to a number of apps.
Thanks for the tips. However, I would like to hear real life experiences before I decide whether to buy it or not because I am unable to test it.
I have always gps on. When I charged battery to 100%. Lock phone and go sleep after 9 hours still 100%. Only gps taking very very very less battery. You shouldn'd see different between turn on and turn off gps.
Sent from my D6603 using XDA Free mobile app
Thanks a lot, but could you repeat the test during the day? Turn google maps e.g. on (even better mytracks + recording) and just go around normally. I had an idea to keep the screen on all the time so that I can see the map whenever I want - if by any chance you could do that as well, well... buy you a beer if the road ever takes you close by .
Hi all
I've had the Pixel 3 since the release and, since over half that time now, my Pixel 3 exhibits terrible lag and kills any app that is not running in the foreground when charging.
At this point the lag when charging from a wall outlet is secondary. What is especially annoying is background apps getting killed when driving because that is typically a situation where I will need mulitple apps running, none being in the foreground (screen off). Android Auto is basically unusable since it requires the phone to be plugged in (and therefore charging) and it will kill everything (waze, spotify, android auto itself) after a few seconds of use. I have noticed the phone will not kill an app that is running in the foreground so I could keep Android Auto alive but other apps will still get killed, rendering Auto useless.
I am therefore forced to keep the phone unplugged, using up the battery, and connect to the car via bluetooth for music and navigation. But when my battery has drained too much (inevitable on longer drives), I have to choose a single app that I want to run on my phone and keep the screen on at all times to keep it alive (e.g. if I need Waze on for navigation and alerts, I have a choice between the radio or silence for entertainment).
There are a couple other issues linked to charging like the phone getting laggy, sometimes to the extreme, when plugged in to charge (with the official charger or otherwise) or the phone charging very slowly (10-15% over 2 hours) on the official Pixel stand. I have a feeling they are all related but, if they aren't, then the issue described above is for me the most pressing.
Gathering from somewhat similar complaints found online (although I haven't found anyone complaining about this specific issue), it sounds like these issues are related to the phone throttling performance to reduce overheating and optimize charging. But when I tried killing a bunch of apps manually (swiping up on recently used apps) and keeping the phone very cool (removing phone cover and blasting very cold car AC straight onto the phone), I saw no improvements whatsoever.
Thank you