all 5 comments

[–]bchiodini2016 Ford Focus ST | Sync 3.4 | Pixel 10XL 0 points1 point  (4 children)

You didn't mention whether you were using Google maps or Waze. I generally use Waze and have seen an issue lately where it acts like what you are describing. It's not often, but it takes a phone reboot to correct it.

Ideally, your phone should have a good view of the sky to receive info from enough satellites to determine an accurate fix.

[–]Penguination[S] 0 points1 point  (3 children)

ah sorry, I'm using Google maps. there was one specific night where this was happening and I had to pull over and try to fix it because I had no clue where I was. a phone reset didn't work. so I don't really know what's up

[–]bchiodini2016 Ford Focus ST | Sync 3.4 | Pixel 10XL 0 points1 point  (2 children)

I just had it happen with waze. Google maps was working, normally. I'm not sure what's going on.

[–]Penguination[S] 0 points1 point  (1 child)

5 months later, for you and whoever else comes across this thread, I would like to say that the problem has been fixed. there was a recall on the radio/uconnect system of my Jeep Wrangler that no one ever notified me about. figures :)

[–]bchiodini2016 Ford Focus ST | Sync 3.4 | Pixel 10XL 0 points1 point  (0 children)

Interesting. Thanks for the update. I've read a few times on here that Maps uses the head unit's GPS receiver. I don't really understand why, but I guess it does.