MRA Community Forum

The options aren't available in AA. But the settings as they are on your phone are taken as the reference for starting the route in AA. At least this is how it should work. But I never start of stop a route in AA. Always on the phone. causes less problems.

@massimo-cardone You wrote something about getting your phone out of the case and put it face down in the tankbag. Are you riding with Android Auto or Apple Carplay? The best place for your phone is somewhere where the wind can cool your phone. No matter what navigation app you use. Also don't let the phone on your in the hot sun during a break. Problems guaranteed. That app stops working because the phone is getting hot. Is something nobody can do much about it. But it would be nice if the app warns you for a hot phone and what will happen if you do nothing. Just a personal experience of mine with TomTom Go on Android Auto in 40 degrees (2022) and how a app can work. Android Auto was pretty new to me at that time. The phone was connected in the topbox. Because the wired connection was placed there. TomTom Go was working fine. No problems. It was just guiding me as expected. After a while (1.5 hour or so). I stopped for a break. I openend the topbox and my phone lay there, blistering hot with a message that TomTom Go has stopped working because of the heat. Strange, 20 sec before that it was just running fine on the Android Auto screen. Knowing this i was a bit worried. It was my only navigation. For the next few days. The phone runs (to) hot every time but TomTom Go on Android Auto was working flawless. The story behind this, is just a message to the developers. Keep pushing on stability. There is still enough to improve there. The app is good but version 5.2 doesn't seems to be most stable version ever released.

I have a similar issue: I'm using a Chigee AO6 CarPlay screen on my bike, with an iPhone 15 Pro Max connected to an inter phone UCOM 16 headset in my crash helmet. When I am following routes via the CarPlay interface, the spoken directions are muted to a level I can't hear. If however I play some music through the iPhone music app, the spoken directions mute the music and are perfectly clear to hear. That means I have to listen to music in order to hear the spoken routing instructions... Any idea how I can unmute the spoken instructions when music is not playing?

I do not share that experience. For me also curvy routes work fine, in online as well as offline mode. Could it be that you are missing map segments? Or try to start from a location too far from a public road?

Zelfde resultaat helaas. Lijkt alsof als je een geplande route in de mra navigatie zet hij vasthoud aan de route en niet de afsluitingen op die route omleid. Hij navigeert gewoon naar de afsluiting toe. Ala je er langs rijdt of omdraait gaat hij pas omrekenen, [image: 1783938951526-screenshot_20260712_185518.jpg]

@Dave-J-0 Extremely pleased to read that! Cannot yet indicate when we will implement those in CarPlay! Isn't top priority now but we definitely want to have it done just for the sake of keeping things in line (like we recently did).

@jomar59 : Du schreibst bitte mal den Service an über ein Ticket und erklärt was Du genau möchtest. Dann gibt es eine Angepasste Lösung bestimmt für Euch. VG [image: 1783928687952-img_0290.jpeg]

@Stevedo-6-0 said: @Nick-Carthew That's great. Where is it documented in the support pages? I looked but couldn't find it. Thanks I’m not sure that it is documented yet.

@Martin-White As far as I am aware it is a maximum of 2000 POI files across all categories.

@Hubert-Thoring What makes you think I didn't...... Sometimes people forget or mis-interpret the instructions or text. That's why this forum exists, no?

This is just an adapter to flexibly rotate the original BMW bracket by 90 ". The display is a sep. Topic. Which display can be horizontal and vertical and still compatible with the WW has to be clarified by someone else. A CP or AA display can also be operated with the glove finger not everyone needs the WW,

@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]

It's on the wishlist

You are most welcome! Seems like an epic trip!

Just tested in the V5.2.1 Beta, just goes [image: 1783797423112-img_0234.jpeg]

What operating system are you using and can the systems file explorer "see" the device?