@David-MP, in all honesty, I never found the traffic feature disturbing through any of my scenic rides. Usually scenic rides are not very prone to traffic jams anyway. I would certainly not let myself be put off the MRA app based on experience in not very likely conditions. Try it in reality, on your bike, with real scenic routes. I think you will be convinced! 😉

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

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

Screenshot_20250213-193228_Gallery.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.

@richtea999 Thanks for the suggestion! It worked! Looks like it was a glitch. Top man 🍻

Screenshot_2025-02-18-11-04-25-20_246e9b1fecab93db9692b019fd6b6299.jpg Screenshot_2025-02-18-11-04-08-13_246e9b1fecab93db9692b019fd6b6299.jpg

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

@Leike-Lodiers the issue is immersive full screen has been added which removes the Android Navigation Buttons and hides the top status bar.

To access the Buttons or Status bar you have to wipe down from the top or swipe up from the bottom. The problem I have is that when I do so the map moves.

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.

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

@JP-d Exactly! It happens to me as well.