MRA Community Forum

It does not work on the 1200/50 gsa so Bmw didn't change anything. It something aa needs to change in there software.

@Sjoerd-Spieker My current solution is to add the routedistance to every route name. IMO this is very good practice especially if you share routes with friends or other riders who use different navigation systems When they load the route they can very easily see if their navigation system has correctly calculated the route by comparing their navigations systems calculated mileage to the mileage in the file name I still add the mileage to my route names as a check that the MRA app is actually loading & calculating the route I planned with the MRA web planner! IMO on a 6" phone screen there is not enough space for any additional columns for mileage or time & certainly not for both

I use Android Auto (as mentioned in my post). Before the 5.1.0-462 update (which was rolled out towards the end of May), I could even leave my mobile phone in its case and it always worked perfectly. Since the update, I – and many others too – have been experiencing problems with crashes and cursor lag. My mobile phone was always getting very hot, so on the second day of our ‘La Route des Grandes Alpes’ motorbike tour, I decided to take it out of its case and place it face down. That was the right decision, because from the second day onwards I had practically no more problems. And where else would I put my mobile phone if not in the tank bag? I certainly won’t mount it on the motorbike, as that would break the camera. And sorry, it used to work perfectly, even in the case. Somehow, the new version uses far too many resources or processing power. Never change a running system. Though that’s always the way it is with improvements. We see it in everyday life. You add a new feature and something else ends up getting worse. In any case, we’re now waiting for Corjan and his team to sort out the problem as soon as possible, because at the moment it’s like a four-leaf clover. Only I don’t say, ‘she loves me, she loves me not, etc.’ Now, before I set off, I always say, ‘does it work or doesn’t it…’ Kind regards Massimo

Voor de duidelijkheid er zijn in bovenstaande voorbeeld omrijd alternatieve genoeg. Het zou zeer handig zijn als de navigatie functie bij inladen van een.route deze punten en eventuele files overslaat en om de afsluiting heen plant In NL weet ik de weg en komt het wel goed maar in het buitenland bv eifel met berg routes krijg ik hier lichtelijk paniek gevoelens van als ik bij een afsluiting kom en doorrijden de andere kant op is over een berg heen...

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.

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?

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