MRA Community Forum

A wonderful good morning We set off on the ‘La Routes des Grandes Alpes’ motorbike tour last Wednesday and came back yesterday evening. It was simply fantastic. I’m talking about the tour, not the sat-nav. There were five of us in total, including me, and my four friends all use MRA because I recommended it to them and they took my advice. Naturally, I’d been promoting MRA and talking about it with great enthusiasm. But when MRA doesn’t work as it should and we’re all frustrated, it unfortunately reflects badly on me, as I was the one who recommended it to them. We set off at 7.00 am on Wednesday. The problems started at around 11.00 am: MRA crashed and the cursor lagged. I got MRA working again, but at almost exactly 12.00 noon the same problem occurred. After that, I had a crash practically every 15 minutes until the evening. As I am – and was – the group leader, I had to let someone else take the lead. After a while, the new group leader also had to let someone else take the lead, as his MRA was constantly crashing too, and it carried on like that until the evening. Each of us took turns as group leader, and it was a HUGE nuisance! I then somehow got the feeling that one of the causes of these problems was the heat, as my mobile phone had been very hot the day before. And for safety reasons, mobile phones reduce their power output. On the second day, I took my mobile phone out of its case and placed it in the tank bag with the screen facing downwards. Why with the screen facing downwards? Because I assumed that the heat is dissipated through the back of the mobile phone. And lo and behold… I didn’t experience any more crashes. I did have to take the mobile phone out of the tank bag during breaks and let it cool down properly in the shade. But towards the evening, the cursor started to lag, most likely due to the heat again. In my opinion, the MRA has required much more processing power since the 5.1.0-462 update. Why do I say that? When the four of us were in Piedmont last year (we were all riding MRAs), the outside temperature was between 35 and 38 degrees for four days. It was really hot; the sweat was just pouring off us. And in Piedmont, there were no mountain passes at, say, 2,000 metres, where it’s cooler. Did we have any problems or crashes? No! None of us did. I’ll repeat a point from my first post. The problems started for all five of us at the same time, following the 5.1.0-462 update. Incidentally, with the iPhones, the app would try to start the route first thing in the morning and MRA would simply crash. Without having driven a single kilometre and without any exposure to heat. This problem was mentioned either in this thread or in another one that I’ve read. Fortunately, I haven’t experienced this phenomenon with my Android mobile phone. On the fourth day, whilst we were on the return journey, I didn’t experience any crashes, but near Bergamo the navigation was so severely delayed that I no longer knew which motorway exit to take, as the cursor was at least 100 to 200 metres behind my actual position. This was very frustrating and tedious, so we had to pull over at the side of the road and once again appoint a different group leader whose MRA was working reasonably well. I know the report is a bit long, but it’s detailed, and now I hope that Corjan and his team will get the problem – or problems – under control and that my MRA will work as well and as fantastically as it did before update 5.1.0-462. Kind regards Massimo PS: By the way, on Peter Zehentreiter’s advice, I tried navigating using the offline maps, but the problems were still there.

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

Probeer dat eens direct in de navigatie app zelf. Eerst in de planner en verrassing laten maken en dan navigeren in de app is een stap teveel

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

A route works... It doesn't matter if I put a point on the map on site, at the destination or select the existing POI there. At Kurvenreich comes the message shown. [image: 1783882936292-img_0284.png]

@cvlmtg said: I have to say I agree with Thomas. I love MRA route planner, it's the most powerful I have ever tried and works quite well, but I tried the navigation app once and I think I'll never use it again. You can say that to solve the first waypoint problem you can just move it to another place, but that's the problem! You always have to remember this or that workaround. You even have to tell the app that if you are calculating a route while you have no internet connection then yes, you want to calculate the route with no internet connection. It seems this app always require a lot of extra manual work just to do what other apps do by themselves. It doesn't matter that there are videos or tutorials explaining how the app work, because the problem is that you need all these videos and tutorials while other apps just work. Bulls eye !

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?

@Mister-B ah ok, dat is toch wat anders, dan waar je ons aanvankelik heenwtuurde. Nee dat kan niet. Wat je wel kunt doen, zoals Nomko schrijft, is, het ount als viapunt aan je route toevoegen en later in een adequate POI-manager (ik gebruik nog steed good old Basecamp daarvoor 🫣) de POI aan een bestaande- of nieuwe lijst toevoegen, die exporteren en in MRA weer inlezen. Het is nogal omslachtig, maar dat is tot nog toe de enige manier.

The BMW Nav 5 can handle a maximum of 30 announcing waypoints (via points) per route, you can also include up to 125 unannounced shaping points between any two waypoints. You have probably exceeded the Via point (announced waypoint limit.). If you MUST have a route overview you'd probably be better exporting the master route as a Track to the Nav 5 and displaying it beneath the magenta line of your routes.

Albyus said: @LE-DIZES-Freddy said: @Albyus È il routing di OpenStreetMap (OSM) a causare questo problema. Utilizza HERE o TOMTOM e il problema scomparirà. traduction Google Ci provo, grazie !! Adesso SI !!!!! tutta un altra cosa, grazie !!!!!!!!!