Database Info

[Q] Strange inaccurate recordings in location history

Hi guys,
I run PA 4.4 for like 10 days now. Since a week ago I have strange locations in my Google location history - constantly, when not moving - and rather accurate when I am outside (maybe has something to do with the wifi connection when stationary at home or at work?)...
One interesting part of it is: the first days of my new PA experience everything was fine. So probably it does not have anything to do with it. That first day I had the issue my phone crashed earlier while I was outside and I had to do a reboot. Maybe some settings were changed during that!? Or... maybe it doesn't and it's just a coincidence after some apps where updated (Google Search or so)...
I tried quite some settings to figure out what happens here - and it is not trivial - to my mind:
I did another clean install of the ROM; had the same issue again
I changed between "high accuracy" and "battery saving" mode in the location settings; no change
I went to the developer settings and unchecked "accept mock locations" (is that how the option is called in English?); no change
I have a Nexus 10 also running Android 4.4.4 and started to record my location history from that device with different settings: all are fine and accurate! When I record from both devices I can actually see my history jumping in 5-minute-mode...
Any ideas, any suggestions?
Please...

Two more findings, which make this issue even stranger:
When I move in the house - e.g. 2nd instead of ground floor - I get different locations, some 100 or 200 meters away, but both far from home.
I turned wifi off for one and a half hour - that resulted in perfect locations!! Locations were inaccurate after turning wifi on again...
What is wrong here?? So I get more inaccurate locations when connected to wifi!?

i always run straight gps and never wifi. imo its a conflict of interest.
gps is dead accurate, so the only time you could benefit from wifi is when you are in a building with no gps signal, and frankly, why would i need 100% accurate gps if im already in the building.
again imo, what is happening is, it can only reference wifi that it knows the exact location of. it has no way to tell how far from that wifi you are, so its guessing based on a limited gps signal and known wifi points.
i think its a waste of battery to be scanning wifi points all the time any ways, unless you have a constant use for it.

bweN diorD said:
i always run straight gps and never wifi. imo its a conflict of interest.
Click to expand...
Click to collapse
Thank you for the answer! And I sort of agree...
But the question is:
what did change that day when my location started to be different? I never had problems for more than two years of using the location history. Even after moving in April everything was fine with the wifi locations. I get one accurate reading like every one to three hours - so the location jumps from time time. Why is that? Is that a gps reading?
Plus: how could I change the settings? The only thing I can chose from is: "battery saving" (cell towers and wifi) or "high accuracy" (the same plus gps). I selected the second option but obviously still the Google location service does not really use it. When I turn off wifi it can only use cell towers plus gps... but obviously I want to be connected to the wifi when being at home.

I can't say why it started acting up.
If you use WiFi you are kinda stuck.
I only have GPS on and denied anything that wants to use WiFi for any reason.
I don't know where the option is found, but I remember it asking if I wanted to use WiFi to help results or something like that, I chose no.
Sent from my LG-VS980 using XDA Premium 4 mobile app

bweN diorD said:
I don't know where the option is found, but I remember it asking if I wanted to use WiFi to help results or something like that, I chose no.
Click to expand...
Click to collapse
I guess that option is the "use wifi for location detection although wifi is turned off" which can be found in the wifi advanced options. But I turned that on and off, no change.
But one more test from myself:
I let wifi on but disconnected from my home network. The result is: accurate locations! So the problem is not the wifi itself but a connected wifi!? And it is not only the home network because I had the same issue at work.
Plus: we just had a thunderstorm, that could have been the reason why cell towers and/or gps reacted differently: my location was at some new place about more than a mile away. The worst thing is: accuracy of that location point was about half a mile -- which means: my real location was not inside the accuracy cycle (that blue cycle when using location history)!!
The accuracy cycle is always very small when I get the real readings at home and always about half a mile in radius when somewhere else...

that is basically the problem with using wifi to help. there are too many variables. location needs to know the location of the wifi, but then there is a broadcast radius that decreases accuracy. there is also the question, what does it do when you are connected to a wifi it doesnt know the location of?, that could cause inaccuracy. maybe it makes an uneducated guess, who knows. there is also the issue, what if it thinks it knows the location but its actually wrong?
the list of possible scenarios could go on and on as to why it isnt reporting correctly.
the only way to truly know why it is wrong is to find out why exactly it thinks you are where you are when its wrong. there has to be some exact source of information its using to base your wrong location on. unfortunately, i doubt there is any way for the common user to get this information, let alone take corrective action so its not inaccurate in the future.

