@richtea999 said:

It doesn't offer an explanation as to why the planned route is being deviated from.

@Con-Hennekens said:

@richtea999, I think it is rather clear what happened. WP2 has been skipped.

'Why' and 'what' aren't the same thing.
Jem knew what happened - but not why. That was my long-winded point. 🙂

If the router knows the original route is closed/jammed with traffic, then ideally it should let the user know and, even better, give a choice of what to do next.

It may be that HERE router doesn't give that information, but if it does it would be brilliant to see it.

Made two road trips last weeks with my BMW Z4 which has Apple CarPlay unit installed. I reported cut-off audio nav messages before, but I used the tip to do a parallel audio streaming (Spotify) and it looks like that indeed this is a working patch to have the audio nav instructions completely instead of cut-off! Although this is not a real solution I assume, but for the time being is works 🙂

@Andrew

Thanks, Android Auto and Apple Carplay are still being worked on

@AWDC-LAO

Zeker als je altijd het spoor gebruikt, zeker bij off-road, is een TourGuide een uitkomst

@Corjan-Meijerink : Hey Corjan, seit ihr wieder an Bord und auch aktiv, wie siehts denn wohl in Zukunft aus mit den hier noch mal erfassten Punkte.

Ich freue mich über eine kurze Rückmeldung !!

VG Hubert

@Roger-Doidge said in Going from Beta to public version.:

When I went back to the Play store it only offered me the beta version.

Just supposing, at some future point in time, you want to stop using the beta version, you have to actively leave the beta program. In Google's Play Store, go to the MRA app page, scroll down the page to the 'You're a beta tester' section, and then 'Leave' (see screenshot below).

You can rejoin the beta again at any time, so apart from losing your app data, it is risk-free.

But as Nick suggests, the beta versions have been stable and actively useful in the past few months compared to the live version.

Screenshot_20230726_163111_Google Play Store.jpg

Thank you both Nick and Rob. I hadn’t understood about the Overlay and Planning maps. I have set the Planning map to HERE format and will give it a try but it looks good.
I am a bit surprised it isn’t set as the default instead of OpenStreetMaps as that is what the nav system uses.

@Rafał-Pach
Have you already tried to change the language selection once and return it to your desired language?

If that those't help, it might be better to create a service ticket for this.

@Carmen-7 Das grappig Carmen
Ik gebruik mijn Samsung S20FE als backup voor mijn XT omdat die nu juist een bende maakt van omleidingen.
Met mijn Samsung kom ik perfect terug op de geplande route.
Misschien dat je jouw telefoon type wil delen

It's worth re-iterating the difference between the two types of 'waypoint' - also known as route points (thanks Nick!):

'shaping' point (an inverted raindrop):
shaping point.png 'via' point (a hand):
waypoint.png

The routing logic forces the route to pass through 'via' points (how close is not clear to me - answers on a postcard please). If you miss it, it will continue to route you back to it regardless of how round-about the route becomes.

Two solutions:

As the other commenters say you need to move the tip of the 'via' point onto the black track, or Swap it back to a 'shaping' point, then you can pass nearby, not exactly through it, and the routing will behave as you expected

@Harley-Stammtisch-Münster
Hi . I've been having the same issues with android auto and found a work around that's very helpful. I use another app called Macrodroid which let's me execute phone functions at specific occurances. In other words, I set a macro in the app to turn the screen on, then start myroute app, then turn the screen off whenever it connects to my car. No more reaching for the phone prior to connecting to the car. I now just start the car, wait for the android auto icon to light up on my dash and away I go. Loading routes is still an issue on the car screen but hopefully that will be fixed in the next update.

If however the route calculation fails because the online servers cannot be used due to no internet, it will suggest turning on the offline mode 😉

@Corjan-Meijerink OK thanks. I look forwards to the update.

@Lynchy67 Das Problem tritt bei mir auch öfter auf. Es liegt also nicht an mir oder meinen Einstellungen. Auch ich bekomme keinerlei Fehlermeldungen oder Absturzberichte.

The problem happens to me more often too. So it's not me or my settings. I don't get any error messages or crash reports either.

Gibt es mittlerweile neue Erkenntnisse?

Are there any new discoveries?

Gruß, Holger
Kind Regards, Holger

@GT-JWR I don't use car play or android auto.

@Corjan-Meijerink ik hoop dat er wat uit komt

These short-term closures due to storms or other reasons are not a problem from MRA. The map supplier (HERE) is responsible for this. Such closures have to be reported first, and then someone has to enter them. This sometimes takes a few days (I noticed this here at a construction site). In Google, TomTom and Here it took one to five days.
And especially in the case of such storm closures, they are reopened more quickly than they are visible on the maps.
These are all things that navigation users have to live with. It may help to use local information or apps for such things.