← Back to topic list

The inbuilt maps doesn’t seem to want to avoid tolls

RespectibleCabbage | 2025-10-17 06:58 | 2 views

In the maps app I have the “avoid tolls” option checked but no matter what I do it just seems to completely ignore that. I’m in Melbourne at the moment for reference, and putting in a destination in port Melbourne for example it wants me to take Citilink all the way. It even says “via Citilink” above the Start button when you enter the destination. Is this just me? Is this working properly for anyone else? EDIT: Also if I hit the alternative routes button there are zero. Google maps on my phone gives me 4 options, none of which are via Citilink…

Comments (18)
xxx_ 2025-10-17 07:15

Do you not like waze?

RespectibleCabbage 2025-10-17 07:27

I do, but my wife doesn’t want to connect her phone to the car most of the time so the inbuilt maps needs to work

red_dragin 2025-10-17 07:47

Same problem in Brisbane

get_in_there_lewis 2025-10-17 08:07

You what?

RespectibleCabbage 2025-10-17 08:19

Ok sweet, not just me at least. Must just be another bug

red_dragin 2025-10-17 08:53

Yeah I don't even bother using it now. The routing was average before the update anyway.

RespectibleCabbage 2025-10-17 09:07

So it’s not using google in the backend for routing? Wasn’t sure if it was a custom thing or just a skinned google maps like Tesla does

red_dragin 2025-10-17 09:30

It uses the traffic data from Google I believe, but does its own routing.

SexyDraenei 2025-10-17 11:14

people use inbuilt nav?

SexyDraenei 2025-10-17 11:15

you say that like connecting is some kind of elaborate chore rather than just having to be in the car

RespectibleCabbage 2025-10-17 11:23

Ok. Regardless of my wife’s weird habits, the inbuilt nav still doesn’t work properly and personally I’d rather it did, call me crazy.

LammersTim 2025-10-17 12:01

I thought so too. But I did a direct comparison of inbuilt and Apple CarPlay google maps (while stuck in traffic). It definitely was not the same. The traffic in google maps actually was accurate, while in built was very bad/old/delayed (not sure where it got its data from). I’ll only be using in built when I know traffic is low and I need an ev charger.

A_Ram 2025-10-17 12:54

You can clear the app cache and data. Long press on the nav icon, go to app info and clear them both. This worked for me.

edgarcillo 2025-10-17 17:12

The inbuilt map is really bad, some times it shows directions through streets that are close, not sure from where the get their info but I don't think it is Google maps as directions could be really different

woodman8u 2025-10-20 02:31

The inbuilt Nav program I really like. Especially the ability to find charges and determine the range. I had the same issue with it ignoring the "Avoid Toll Roads" Here is the fix. You are welcome. Under "EV Trip Preferemces" Turn OFF "Automatically Add Charging Stations" Solved the issue for me.

RespectibleCabbage 2025-10-24 21:02

Hey you’re right, that did actually work, thanks

Numerous-Implement47 2025-10-29 21:57

Or if you do want it to re-adjust on the go for charging stations which likely routes you on to toll roads then set the battery level low.

Numerous-Implement47 2025-10-29 22:03

I do like sometimes having the full screen inbuilt navigation map showing, but turn off the volume for it, and waze is launching in background so I get the voice prompts from that around speed cameras, congestion etc. Not the biggest fan of the waze map itself in AA. Definitely trust waze more for directions, though since update to in built have found its pretty close, when you turn off or adjust the find charger automatically setting.

Add comment

Login is required to comment.

Login with Google