@Con-Hennekens As I mentioned in my previous post last week, we discussed this issue extensively in this forum, and no one mentioned that it was an inherent problem with Here. In fact, I personally was unaware until you mentioned it that the problem stemmed from Here and its behavior. I was already wondering why the only solution was to zoom out and manually skip points to the next real point on your pre-designed route. In that case, let's hope Here corrects this issue and the improvement can be implemented in future versions of MRA.

i use comaps when i use osm maps and that app uses kml or kmz. with import it is not always the same. so maybe export kmz will give better result.

@Con-Hennekens It worked, but it sure is a PITA to do...

@ginogino ((If, instead, you start it from the app outside of Android Auto by activating the "Start from nearest waypoint" and "Use current location" options, navigation will correctly start from the nearest waypoint, which is in the direction of the route's end.)) I'm sorry, I disagree with my opinion about this part of your answer. Last week we were discussing this point in another post on this forum... and it was concluded after much discussion that in both iOS and Android, if you activate the boxes you mention, you will indeed go to the nearest point on your route (but the nearest point isn't always in the direction of the route's end). Sometimes the nearest point is very close to you (but behind you), and therefore you will go backward on your route and not towards its end... (I suggested this as an idea if it might be of interest for future updates of the navigation app)... but the only solution offered to me was that I had to manually navigate through the previous waypoints or zoom out and go directly to the next point towards the end of the route) Both solutions don't convince me. Normally, a browser should redirect only from your position to the next point (not to a previous one you've already passed) simply because it's closer.

@Jozef-Malik-0, that is already a feature in the v5.1 update (it just seems that Google is not very speedy releasing it into the PlayStore...). That is, as far as routes are concerned. Tracks (and thus the result from the roundtrip generator) will not be possible to reroute. (it would not be a track if it did).

Awesome!

Route omdraaien kan ook bij routes uit je bibliotheek. Onvermijdelijk verandert de route wel enigszins, zoals hierboven al uitgelegd.

@nomko De remotes die bij de camera horen.

Eens, hoe minder handelingen je onderweg hoeft te doen, hoe beter

Ik vermoed dat @paul-pels bedoeld of het net zo werkt als met MRA en Adroid Auto/Apple Carplay. Denk het niet als het 2 op zichzelf staande apps zijn.

Explore is de kaart die ik altijd gebruik, somlige wegen hebben bijne dezelfde kleur, dat is het een minimum verschil, ik gebruik MRA ook voor rit tracking in de auto, zodat ik snel kan kijken waar ik reeds geweest ben, soms ook op de motor.

I have been using the app for a couple of months now and moved over to gold. Pleased with it so far. I find the distance to next change of direction numbers to small to read, in the top left corner, when using a route, and ideally would like to increase in size. Is there a way of doing this please.

Lieben Dank für die Information, habe ich gerade mal ausprobiert [image: 1778433241412-bildschirmfoto-2026-05-10-um-19.13.20.jpg]

You missed something in the app. On the bottum you can swipe the buttons and there you’ll find the download Utton

For privacy sensitive information, please create a support ticket. We won't answer these specific questions on the forum. Support can see exactly which devices logged activity at which dates.

Thanks..

and you have to use a route and not track. offline track calculation is not what you want