@Corjan-Meijerink excellent, thanks for the speedy reply.

@Next-Stop nice!

@ginogino, That is not so much a MyRoute-app problem, but more like an Android Auto problem (which Carplay suffers from as much). If you are navigating "routes as track", on your phone you can simply long press ahead of your position anywhere on the track line. That will be your first calculated track entry point. AA/CP wil follow there, so you can put away your phone again.

Yesterday I navigated the test track again, using MRA version 4.3.6. The same recalculation happened just after re-joining the track. @Corjan-Meijerink Have you found the cause of this problem?

@Han-Jansen-0 Interesting. It should work if you've used "navigate route-as-track" (as you said). There is a violation stated at Point 8, probably caused by the ferry connection: [image: 1738499669522-ferry-2.jpg] You might want to add an "offroad" waypoint to avoid this. [image: 1738499698254-ferry.jpg]

@Jörgen hallo Jörgen, ja diese Einträge sind alle auch auf deutsch eingestellt..somit werde ich ein Ticket erstellen..Danke und lieben Gruss René

@Con-Hennekens Thanks. I guess we will have to get used to it. I do not think Apple will do anything about that anytime soon.

@Barto fijn dat het is opgelost

https://www.myrouteapp.com/nl/social/route/10479084?mode=share

@Mark-Hamilton-0 Awesome!

@Rob-Coblens ik had dit probleem ook dat er alleen Aziatisch gesproken werd. uiteindelijk TTSengine Android gekozen en alles opnieuw opgestart. Werkt naar behoren. Waarom dit ineens niet werkte begrijp ik niet.

@John-S-Parry said in MRA and Garmin XT2 / Tread: Why is the MRA Connector preferable to a straight copy into the XT2 GPX folder? Basically you do the same thing, just with fewer steps.

Het heeft even geduurd, maar ben er achter. Wanneer ik via Safari werk kan ik de kaarten van Google wel selecteren maar zie geen kaart. enkel de route. Wanneer ik via Chrome werk, werkt alles wel zoals het hoort. bedankt voor de reacties...

@Marinus-van-Deudekom ik druk op het hamburger menu en vervolgens routes en tracklogs. Die synchroniseer ik. maar helaas staat de notificatie er nog steeds. Gr Roel

@Nick-Carthew thanks Nick.

@Corjan-Meijerink Thanks for the response. It works, wired. But wireless tends to crash. Is it due to the version that I am not able to see the exit graphic on the AA? I can see the image of an exit on the phone, but not on the AA screen. Also, I don't see any nearby fuel station icon on the AA. It would be great if I could see that on the AA screen, as I can simply tap on that to find what's nearby. Another issue I noticed on the phone is that while searching, the search results are blocked by the keyboard. It would be great if it could be resolved. Usually on other apps, either the search option resides on top of the screen. Thanks for the great app. I am enjoying it among the other 5 I use.

@peha no worries Glad we got it resolved!

@Herman-Veldhuizen Thanks for letting me know!

@Thomas-Neumeyer I have been testing on both iOS 18 and Android 15 and usually set 'Route as Track' on my Android device. Not experienced any issues with this setting except when I have a weak signal and the app is calculating the conversion of the route to track. The calculation can take a little more time than usual when offline and, as the videos have explained, the track may not always be exactly calculated to the route when 'offline' - there can be deviations. As @Con-Hennekens has suggested, it would be useful to see the route you have been trying to use for the 'route to track' to provide us with a little more context.