MRA Community Forum

I realise this is for XT but with my XT2, I do have Traffic enabled and do not allow it to auto-optimise. Road Closures which was the original post are still acted upon by my Zumo. With GPX1.1 they are deviated around fairly locally between the shaping points surrounding the closure. However, if there are any shaping points within the closure, it seems they need to be manually skipped on the Zumo screen otherwise you'll still be guided there. I think GPX1.2 offers an even better solution and just auto-guides you around the closure locally without destroying your whole route. This is all obviously dependent on the closures being notified to HERE mapping. Definitely no guarantees there, especially for night time closures as we recently found. Options you do have in this case are to manually map read your way round the closure or edit the route on screen and add shaping points (1.1 only as this would force a total route recalculation with 1.2) or even a mileage avoidance which can work well. I wanted to add this comment in case anyone is offering a solution that is XT2/3 only. Reading this and other forums it seems that the XT1 (which I've never owned but have friends that do) is more like the older Zumos in its Traffic/Closures handling.

@Wallace-Shackleton said: We (I) can not even tell Garmin that there is an issue with Drive so some connectivity can be reestablished with my XT, so ultimately there is no hope of a future for the Zumo devices. There is a lot of truth in your overall post. With the emergence of smart phones, navigation apps, and now CP/AA, dedicated GPS devices like Garmin are a dying breed. People use their phones for everything, and it's a natural evolution to extend their use to routing/navigation. However, I don't think Garmin will abandon the dedicated GPS market. Niche or not, they own it, and it gives them an overall market exposure they find valuable. It doesn't help that the Garmin Drive/Tread apps have issues. This isn't the first time Garmin broke Drive with an update. And Tread is not always friendly wirelessly transferring routes, due to the Explore architecture they're pushing on their ecosystem of products. The only thing I'd argue here is that Drive/Tread issues are well known. Or should be known to anyone doing their research. You don't have to use either app at all to effectively use the XT/XT2/XT3 devices for core navigation. Wired route transfer is effective 100% of the time. It never falters. In the years I used my XT, I didn't use Drive after I understood the risks of encountering a bad app update. On my XT3, I only use the Tread app for Traffic, Phone, Music and Weather. However, on Tread, I did not enable external storage (Explore), which is the component that allows for app transfer. Explore is the source of 99% of problems on XT2/XT3 devices. So, by understanding Drive/Tread behavior and only using the components that are stable and always work, I've never had export/import or route calculation problems with my XT/XT3 devices. If you insist on using apps for transferring your routes, then Garmin is not your long term solution. In my case the XT3 has navigation functionality that doesn't exist in any phone app, so I live with the inconvenience of wired transfer. But honestly. it's not that big of a deal.

If you set navigation to start at route point 1 it will guide you to route point 1... Without repeating the complete manual, I can just hint you at longpressing the route punt you want to go to next, or if you are navigating (as) track, just longpress the route line a bit ahead from where you want to rejoin. Make sure you have offline maps available to prevent bad internet situations also.

I agree, the maps on Car Play are far too washed out. You can see your highlighted road but you have no context to other streets. I have stopped using MRA Nav for this very reason.

@Marinus-van-Deudekom thanks for the hint - but never heart the word gearwheel before for the settings icon so it took a while to detect how toget to the waypoints. But now I think it's fine and a working workaround for this issue.

Offline navigeren kan minder precies zijn dan online. Daarom kan de blauwe lijn wat naast de weg komen te liggen

vandaag bij mij ook weer gebeurd na 200km ongeveer op mijn chigee 6 scherm het geval log bestand gestuurd

@superg Moet ik dadelijk een keer proberen met de routes die niet wilden lukken Had nu een andere route geprobeerd, maar ik gebruik eigenlijk nooit rare tekens in de naam van mijn route spaties wel tussen bijv de naam en D1 en de lengte van de route etc etc

Oh, ik zie dat de V4 ook via een update naar Android 13 is te upgraden. Daarmee draaien ze allemaal op Android 13. Op deze versie zou MRA gewoon goed moeten werken. Wat ik zelf altijd doe als ik veel vastlopers ervaar is de tijdstippen onthouden/noteren en de logfiles delen via een ticket.

@Peter-Zehentreiter Thanks a lot for the tip Peter

Garmin Drive works perfectly for me when it comes to tracks and routes, now that I’ve replaced the latest version, v4.29.25, with the older v4.28.14.

So it seems after lots of mails back and forth that the problem came from a messy update policy at Carpuride. First they had OTA updates, which they then switched off themselves without notifying anyone. Then you had to download updates, but only for PC and on a flash drive. In my audiovisual profession no one has PC's, so there you go. After complaining, they suddenly turned OTA on and I could update the device. By then I had finally found someone with a PC, so I could also do the firmware update with the SD-card. Now everything is updated and for the moment works fine! Welcome to the 21st century...

It is possible to use more than two devices; please contact support, and they will provide a proposal.

If you use the connector to transfer your routes to the Zumo, the routes are transferred correctly. Garmin is really moving towards using tracks; however, you can still add your waypoints to the track within Explore.garmin. Currently, the connector only works on a Windows PC; hopefully, it will work on Apple PCs again with the new website.

You have to zoom in, in Plan.TomTom to about 200 or 300 meter to see all the closures. Did you do so?

De grootte van de de iconen kan worden aangepast, zie de handleiding.

@Laurent-Kaczor-0 Thank you for reporting, this is a know issue that’ll be fixed soon.

@Mark-ks-0 Many of the points you mention are also on the wish list for the website that will hopefully see the light of day in the near future!

Ik heb best wel (opbouwende) kritiek op MRA, maar van die tunnels en breedte van straten heb ik echt een ander ervaring, toen ik met mijn camper (7,30x2,95x2,20) bijna 3 maanden door Spanje en Frankrijk heb getoerd. 1x stond ik voor een tunnel, die nog geen 1,50 hoog was, maar dat was duidelijk een fout in het kaartenmateriaal. Je moet dus onderscheiden, of de fout een fout van MRA is of een fout (geen of foutieve melding) bij HERE is. In de meeste gevallen is dat de laatste. Met Android Auto heb ik oudere, niet al te positieve ervaring, dus daar mag een ander zijn blik op werpen.