@M-Schrijver Ik heb dezelfde ervaringen en kan je antwoord dus alleen maar bevestigen als MRA- en TomTom-gebruiker.

@GT-JWR To clarify, in my case it was an endless freeze even if I restarted the app, which I did several times. As long as I stayed in that same area the app would freeze as soon as I tried to start navigation. I also don't think in my case it had to do with WiFi as I had downloaded the routes and I had the phone in airplane mode, since I was touring in France and trying to avoid roaming. That being said, I also tried disabling airplane mode and connecting to the mobile network to see if that would make a difference, but the app would still freeze every time, becoming completely unresponsive. Only moving somewhere else and then restarting the app would fix it.

@Herko-ter-Horst said in Melden fout in HERE kaart: @Hans-De-Geest Je kunt dit direct bij HERE melden, via: https://mapfeedback.here.com Ik heb goede ervaringen met HERE. Je kan ook zelf wijzigingen aanbrengen. Dat heb ik enkele malen gedaan en werd binenn enkele weken door HERE opgepakt en verwerkt in de HERE kaart.

@Thomas-Keßler Happy to hear it worked for you.

@Con-Hennekens dank

@Peter-Schiefer said in Carplay Problem Ton bei Unterbrechung der Verbindung.: Unterwegs auf Apple Maps umgeschaltet, aber auch hier kein Ton. Is this not a clear indication that the problem is in your hardware, and not in the app?

@Kudee, Yes, the MRA app also immediately recalculates once you deviate from it. Similar to Google Maps. if you use a direct route (that also means NO curvy options!) it will calculate the quickest routes to the finish, just like Google Maps. if you are navigating a track (that includes a A2B route using curvy options) it will redirect you to the track in a logical manner. But not everyone's logic is the same if you are navigating a route with waypoints, it will use an algorithm to decide to which next waypoint you will be redirected. This happens at the third recalculation. It is assumed that when you meticulously plan a route, you will want to ride as much as possible of it. Therefore you are not immediately redirected to the next waypoint indeed, but only after the second recalculation. It then goes to the closest waypoint ahead in the route. That CAN still be the same waypoint, but can also be one of the next waypoints (with a maximum of 10). Iirc after 5 recalculations it will not try to reach the same waypoint anymore, but usually it will have skipped it by that time anyway. For situations in which you want to skip waypoints quicker, there is a convenient button on the screen. Personally I think this is way better than needing to revert to previously unintended auto skipped waypoints, because there is no convenient way to do that without stopping.

@Makro, What I remember from my Zumo 660 and 390 is that there really was no logic at autoskip at all. If you missed a point, it simple went to the next, not considering anything. Maybe if you are used to that, you consider that to be better, but I personally don't. I don't know though if things got better on the newer Zumo's. Maybe you can tell the logic behind the XT skipping waypoints? The philosophy behind the skipping algorithm is that you want to ride as much of the route as possible. Hence it does not immediately skip at the first occasion.

also on android i have same thing. only option is totaly clean apps and start app again. this is not what i like but it happens.

@Simon-Reeve, Even when roaming, your off-line maps will take priority over on-line maps. So I still think that is the culprit. Try updating them and see if it helps.

@Dikke-Wim Great! I will be going on a 7 day roadtrip starting 22nd June through the vosgezen, alps, Dolomites and black Forrest. Really anxious to see what curves CRN will throw at me but after that i should really know it a lot better. Will share my experiences.

@Corjan-Meijerink said in Behavior if a read closures reported: @TomOnTour I'd need to think about this slightly longer So it really kinda makes sense that even when you drive on a closed road, the active navigation guidance wants to minimise the penalty. Therefore you'd have to turn around until it's better to just cross it. This is a decision that we do not make How this "issue" can be fixed is not obvious to be fair. Hi Corjan, I would disagree with you on that. In the case I described the problem was not, that I was driving a closed road, but the information coming from the traffic data was just wrong: Hundreds of people have been using this route and it just wasn‘t closed. I think it is just fair to assume, that if I use a closed road, that I know what I do and I am allowed to do so. What about alle the special cases in France and Italy, where you can apply for special permits to use specific (mostly off-road) roads and tracks? The assumption should be, that if I can access the road it is usable for me! Greetings Thomas

@Marinus-van-Deudekom, niet iemand zijn hobby dus, maar eerder activisme. Geen belediging aan Putin kan misplaatst zijn . Maar iets aan die tekst lijkt eerder het omgekeerde. MIsschien wel Poetin's eigen "hackers".

@Corjan-Meijerink als ik oude android app hou en ook de kaarten op sd blijft dat dan offline werken ? ik heb ook beperkte ruimte en ik begrijp dat oplossing nog wel lang kan duren.

@Greenham said in Restarting a route that didn't: If I had force closed MRA reopened are you saying it would have picked up where it left off (Stopped moving) and started again? Yes, if you force-close the app and restart afterwards, you get the question if you want to resume the route. If press "navigate" there, the route resumes from the waypoint it was going to when you force-closed it. If you press NO instead and restart the route, it will go to WP1 and you will need to press and hold the desired next waypoint indeed. Have a nice trip!

@Erdna very nice trip beautiful roads...

@Zijderhand, Als tolpoorten invloed hebben op je navigatie, dan kan dat eigenlijk alleen maar een hardware issue zijn. Ik heb wel eens vaker gekke dingen gehoord over tolpoortjes, maar vind het wel interessant om te weten of dit ook bij anderen tot problemen leidt. Krijg je bij het instellen van meerdere meldingen eerder een melding? Ja, extra meldingen komen éérder dan de feitelijke afslag. Erna heeft namelijk niet zoveel zin

@BFG happy it works. Good luck.

@Bouke-Ent, @M-Schrijver, @Harry , Dat klopt inderdaad, óók bij een track is de start een VIA punt. Dat roept inderdaad wel wat vragen op, vooral omdat je bij het rijden van een track géén routepunten kunt overslaan. Het overslaan van het startpunt zou tot de snelst mogelijke route naar het eindpunt leiden, en dan ben je weer terug bij het "Garmin dilemma" dat je routeberekening uit zou moeten kunnen zetten. Wat een Garmin vervolgens wèl doet is dat het niet uitmaakt op welk punt je de track "raakt", hij zal vanaf dat punt de track vervolgen. Misschien is dat iets wat implementeerbaar is @Corjan-Meijerink?

@Marinus-van-Deudekom said in How can I make poi's visible on routes.: @Leike-Lodiers als je die hebt geïmporteerd kun je die ineens zichtbaar maken. Maar niet in een route! Ze staan wel allemaal in je bieb maar moet ze wel handmatig één voor één toevoegen aan de route die je wilt navigeren. Dat zou wellicht handiger kunnen.