Issues since the 5.1.0-462 update / Crashes and lag
-
I updated to version 5.2, and navigation worked without any issues on my next trip.
However, yesterday during a 440 km, 8.5-hour trip, MRA shut down shortly before reaching the destination (about 35 minutes remaining). I was able to restart the app, but the map was no longer displayed on CarPlay. An error message appeared when saving the tracklog, but it was saved anyway.
Using MRA on
BMW R1300GSA with Carpuride CarPlay
Ducati Monster 937+
Honda X-ADV750
VW Golf R with CarPlay
VW Crafter/Eribacar600 with Carplay -
Today 480 km and over 9h without any problems, at the end the trackroute was able to save
-
Same situation like yesterday, no problems at all - 200 km in 5 hours, was able to save the tracklog
-
We drove 465 km today.
MRA Next crashed twice today.
Suddenly, the mobile phone’s home screen appeared.After reopening the app, I had to tap ‘Navigate’ to continue navigation.
I also had a second mobile phone running with the identical route "offline"
There were no problems with this.
-
I updated to version 5.2, and navigation worked without any issues on my next trip.
However, yesterday during a 440 km, 8.5-hour trip, MRA shut down shortly before reaching the destination (about 35 minutes remaining). I was able to restart the app, but the map was no longer displayed on CarPlay. An error message appeared when saving the tracklog, but it was saved anyway.
@Roland-Busenhart I had the same issue while driving the last kilometers to my destination in Glasgow. It was very annoying, since I was in heavy traffic. Until that moment I was successfully navigating for over 200 km that day. I also got an error message when saving the tracklog, which was saved anyway. All other days of my 11 day trip went very smoothly. So it's not a big issue for me, but still it's peculiar that the same happened to you. I use Android Auto.
-
Today we drove 335 km
After about 130 km, the MRA App stopped working and the start screen appeared. Restart the app and tap ‘Navigation’ to resume navigation.My colleague, who uses iOS, experienced a white screen several times and the app stopped responding.
It was only after restarting the app three times that navigation could be resumed.
-
Pas few days similar with 5.2.
This is the 5.1 topic but I assume you ride with 5.2(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
Pas few days similar with 5.2.
This is the 5.1 topic but I assume you ride with 5.2@M.-Schrijver Yes, of course, I’ve downloaded the latest update, 5.2.0-474
-
undefined Massimo Cardone referenced this topic
-
Yesterday 315 km in 5 h without any issue completed
-
Yesterday I covered 325 km in 3.5 hours; experienced several crashes during the ride; couldn't save the track log
-
It almost seems like after a certain number of hours the problem starts to appear…
-
Not always... We also had this problem a few times after setting off, after about half an hour or so.
But most problems do tend to occur in the afternoon, after about six to eight hours of driving. -
I think that’s difficult to pinpoint.
I’ve experienced crashes after about 2 hours, as well as after about 5 hours or more. -
Hi everyone,
Ever since the last update (version 5.1.0-462), I’ve been having nothing but problems. Here’s the situation:
We (me and two friends) went to Lake Como the weekend before last (from Friday, May 22, to Sunday, May 24, 2026). Both of my friends have iPhones (one has an iPhone 13 Pro and the other an iPhone 15 Pro) and received the update a week earlier. I myself have an Android phone running version 16.
I drove to Lake Como on Friday still using the “old” version, and everything went smoothly as always. That evening in bed, I saw that MRA had an update and installed it full of joy and confidence in the new features.
When we set off on Saturday, the problems began. I should also mention that the friend with the iPhone 15 Pro had been in Sardinia with another group a week earlier and had already experienced problems there, which I’ll mention shortly.
What were my—or rather, our—problems? The MRA navigation app kept crashing. And when did that happen? Always at the worst possible moment, such as in a city with many turns or roundabouts, or in areas we weren’t familiar with. At times, I couldn’t even launch the app anymore.
Consequently, the tracklog was no longer recorded, so we simply had a straight line across the map.
What also happened halfway through the trip—or at the latest three-quarters of the way through—was that the navigation cursor started to stutter or lag, which suddenly isn’t so fun anymore when you’re in a city or in an area where you have to make a lot of right and left turns.
When I’d drive out of a hairpin turn and, say, find myself back on a straight stretch 100 meters later, the cursor was still at the hairpin turn.
Last weekend (from Thursday, May 28, to Sunday, May 31, 2026), we spent four days at Lake Garda. The night before, I had cleared the cache just to be safe (which works on Android phones; I have no idea if it works on iPhones too), but the problems on the way there were still there.
That evening, I deleted all the data, uninstalled the app, even restarted the phone, and, full of confidence and hoping that this would solve the problems, reinstalled the app. But for the remaining three days, the problems were still there.
My logical conclusions:
- If I were the only one experiencing this problem, it would either be a local issue with my phone or a problem with Android phones in general.
- But since both of my friends have also had problems with it since the update (for both Android and iPhones), I believe it must necessarily be an issue with the update.
- This is also shown by the fact that on Friday, May 22, when I drove to Lake Como using the “old” version, I had absolutely no problems. It all started after the update, both for me and for my friends.
- I also did what was described: I deleted the data, restarted my phone, and reinstalled the app, but nothing changed. Constant crashes and lag.
What has been your experience with the new update?
Best regards,
Massimo
P.S.: Before the update, I never—and I mean NEVER—had any problems with the navigation. Everything always ran smoothly and perfectly.
Translated with DeepL.com (free version)
-
@Bart-9a-0 This thread was started in English; please be so kind as to continue using that language
BMW R 1250 GS
MRA Navigation & SilverFox C1 Controller
BMW Connected Ride Cradle
Wunderlich USB Ladebox mit Quadlock
Pixel 9 "online"
SPC Universal mount
Motorola Edge 40 "offline"
Sena SLR 3
Sena 50 R -
@Bart-9a-0 This thread was started in English; please be so kind as to continue using that language
@Peter-Zehentreiter , Sorry
-
Hi, OP's post is exactly what I have experienced on my trip to Garda and Trento last week on my Android phone. First, I thought the Android Auto was the culprit of the lag, but no, even using app just on the phone, each time there was a lag, I had to restart the app for it to work only for a few minutes. The real issue is that you're in hairpins and constantly need to think which turn you are taking. This resulted in countless turnarounds, recalculations, etc, not so great if you are leading the group. Another massive issue is that very tight hairpins on top of each other look to the navigation as if you are still in the same spot, a couple of hairpins below, then it starts recalculating, switching from online to offline mode, and everything is delayed. This is almost unusable in real time.
What can be done to fix this? Because as OP pointed out, in the city or tight mountain roads, this isn't working, and the motorcycling trip is exactly that, not straight roads. I don't need a navigation for that or MRA to be more precise.
thanks
joe -
Hairpins are indeed difficult voor navigations. I've got lot experience with TomTom Go (Expert). At first TomTom had also this issue. But they managed to solve this. I don't how they solved it. But it looks like they do a similar thing as in tunnels. Assuming you stay on track whit the same pace.
-
Same problem I was facing. After 2-3 hours app stopped working. New version not used yet for longer time.
-
I wonder if the 'Tracklog' feature is filling the processing capabilities and cachiing the data?
Would it be worth a long trip without recording a tracklog perhaps to see if it frees up some processing bandwidth?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
-
1612.8k
-
28462.9k
-
01091
-
19230
-
0363
-
3225
-
0220
-
0255
