Related
Apologies in advance for creating yet another GPS thread, but I'm just too paranoid that the people I want to see this are probably ignoring all the other ones (I know I am, mostly).
Back in my WM days, I had an app on my Omnia II that could load the GPS cache with fresh almanac and ephemeris data. This would result in a near instantaneous lock after refreshing the cache.
It wasn't necessary to work around a bug or anything -- rather, it was for paranoid types that didn't want to enable aGPS.
Is there anything like this for Android, and that works on the Epic? While the stale cache bug pisses me off as much as anyone, this would be a far more convenient workaround than the Cold Start (which I'm using), and less finicky (I have to force roam at my home due to near non-existent Sprint signal, and the Cold Start workaround fails in this circumstance).
dwallersv said:
Apologies in advance for creating yet another GPS thread, but I'm just too paranoid that the people I want to see this are probably ignore all the other ones (I know I am, mostly).
Back in my WM days, I had an app on my Omnia II that could load the GPS cache with fresh almanac and ephemeris data. This would result in a near instantaneous lock after refreshing the cache.
It wasn't necessary to work around a bug or anything -- rather, it was for paranoid types that didn't want to enable aGPS.
Is there anything like this for Android, and that works on the Epic? While the stale cache bug pisses me off as much as anyone, this would be a far more convenient workaround than the Cold Start (which I'm using), and less finicky (I have to force roam at my home due to near non-existent Sprint signal, and the Cold Start workaround fails in this circumstance).
Click to expand...
Click to collapse
first you would have to put the device in standalone, through *#1472365+/position mode/operating mode/standalone. Otherwise you will get data calls via 3g (vs ms (device) based).
this like, cold start, has situational disadvantages, in that if you could get manual population of xtra data (assistance) cache to work, when you did not you could be waiting some time.
Next come to manual populating cache and ephemeris from a non sprint (agps) and non satellite (standalone gps) source. Since developers cannot get standard android programs such as gps status to clear the cache (manually or through standard xtra data mechanisms), it seems Samsungs cache systems, at least in the cdma versions is not standard.
So I would like to hear of any ideas as well.
aero1 said:
Next come to manual populating cache and ephemeris from a non sprint (agps) and non satellite (standalone gps) source. Since developers cannot get standard android programs such as gps status to clear the cache (manually or through standard xtra data mechanisms), it seems Samsungs cache systems, at least in the cdma versions is not standard.
Click to expand...
Click to collapse
I used to think that the GPS Status refresh just wasn't working, and I know you have talked to its developer about his difficult experience. But lately I have been careful to turn off 4G and WiFi (thus forcing 3G or even 1X standards) before starting GPS Status and it seems to work. But if I try GPS Status first, forgetting to stop 4G first, it seems like I can't recover from that by turning it off later. The botched refresh seemingly prevents a good refresh. This is similar to my experience with 4G when just using Cold Start alone and starting the GPS. So I wonder if there is some 4G problem specific to the Epic, which complicates the underlying cache bug. I doubt that it is a CDMA issue, because the refresh is done over the IP network. And there are all those anecdotal reports from users who, without knowing how, are keeping their GPS cache from becoming corrupt.
[EDIT: As I think about it, I still have been running Cold Start all along. So perhaps it is the Cold Start voodoo that is working, not the GPS Status refresh. I'll try resetting to factory stock and then try GPS Status again.]
As for XTRA, it looks like that feature it was planned or semi-developed but not finished. Or maybe it is just broken. There is a whole menu system within the UI of the GPSSetup utility to control XTRA, seemingly allowing XTRA refresh to be triggered manually or automatically on a schedule. But those menus don't seem to do anything, and even if you change the settings there your change will not survive a reboot.
Bummer.
The CS workaround works for me, but I have to remember to
Use Roam Control to switch to Home Only when I'm at home (otherwise I can't be sure Automatic will bind to Sprint's network and towers)
Turn off wifi (which, of course, I'm using 100% when at home to get decent data throughput)
Turn on GPS
Launch app I want to use
It would be so much better to just punch a shortcut on the screen, then run the app I want. All-too-often I forget one of those conditional steps above, and then run into the "can't get a lock until my "children's children have children" fiasco.
All I need is for the RC dev to add what we need to control it from tasker -- then I can create a shortcut to fire up Google Maps, Navigator, and anything else that uses GPS that automates all those steps.
boomerbubba said:
I used to think that the GPS Status refresh just wasn't working, and I know you have talked to its developer about his difficult experience. But lately I have been careful to turn off 4G and WiFi (thus forcing 3G or even 1X standards) before starting GPS Status and it seems to work. But if I try GPS Status first, forgetting to stop 4G first, it seems like I can't recover from that by turning it off later. The botched refresh seemingly prevents a good refresh. This is similar to my experience with 4G when just using Cold Start alone and starting the GPS. So I wonder if there is some 4G problem specific to the Epic, which complicates the underlying cache bug. I doubt that it is a CDMA issue, because the refresh is done over the IP network. And there are all those anecdotal reports from users who, without knowing how, are keeping their GPS cache from becoming corrupt.
[EDIT: As I think about it, I still have been running Cold Start all along. So perhaps it is the Cold Start voodoo that is working, not the GPS Status refresh. I'll try resetting to factory stock and then try GPS Status again.]
Click to expand...
Click to collapse
Alas, I did rerun that test of GPS Status with Cold Start off. No joy.
I reset the startup mode to the factory default of Hot Start and waited a couple of days to let the cache go sour. Then I opened GPS Status, which is set to refresh the cache itself automatically. GPS Status then seemed to think it was using multiple satellites (7 green in the tiny histogram), but the GPS would never lock. I closed GPS Status and opened GPS Test, which seemed to use only 3 satellites with no lock. I was using 3G data throughout this test.
I reset to Cold Start and rebooted. GPS Test opened with multiple satellites and a good lock.
So I now believe, once again, that GPS Status alone is not a viable workaround for the Epic's GPS cache bug. I have reverted to using the Cold Start workaround routinely.
Just an observation. This probably belongs in the development thread, but I don't have 10 posts yet.
I installed Kiss 2.2 kernal after installing ICS Passion R13.
After a reboot, I got a quick lock. GPS locked ok after periods of deep sleep over the course of two days.
Then I turned off GPS, which is a normal battery-saving move. It seems that if GPS is turned off (via the notification bar) and later turned back on after deep sleep, GPS does not work. GPSTest and GPS Status could see or lock on any satellites.
Second experiment was to reboot with GPS enabled indoors, thus not locking onto satellites. After deep sleep, the GPS was able to see and lock in about a minute.
It seems that the GPS will work after deep sleep, but only if the GPS is left enabled. I would be curious to know whether others see this pattern.
Have you tried build.prop modification?
Try it out to see if it helps.
In my case, I always managed to make my GPS lock every time (deep sleep or bad dream sleep lolz)
dougc405 said:
Just an observation. This probably belongs in the development thread, but I don't have 10 posts yet.
I installed Kiss 2.2 kernal after installing ICS Passion R13.
After a reboot, I got a quick lock. GPS locked ok after periods of deep sleep over the course of two days.
Then I turned off GPS, which is a normal battery-saving move. It seems that if GPS is turned off (via the notification bar) and later turned back on after deep sleep, GPS does not work. GPSTest and GPS Status could see or lock on any satellites.
Second experiment was to reboot with GPS enabled indoors, thus not locking onto satellites. After deep sleep, the GPS was able to see and lock in about a minute.
It seems that the GPS will work after deep sleep, but only if the GPS is left enabled. I would be curious to know whether others see this pattern.
Click to expand...
Click to collapse
I assume that you are talking about this thread?
http://forum.xda-developers.com/showthread.php?t=1447925
I have not tried this. Some of the keys you list don't exist in my build.prop. Is that ok? Should I add them? I will try this, but have to wait until I am near my computer in case something goes wrong.
It also appears that the GPS stops tracking as soon as the phone sleeps. This is not an issue when using in car mode because the phone does not sleep, but Google Tracks, which I use used while hiking, cycling, etc., does sleep (or at least shuts of the display) while tracking. I tried Google Tracks and it seemed to need to reacquire satellites when waking up the phone. I did not walk far enough to see the effect of that in the recorded track, but I assume that it was not tracking while asleep.
I also noticed the same effect when using GPS Status and GPS Test. If the display shut off, the apps had zero visible satellites when display was powered back on.
Yes, that's the post I was talking about.
If the line(s) is/are missing, just add them at the bottom for your convenience in case it does not work.
I don't want to say anything regarding the phone is having a good sleep or having a bad dream (lolz) because I never bothered to checkup on my phone. All I know is that when I need to use my GPS, I just poke my phone with my crooked finger to unlock, select the 2G Only checkbox, select the GPS Satellite checkbox, launch the Google Maps, type the destination address. (run on sentence lolz)
dougc405 said:
I assume that you are talking about this thread?
http://forum.xda-developers.com/showthread.php?t=1447925
I have not tried this. Some of the keys you list don't exist in my build.prop. Is that ok? Should I add them? I will try this, but have to wait until I am near my computer in case something goes wrong.
It also appears that the GPS stops tracking as soon as the phone sleeps. This is not an issue when using in car mode because the phone does not sleep, but Google Tracks, which I use used while hiking, cycling, etc., does sleep (or at least shuts of the display) while tracking. I tried Google Tracks and it seemed to need to reacquire satellites when waking up the phone. I did not walk far enough to see the effect of that in the recorded track, but I assume that it was not tracking while asleep.
I also noticed the same effect when using GPS Status and GPS Test. If the display shut off, the apps had zero visible satellites when display was powered back on.
Click to expand...
Click to collapse
The changes to build.prop and the GPS settings in AngryGPS made getting a fix much quicker and more reliable (<30 seconds from cold start). Thanks.
I also had to remove Weatherbug Elite. It has some wierd interaction with the GPS even when all location services are disable in the app. It ssems that it won't let the GPSLocationProvider shut down when the GPS is turned off. BetterBatteryStats showed wakelocks and the CPU could not go into deep sleep. At that point, reenabling GPS had no effect and GPS could not see or lock onto any satellites. Only a reboot cured it. Even if no widget is set up, Weatherbug still fires up, probably because of the Background update feature. I had to completely remove the app to prevent this interference.
Only one more problem and it is preventable. If GPS is on AND phone is plugged in with USB AND I run PowerAmp music player, the CPU run solid at 1000 mhz. Only shutting down PowerAmp, turning off the GPS, and unplugging/replugging the USB cable restore normal operation (lower CPU speeds, sleep). Merely unplugging USB does allow the CPU to run normal, but it pops right back up to 1000 when plugged in again. Wierd.
Any other leads?
Vibrant from aug 2010, made the changes but after a sleep the changes to the GPS settings and the libgps.so being added to /system/lib hasn't seemed to have made a difference. After a deep sleep, the gps seems to be dead. "Searching for GPS" appears in the status drawer, and otherwise it's all dead.
What can I do to provide better debugging feedback about this. Does anyone have e.g. a debugging or interposition library to help figure out where this is freezing?
Heck, does anyone have the source to the various GPS libraries being used here so that we can compare what works to what doesn't work for various people?
*edit
I'm completely floored. My GPS came back to life after I got down the elevator leaving work after I posed this. I'm still curious about the source to libgps.so, and I'm honestly not sure it can play a part here since it's not replacing a library in my current /system/lib. If I get some time I may see what symbols are available in it and what library it may/may not be replacing.
I suspect that the change of the supplementary (that's what supl stands for, right?) data and GPS settings have as much to do with this as well. I may try to revert the gps library changes and see if it still works with just the changes made via angrygps. I do know that the build.prop changes did absolutely zero by themselves.
Hi everybody.
I have SM-N9005 phone, currently running Temasek V16.0.
My GPS usually works fine, however sometimes it finds the satellites and uses them but doesn't get GPS fix for a long time (actually - never, as far as my patience go, which was about 15 minutes). After rebooting the phone the GPS fix is almost instant, with no problem.
So, what can cause GPS to be unable to get a fix, while it can use the satellites. Seems to be software related as reboot makes it fine. It is not ROM related, cause I've had it on stock as well as custom ROMs. Anybody can think of a fix that doesn't require me to reboot?
No, I have given up on GPS of this phone, Snapdragon variant. As you said, rebooting the phone makes the GPS lock fast/ instant, but for normal usage sometimes GPS just won't lock. All I can gather from my personal experience is its about Assisted GPS. When you are restarting your phone the AGPS data is being downloaded automatically, that is how Android works anyway, and that's probably why the phone gets a super fast lock after a reboot. Use app like GPS Status or something to have the phone download AGPS data at short interval, see if that helps in anything or not.
However I have never had any problems when I am outside, the GPS locks within 30-45 seconds no matter what, its the inside problems which used to bug me, but as I said, I have given up.
Hm, I've never seen such a problem. I use my N9005 for travelling across Europe quite often, and it usually locks within 10 seconds to 2 minutes, depending on the location and the number of satellites.
Aside from the occasional glitch, of course. Like going backwards or sideways. :silly:
And it seems to think I'm somewhere off the coast of Norway right now. That one creeps me out quite a bit...
The thing is that when you reboot, it uses all available connections to pinpoint your location. Including your mobile data. (And WiFi if available.) So if you turn on location services right after rebooting, your approximate location is still in the cache.
Triangulation Over Data works within seconds, as opposed to the time required to lock on to the satellites in orbit when it is only allowed to use GPS. If you turn on the higher location modes, it locks much quicker. You can turn it back to GPS once your location has been established.
ShadowLea said:
The thing is that when you reboot, it uses all available connections to pinpoint your location. Including your mobile data. (And WiFi if available.) So if you turn on location services right after rebooting, your approximate location is still in the cache.
Triangulation Over Data works within seconds, as opposed to the time required to lock on to the satellites in orbit when it is only allowed to use GPS. If you turn on the higher location modes, it locks much quicker. You can turn it back to GPS once your location has been established.
Click to expand...
Click to collapse
I am talking about GPS only. I use GPS Status app for a long long time (with my previous Android devices as well), so I can monitor the GPS fix. After reboot I get GPS position almost instant or sometimes I need to go into GPS status app and re-download A-GPS data (which is max 1h old, because of my settings) and then I get my fix.
When my problem occurs NOTHING (short from reboot) can get it to get a fix. I tried deleting and downloading A-GPS data, turning location on and off and from high precision to power saving - it just won't work. Of course I'll get postition from WiFi or cell towers, but GPS just won't fix, even with 12 satellites in use, after waiting over 15 minutes (which should be more then enough, cause whole GPS almanach is transmitted over 12,5 minutes and I get it from A-GPS anyway).
I would start by wiping the phone installing stock rom and testing . Still a problem then its hardware .
Starting today, my S7 Edge has a problem when WiFi is turned off: every two or three seconds, the WiFi turns on for about a third of a second (as shown by the WiFi quick-settings icon). When this happens, the phone gets warm (even if otherwise idle) and the battery drains rapidly.
The problem disappears if I turn off the Location Accuracy setting that scans for WiFi networks even with WiFi off. But it shouldn't be scanning constantly even if that setting is turned on--it's using much more power than if I just leave WiFi turned on.
Turning off the WiFi Location Accuracy setting also fails because then, when I use a location-enabled app such as Google Maps, it pops up a message asking me to turn on Google Location services (which is already on, and the phone has a good GPS signal). If I tell it to go ahead and turn location services on, it then turns WiFi Location Accuracy back on and the constant scanning resumes.
So there's clearly a bug, but the problem is very recent and my phone (AT&T) has not received a recent update.
Has anyone else encountered this problem or does anyone know how to fix it? (Rebooting doesn't help.)
Gary02468 said:
Starting today, my S7 Edge has a problem when WiFi is turned off: every two or three seconds, the WiFi turns on for about a third of a second (as shown by the WiFi quick-settings icon). When this happens, the phone gets warm (even if otherwise idle) and the battery drains rapidly.
The problem disappears if I turn off the Location Accuracy setting to scan for WiFi networks even with WiFi off. But it shouldn't be scanning constantly even if that setting is turned on--it's using much more power than if I just leave WiFi turned on.
Turning off the WiFi Location Accuracy setting also fails because then, when I use a location-enabled app such as Google Maps, it pops up a message asking me to turn on Google Location services (which is already on, and the phone has a good GPS signal).
So there's clearly a bug, but the problem is very recent and my phone (AT&T) has not received a recent update.
Has anyone else encountered this problem or does anyone know how to fix it? (Rebooting doesn't help.)
Click to expand...
Click to collapse
Same issue here, started yesterday. I'm on T-Mobile, and have had no new updates to the system.
I saw this was happening (on other threads) to other phones, not just Samsung phones.
Same here in France with SFR, it's very annoying ...
Hope we're getting a fix soon!
*Link to video if it doesn't play above (gives an error on playback for me for some reason): https://www.youtube.com/watch?v=X5dbrBMqsuU
Here's a video of the issue I've been having, which I believe is the same as the one you're describing. My WiFi switch just constantly turns on and off, and I am unable to connect to my network. I have found a way to get it to connect to my network by first clicking the WiFi Direct button (when it's clickable and not flashing), and then when I go back, the list of available networks shows just like it normally does, and I am able to connect. Turning off WiFi again, would then reproduce the problem though. It started happening recently after the latest update for me. I'm non-rooted, completely stock for now.
http://forum.xda-developers.com/s7-edge/help/wifi-off-constantly-t3499683
Oops, sorry, I see now that there was already a thread here about this problem.
When I go to use Google Maps for navigation, I often get the message "To continue turn on device location which uses Google's location service". The problem also affects ViewRanger, an app I use for walking. GPS appears to turn off during a walk so I lose the track of my route. In this case the message is "GPS is disabled in the settings. Please enable it."
I recognise this happens after the phone has been "asleep" for a while but have not been able to measure how long it must be asleep before the problem arises. I think it is at least 30 mins.
It feels like a "battery saver" problem, but I can't see any obvious power saving setting to turn off. ViewRanger is set in App Power-saver to have no optimisation policies.
I have had my Axon 7 since Jan 2018 and this problem has only occurred in the last few weeks. My model is A2017G on stock Oreo B03 and unrooted. The problem did not emerge when I first moved to Oreo. It may have started when I moved to B03 though I think GPS was fine for a while after I moved to B03.
Something is turning off location services in the background; how do I find out what it is? Is there some sort of log I can read? What other solutions are there? Many thanks in advance, Evan
I moved from stock Oreo B03 to B04 (via B02) and wiped the cache. All now seems to be well; ViewRanger recorded a 4 hour track with no problem yesterday. Slightly strange though as I had previously wiped cache while on B03 and found that didn't fix my problem.
Too good to be true
grantem2000 said:
I moved from stock Oreo B03 to B04 (via B02) and wiped the cache. All now seems to be well; ViewRanger recorded a 4 hour track with no problem yesterday. Slightly strange though as I had previously wiped cache while on B03 and found that didn't fix my problem.
Click to expand...
Click to collapse
It did all seem a little too good to be true and, sadly, Location Services again began "turning off automatically" only a few days after my upgrade to B04. I have attached 2 screenshots from the notification log for when I started recording a route in ViewRanger at 15:07 and again 3 mins later at 15:10 when tracking appeared to stop. The logs mean nothing to me, so any insight would be very welcome.
In the meantime, I uninstalled ViewRanger, deleted all ViewRanger directories, restarted the phone, re-installed ViewRanger and wiped cache again. After that, for now at least, Location Services are again behaving.
As all this appears to point the finger at ViewRanger, I will raise direct with the application owners too.
grantem2000 said:
As all this appears to point the finger at ViewRanger, I will raise direct with the application owners too.
Click to expand...
Click to collapse
ViewRanger, support were very responsive and supportive. They made a convincing case that the problem is not caused by ViewRanger, not least as the app has no capability to turn off Location Services.
But something is still turning off Location Services when the phone goes to sleep. How can I tell what is doing this?
In the meantime, wiping cache solves the problem for a few days, but, so far, it has always come back.
I have the same issue and that's why I think this phone's gps is useless. I find this gps not in accurate way to detect the coordinates even in all previous firmwares (nougat, all ver of oreo)
The auto turned off gps services maybe the case of software, but I think the hardware is bad either.
This is the worst part as I work using GPS a lot but I still love this guy's music features. I ended up using secondary phone/tablet to run some geographical apps, sad cant have em running in one phone only.
Update: my GPS get fixed on B04 with locked bootloader, it seems fine and fast to get POI. It's usable now. Guess the previous rom has bugs on GPS or it's broken by other apps I used before