Related
Well it seems the GPS on our Captivates has been improving over time due to adjusted Jupiter files, ROM updates, improvements in some leaked builds, and now a new GLGPS Daemon port, etc, but still seeing posts by lots of folks who still have trouble achieving good results. So, while the improvement quest continues, was thinking it might be helpful to have a common scoring or grading system for people to use when reporting on their gps results.
Would appreciate any comments on the usefulness of this, or agreement or disagreement with the descriptions. Just seems to me that currently it is often difficult to know what someone means when they say their GPS is good, best its ever been, or terrible.
(Note - to be most helpful to others please post your grade/results and anything you've done that has improved the gps performance.)
It would go something like this:
Captivate GpsGrade
A Common Way to Report GPS Effectiveness
Grade = A. Description – Performance is excellent at all times and very consistent. Applications such as Maps, Copilot, Google Nav, MyTracks always perform perfectly. Tracks as recorded by MyTracks consistently show the route accurately. GPS Locks are quick – under 30 seconds, and accuracy shows 5 to 10 meters or better as measured by lbstest, or GPS Test applications. When used for navigation, there is no drifting off of the road, no lag, and no overshoot of intersections. In short – its how we would want it to be.
Grade = B. Description – GPS function often works as expected, but occasionally does not. Usually no problem seeing several satellites and get locks within 30 seconds but always under a minute. Navigation apps are usable but sometimes there is a small bit of drift and sometimes will lag or show overshooting of intersections. Tracking via MyTracks is often accurate to the route taken, but sometimes off by a bit. Locks are sometimes lost but the system usually locks on again in just a few seconds. Accuracy often around 30 meters. Its not quite what we would like, but can live with it. Might call it pretty good.
Grade = C. Description – system achieves locks but often takes 60 seconds or longer. Locks are sometimes maintained while moving, sometimes not. Erratic performance. Can sometimes get Apps like Maps and Nav to work, but often have trouble with them or the system shows being on the next road or off the road. Routes recorded by MyTracks show inaccurate performance – route shown is close to the one taken but has occasional gaps with loss of lock. Accuracy is between 30 and 50 meters. In other words, performance may be good enough for location based services to be used, but not too useful for map or navigation functions. Mediocre.
Grade = D. Description – system sometimes gets a lock but cannot maintain lock. GPS Apps are not useable do to poor performance. In GPS Test or lbstest can sometimes see a couple satellites, but trouble getting a fix. Basically the GPS Icon is flashing pretty much the entire time. Awful would describe it.
Grade = F. Description – system does not work at all – cannot get locks, and cannot use any GPS Apps such as Maps or Nav, ever. Its just horrible.
good idea.
The problem with this, is most people have no idea how to properly test anything. For this to have any meaning, all tests should be conducted as follows:
Using multiple devices - not just a Captivate but another phone as well on another run
Not holding the phone in your hand - we know this can cause signal issues
Repeatable routes (testing on the same route)
Driving - walking does not allow for fast enough position change to reveal problems
No other apps running on phone - try to reduce any type of processor or storage contention issues
1. Mount device in car mount in the front windshield - other windows may have tint that interfere with signal reception
2. Launch Google mytracks - start driving after 10 seconds (fixed time for lock - equal for all)
3. Drive route with local and highway speeds and turns
4. Repeat with another device
5. Compare MyTracks recordings
Turn-by-Turn nav is a nice way to view accuracy BUT it has no way to record measurements. Comparing devices with a tool like Googles MyTracks is the only way to show that the captivate GPS sucks or not - maybe other phones suck too in certain environments.
This same methodology should be used before and after any mods as well - otherwise it is all hearsay.
alphadog00 said:
The problem with this, is most people have no idea how to properly test anything. For this to have any meaning, all tests should be conducted as follows:
Using multiple devices - not just a Captivate but another phone as well on another run
Not holding the phone in your hand - we know this can cause signal issues
Repeatable routes (testing on the same route)
Driving - walking does not allow for fast enough position change to reveal problems
No other apps running on phone - try to reduce any type of processor or storage contention issues
1. Mount device in car mount in the front windshield - other windows may have tint that interfere with signal reception
2. Launch Google mytracks - start driving after 10 seconds (fixed time for lock - equal for all)
3. Drive route with local and highway speeds and turns
4. Repeat with another device
5. Compare MyTracks recordings
Turn-by-Turn nav is a nice way to view accuracy BUT it has no way to record measurements. Comparing devices with a tool like Googles MyTracks is the only way to show that the captivate GPS sucks or not - maybe other phones suck too in certain environments.
This same methodology should be used before and after any mods as well - otherwise it is all hearsay.
Click to expand...
Click to collapse
Are there actually people that have GPS that is consistently accurate to 10 meters or less? I can't even get a lock like that standing in one spot on a sunny day. If I don't enable wireless networks, my GPS icon will flash forever.
ChaoticKinesis said:
Are there actually people that have GPS that is consistently accurate to 10 meters or less? I can't even get a lock like that standing in one spot on a sunny day. If I don't enable wireless networks, my GPS icon will flash forever.
Click to expand...
Click to collapse
Yes, many of us has GPS that works fairly well. I have had my phone since launch and running the stock GPS config.... it works OK.
My GPS is an A. I got a replacement and has worked perfectly since.
Sent from my GT-I9000 using XDA App
ChaoticKinesis said:
Are there actually people that have GPS that is consistently accurate to 10 meters or less? I can't even get a lock like that standing in one spot on a sunny day. If I don't enable wireless networks, my GPS icon will flash forever.
Click to expand...
Click to collapse
Results are extremely variable. Your phone sounds like mine. By trial and error I have gotten mine to an "A", but only by doing these four things 1) flashing new ROM - Assonance (5.0), 2) installing Da_g's GPS fix, 3) Removing the rear cover and just using my Bodyglove cover, and 4) when in the car plugging into car charger.
There are other solutions and reported good results from other ROMs and methods, but these are the things that work for me. I have done extensive testing with each of the four items, including MyTracks recordings, to validate the impact they each have. Good luck with yours - it IS possible to get a working system.
Mines grade b at most.
Sent from my SAMSUNG-SGH-I897 using XDA App
Where can I get this Da_G fix? I'm using Assonance 5.2 and it works fairly well - about a C+ or B I guess. I tried searching XDA for the Da_G fix and couldnt find anything
PixelPerfect3 said:
Where can I get this Da_G fix? I'm using Assonance 5.2 and it works fairly well - about a C+ or B I guess. I tried searching XDA for the Da_G fix and couldnt find anything
Click to expand...
Click to collapse
You can get Da_G's fix at the post below. Three options - I have been using the Google version and had good success with it.
http://forum.xda-developers.com/showthread.php?t=881941
I've owned a GSM Galaxy Nexus (Samsung i9250) with JB 4.2.1.
The one deficiency that I didn't initially notice is the lack of decent GPS reception.
My friend have a galaxy S3 take 30seconds or less for fix gps without wifi ou 3g. The nexus make maybe 10min GPS lock on its own (no Wi-Fi required) and then would keep the lock the whole time when the phone was in my pocket.
The GPS of nexus is, quite simply, broken. It takes, on average, 5-10 minutes to get a GPS lock when standing outside with a clear view of the sky and the phone in the palm of my hand. Sometimes it takes longer but usually I give up after 10 minutes because, strangely enough, I do have a life. Unfortunately, even after this GPS lock is achieved, it loses it easily. Putting the phone in my pocket will cause the GPS lock to be lost within a few minutes, typically.
Unfortunately, it appears that I'm not the only one with the problem. This is unfortunate because this means if I call Samsung asking for a replacement phone most likely my situation will not improve.
Strangely enough, if I enable Wi-Fi and are within the vicinity of some networks, I can get a GPS lock fairly quickly. In fact, even sitting here in my condo typing this, with Wi-Fi enabled I can get a lock within a few seconds by holding the phone near the window. The phone will only see 4-5 satellites, but that's all that is needed for a 3D lock. This makes a little bit of sense because WPS probably seeds the GPS subsystem with location data so it knows exactly where to start (vs. a cold or warm start).
After searching around a little bit I found a few suggestions. One was to shut off the phone and remove the battery for a few minutes, which seemed silly since this suggestion only temporarily fixes the problem. The second, that seemed to work for a few people, was to force a cold start and redownload A-GPS data, both of which can be done using GPS Status & Toolbox, an application I've used in the past and is pretty darn neat.
Unfortunately, performing the cold start (reset) and redownloading the A-GPS data didn't work out for me. I was still left in the same situation as I was before. However, using the GPS Status & Toolbox provided me with some additional information about the GPS problems. Apparently when the Galaxy Nexus is stuck searching for a GPS lock, usually it actually does see a whole boatload of satellites, but fails to receive any data from them.
GPS lock with Wi-Fi enabled. I don't even have a clear view of the sky since I'm indoors. However, I'm standing at a window:
Why does the GPS on the Galaxy Nexus not quickly receive the second and third parts of the GPS message from any satellites when Wi-Fi is disabled? According to the first screenshot above, it can clearly be seen that a number of satellites are providing adequate signal strength, but most are just stuck in the no info stage or have only processed the first GPS message. I wish I had an answer.
I suspect the problem may be due to inadequate RF shielding of the GPS receiver inside the hardware itself. Perhaps the GPS receiver is getting a strong signal but it's too noisy and the messages are chock full of errors and can't be processed correctly. This is really only speculation, though
I tried so many things, gps.conf etc..maybe is a hardware problem ? isnt the google location server problem..
Anyone have any suggestions or comments?
hoobinho said:
I've owned a GSM Galaxy Nexus (Samsung i9250) with JB 4.2.1.
The one deficiency that I didn't initially notice is the lack of decent GPS reception.
My friend have a galaxy S3 take 30seconds or less for fix gps without wifi ou 3g. The nexus make maybe 10min GPS lock on its own (no Wi-Fi required) and then would keep the lock the whole time when the phone was in my pocket.
The GPS of nexus is, quite simply, broken. It takes, on average, 5-10 minutes to get a GPS lock when standing outside with a clear view of the sky and the phone in the palm of my hand. Sometimes it takes longer but usually I give up after 10 minutes because, strangely enough, I do have a life. Unfortunately, even after this GPS lock is achieved, it loses it easily. Putting the phone in my pocket will cause the GPS lock to be lost within a few minutes, typically.
.
Unfortunately, it appears that I'm not the only one with the problem. This is unfortunate because this means if I call Samsung asking for a replacement phone most likely my situation will not improve.
Strangely enough, if I enable Wi-Fi and are within the vicinity of some networks, I can get a GPS lock fairly quickly. In fact, even sitting here in my condo typing this, with Wi-Fi enabled I can get a lock within a few seconds by holding the phone near the window. The phone will only see 4-5 satellites, but that's all that is needed for a 3D lock. This makes a little bit of sense because WPS probably seeds the GPS subsystem with location data so it knows exactly where to start (vs. a cold or warm start).
After searching around a little bit I found a few suggestions. One was to shut off the phone and remove the battery for a few minutes, which seemed silly since this suggestion only temporarily fixes the problem. The second, that seemed to work for a few people, was to force a cold start and redownload A-GPS data, both of which can be done using GPS Status & Toolbox, an application I've used in the past and is pretty darn neat.
Unfortunately, performing the cold start (reset) and redownloading the A-GPS data didn't work out for me. I was still left in the same situation as I was before. However, using the GPS Status & Toolbox provided me with some additional information about the GPS problems. Apparently when the Galaxy Nexus is stuck searching for a GPS lock, usually it actually does see a whole boatload of satellites, but fails to receive any data from them.
GPS lock with Wi-Fi enabled. I don't even have a clear view of the sky since I'm indoors. However, I'm standing at a window:
Why does the GPS on the Galaxy Nexus not quickly receive the second and third parts of the GPS message from any satellites when Wi-Fi is disabled? According to the first screenshot above, it can clearly be seen that a number of satellites are providing adequate signal strength, but most are just stuck in the no info stage or have only processed the first GPS message. I wish I had an answer.
I suspect the problem may be due to inadequate RF shielding of the GPS receiver inside the hardware itself. Perhaps the GPS receiver is getting a strong signal but it's too noisy and the messages are chock full of errors and can't be processed correctly. This is really only speculation, though
I tried so many things, gps.conf etc..maybe is a hardware problem ? isnt the google location server problem..
Anyone have any suggestions or comments?
Click to expand...
Click to collapse
Hoobinho,
I'm having the same problem.
I'm pretty sure it's software related, because 4.1.2 worked very nice with GPS. This issue started after 4.2, and continues with 4.2.1. I will roll back to 4.1.2 as soon as I have time to do it, and stay there until Google fixes it.
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.
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.
Ever since updating my phone to Nought we're getting speed readings of 4-7 meters per second (which translate to speeds of around 22-25km/h) when before the update we used to get normal, realistic speeds.
Comparing with other GPS test apps out there, they are showing same result so it's not necessarily an implementations issue. Looking at running apps like runkeeper, mapmyrun, endomondo and such - they are giving correct pace calculation.
As of now I can't seem to pin point the source of the problem - GPS apps are showing high readings like my own app but running apps seem to overcome this issue.
Did anyone encounter such a phenomena, when upgrading to android N? My phone is Galaxy S6, upgraded from android M (Where it worked fine) to N where it started reading much higher values
I have the same problem on my S6 when I upgraded to N. I have a t-mobile S6.
I'll be hiking at 4 mph but GPS Status and my hiking app (Oruxmaps) will showing current speed as like 11-12 mph. Yet, my average speed in the app and the speed in my track statistics when i stop recording comes out ok.
I don't know what the heck is going on.