Issues since the 5.1.0-462 update / Crashes and lag
-
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)
@Massimo-Cardone Why are you opening a new topic about the same subject? That really won’t get you an answer any faster. It just clutters the forum and at most causes irritation.
Short answer to your findings: I’m not experiencing this issue at all.
🏍️ BMW K1600GT-P (2013) | Nolan N100-5 with Sena 30K
📱 iOS on iPhone 13 & 16 (mounted on Quadlock or AliExpress extention on BMW-cradle)
🚙 Apple CarPlay in VW T-Roc
💻 Routelab on MacBook Air & iMac (Tahoe & Ventura) -
I think the problem is the tracking
-
@Massimo-Cardone Why are you opening a new topic about the same subject? That really won’t get you an answer any faster. It just clutters the forum and at most causes irritation.
Short answer to your findings: I’m not experiencing this issue at all.
Why are you opening a new topic about the same subject? That really won’t get you an answer any faster. It just clutters the forum and at most causes irritation.
Short answer to your findings: I’m not experiencing this issue at all.
Sorry, I don't want to upset anyone or clutter up the forum. I just thought there might be more English speakers here.
@Admin: Feel free to delete a post or two if you want. -
Hello
It’s interesting that no one else is experiencing these issues. If I were the only one affected, then—as I mentioned earlier—it would be either a local issue with my phone or a general problem with Android phones.
But since my two friends also had the exact same issues with their iPhones after the update, I believe there must be a problem with the update itself.
@Rob Verhoeff: You wrote that you don’t have these issues, okay. How long was your last trip since the update to 5.1.0-462?
On our last two trips to Lake Como (the week before last) and Lake Garda (last week), we were on the go for between 9 and 12 hours (including breaks) each time.
And the problems never or rarely occurred in the morning, but only in the afternoon or toward the end of the tour. That means that if you’ve only used MyRouteapp for a few hours since the last update, you may not have had any problems with it at all.
It can’t be that we’re the only ones having these issues, because we use different smartphones with different operating systems: an iPhone 13 Pro with a slightly outdated version, an iPhone 15 Pro with the latest iOS version, and an Android smartphone running version 16.
Best regards,
Massimo
Translated with DeepL.com (free version)
-
Hello
It’s interesting that no one else is experiencing these issues. If I were the only one affected, then—as I mentioned earlier—it would be either a local issue with my phone or a general problem with Android phones.
But since my two friends also had the exact same issues with their iPhones after the update, I believe there must be a problem with the update itself.
@Rob Verhoeff: You wrote that you don’t have these issues, okay. How long was your last trip since the update to 5.1.0-462?
On our last two trips to Lake Como (the week before last) and Lake Garda (last week), we were on the go for between 9 and 12 hours (including breaks) each time.
And the problems never or rarely occurred in the morning, but only in the afternoon or toward the end of the tour. That means that if you’ve only used MyRouteapp for a few hours since the last update, you may not have had any problems with it at all.
It can’t be that we’re the only ones having these issues, because we use different smartphones with different operating systems: an iPhone 13 Pro with a slightly outdated version, an iPhone 15 Pro with the latest iOS version, and an Android smartphone running version 16.
Best regards,
Massimo
Translated with DeepL.com (free version)
@Massimo-Cardone My last trip was to Switzerland in May, using version 5.1.0-462 (still in alpha testing). While in Switzerland, I also made another trip there (about half a day). Back in the Netherlands, I made two more day trips. Apart from that, I use it daily whenever I’m driving, whether for errands or commuting to and from work.
I haven’t experienced any of the issues you’re describing on my side.
-
Hello
It’s interesting that no one else is experiencing these issues. If I were the only one affected, then—as I mentioned earlier—it would be either a local issue with my phone or a general problem with Android phones.
But since my two friends also had the exact same issues with their iPhones after the update, I believe there must be a problem with the update itself.
@Rob Verhoeff: You wrote that you don’t have these issues, okay. How long was your last trip since the update to 5.1.0-462?
On our last two trips to Lake Como (the week before last) and Lake Garda (last week), we were on the go for between 9 and 12 hours (including breaks) each time.
And the problems never or rarely occurred in the morning, but only in the afternoon or toward the end of the tour. That means that if you’ve only used MyRouteapp for a few hours since the last update, you may not have had any problems with it at all.
It can’t be that we’re the only ones having these issues, because we use different smartphones with different operating systems: an iPhone 13 Pro with a slightly outdated version, an iPhone 15 Pro with the latest iOS version, and an Android smartphone running version 16.
Best regards,
Massimo
Translated with DeepL.com (free version)
@Massimo-Cardone From tomorrow until Monday, we’ll be heading to South Tyrol as part of a larger group.
Four of us will also be using MRA for navigation.
2x iPhone
2x AndroidThe tours start daily at 8.00 am and last until around 6.00 pm.
I’ll be paying particular attention to how MRA performs and will post daily updates here.
-
I experienced the same issue as well. At first everything seemed to run smoothly, but over time it started to stutter and the navigation began lagging behind my actual position. Eventually, the display stopped refreshing altogether, and I even ended up with a white screen showing only the instructions in the top-left corner. The voice guidance, however, continued to work correctly and on time.
I have also previously reported this issue to MyRouteApp. -
The only thing that happened to me that I was quick starting MRA on my tablet.
That resulted in the cursor not keeping up with my actual position.
After rebooting and waiting until the tablet was ready is was 100%ok. Conclusion user fault -
I'm experiencing the same issues (iPhone 15 Pro Max, iOS 26.5, MRA 5.1.0-462).
Since the last update, the app close occasionally while in navigation mode, it was possible usually to restart the route immediately after reopening MRA — this happens multiple times on trips lasting 8–10 hours.
At the end of the route, Tracklog displays an error message stating that the data cannot be saved (the error message mentions too few waypoints or something similar — I can’t remember exactly).
Starting Friday, I’ll be traveling through Norway and Sweden for three weeks, and I’ve planned my routes using MRA. If I continue to encounter issues, I’ll post an update here.
I’ve already submitted a support request regarding MRA, including the two log files from the device.
-
As promised, here is the report for Day 1
Set off at 08:30 in the rain and 11 degrees
Arrived at 18:00 in sunshine and 25 degrees
No track was recorded.My Android basically worked without any problems all day.
I only had the following problem once... Waypoint 12 was shown as the next destination in the top right-hand corner of the screen, but I was already at waypoint 20. The navigation system therefore kept trying to send me back.
I couldn’t skip this waypoint... the app did not accept the relevant commands.
However, the cursor was always at my current position.I then closed the app and restarted it... the rest of the day went smoothly.
My colleague’s Android device, however, had the following problem.
After a stop, the cursor remained at that position and would not move.
The voice instructions continued to be given, however.My colleagues using iOS, however, were less happy.
The following problem occurred on two different iOS devices.
During navigation, the screen turned white several times a day and the navigation stopped working.
Navigation could only be resumed by closing the app and restarting the route.
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-
012150
-
1896.1k
-
234850
-
0393
-
0351
-
0345
-
06106
-
3141.3k
