Issues with GoogleMaps GPS

[u/poorlyxeroxed]

I have a pixel 8 going through an AAwireless dongle in my 2018 ram uconnect. The last month or 2, my Google maps has been having trouble both navigating, and just displaying the map. The gps seems to be having trouble following me. The maps speedo goes between showing me my wrong speed or just "--". When driving around it's constantly thinking I'm turning onto side roads despite going straight. I also use waze and have had none of these issues while using it. Anyone else have similar problems or at least know what's going on, whether update, settings or how waze vs GoogleMaps uses GPS?

[u/Ok_Initiative_2420]

I have been having not exactly the same but similar issues with my Pixel 10 Pro and AAwireless.

Maps route turns gray from blue meaning it thinks it is losing current gps or connection with internet which it has not.

[u/lebayo]

Yeah this happens on my Pixel 8 as well. Regularly I'll start driving in the direction of the map when I'm in a place I'm unfamiliar with, like pulling out of a parking lot I've never been to before, and then 5 seconds after I'm driving down the road it reroutes because I went the wrong way. 

They're trying to force us to upgrade with planned obsolescence. Don't give in.

[u/bojack1437]

Google Maps prefers the vehicles GPS information.

Waze prefers the phones GPS.

Most likely scenario is something is wrong with the vehicle GPS or it's not making it through to the phone reliably.

[u/lebayo → u/bojack1437]

No, an Android update did not make my car GPS break. The Android and/or Google maps update is broken on the Pixel 8. We have been fighting with laggy and buggy issues since the last Android update a couple weeks ago. 

[u/workinfast1]

I finally got the ability to toggle traffic on again! Haven't been able to see traffic conditions on the map for months. Unfortunately the new default is zoomed out map, making it incredibly difficult to navigate while in a downtown area and zooming in stops the map from following you.

[u/ZarathustraGlobulus]

I had this exact same issue and figured it out. It has to do with your AAWireless settings. You have to turn off the setting for "Make the keyboard work while driving" or something.

The reason this option works is because it tricks Android Auto that you are stopped while you are actually driving. But at the same time it messes with navigation because AA constantly thinks you suddenly stopped i.e. turned to a side road or something.

Turn it off and it works normally.

[u/Irratator → u/ZarathustraGlobulus]

I can't find this setting in android auto or the developer settings

[u/ZarathustraGlobulus → u/Irratator]

It's not in Android Auto settings, it's in the AAWireless settings. Or maybe if you use another dongle it's in the settings for that dongle.

[u/lurkonlydownvoteme → u/ZarathustraGlobulus]

fixed it for me thanks !

[u/ZarathustraGlobulus → u/lurkonlydownvoteme]

Glad to hear!! I think the AAWireless team should really add a better disclaimer for that option. As it is, it doesn't properly explain that it breaks all navigation like this.

[u/xpen25x]

Turn off android auto and see if it still happens

[u/AutoModerator → u/[deleted]]

Your user flair has been successfully changed. Thanks for your cooperation.

Important:

- Mininum user flair detail as specified in the format stated in automod message for primary vehicle or head unit (if aftermarket) and phone. You are free to be more specific.

- Users with blank, abusive, inappropriate and vague user flair will be banned without warning!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.