So, I've got two devices I can use on my bike, either a phone cradle or Android Auto. With mra running, no matter which one I choose, both experience the same issues as above. Last week went to Annecy, and decided to use the simple Waze. Well, funny, I've got no issues with a hot phone, lags, or crashes, etc. Why mra needs to use so much of the phone's resources is beyond me?

I honestly can't tell you why it happened, but I can assure you I didn't accidentally disconnect... the same thing happened when the ability to automatically deactivate additional devices was implemented (if I remember correctly)... but I remember it was a normal thing... here it even synchronized my entire route database from scratch...

@ErikMatthezing The irony is that if you use Google Maps or Apple Maps, you wouldn't think (I certainly wouldn't) to verify the map against HERE, OSM, TomTom, etc. You accept the map/route is accurate and go on with your life. Somehow, we've come to believe that a checklist item in using HERE is to compare it against others maps for accuracy for everyday use. It's reality. At the same time, it's not ideal, but an aspect of MRA that all users should understand.

The same thing happened to me but on mobile devices, both iPhone and iPad, but it seems to me that if I put Google on top, this is what I think the problem is, the map doesn't respond correctly, as if the software needed more resources for a stretch and the processor couldn't handle it, then if I change the map and put MICHELIN for example, everything goes back to normal... it's been happening for a few weeks now, I even wrote about it somewhere, but it seems to me that it wasn't given too much importance... I thought it was just my problem... but apparently that's not the case...

@corjan-meijerink : any News about this Problem?

@RetiredWingMan

In settings and then audio , you can (second from the bottom) what next will speak out . Check the box all.

@Brian-McG @brian-mcg You're right. This has nothing directly to do with transferring files other than it being one of the pieces that ensure Zumos operate correctly as navigation devices. If that doesn't interest you, so be it. BTW, Garmin GPS routing algorithms have changed over the years, pre-Zumo you could take a Basecamp route calculation to the bank in that it would 100% match when recalculated in the Garmin GPS. That's no longer the case. I'm surprised you didn't know this given your "mult-multi years" Garmin experience. To the topic, this discussion has everything to do with: The HERE map not placing the road where it actually is. The MRA app recognizing the map discrepancy, but the Web Routeplanner not showing any overt alert. Sync should actually mean Sync. The MRA "Skip Waypoints automatically" enabled not working in this scenario. I was able to dynamically enable the XT3 to successfully recalculate at WP#7, so what's with the blanket "advice not to enable the recalculate function is decades old"? Nothing is absolute, yet you're hanging your hat on it. Odd. I'm trying to be transparent and reasonable, and I can say with complete honestly that the XT3 worked better than the MRA app in successfully routing the section from WP#7 to WP#8. If this had not been a verification test, and I was just routing with the XT3 (forgetting the app), I probably wouldn't have known there was a problem at all. I would have been on the straighter section on top of the mountain ridge before being able to look down at the route, and I wouldn't have seen that the XT3 handled the situation without any intervention. Again, thank you for helping me unravel what happened. We obviously don't agree on some things, but I appreciate the input you provided.

WenPlanung [image: 1783844722389-img_0241.jpeg] In der MRA Navi App Next [image: 1783844746640-img_0242.jpeg]

Het is audiofunctie van je AA headunit. Bij schermen als Chigee wordt meestal de telefoon als basis voor de audio gebruikt. En die kent de scheiding niet. Tenzij MRA je de keuze gaat geven om MRA over een ander kanaal te laten afspelen dan het standaard mediakanaal. (Wellicht een idee voor een toekomstige update). De muziek wordt nu inderdaad wat gedimd. Maar bij een echte scheiding zoals AA dat kan, kan je gewoon voor 2 verschillende volume niveaus kiezen. Je muziek relatief zacht en je navigatie juist vrij luid, of wat je voorkeur ook is. Waarbij het navigatiekanaal altijd voorrang heeft op het mediakanaal. Als het ik me goed herinner, wordt de muziek niet gedimd maar volledig stil gelegd. Bij mijn Goldwing kan ik er zelfs nog voor kiezen om de Google assistant ook een eigen volumeniveau mee te geven.

Here is a new update on that problem. Yesterday, i had that same problem again. I then closed the app on my iPhone and start it directly on the Chigee. From there, i was able to start last route and it displayed instantly. Any idea about a real solution ? Thanks

@Hans-van-de-Ven-MR.MRA ik heb gisteren een vandaag de functie uitgebreid getest. Met een AB route en afwijken van de route, hetzij doordat ik dat zelf deed naar bij wijze van toeval ook omdat ik een onverwachte afsluiting tegen kwam. In beide situaties werd herberekenen keurig volgens verwachting uitgevoerd. Ik kwam keurig op mijn route terug

