GPS/Google Maps issue - Turn-by-turn timing is miles off

[o2bnclemson]

Two issues:

Drove a few hundred miles this weekend and used my Google Maps for navigation. The further in to the trip I got, the less accurate the turn-by-turn directions became. On the way up, it would tell me my next turn was, for example, 3 miles away, when in reality it was immediate. On the way down, I was anticipating the problem and noticed the reverse, it told me the turn was 3.5-4 miles before it actually was. The turn-by-turn was wrong, but my location on the map was correct. Thankfully, these were routes I knew fairly well and was using the GPS primarily for traffic and progress, but had they not been familiar, this could have been a real problem.

Second, and I think this is an app issue, is that I've been doing a lot of hiking and experimenting with AllTrails and Strava. On my hike this past weekend, Strava said I went 9.2 miles and AllTrails said I went 8.7 - a half mile difference!

Last, I just received an update over the weekend before my trip. My current version is 7.0. I can give you all the other stuff, but it's too much to just list not knowing what's significant and what isn't.

I'm more concerned about the Google Maps issue than the AllTrails/Strava, but would be nice to get that figured out, too.

 

[N4Newbie]

I had that problem once while driving through South Carolina a few years ago. It turned out that the limited-access roadway that I was on was quite new and the mapping was all wrong.

So, that would be my first question - were you driving on new or recently reconstructed roads?

 

[Gary_Berg]

Is it possible you don't have high accuracy turned on for location?

 

[dropoffmapdeveloper001]

As a follow up to the accuracy question, even if you have high accuracy enabled, GPS can still be inaccurate. Buildings and mountains can impede the satellite signal, causing degraded performance. This might explain your hiking observation.

Also, if your network signal is relatively poor, AGPS could be affected.

 

[o2bnclemson]

I had that problem once while driving through South Carolina a few years ago. It turned out that the limited-access roadway that I was on was quite new and the mapping was all wrong.

So, that would be my first question - were you driving on new or recently reconstructed roads?

Nope, going down well established interstates. Have driven them before with this phone without a problem.

 

[o2bnclemson]

Nope. I checked, it's on.

 

[o2bnclemson]

As a follow up to the accuracy question, even if you have high accuracy enabled, GPS can still be inaccurate. Buildings and mountains can impede the satellite signal, causing degraded performance. This might explain your hiking observation.

Also, if your network signal is relatively poor, AGPS could be affected.

For the turn-by-turn, this shouldn't be a problem. Going up to Virginia, maybe - was in a lot of mountains there. Coming home to SC, shouldn't be a problem. Much more flat there.

 

[N4Newbie]

As an aside, I generally prefer to use Waze for navigation (https://forums.androidcentral.com/e...store/apps/details?id=com.waze&token=9iQ-wm5I).

Might be worth a try.

 

[o2bnclemson]

As an aside, I generally prefer to use Waze for navigation (https://forums.androidcentral.com/e...store/apps/details?id=com.waze&token=zKsdukF1).

Might be worth a try.

It's a good option to have out there. It's just odd - I use Google Nav ALL the time and this haven't had any issues until this past weekend. Very odd. There's gotta be something causing it....

 

[android-Floyd]

You are not crazy. The same thing is happening to my android phone. Trip must be over 100 miles long... attached photos show voice about 3 miles behind.
Did you figure out a fix?

 

[o2bnclemson]

I guess it's good to know it's not just me. Nope - haven't figured anything out yet. I did get an update recently, so I'm hoping it was addressed there. Has to be an app issue, but, like you said, since it's just long trips, it may not be as apparent to some. I didn't see any mentions of this problem on the apps page in Google Play store. Hopefully they'll get it identified and fixed. It could be very dangerous!

 

[Ca_lvn]

Don't remember the specifics, but call your cell provider and ask them for your MSN number and tell them you need to reset your GPS for accuracy, it's been a couple of of years since I have done this, also Google GPS accuracy

 

[1812dave]

Don't remember the specifics, but call your cell provider and ask them for your MSN number and tell them you need to reset your GPS for accuracy, it's been a couple of of years since I have done this, also Google GPS accuracy

What would one do with an MSN number ?

 

[CWinkler]

What would one do with an MSN number ?

@Ca_lvn might mean the MIN number ... I've learned from other conversations with US Cellular that each phone has a Mobile Identification Number (MIN) which is how the network knows your phone (not by your phone number).

Find the MIN under Settings, About Device, Status, IMEI Information

 

[Ca_lvn]

To clarify it's MSL number

It's been a while so I don't remember exactly, but your carrier or your self with the MSL# Can reset your phones GPS location or it can be used for other things like Turing on Hotspot tethering, start a chat conversation with your carrier and see what happens.
Just tell them you need to reset GPS location for accuracy

 

[Ca_lvn]

https://youtu.be/qRhaUznKbLg

Do a full rotation on the screen and you'll see it Go Green when it sets for accuracy, not a partial turn like demonstrated in the video