@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.

@Mark-Thomas-3 as indicated in the previous response, you have to make the change in the options section in the App.

@Ton-Machielsen same Problem also on Android-Auto

@Rob-Kelley said in Not zooming in on junctions: I would be good if it briefly flashed up on the screen which view mode it was in when tapping the compass. That's actually not a bad idea. It happens more often that people are confused by this.

@Herman-Veldhuizen said in App does recalculate despite recalculation setting being off: Then while driving I need to see the ETA to the next possible stop. Yes that's what I meant of course, the first stop in line. Let's see if devs (they are reading along) see a possibility to a plausible solution for you.

@Corjan-Meijerink : Bedankt voor je reactie. Ik heb een support ticket aangemaakt met alle gevraagde info toegevoegd.

@Corjan-Meijerink Thanks.

@borde-0 graag gedaan

@white-mouse-on-the-motorbike if you are using an Android device, check if Animations are turned off from system settings ! Same happened to me, and everything is working fine after enabling animations.

@Angelo-d op die manier machtig je de incasso

@white-mouse-on-the-motorbike Dank je!

I don't see the 377 number when looking at my installed app in settings. The version number (in this case '4.3.4 - 377') can be seen in the account screen within the app: Menu (top left) -> Account (top right) scroll to the bottom You won't see the full version info in Google Play Store. [image: 1735063661673-version.jpg]

@M-Schrijver That's what threw me, the original settings that I had on the phone worked well with Waze, and Google maps, but affected MRA, which made me feel I was doing something wrong in the app. Trouble is I don't like messing about too much with phone settings, as before I know it I've buggered everything up.

I did some more tests and probably figured out what was going on. Here are my thoughts: When creating a route with the web planner, the calculated result is supplemented with "hidden shaping points" (similar to the GPX 1.2 format) to store and preserve its shape. An imported track (route track) gets its shape from the (typically huge amount of) track points. Let's call this the "original shape". Opening such a route or track with the navigation app shows its original shape as a preview. When starting navigation, the original shape is drawn on the map as a white line. On top of it, a route will be calculated using strictly HERE data that follows the original shape as closely as possible. The result is drawn as a blue line. If white and blue match, we see just a blue line; otherwise, both. If a part of the blue lines deviates too far from the white line, it will be cut and replaced by a straight line. The same happens when deviating during the navigation: the blue line will be recalculated and leads back (or close) to the white line. All turn indications refer to the blue line, not the white line. So, we are not navigating a pre-calculated route or track; we are actually navigating a route that is calculated on top of it and is always based on HERE data. I'm curious about any feedback. Am I right? Or, if wrong, what's then going on?

@M-Schrijver when navigating an offroad road as track, the original track data is used. However, as the entire route is marked as offroad, there is no track data. The track data is just straight lines between all waypoints The app does calculate a nice route to the nearest point on the track. Therefore you get a correct route to a point on the track and then just straight lines as the offroad route has no information.

I haven't used lane assist very often so far. For some tests, I gave it a go yesterday on a 50 km trip with a mix of highway, overland and cities around Hamburg / Germany. About 30 % of all lane assists were not exact or downright misleading. I turned lane assist off again...