wrong locations only when wifi is connected, only on one device
OK, what do we already know?
I have the problem for some 8 to 10 days now. Never had it before, only have it on one device.
Maybe a coincidence but this behavior started on a day where my phone crashed and I had to reset.
I made a clean new re-install of the PA 4.4 and recently received the update to PA 4.42. There are no changes in the behavior.
It is only my phone (running ParanoidAndroid based on KitKat 4.4.4), my tablet (Nexus 10 running stock KitKat 4.4.4) does not have this problem (so it's no wifi relocation because of moving or such general problem).
I have the problem with more than one wifi! Have already seen these false locations when connected to the home and when connected to the work network. Problems with both networks started the same day...
Wrong locations are constantly there when my phone is connected to a wifi.
It's not always the same location, sometimes I get different readings, but it's 90% a position ~430m west of my home.
The correct locations have high accuracy (a few meters), the wrong locations have very low accuracy (~1000m or even more).
When I start Google Maps (i.e. probably when the phone uses gps) I can see my position moving towards the correct location.
When I switch off wifi or when leave wifi on but disconnect my phone from the network, then I get the correct location constantly.
Roughly every 1 to 3 hours there is one correct location within the list of false locations.
I tried virtually every combination of settings, "high accuracy" and "battery saving" for the location service, "no mock locations" in the advanced developers settings, "use wifi for location detection although wifi is switched off" in the wifi settings, ...
Is there some sort of cache that might be corrupted!?
Is there a possibility to force using gps?
What else...

Tho-D said:
OK, what do we already know?
I have the problem for some 8 to 10 days now. Never had it before, only have it on one device.
Maybe a coincidence but this behavior started on a day where my phone crashed and I had to reset.
I made a clean new re-install of the PA 4.4 and recently received the update to PA 4.42. There are no changes in the behavior.
It is only my phone (running ParanoidAndroid based on KitKat 4.4.4), my tablet (Nexus 10 running stock KitKat 4.4.4) does not have this problem (so it's no wifi relocation because of moving or such general problem).
I have the problem with more than one wifi! Have already seen these false locations when connected to the home and when connected to the work network. Problems with both networks started the same day...
Wrong locations are constantly there when my phone is connected to a wifi.
It's not always the same location, sometimes I get different readings, but it's 90% a position ~430m west of my home.
The correct locations have high accuracy (a few meters), the wrong locations have very low accuracy (~1000m or even more).
When I start Google Maps (i.e. probably when the phone uses gps) I can see my position moving towards the correct location.
When I switch off wifi or when leave wifi on but disconnect my phone from the network, then I get the correct location constantly.
Roughly every 1 to 3 hours there is one correct location within the list of false locations.
I tried virtually every combination of settings, "high accuracy" and "battery saving" for the location service, "no mock locations" in the advanced developers settings, "use wifi for location detection although wifi is switched off" in the wifi settings, ...
Is there some sort of cache that might be corrupted!?
Is there a possibility to force using gps?
What else...
Click to expand...
Click to collapse
I guess you shouldn't rule out that it is an issue caused by the ROM some how.
On my phone I can force it to use GPS only, I have the option anyways.
Under location I have device only or something like that, it says it only uses GPS when that option is selected.
Sent from my LG-VS980 using XDA Premium 4 mobile app

bweN diorD said:
I guess you shouldn't rule out that it is an issue caused by the ROM some how.
Click to expand...
Click to collapse
I thought about that, too. Means to installiert something else, CM11 vor so...

There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...

Tho-D said:
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Click to expand...
Click to collapse
Ohh OK, I didn't know that. Thanks for the info
Sent from my LG-VS980 using XDA Premium 4 mobile app

Tho-D said:
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Click to expand...
Click to collapse
so i did a little test today on the way home from work, as i took a different route than normal to avoid traffic.
when i started "maps" i had to allow google location services to navigate. so im pretty sure you can use device only as long as you allowed google location for apps, as it said something about my google now functionality when i turned it off after navigating.
last week i navigated a 3 hour trip, on a different rom, with no issues. today, maps couldn't seem to start gps to find my location to start navigating. so i turned on "high accuracy", more to test than anything else, and it found my location and we were navigating home .
i knew where i wanted to go but at some points that varied from where maps wanted me to go. for a while it did good at making quick corrections to my path. about 20 minutes in, i didn't follow its directions again. well this time, it didn't recognize that i didn't turn, then advised me to make a subsequent turn onto a road that was off the road i didn't turn onto. now, the road i am on is about 1/4 mile from the road it thinks im on, the 2 roads are parallel. well it took maps over a mile, after i made another turn towards the road it thought i was on, before it realized it was wrong and made corrective instructions. after that, i made a quick stop to grab some liquid refreshment for the night and turned off navigation, as i was close to home.
this really goes to prove nothing more than "high accuracy" is not always highly accurate. i traveled across 3 states last week for 3 hours on "device only" and never once was it wrong about my exact location.
just wanted to share my experience, really doesn't help or fix your problem, but may shed some light on the possible inaccuracies across multiple devices.

bweN diorD said:
so im pretty sure you can use device only as long as you allowed google location for apps, as it said something about my google now functionality when i turned it off after navigating.
Click to expand...
Click to collapse
I tried this and yes, Maps works with the "device only" setting. But when using Now it said that location-based cards (weather, traffic, ...) only work with "high accuracy" or "battery saving". So for me this setting is useless.
I guess I'll do another clean install and try CM11 or so...

it's not ROM related
I trid to install CM11 M8 today. For some reason I wasn't able to, received these strange "Unfortunately process ... has stopped" messages all the time and was not able to complete the initial setup. The only hint I found online is to make sure CWM recovery is up to date. I use v6.0.5.0 which I assume is up to date.
So I made another clean install of PA 4.42. Then I downloaded another ROM: did a clean install of SlimKat. This went smoothly, but I have the same location problems, both times!!!!
I guess we can be sure my location problems are not related to the ROM.
One thing I saw that seems noteworthy: I had correct locations for some time and then the wrong locations started again. Maybe this has to do with the system restoring backed up settings or installing / updating all the apps!?
Any ideas?

Tho-D said:
I trid to install CM11 M8 today. For some reason I wasn't able to, received these strange "Unfortunately process ... has stopped" messages all the time and was not able to complete the initial setup. The only hint I found online is to make sure CWM recovery is up to date. I use v6.0.5.0 which I assume is up to date.
So I made another clean install of PA 4.42. Then I downloaded another ROM: did a clean install of SlimKat. This went smoothly, but I have the same location problems, both times!!!!
I guess we can be sure my location problems are not related to the ROM.
One thing I saw that seems noteworthy: I had correct locations for some time and then the wrong locations started again. Maybe this has to do with the system restoring backed up settings or installing / updating all the apps!?
Any ideas?
Click to expand...
Click to collapse
the only way to rule out the rom's is to return to stock and check it there.
its not uncommon to have similar issues across multiple rom's.
im not saying you are wrong, changing from one rom to another is just not a good way to check an issue.

bweN diorD said:
the only way to rule out the rom's is to return to stock and check it there.
its not uncommon to have similar issues across multiple rom's.
im not saying you are wrong, changing from one rom to another is just not a good way to check an issue.
Click to expand...
Click to collapse
Oh, is that the case?
Then I should install the stock Samsung ROM and check. Probably will do it in a few days since I am busy the next days.
BTW: I installed SlimKat and then PA again. After installing SlimKat I now have TWRP instead of CWM recovery and the settings of 5x5 Icons on the home screen plus smaller font size and probably a few other settings remain in PA although I did factory reset, format cache and so on...
The thing is: how can I change this back!?!? Didn't find it in the settings. It'not font size (which is set to 100%).

Tho-D said:
Oh, is that the case?
Then I should install the stock Samsung ROM and check. Probably will do it in a few days since I am busy the next days.
BTW: I installed SlimKat and then PA again. After installing SlimKat I now have TWRP instead of CWM recovery and the settings of 5x5 Icons on the home screen plus smaller font size and probably a few other settings remain in PA although I did factory reset, format cache and so on...
The thing is: how can I change this back!?!? Didn't find it in the settings. It'not font size (which is set to 100%).
Click to expand...
Click to collapse
there is another partition thats not normally wiped with a factory reset. i believe its called "data/media". the official cwm's that i have used have an option to wipe this separately, but i havent seen this option in twrp, or know if it wipes it by default. my guess would be no, but i could be wrong.
anyways, some settings and/or app data is stored in this area. you likely need to wipe this to fix the problem. that would be my best guess anyways.

bweN diorD said:
there is another partition thats not normally wiped with a factory reset. i believe its called "data/media". the official cwm's that i have used have an option to wipe this separately, but i havent seen this option in twrp, or know if it wipes it by default. my guess would be no, but i could be wrong.
anyways, some settings and/or app data is stored in this area. you likely need to wipe this to fix the problem. that would be my best guess anyways.
Click to expand...
Click to collapse
Just rebooted into recovery and was surprised its CWM again!? Anyways, good its back!
The one option I always used is "wipe data/factory reset" (plus of course "wipe cache"). Under "mounts and storage" there's an extra option "format /data". Should I try this one?

Tho-D said:
Just rebooted into recovery and was surprised its CWM again!? Anyways, good its back!
The one option I always used is "wipe data/factory reset" (plus of course "wipe cache"). Under "mounts and storage" there's an extra option "format data". Should I try this one?
Click to expand...
Click to collapse
I'm pretty sure it says data/media. I don't have cwm on right now or I would check, but I think it is under mounts and storage. It was in the same dir where you can format system and such if I remember correctly.
Its also possible someone removed that option from your version, but I don't know why they would unless your phone doesn't have that partition.
Sent from my LG-VS980 using XDA Premium 4 mobile app

weak GPS signal problem?

Is anyone experiencing problem with their GPS signal? Mine would lose the GPS lock constantly. Thanks.

Working fine on my end. Out and back, my drive was 5 hours total.
Sent from my VS995 using Tapatalk

No, no problems at all. And I used the GPS allot.
Sent from my LG-H918 using Tapatalk

Make sure yours is set to High accuracy. Mine was not after set up. I had to change.
Sent from my SM-T813 using Tapatalk

Even in high accuracy, I lose the gps signal frequently. Sigh

Do you have a case on your phone?
I just got my cases in and have noticed weaker gps performance since putting the phone in a case.

I've been having major GPS problems. Going for a run and expecting the phone to track my route and calculate my speed accurately shouldn't be too much to ask in late 2016. But my phone constantly loses the GPS signal (this was never a problem with my previous phone in the same location) and even when it doesn't, it can't figure out where I am. My run traces often show me two streets over in addition to thinking I'm jumping back and forth across a busy 5-lane road every 5 seconds or so. I run 6 miles and the phone thinks I've gone 8.25. Not useful for training for events.
Even if you don't want to use the phone to track exercise, there's another reason the bad GPS is annoying. It makes it impossible to take advantage of the feature allowing you to unlock the phone without using your fingerprint or pin based on your location. I have my phone set to be unlocked at home, but the phone apparently can't tell when I'm at home, making this setting completely useless.
As to GPS issues while driving, I haven't noticed them, but I've not used the phone for navigating either.
Would like to mention that while I have a case on it, it is quite light and doesn't seem like it should interfere so badly with the GPS. Will try checking the accuracy without the case and will update if this resolves the issues. Also, I have tried tinkering with the GPS accuracy settings but even selecting all the options to optimize accuracy has not worked for me.

The only thing you can do to test the case theory is to use the phone without that case. That said, it is possible you have a defective phone. I have read many articles about poor GPS being caused by a loose, internal connection. You might want to take your phone to a repair facility and have them check it out.
I have a US996 and, so far, GPS is nice.

how
wtharp2 said:
The only thing you can do to test the case theory is to use the phone without that case. That said, it is possible you have a defective phone. I have read many articles about poor GPS being caused by a loose, internal connection. You might want to take your phone to a repair facility and have them check it out.
I have a US996 and, so far, GPS is nice.
Click to expand...
Click to collapse
how can you change it to high?

No issues on my end yet, I use it navigating on a daily basis (racking up Waze points basically) and walking around, can't think of maybe one time it lost GPS driving and that was only briefly.

Mine was misbehaving horribly. I tried using google maps to see if it was something to do with Navigon, (my normal gps app) and somehow it seems like just running maps fixed it. It has been working great with Navigon now.
Go figure.

GPS on my Sprint version has worked great in all 3 options since day 1
Sent from my LG V20 using XDA Labs

On my rooted VS995 software version VS99513A on notsostock kernel v1.2 the GPS seemed to never be able to locate my current location. When I used it before without root it picked up quickly. Am going to try nostock kernek v1.1 the updated version and see if I get a difference. Plus now am running magisk instead of supersu so will see if that makes a difference.

It's possible that the a-gps data is corrupt. I'm not sure how you'd go about clearing that. There must be a cache file associated with gps daemon.
Try installing this:
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
And when GPS isn't working, run the app and see if it's receiving/decoding any satellites at all (bar lengths indicate strength, colour indicates successfully received all ephemeris data from satellite and therefore has lock - it can take a while without a-gps).
---------- Post added at 08:29 AM ---------- Previous post was at 08:27 AM ----------
P.s. I found that taking the back off my phone improves Wi-Fi. Metal blocks radio signals.
If you have low or no signals in a specific location, try popping the back of the phone and seeing if the signals become useable.

mmar3087 said:
Is anyone experiencing problem with their GPS signal? Mine would lose the GPS lock constantly. Thanks.
Click to expand...
Click to collapse
Sorry to bring up an old thread. I just bought a used LG V20 (at&t version, H910) on Craigslist the other day, and have had GPS issues that made me highly annoyed like I bought a lemon phone, and was getting ready to call LG Support, and pay a lot of money for repairs.
Happily, I did discover a trivial solution that I haven't really seen, so I thought I'd share it.
After I purchased the phone, I factory reset it. It seemed like the device would be able to triangulate a position, but it would be unreliable, move around, and the accuracy would be highly variable. (observed in Google Maps and Waze). These symptoms seem to be consistent with other people's experiences. The useful and highly recommended "GPS Status" and "GPS Test" apps, that normally show visible satellites were showing ZERO satellites. As suggested in various places, I used "GPS Status" to re-download the A-GPS databases, set "sensor filtering" to medium. Still, zero satellites, but a semi-functional GPS, which is confusing. I found the hidden menu code for the H910 (*#546368#*910#), and SAAT->"Manual Test"->"GPS/BT/Wifi test" and ran the hardware-level GPS diagnostics. I was getting signals of 0.0 db for GPS and GLO satellites, kind of suggesting the GPS hardware was faulty, and made me even less optimistic/more annoyed.
I was basically convinced GPS on my phone was kaput, and would need to be serviced, until I discovered ........
Rebooting the phone solved all of the GPS problems, and made GPS and GNO satellites visible and now GPS is 100% functional. It seems that since I initially factory reset the phone and did my normal installation, I never did a simple reboot. Since I haven't seen that kind of obvious solution on any of the forums, I thought it would be useful to report. I'm cautiously optimistic that was my only problem ......
good luck
=mxasf=

Bought a used one and having problems: it'll fix on several satellites but it's usually unable to acquire the specific location (latitude and longitude). Depending on the program, it will say "waiting for GPS fix" in osmtracker or "looking for GPS location" within 'GPS Status' (the app).
When it does get a 'Lock' (a specific location), its accuracy is 200-300m off. :/
I tried some of the other common tips and tricks:
I've downloaded new A-GPS data (using the 'GPS Status' app); tried using the GPS without my case on; doing a simple reboot, none of them work.
After more searching, I found this guide: https://imgur.com/a/VxeaU which recommends to place copper tape on the GPS antennas of your phone.

i have 2 V20's.. the one i bought back for myself is 12/2016 and another one is another batch 3/2017 for my wife..
What i'll found is the earlier one ( 12/2016 ) have the following issue :
- overheat
- kaput gps
- screen burn
While the one i bought for my wife ( 3/2017 ) doesn't even have the following issue above.. Furthermore, the screen also different.. my wife V20's tend to have a more saturated color, brighter screen and doesn't overheat as much as mine..
My conclusion is, only those with earlier batch of production have all this defect.. and to those who own it ( including me ).. i guess, we're unlucky!
i'll use my wife V20's as gps since mine V20 is good for nothing when GPS is a needs.... if she's not around, i'm totally doomed !
-----
if you guys wonder, there was no different in camera.... unlike G6 ( pheww~ )
both my and my wife V20's produce the same images quality..

mxasf said:
Rebooting the phone solved all of the GPS problems, and made GPS and GNO satellites visible and now GPS is 100% functional. It seems that since I initially factory reset the phone and did my normal installation, I never did a simple reboot. Since I haven't seen that kind of obvious solution on any of the forums, I thought it would be useful to report. I'm cautiously optimistic that was my only problem ......
good luck
=mxasf=
Click to expand...
Click to collapse
It's an old common fix

skorasaurus said:
Bought a used one and having problems: it'll fix on several satellites but it's usually unable to acquire the specific location (latitude and longitude). Depending on the program, it will say "waiting for GPS fix" in osmtracker or "looking for GPS location" within 'GPS Status' (the app).
When it does get a 'Lock' (a specific location), its accuracy is 200-300m off. :/
I tried some of the other common tips and tricks:
I've downloaded new A-GPS data (using the 'GPS Status' app); tried using the GPS without my case on; doing a simple reboot, none of them work.
After more searching, I found this guide: https://imgur.com/a/VxeaU which recommends to place copper tape on the GPS antennas of your phone.
Click to expand...
Click to collapse
I followed that guide (credit https://www.reddit.com/r/lgv20/comments/7fx2gz/becareful_buying_the_top_plastic_bezel_of_the_v20/)
and bought copper tape (https://www.amazon.com/Copper-Conductive-Adhesive-1inch-12yards/dp/B018RDZ3HG) off amazon.
For me and my VS995; there were metal contacts (see picture 1 of the imgur album) and the metal contacts were silver, not gold.
Nonetheless, I put some copper tape only on the first contact as shown in picture 1 and my signal improved dramatically. The lowest accuracy that I can get (lower is better) now is about 8m and it has been hovering around 15m; and still takes a few seconds to
This is compared to my s5, where I could get an accuracy as low as 4-5m and usually hovers around 8-10m and could obtain my location within 10 seconds after turning on GPS.

How to track a run with GPS?

So I went for my first run with just the watch - no phone. I started the S Health run tracking on the watch as I left. Initially it said it couldn't find location but then this message went away. Throughout the run the location icon on the watch was flashing grey to white. I don't know if this meant actively tracking or trying to find location?
When I came back the data synced over to S-Health on my phone, but there is no map.
I don't know if the distances and speeds have been tracked based on steps and cadence or by GPS?
How is this supposed to work? I presumed the watch GPS data would produce a map when synced with the phone?

It should show you a map in s health. You have to click on the specific run activity though to see it. If it isn't there then maybe GPS wasn't working for some reason. Did it show you the map on the watch in the completed workout summary?
Sent from my Pixel XL using Tapatalk

photojonny said:
So I went for my first run with just the watch - no phone. I started the S Health run tracking on the watch as I left. Initially it said it couldn't find location but then this message went away. Throughout the run the location icon on the watch was flashing grey to white. I don't know if this meant actively tracking or trying to find location?
When I came back the data synced over to S-Health on my phone, but there is no map.
I don't know if the distances and speeds have been tracked based on steps and cadence or by GPS?
How is this supposed to work? I presumed the watch GPS data would produce a map when synced with the phone?
Click to expand...
Click to collapse
I have had this happen with other watches and with a Gear Fit 2. I did a run this morning and had the map show up instantly on my watch at the completion of my run (LTE version). When you have the watch in S Health Run mode and hit the start button you will see a small icon at the top left that looks like a balloon, it is the icon for your GPS. It will be flashing. Once it is always on it means you have a GPS lock. Sounds like you never got a lock.
I recommend 2 things. Go outside with your phone and put the watch in run mode. Watch for the GPS icon, it should lock very fast since you have your phone working with the watch. Now put your phone inside or turn it off so you can try a stand alone test. Put the watch into run mode and see if you get a quicker GPS lock.
Good Luck

cdd543 said:
It should show you a map in s health. You have to click on the specific run activity though to see it. If it isn't there then maybe GPS wasn't working for some reason. Did it show you the map on the watch in the completed workout summary?
Click to expand...
Click to collapse
Thanks. No map, it's appears it failed to get a lock over the whole run.
Bladder61 said:
I have had this happen with other watches and with a Gear Fit 2. I did a run this morning and had the map show up instantly on my watch at the completion of my run (LTE version). When you have the watch in S Health Run mode and hit the start button you will see a small icon at the top left that looks like a balloon, it is the icon for your GPS. It will be flashing. Once it is always on it means you have a GPS lock. Sounds like you never got a lock.
I recommend 2 things. Go outside with your phone and put the watch in run mode. Watch for the GPS icon, it should lock very fast since you have your phone working with the watch. Now put your phone inside or turn it off so you can try a stand alone test. Put the watch into run mode and see if you get a quicker GPS lock.
Good Luck
Click to expand...
Click to collapse
Thanks. I'll try this but a bit concerned it failed to get a lock over the whole run. I hope the GPS chip isn't faulty after the hassle actually getting hold of it.
Edit: I should say I'm in the UK so this is the non LTE version. Don't know if that makes a difference.

I don't think the non LTE has GPS. It would only acquire GPS from your phone.
Sent from my Pixel XL using Tapatalk

cdd543 said:
I don't think the non LTE has GPS. It would only acquire GPS from your phone.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Of course it does.

Fozzee1970 said:
Of course it does.
Click to expand...
Click to collapse
You don't need the phone. But if you have the phone connected, the connection will be faster as it uses the phone for GPS locking
Sent from my SGP521 using XDA-Developers mobile app

Fozzee1970 said:
Of course it does.
Click to expand...
Click to collapse
Yep you're correct. My bad.
Sent from my Pixel XL using Tapatalk

photojonny said:
So I went for my first run with just the watch - no phone. I started the S Health run tracking on the watch as I left. Initially it said it couldn't find location but then this message went away. Throughout the run the location icon on the watch was flashing grey to white. I don't know if this meant actively tracking or trying to find location?
When I came back the data synced over to S-Health on my phone, but there is no map.
I don't know if the distances and speeds have been tracked based on steps and cadence or by GPS?
How is this supposed to work? I presumed the watch GPS data would produce a map when synced with the phone?
Click to expand...
Click to collapse
Check your location settings on your Gear. You should have GPS+ wifi not only wifi.
Sent from my SM-G935F using XDA-Developers mobile app

Bladder61 said:
I have had this happen with other watches and with a Gear Fit 2. I did a run this morning and had the map show up instantly on my watch at the completion of my run (LTE version). When you have the watch in S Health Run mode and hit the start button you will see a small icon at the top left that looks like a balloon, it is the icon for your GPS. It will be flashing. Once it is always on it means you have a GPS lock. Sounds like you never got a lock.
I recommend 2 things. Go outside with your phone and put the watch in run mode. Watch for the GPS icon, it should lock very fast since you have your phone working with the watch. Now put your phone inside or turn it off so you can try a stand alone test. Put the watch into run mode and see if you get a quicker GPS lock.
Good Luck
Click to expand...
Click to collapse
So I've tested this out and either I have a faulty device or the S3 is useless. I repeatedly tried to get a GPS lock on a long walk today - in open countryside with no buildings around and under clear skies. The watch connects instantly when using the phone GPS via bluetooth. When I disconnect bluetooth the watch will not connect on it's own at all despite repeated attempts. It will try for around a minute and then say 'cannot connect, move to a more open area' - this is whilst I'm stood in a field k's from the nearest building under a blue sky.
After the hassle I had getting hold of this I'm tempted just just get a refund, but if this is just a faulty unit and they generally work I guess I'll give one replacement a go - though I suspect I'll be waiting weeks for one.

photojonny said:
So I've tested this out and either I have a faulty device or the S3 is useless. I repeatedly tried to get a GPS lock on a long walk today - in open countryside with no buildings around and under clear skies. The watch connects instantly when using the phone GPS via bluetooth. When I disconnect bluetooth the watch will not connect on it's own at all despite repeated attempts. It will try for around a minute and then say 'cannot connect, move to a more open area' - this is whilst I'm stood in a field k's from the nearest building under a blue sky.
After the hassle I had getting hold of this I'm tempted just just get a refund, but if this is just a faulty unit and they generally work I guess I'll give one replacement a go - though I suspect I'll be waiting weeks for one.
Click to expand...
Click to collapse
I had carried out similar test this evening, the built in GPS worked when the bluetooth of my phone was off.

RayHK said:
I had carried out similar test this evening, the built in GPS worked when the bluetooth of my phone was off.
Click to expand...
Click to collapse
I tried a factory reset and it's now working. I found a thread on a Strava forum where someone had the same problem and switching the watch on and off worked. Must reset the GPS.
It takes around 30-60 secs to get a lock but it has worked since the reset.

photojonny said:
I tried a factory reset and it's now working. I found a thread on a Strava forum where someone had the same problem and switching the watch on and off worked. Must reset the GPS.
It takes around 30-60 secs to get a lock but it has worked since the reset.
Click to expand...
Click to collapse
But if you are going for a run do you just stand there for 30-60 after the 3,2,1 countdown? If so, isn't that going to throw off your average mile times?

awilson181 said:
But if you are going for a run do you just stand there for 30-60 after the 3,2,1 countdown? If so, isn't that going to throw off your average mile times?
Click to expand...
Click to collapse
Yes, a significant design flaw seems to be the inability to get the GPS lock before you start the run as you do with all dedicated running watches. I'm not sure what happens if you start the run then immediately pause it - whether it will continue to try and get the lock. There should be an option to set the lock then start the run. It's far from perfect.

photojonny said:
Yes, a significant design flaw seems to be the inability to get the GPS lock before you start the run as you do with all dedicated running watches. I'm not sure what happens if you start the run then immediately pause it - whether it will continue to try and get the lock. There should be an option to set the lock then start the run. It's far from perfect.
Click to expand...
Click to collapse
Yes definitely not a well thought out design of the software. Did they really test it with someone that actually runs?
It was the major reason I returned my Gear Fit 2 and went with a Garmin. I love my Gear S3, and I di exactly what you mentioned, I start the run program and when it counts down 3,2,1 I immediately hit the pause. I then wait a minute and resume it and make sure I have a locked GPS signal.
I went on too many Gear Fit 2 runs only to get back and find out I didn't have a GPS lock so info was estimated and no map info. Maybe Sammy will do a software update to the run program to fix this. Again, did Sammy have any real runners test the watch and give them feedback?

Bladder61 said:
Yes definitely not a well thought out design of the software. Did they really test it with someone that actually runs?
It was the major reason I returned my Gear Fit 2 and went with a Garmin. I love my Gear S3, and I di exactly what you mentioned, I start the run program and when it counts down 3,2,1 I immediately hit the pause. I then wait a minute and resume it and make sure I have a locked GPS signal.
I went on too many Gear Fit 2 runs only to get back and find out I didn't have a GPS lock so info was estimated and no map info. Maybe Sammy will do a software update to the run program to fix this. Again, did Sammy have any real runners test the watch and give them feedback?
Click to expand...
Click to collapse
Yeah It doesn't seem like they did as it lacks some basic functionality you would expect as a runner. I'm finding pace to be off as much as 20-30 seconds per mile compared to strava. I no longer have my fenix or I'd compare that.

Make sure Location is turned on in the settings

I started a thread on XDA comparing the G3 to my Garmin 620. In addition to the GPS issue, the HR wasn't consistent day to day either. I wasn't as concerned with that as I was the GPS. No way did they have somebody actually run with this watch. The lack of lap/split times in the run summary says it all.
Seems like an easy fix to just disregard that whole countdown timer and take you to the run screen so you can see if/when you get a GPS lock. My Garmin has a little satellite that turns solid when it locks. I'd probably get the watch, again, if they resolved this run issue.

After firmware updated today, the built-in GPS locked within 3 to 4 sec (after the count down) without a phone.

awilson181 said:
I started a thread on XDA comparing the G3 to my Garmin 620. In addition to the GPS issue, the HR wasn't consistent day to day either. I wasn't as concerned with that as I was the GPS. No way did they have somebody actually run with this watch. The lack of lap/split times in the run summary says it all.
Seems like an easy fix to just disregard that whole countdown timer and take you to the run screen so you can see if/when you get a GPS lock. My Garmin has a little satellite that turns solid when it locks. I'd probably get the watch, again, if they resolved this run issue.
Click to expand...
Click to collapse
I'll stick with it for now but it seems 5 mins with an actual runner and some of the problems would have been avoided. How are you supposed to time a race with a 3 2 1 countdown? And does the first part of the run not count whilst it's finding the GPS? If they are going after Garmin's market these are bad oversights.
RayHK said:
After firmware updated today, the built-in GPS locked within 3 to 4 sec (after the count down) without a phone.
Click to expand...
Click to collapse
I saw there is an update out. Haven't been able to push it to my device yet. Hopefully it'll show up soon.

Gear S3, S Health, not tracking location during run

Galaxy Samsung S7
Samsung Gear S3 watch
All updated, no outstanding software updates available.
I having the issue where 8 runs out of 10 S Health just stops tracking my distance.
Steps continue to count
Clock continues to count
The issue seems to happen when either I stop running - i.e. waiting to cross a road or when I pass under a bridge (bridge is probably 3 metres)... the watch seems to drop out. Only way is to stop and restart.
The interesting thing is if I stop and restart it works straight away - so that tells me I am within GPS signal.
The problem seems to be that if it drops out, it never can reconnect and start again. I have ran 7km, it has dropped out after 2km - yet for the rest of the other 5km - your telling me that I was never in GPS signal to pick up again ??
Can someone confirm that if I have my watch connected via Bluetooth, is the S Health app taking GPS from the watch itself or from the phone?

autonm said:
Galaxy Samsung S7
Samsung Gear S3 watch
All updated, no outstanding software updates available.
I having the issue where 8 runs out of 10 S Health just stops tracking my distance.
Steps continue to count
Clock continues to count
The issue seems to happen when either I stop running - i.e. waiting to cross a road or when I pass under a bridge (bridge is probably 3 metres)... the watch seems to drop out. Only way is to stop and restart.
The interesting thing is if I stop and restart it works straight away - so that tells me I am within GPS signal.
The problem seems to be that if it drops out, it never can reconnect and start again. I have ran 7km, it has dropped out after 2km - yet for the rest of the other 5km - your telling me that I was never in GPS signal to pick up again ??
Can someone confirm that if I have my watch connected via Bluetooth, is the S Health app taking GPS from the watch itself or from the phone?
Click to expand...
Click to collapse
-Deleted
I somehow but dialed I response to your post, smh sorry about that.
Sent from my SM-G935T using Tapatalk

gguy1 said:
Esw1122wqb4 vr7 gf miwd21111282rnI e5
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Thanks for that helpful insight !

autonm said:
Thanks for that helpful insight !
Click to expand...
Click to collapse
-Deleted
I somehow but dialed I response to your post, smh sorry about that.
Sent from my SM-G935T using Tapatalk

I have the same issue. I've tried: turning off auto pause, changing type from GPS only, GPS+wireless. I changed distance, adjusted guide, nothing has fixed it. Has been like this since Day 1 for me.

No issues for me. I'm normally tracking with S-Health on the watch and Strava on the phone as S-Health integration into Strava isn't very good.
I thought I read somewhere that when its paired it uses the phone GPS. Try it stand alone and see if it works.

just quick update - I ran 6km + on Sunday - following the same run / trail as I did previous when the S3 bombed out on me. This time I changed the following:
settings - connections - wifi - Off
settings - connections - location - on - methods GPS
It managed to track the entire 6km + without any issues or dropping out. I am running twice again this week and will let you know how it goes...

autonm said:
just quick update - I ran 6km + on Sunday - following the same run / trail as I did previous when the S3 bombed out on me. This time I changed the following:
settings - connections - wifi - Off
settings - connections - location - on - methods GPS
It managed to track the entire 6km + without any issues or dropping out. I am running twice again this week and will let you know how it goes...
Click to expand...
Click to collapse
I'll try that tonight. I had WIFI on.
Wonder if that's the key.

ok so cancel that... had the same settings as Sunday and it failed again tonight after 0.9km
Restarted the tracking again ... failed after 0.2km ... retired again - failed after 0.5km
Something is seriously wrong with the S Health app for tracking..
Next i am going to try a factory restart and see if I can block all notifications from my phone - incase the alerts / pop ups are causing issue....
not good

I have similar issue.

Ok, so I tried the suggested idea of turning off wifi, leaving BT on and GPS only. No change.
I tried turning off wifi, turning off BT. Then using gps and it worked. HOWEVER, it was only 1 test. (Basically watch only)
More testing needed.

Same issue here. Like others, I've tried different combinations of settings (wifi on/off, gps only, auto-pause on/off, etc.). I haven't turned off the Bluetooth connection to the phone, because without notifications, what would be the point - I can buy a dedicated gps watch for less than $50.
However, here are a couple of things I have found that are consistent.
shutting down the gear app on the phone, and restarting it seems to immediately help "location"
doing a reset of the watch, and reconnecting to the phone/app seems to make the s-health record distance consistently and correctly for a few days. HOWEVER, after 3 or 4 days it will stop recording distance during a run. After that, no matter what I do, it is flaky. Sometimes it won't record distance at all, and other times it will record sporadically. After a reset, it will function correctly for 3 or 4 days, and then flake out again.
After reading several threads in several forums, it appears that this is common and Samsung has no response. I really want to like the Gear S3, but this is too much money to spend on a mediocre product.

Samsung Gear S3 works fine, The S-Health app also works fine. The only thing is the working concept is not clearly understood by some people and not well explained by Samsung itself.
If your Samsung Gear S3 has problem tracking your location or distance during cycling or walking activities, here how to solve that:
Condition 1: Your Gear S3 is paired to Phone vie Bluetooth.
In this situation your Gear S3 will rely the location information from your phone.
You do not have to change any setting in your gear S3 ( Bluetooth still on, Wireless on, Location mode GPS & wireless, autopause on)
Make sure your phone Location setting is set to "On" and at "highest accuracy" mode. It means enable all GPS, WiFi and wireless networks for location searching from your phone.
Make sure your phone is not in "Power Saving" mode, because it limits the location tracking ability from your phone.
In this way your gear S3 can track your location, map your distance, and generate the route correctly. Even autopause works correctly and precisely.
Any location tracking faulty in this situation is mostly your phone location tracking faulty.
(You can test your phone tracking problem by running with your phone and S-Health app installed on it separately from your Gear S3)
Condition 2: Your Gear S3 is disconnected from the phone (stand alone)
In case you are not sure your phone can track location correctly in certain condition or you want to save your phone battery, disconnect your Gear from the phone. (Bluetooth Off, Wirelss Off, Location On- GPS & wireless / GPS only, or just simply press flight mode)
In stand alone mode, your Gear S3 will rely on its own GPS.
In this way your gear S3 can track your location, map your distance, and generate the route correctly (without detailed maps). Even autopause works correctly and precisely. The cycling and walking data will be synced to your phone after it is connected again.
Before starting your activity, make sure Gear's GPS has found your location.
At the first time you are using "standalone" mode, Gear may need some time (around 1-3 minutes) for GPS to locate your position. The small location (balloon) icon is blinking when searching and turns solid when it has found your location. Once is done, next time you use standalone GPS mode, it will locate you quickly.
At the first time you are using "standalone" mode after switching from phone connected mode, it's a good practice to restart your watch especially if it takes too long to find your location at first.
I hope this helps. I have tested it consistently on my Gear S3 Frontier, and my phone is Samsung Galaxy S6.

Samsung Galaxy A5 2016 [SM-A510F] - GPS issue after OTA firmware update to Android 7

I recently received an OTA firmware update for my Samsung Galaxy A5 2016 [SM-A510F].
The new firmware version is A510FXXU4CQDJ / A510FOXA4CQDJ / A510FXXU4CQDH.
The new Android version is 7.0.
After the update I started to experience a GPS issue which I try to explain:
it's like at a certain point (can't figure out the trigger cause) my GPS location remains stuck while tracking it.
I noticed this while using a sport tracking app (the workout distance sometimes had been stuck to zero while sometimes had started increasing but suddenly had stopped).
I first thought about a bug of the sport tracking app, but this morning I made a test workout while monitoring the GPS sensor with the GPS Test app.
When the issue occurred in the sport tracking app (the workout distance stopped increasing), I switched back to the GPS Test app to see what was happening: the GNSS Status was still on 3D Fix and there were about 20 satellites in use, but the accuracy was a s****y 32 meters (while it is usually about 4/6 meters).
It took a couple minutes to have the accuracy around 8 meters again. At that point my location in the sport tracking app was updated and the distance started increasing again when moving.
I had never experienced any GPS issue since I bought the phone. I never monitored the GPS sensor but there had never been any issue when tracking my location with the sport tracking app that I use.
I tried to toggle off and then on again the location functionality on the phone, to restart the phone, to clear and update the AGPS but the issue still persists.
Has anyone any idea on how to solve it?

Exact same problem!
Hi, i have the exact same problem!! I can't seem to figure out what is wrong....
Have you found the answer yet???
elbro84 said:
I recently received an OTA firmware update for my Samsung Galaxy A5 2016 [SM-A510F].
The new firmware version is A510FXXU4CQDJ / A510FOXA4CQDJ / A510FXXU4CQDH.
The new Android version is 7.0.
After the update I started to experience a GPS issue which I try to explain:
it's like at a certain point (can't figure out the trigger cause) my GPS location remains stuck while tracking it.
I noticed this while using a sport tracking app (the workout distance sometimes had been stuck to zero while sometimes had started increasing but suddenly had stopped).
I first thought about a bug of the sport tracking app, but this morning I made a test workout while monitoring the GPS sensor with the GPS Test app.
When the issue occurred in the sport tracking app (the workout distance stopped increasing), I switched back to the GPS Test app to see what was happening: the GNSS Status was still on 3D Fix and there were about 20 satellites in use, but the accuracy was a s****y 32 meters (while it is usually about 4/6 meters).
It took a couple minutes to have the accuracy around 8 meters again. At that point my location in the sport tracking app was updated and the distance started increasing again when moving.
I had never experienced any GPS issue since I bought the phone. I never monitored the GPS sensor but there had never been any issue when tracking my location with the sport tracking app that I use.
I tried to toggle off and then on again the location functionality on the phone, to restart the phone, to clear and update the AGPS but the issue still persists.
Has anyone any idea on how to solve it?
Click to expand...
Click to collapse

I am also stuck with this issue

Yvon85 said:
Hi, i have the exact same problem!! I can't seem to figure out what is wrong....
Have you found the answer yet???
Click to expand...
Click to collapse
Try disabling battery optimizations maybe it's causing the problem

Yvon85 said:
Hi, i have the exact same problem!! I can't seem to figure out what is wrong....
Have you found the answer yet???
Click to expand...
Click to collapse
If you have social media apps installed(Facebook, Messenger, Whatsapp, Snapchat, etc...), then your issue could be caused by one or more of these apps overloading the CPU and/or consuming all of your bandwidth(not allowing GPS to send or recieve any data to update exact location).
These social media apps are processor and data hogs. They interfere with other things functioning while they are scanning, sending and receiving information packets. They also dramatically impact how long your battery lasts per charge and they can also cause the device to get hot when using these apps heavily, it's even worse if you're charging the device while using these apps heavily.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I recently had an intermittent GPS problem which finally got so bad that the device (unrooted Samsung A3 (2016) , Lollipop) was not picking up any satellites and thus not getting a fix. After trying all sorts of things, such as deleting files in the phone memory, installing various GPS fixer apps I came across TopNTP in the playstore, installed and ran it. The GPS immediately started working properly again. Don't be put off by the age of the app or the requirement stated in the playstore that the phone be rooted. Mine wasn't and it still worked. Also the install and automatic reboot option in the app does not work. You have to restart your phone manually, but it still fixes the GPS problem.