@Marinus-van-Deudekom, we know of course that there are (quite a few) restrictions by Apple and Google, but @Achim-Kaluza complaint about crashes, not about missing features. @Achim-Kaluza, nevertheless AA/CP are quite complex protocols, many things can go wrong outside of the MRA app. @Rainer-Treichel tip about trying a cable for testing purposes is certainly not a bad one. If you have a tankbag or something, it is quite easy to do. Of crashes do not occur while using a cable, we can rule out the origin of the problem being in the MRA app. Complaining in the forum is not making things better. Did you submit a supportticket already? That could be helpful in solving the issue.

@HighPeakRider I have seen odd behaviours at the end of a trip & messages that there are problems with the log. Fortunately I have not lost any as I navigate in offline mode all logs have still been in the upload que My feeling is that the log problem is secondary to an issue of the navigation failing at the end of the trip & crashing the app. I think the root problem may be to do with the introduction of the stop navigation switch at the end of journey. The log issue never used to happen.

It takes a little bit but there must be so much time, ... good thing is that it was reported fairly promptly. Best regards

Thanks for the replies guys! So I will stop looking for the hidden option to turn this on. I understand the reasoning, but would like to be able to turn this on of off. And when I pass the pause point the route time can be calculated again right. Just the same as I do a stop now and then start riding again in 30 mins, or 45 mins. Anyways... thanks for the confirmation. And on to the feature request part of the forum

@richard-crombie, Google map overlays are indeed restricted to Gold planner memberships. Are you sure you have Gold lifetime, or only Navigation lifetime? browse to: https://www.myrouteapp.com/account Scroll down and check your memberships. Mine look like this: [image: 1754313109626-78df9a81-e4c5-4e35-b3b5-8eb7cdb7f0bc-image.png]

@Simon-Cox Hi Simon, did you get this issue resolved as I have now experienced the same issue. I use a Mac and iPhone so it won't load the saved as gpx 1.1 file into Garmin XT therefore u unable to use the route in a Garmin. I have used the same process for years and no problems at all and now suddenly I am getting this issue. I have raised a support ticket as I believe it to be a fault. Many thanks. John

@Banshees, A) There is no switching maps while navigating, because Navigation is built on the HERE platform, it ONLY uses the HERE map. What you are probably confused with are the offered map-themes, but they don't influence the map-availability, only the rendering. B) A map caching facility is already in place, but just like with any on-line map provider (you named gMaps) you can run out of map data after a while C) B can be mitigated by downloading maps for offline use. Check the app settings, and download the countries you ride through beforehand.

Thanks Corjan!

This URL leads you a checklist. It should make it easier to understand the parameters you used for route planning and navigation. myrouteapp is close to being the perfect all-rounder. But that also means that the parameters you set play a role that is not taken into account in the error description. Perhaps this will make it a little easier. RT Translated with DeepL.com (free version)

I have downloaded all the maps

Het kruisen van je route gaat tegenwoordig een stuk beter dan jaren geleden. Maar inderdaad het kan problemen opleveren. Al heb ik dat met de moderne navigatie apps nog niet gemerkt.

Grazie. Trovatooooo.

@Lex.Kloet.RX said in Snelheid van route en beperkingen: @white.mouse Estimated Time of Arrival Lex, klopt. Helemaal juist. @Koen Knevel: In het oude Mapsource maar ook in Basecamp kun je voor de Garmin's de gereden snelheden aanpassen naar wegtype. Maar ik zelf heb gemerkt dat dit ook niet het beoogde resultaat opleverde. Daarom ben ik gestopt met het aanpassen daarvan en gebruik ik gewoon de standaard. Als e een aantal malen met een programma gereden hebt dan weet je zelf wel ongeveer wat het verschil is tussen de ETA tijd en de werkelijke aankomsttijd.

@Jörgen the white line is supposed to be a "track" of the "original route", I think the idea is so that when your route (blue line) on your device deviates from the planned path (because of recalculation or other factor) the "original route" (white line) allows you to easily see original planned path & where you should be The issue @Aiello-antonino & I am describing has nothing do do with maps, overlay or otherwise, it is purely down to the fact that when try to start navigating a route offline the "original route" is not always calculated correctly/accurately enough so that it matches the path of the roads I believe it is because sometimes when the file is synchronized, in the name of efficiency, less points are used to represent the "original route" If you plan a route with the Tomtom routing, then the path of the track associated with this route would naturally follow the roads in the Tomtom map I would then expect when you show the Tomtom "original route" in the navigation app with the Here map, there would could be small differences, these differences would be differences between the Here & Tomtom maps [image: 1753301598932-959bd576-0857-42bf-b6b6-f910e66f45d6-image.png]

In case you open a route, that was created AND stored with OSM-Routing active, in Navigation the track Navigation will be advised or automatically switched ON. RT

@Peter-3b Ik neem aan dat het voor iOS en android hetzelfde werkt, maar als ik inzoom tijdens het rijden dan gaat na een paar seconden het beeld automatisch in de dynamishe stand waar ik hem op heb staan. Als ik wil kan ik 1 keer op het compas icoon klikken en komt ook die view terug. Op de support pagina staat het ook zo beschreven. https://ondersteuning.myrouteapp.com/nl/support/solutions/folders/12000020339 , "App - Navigatie" . Kompas: Standaard staat de camera op dynamisch, dus gekanteld en automatisch in- en uitzoomen. Klik je een keer op het kompas, selecteer je de vaste camera. Deze is top down en behoudt het zoomlevel. Deze is wel aan te passen met het plusje of minnetje. Houd de knop langer ingedrukt en de track wordt in zijn geheel getoond. Heb je in- of uitgezoomd, klik dan ook op het kompas om weer naar de dynamische instelling terug te gaan.

https://support.google.com/nexus/answer/3467281?hl=de https://support.google.com/nexus/answer/6179507?hl=de https://support.google.com/nexus/answer/3467281?hl=de&sjid=12928737613070150242-EU

With the little info that you”ve shared I would say no, not a known issue. Maybe you can share a bit more like whatls your setup. Is there a pattern in the quiting

Further data on this issue: I turned off “background app refresh” in settings; rebooted the phone; launched MRA and killed it by swiping up. I confirmed that it is not running. I left the phone locked and idle. It is still looking for my location constantly according to the IOS battery measurements. This may only be consuming a few % of battery but it is the only app on my phone which does this. [image: 1752947447398-img_3775.jpeg]