Issues since the 5.1.0-462 update / Crashes and lag
-
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)
-
[[topic:post-is-deleted]]
@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
DMD-NOR7E 7"
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? -
Today I navigated 460 km from Copenhagen to Hamburg in just under 5 hours—a total of 2 crashes, the first after about 50 minutes and the second about halfway through the trip. The app closed on my phone, but after reopening it, I was able to continue navigating. Once again, I couldn't save the track log.
-
Sometimes I feel like I'm not being taken seriously. Whether I write diplomatically or let my emotions run wild, there are always people who defend MRA to the bitter end.
What are the typical responses? "I have absolutely no problems. It's most likely your fault." Or "The problem is simply with CarPlay or Android Auto." Or or or…
Here are the facts:
-
Before the 5.1.0-462 update, I had absolutely no problems.
-
The problems started at the same time as my two friends, after we installed the 5.1.0-462 update. They both have iPhones, while I have an Android phone.
-
If only I had the problem, it would have been a local issue with my phone or an Android problem. But no, both my friends also experienced these crashes.
-
The problems also occur when I use my phone without Android Auto, mainly in the car, since I don't have a wireless connection to the car and I don't want to use a cable. In those situations, I only use my phone.
-
My friend (an iPhone user) uses MRA on his Ducati Monster without CarPlay and also experiences crashes.
-
Therefore, the problem cannot be fundamentally related to Android Auto or CarPlay.
On my motorcycle tours, I experience between two and four crashes per day, then there's the issue of the track log not being saved, and finally, the stuttering. The cursor is sometimes 100 to 200 meters behind my actual position. These are the three most serious and main problems.
I've reread every post individually, and everyone reports similar problems, especially since update 5.1.0-462.
I now also have update 5.2.0-474, as does my friend Roland Busenhart, who tested it extensively for three weeks. And the problems persist.
Peter Zehentreiter, Marcel Versluis, MarcM, M. Schrijver, Antonino Aiello, and others report similar glitches and problems.
And let's not forget the other threads where people could have shared their experiences in my thread, as they report identical or similar problems.
We (five friends, all with MRA) are going on the Routes des Grandes Alpes on July 8th. And I really don't have the desire, and especially not the time, to deal with navigation problems.
I know of several people who have opened a ticket and sent their log files to the support team. I hope the MRA support team can locate and solve the problem, because I want to navigate without a care in the world. It's simply annoying when the navigation doesn't work, especially when you need it most. I'm constantly setting off with a bad feeling. Will it work, won't it work, will it work, won't it work…
Dear Support Team, I believe in YOU!
Sincerely,
Massimo
-
-
Massimo did you send in the log files so support can have a look at it.
What you experiance is certainly not meant to be. It is however strange that there is so much diversity. Some users have no problems and others, like you, have a lot.
Can you pinpoint the moments it goes wrong. That might help finding the solution -
Hi Marinus
Yes, I sent my log file to the support team, and my friend (Roland Busenhart), who has also posted here regularly, sent his log file as well.
He's the one who was traveling in Norway with his camper from June 6th to June 27th and used MRA almost every day. He wrote several posts about his experiences, and in 80% of cases, MRA crashed at least twice a day and didn't save the track log.
We were at Lake Como with another friend at the beginning of June, where we installed update 5.1.0-462 on Friday night, and that's when the problems started.
And as I said, we have different mobile phones. I have an Android, and they both have iPhones. Roland has an iPhone 15 Pro, and the other one has an iPhone 13 Pro.
After that, we also installed the latest update, but the problems persist.
And the following users are experiencing the same problems:
Peter Zehentreiter, Marcel Versluis, MarcM, M. Schrijver, Antonino Aiello, etc.
And user Joseph Malik 0 writes: “Hi, OP’s post is exactly what I experienced on my trip to Garda and Trento last week on my Android phone.”
When you read the facts and realize this isn’t a local problem, but a widespread one.
Best regards,
Massimo
-
I also sent my log file to support, saving it immediately after it happened, but I didn't get a response from anyone... but maybe that's the right thing to do... I don't know... I had contacted them previously and they had written to me to send them the log file as soon as it happened again... so I did...
-
If I remember correctly, @corjan-meijerink also had similar problems
-
Massimo did you send in the log files so support can have a look at it.
What you experiance is certainly not meant to be. It is however strange that there is so much diversity. Some users have no problems and others, like you, have a lot.
Can you pinpoint the moments it goes wrong. That might help finding the solutionIt is however strange that there is so much diversity. Some users have no problems and others, like you, have a lot.
Can you pinpoint the moments it goes wrong.Hi Marinus,
I don’t think it’s strange.
I agree 100% with Massimo.The errors don’t occur straight after start-up, nor do they always happen at the same time – sometimes they only appear after hours, sometimes not at all, and sometimes as early as an hour later.
I, too, have friends with all sorts of different set-ups – Android, iPhone and/or Apple CarPlay – who I travel with, and I experience these errors myself with them; however, these people aren’t registered here on the forum at all and don’t express their frustration or report these errors, because not everyone is willing to take the time to contribute here.
It’s more a case of me hearing people say… ‘Oh well, I’ll just try something else.’
Not everyone is as deeply involved in the subject as many users here on the forum; they just want a reliable navigationsystem.
MRA was the best system on the market before the 5.0.1 update, and in my view, it remains the best even after the 5.0.2 update.
In my view, there is also a difference between navigating offline and online.
There are a wide variety of options and settings in MRA – Route, Track, online, offline, etc. – which is why the error does not occur for all users.
However, it makes a huge difference whether I’m driving round on my own or just with one other person and have to stop quickly to restart the system, or whether I’m leading a group and then have to explain problems with the navigation system to the whole group!
I’m absolutely delighted that Corjan was able to identify identical errors whilst on holiday – it’s proof, so to speak, that the many posts and reports of issues from users here are indeed real.
But I’m sure Corjan will find the bug and will provide us an update soon, to make MRA great again
-
Its not that MRA dev team doesn't take all those complaints serious. I know for a fact that they are trying with all their power and skills to isolatie the problem and fix it.
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT sold
Samsung S24FE mounted on a Quadlock and using Android Auto in my car -
Its not that MRA dev team doesn't take all those complaints serious. I know for a fact that they are trying with all their power and skills to isolatie the problem and fix it.
Its not that MRA dev team doesn't take all those complaints serious
Nobody’s claiming that either!
However, there are users on the forum who, for the reasons mentioned (track, online, offline, use, etc.), haven’t had any problems so far and therefore doubt that other users are experiencing issues.
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
-
0572.0k
-
0664
-
28506.6k
-
16241.2k
-
07277
-
-
