@Con-Hennekens I agree, it could be an elegant solution for this problem without changing the internal algorithms in dynamic mode. The question is whether it can be changed effectively without breaking the ride.

I started using android auto with MRA in my car (xc40) a few days ago, because I wanted to see how it works before i used it on the carpuride. I must agree on issues with the zoom option. I think it is mainly caused by the difference in screen resolution and sizing if you compare phone and device. But I do miss a zoom option on the android auto screen and an option to move around the map, with finger and pinching ,like Google maps can, to look a bit around on the map for example when stopped.

@Corjan-Meijerink I cleared the Nav app's Cache and that fixed the problem. I can can now click the cancel button.

@richtea999 Thanks for the suggestion! It worked! Looks like it was a glitch. Top man [image: 1739876734733-screenshot_2025-02-18-11-04-25-20_246e9b1fecab93db9692b019fd6b6299.jpg] [image: 1739876732834-screenshot_2025-02-18-11-04-08-13_246e9b1fecab93db9692b019fd6b6299.jpg]

@Nick-Carthew thanks Nick, it's a strange one as there is no lag on Google maps, TTGo or Sygic. I'll keep messing around with the settings to try to solve it as the integrated native of the app with the excellent planner appeals to me.

@Herman-Veldhuizen My test route: https://www.myrouteapp.com/route/open/10551424 On this route with 8 waypoints I have seen the following behaviour and the behavior is constant, driving at approximately 50km/h. Listed below are the waypoint numbers, the distances from the previous waypoint, the message spoken before or at that waypoint (or not in strikehrough ) 1 2, 1130m, "Upcoming", "Reached" 3, 440m, "Upcoming", "Reached" 4, 780m, "Upcoming", "Reached" 5, 630m, "Upcoming", "Reached" 6, 2100m, "Upcoming", "Reached" 7, 600m, "Upcoming", "Reached" 8, 3220m, "Upcoming", "Reached" 150m TOO early I can understand that I don't get the "Upcoming" message at 3, 4, 5 and 7 if the minimal distance is hard coded to be 750m (waypoint 4 is on the edge of this distance). However I do not understand that I do not get the "Upcoming" message for waypoints 6 and 8. The distance to their previous waypoints is quite large. Also I would have expected the "Reached" message for 3 and 7. When driving slowly (or cycling) there is plenty of time to speak this message. The other thing which is strange is that I get the "Reached" message far too early for the last waypoint. And I get this too early each time. [image: 1739471601158-screenshot_20250213-193228_gallery-resized.jpg]

@b0hd1 yes! Not really sure if I can learn anything from this as it evidently was a device issue. But well! Glad you are up and running.

@Con-Hennekens that's what @Corjan-Meijerink said above. In top of that the amount of space needed on your phone for the offline maps is not that big zo why take the chance of mishaps occurring by putting them on an sd card. I stopped using the sd card for that purpose

@Corjan-Meijerink hier loopt die nog steeds vrijwel dagelijks vast. Ik heb al meerdere meldingen gemaakt via TestFlight. MRA is steeds actief op de achtergrond en wordt niet gebruikt. De melding zie ik steeds na het uitstappen als ik m'n telefoon weer heb gepakt.

@Herman-Veldhuizen said in Definition of nearest point on track: Having to zoom out and check what MRA has come up with after each restart is not really a motivating solution. That's just a question of habit I think. I never leave without having seen for myself I am going in the right direction.

@white-mouse Ist das wirklich so? Die anderen Navis können den Zoom ändern! Liebe Grüße

Mijn vrouw heeft het zelfde. Haar abbo beëindigen we deze maand hierom. Het werkt immers niet. Zij heeft ook/ kan ook géén kaarten downloaden om de zelfde reden (geen internet). Mijn online functie (route rijden & kaarten downloaden) heeft het bij de aanvang van m'n abbo wél gedaan en daarbij heb ik gelijk kaarten gedownload. Ik kan dus off-line wel MRA gebruiken. Weliswaar met oudere off-line kaarten maar toch. Bij ons zou het de VPN van ons werk zijn (beide zelfde werkgever) volgens MRA helpdesk. Erg jammer van mijn live-time Gold abbo, en ik was zo enthousiast:(. Ik vindt het raar dat het eerst wél werkte. Een update moet dit dus de nek hebben omgedraaid. "We" kunnen dus niet op de Here server komen. Dát is het issue.

Dat is mij bekend. Ik vergelijk de routes altijd met de Here en TomTom kaart. Dus de extra benodigde punten staan er ook al. Het omschakelen is dus niet het grootste probleem. Was alleen verbaasd dat deze aanpassing was doorgevoerd.

@Albyus You’re replying to a 2 year old Caraplay post with a gripe about AndroidAuto!

@Harv-0 nothing changed in the app. The Android specific settings for the app might have changed not allowing the app to keep the screen on.

@Francisco-j-0 wat voor telefoon heb je want in een Android telefoon zou je voor de Google tts moeten kunnen kiezen

@Rajp If you ever ride it again, feel free to turn on screen recording Sharing that file could be interesting. If it's not closed that's fine but I mean that it is marked as such by HERE. When that's indeed incorrect that can be reported here: https://mapfeedback.here.com/#/report