Why does route change when connecting to Android Auto?

[Brian Martin]

Quite often after selecting a route on my Android phone then connecting to Android Auto the route changes. After carefully designing a route on my pc and syncing it to my phone and after connecting to Android Auto and Start navigation, I find part of the route sometimes gets changed. It's most frustrating as I have to keep checking the map before I start navigation to make sure my original route hasn't been altered. Anyone else have this happen?

[Rob Verhoeff]

@Brian-Martin In principle, Android Auto is a mirror of your phone, and AA will not change a route on its own. Any route changes would also occur on your phone as soon as you tap Navigate.

Could it be that you created the route using a different map than the HERE map (for example, OSM or TomTom)? Are any road closures visible on the map along the route you created? Which area does the route pass through? Is there a seasonal road closure involved?

It might be helpful to share your route in this topic so others can take a look.

[M. Schrijver]

Not especially altered. But when connecting to Android Auto after starting a route on the smartphone. MRA seems to do a sort of refresh. This does things with the route. You see things happens on your phone screen.

[Marinus van Deudekom]

That can only be the case when selecting a A B route. A route from your librairy doesn't change

[nomko]

@m.-schrijver
Did you placed enough waypoints? And what are the settings in your MRA app?
And as @rob-verhoeff said, please share the route and provide more info.

[M. Schrijver]

waypoints are not the issue. In my case the routes are not altered but when connecting to Android Auto i see things happening on the screen of the phone. It looks like MRA is bit confused whats going on.

[Herman Veldhuizen]

Could it be that there is a closed road on your route? Then the route could indeed be different than what you see in the planner and it is indeed very frustrating when you have used the HERE maps only and when timing is not the issue (navigating straight after editing).

[Atse Kroes]

@Rob-VIkerhoeff

Ik heb hetzelfde probleem. Ik lees elders dat je beter Here map kunt gebruiken. Ik heb TOTOM map gebruikt. Is het waar dat ik dus beter Here map moet gebruiken voor in de auto met MRA app te reizen?

Groet Atse Kroes

[white.mouse]

Ja. De navigatie werkt altijd met de Here map. Dus als je een route maakt met een andere kaart als laatste de route op de Here-kaart leggen en controleren.

Yes. The navigation system always uses the Here map. So if you plan a route using a different map, make sure to finalize the route on the Here map and check it.

[Brian Martin]

Thanks for the replies. I do use the here maps and I use MRA in offline mode. I shall keep monitoring the situation to see if it keeps happening. I have an existing route planned for tomorrow, so I'll see if it behaves itself or not.

[Atse Kroes]

Als ik de knop start indruk van de route dan verschijnt er een popup schermpje met de tekst; 'TomTom route Track navigatie gebruiken'
Wat betekend dit???

[Herman Veldhuizen]

Using here maps only is no guarantee that the navigation comes with the same route as what you crafted in the planner. At least that is what I have observed. Dont know where the problem is. Could it be that planner and navigation are not using the same user settings? Differences between the routing engine in the app and on the server?

[Rob Verhoeff]

@Herman-Veldhuizen Or maybe you should use more route points at critical locations! I use as few as possible, but as many as necessary...

[Con Hennekens]

@Herman-Veldhuizen said:

Could it be that planner and navigation are not using the same user settings?

No, theoretically not, since the avoidance settings in the planner replicate to the app along with the route. There can be differences in map-versions though, and also of course in trafic information.

[Con Hennekens]

@Atse-Kroes said:

Als ik de knop start indruk van de route dan verschijnt er een popup schermpje met de tekst; 'TomTom route Track navigatie gebruiken'
Wat betekend dit???

Please try to adhere to the language in the opening topic.
The message indicates that the route was planned on the TomTom map, and therefore will be navigated as a track instead of a route.

[Herman Veldhuizen]

@Con-Hennekens There are more settings. The functional navigation settings in the profile.
What I observe is that when I navigate a route as track, a closure can be ignored, but only when I navigate from the opening page of the route. When I navigate from the in-app route editor the closure is not ignored.
In areas with few roads, like here in Norway, a closure of a road can have a big impact. So what the app navigation comes up with can be very different to what you crafted in the in app editor, all with the same type of maps.

[Con Hennekens]

@Herman-Veldhuizen, I was merely referring to @atse-kroes addition.
To answer your comment, I think when you open a route in the app-planner, and the detour is already shown there, that becomes the new "original calculation" of the route.

[Herman Veldhuizen]

@Con-Hennekens not sure what you mean, but all what I am after is consistency. Ignoring closures might be the right thing to do but then i would like to see the same in the in-app route editor, without having to sprinkle my route with waypoints which don't represent anything and without having to change some settings between editing and navigating. The in-app editor is the only editor I ever use.

The images below illustrate the issue.

The first one shows my mini test route in the editor.
The 2nd and 3rd show what I can see during navigation (route as track). Sometimes the 2nd, sometimes the 3rd.

[Con Hennekens]

@Herman-Veldhuizen, Thanks for clarification. Do I understand correctly that one is opened direfrom the route menu, and the other from the in-app planner? Interesting...

[Herman Veldhuizen]

@Con-Hennekens correct.
The first one (2nd picture) from the opening page of the route (select route, navigate).
The second one (3rd picture) from the in-app editor (select route, edit, navigate).
Corjan had a look at it but I am not sure what the conclusion was.
I dont often start the navigation from the editor but in this case it would actually best match what I see during planning.