@Günter-Schwarz said: Ich war jetzt mehre Tage von Deutschland nach Österreich und zurück unterwegs. Arbeite mit dem R7M Display und der Route APP Nach gefühlt einer Stunde Fahrt stürzt die App ab. Wenn ich dann neu Starte beginnt diese dann am Anfangspunkt und vor allem berechnet und verändert sie die vorgeplante Route. Bsp. zuvor ohne Autobahn geplant nach dem Absturz und Neuberechnung führt sie über die Autobahn und hat einen Teil der alten Route verworfen. Zuvor hatte ich die geplanten Routen auf mein Garmin Navi übertragen dort hat es zwar auch mit dem einen oder anderen Problem gekämpft aber in Summe funktioniert. Hey, du kannst in den Einstellungen den Startpunkt einer Route einstellen, gerade wenn man unterwegs neu starten muss ist das sinnvoll. Nachdem du auf navigieren gedrückt hast dann s. Bilder beachten , das einstellen bevor du auf Start drückst. [image: 1783405084540-img_0039.jpeg] [image: 1783405084943-img_0041.jpeg]

I've always used routes and an active tracklog, and I've had problems. I was trying to make some hypotheses to understand what the conditions are that cause the app to crash. It seems to work well with offline navigation. I don't know, but let's hope they find a solution.

@Marinus-van-Deudekom said: Did you make the route with the webplanner. I see that the route is with the Here map. I always plan my routes on the web planner, and use Here, I do compare with OSM and tom tom while making them. I also use the Michelin overlay as the Here is very wishy washy, and bad contrast. perhaps I inadvertently changed it, but I do not know why I would do that. @Brian-McG said: I think the only way to try & figure out what is occurring is if you can re-ride the route & get a repeat of the issue then save the app log file for the devs as stated above, I have ridden the route previously (3-4 times) without issue. I have sent the logs. @Brian-McG said: in fact I get the exact opposite, at every junction it is telling me to stay ON the m-way or main A-road when I have ridden the route before, that is what normally happens. For info to all, I merely put this on here as discussion point, and to highlight the behaviour, although it is good to read the differing points of view. I am touring around Ireland from Thursday, no motorway to speak of so may not see this again. @Brian-McG said: It looks like a decent ride to Hawick so should not be to much of a hard task it is a very nice route, although the road between Middleton and Alston is very uneven, not great on my K1600, almost throws me out of the seat in places, enjoyed it more when I had the GSA @marinus-van-deudekom, @Marinus-van-Deudekom said: That could be the result of the settings in NN. Could you share your settings I use fastest route in optimisation, the rest is below [image: 1783355754115-img_1231.jpeg] [image: 1783355764069-img_1232.jpeg] [image: 1783356048716-screenshot-2026-07-06-at-17.37.25-resized.png]

@Brian-McG In dit specifieke geval had ik een route-track geïmporteerd die de maker in Basecamp had gemaakt. Ik had de route alleen geïmporteerd, dus niet met MRA bewerkt in de HERE kaart. Gemini zegt hierover: Let op bij tracks (.GPX): Zuivere tracks of 'route-tracks' kunnen soms moeite hebben met offline opstarten omdat de app deze probeert te herberekenen. Zorg er dus voor dat je gpx-bestanden in de MRA planner (op de HERE-kaart) eerst netjes hebt omgezet naar een definitieve route met routepunten. Wat betreft het overslaan van routepunten. Na een uur terug verwezen te worden is inderdaad mijn geduld op. Ps Ik zie dat bovenstaande tekst bij het verzenden verandert. Zo wordt “geïmporteerd” verandert in het woord vervangen. Hierdoor kunnen leuke misverstanden ontstaan.

@Mark-Williams-5-0 I think we may be talking at cross purposes or different things as this is not adding up at all correctly for me & does not match what I see when I "enter a destination". You say..... When I enter a destination on the MRA Android app and select the allow Highways option For me this means a simple A > B route from your location to a destination To do this I would select "Destination" from the route options draw, Search for & then select my destination, followed by pressing the Navigate button & my route options would be shown [image: 1782936974149-392084b1-2409-4e32-91d1-fc2f1a419ee8-image.jpeg] As you can see when select Leicester as my destination from west London it definitely allows me to use motorways / highways as it gives me the choice of routing via the M1 or M40 Under "Avoidance options" the "Highways" button is the default green as an allowed road I think to help further you will need to explain your steps a bit more fully

It is what it is by design

I have no clue why other apps do work fine and MRA is lagging beside a different approach of tracking and/or different usage of resources

M.-Schrijver said: @Michel-71-0 said: Gisteren een ritje gedaan en ik moet zeggen dat de ervaring al een stuk beter was. Wat ik me nog wel afvroeg: gedurende de rit heb ik één waypoint overgeslagen omdat dit eenrichtingsverkeer was geworden. Het apparaat probeert dan eerst terug te navigeren naar dit punt, maar als je dat negeert, springt hij vanzelf over naar het volgende punt. Rechtsboven wordt dan weergegeven dat je het punt gemist hebt. Wanneer ik daarop tik, wordt er gevraagd of ik dit punt wil overslaan; ondanks dat ik op 'ja' drukte, bleef het waypoint echter de rest van de rit staan. Is dit zo "by design" of ging er iets niet goed? Nee, dit is niet "by-design" Rechtsboven moet altijd het volgende routepunt getoond worden. Doe je een correctie door handmatig een punt over te slaan, moet dit ook rechtsboven zichtbaar zijn. Dit doet mij denken aan een ander topic. Ik kan deze helaas niet meer terugvinden. Ook hier bleef het verkeerde routepunt rechtboven staan.