Issues since the 5.1.0-462 update / Crashes and lag
-
@Marinus-van-Deudekom I suppose I didn't make myself quite clear...
Track recording wasn't activated!@Peter-Zehentreiter so it worked ok
-
I read the first post and can say and i had roughly the same experience right after the update to 5.1 beta. Did check some settings and did the update to final 5.1 (came pretty quick after the beta). With the final 5.1 i had no problems. Navigate a few days without any issues.
-
Day 3 of our South Tyrol tour
Departure 08:15
Return 16:45Android Pixel
At 14:00, the cursor on the Pixel 9 drifted 2 cm away from the blue line.Pausing and resuming navigation fixed this issue; otherwise, it worked without any problems all day.
Android Samsung A52 navigated without any issues all day.
iPhone 15
Around 14:00 the screen went white, but after about 1 minute, navigation was working again.Once during the day, navigation stopped automatically, and a prompt appeared asking to ‘Continue navigation’ or ‘Stop’.
Pressing ‘Continue’ restored navigation.
The iPhone 2 navigated offline all day without any issues.
-
I had the same problem with CarPlay on my green journey, the app closed at least 1-2 times in a day, the apps screen appeared from CarPlay, I had to reopen MRA and it asked me if I wanted to navigate the route that had just closed, this happened at least 2 days out of 5, I also sent the log file to support because I had already reported the problem a few days earlier, they replied that they had happened again to send the log file immediately, so I did, but no one contacted me again... iPhone 16 plus but with iOS 18, I decided not to update to the latest iOS because in my opinion it is only creating problems... especially on my iPad, but given what has been written, I think it absolutely does not depend on iOS 18 or 26...
-
Hello everyone
There have been quite a few posts from people experiencing similar or identical problems. It must inevitably be an issue with the new update. I hate to repeat myself, but if three friends are out together, all have the new update, and from that point on all three have experienced crashes, tracklogs not being recorded, and severe stuttering, then that’s no longer a coincidence.
And it’s worth mentioning that we have different mobile phones. It’s just like with other operating systems, such as Windows. You install an update from Microsoft and some people have problems whilst others don’t. It seems that’s the case with MyRouteapp too.
I really had absolutely no problems before the update, or at least I can’t remember when I did.
The next update is due to be released around 18 June. Let’s hope that solves the problems.
Kind regards,
Massimo
Translated with DeepL.com (free version)
-
Yesterday I had the chance to test the 5.1 app for the first time on Android Auto and on a Galaxy S25 on a 340km route. I had no problems navigating the tour apart from the 20km I did extra because the app doesn't warn you if you take the wrong road, but this also happened with the previous apps.
-
So here is the report on the last day of our trip to South Tyrol.
We set off today at 08:00
Arrived in Passau at 17:30
Temperatures ranging from 18 to 28 degreesThe iPhone 15’s online navigation had a blank screen again today and could only be
restored to working order by restarting it.The other iPhone was used offline... everything was fine with that one
The Pixel 9 had the following problem today... the navigation suddenly disappeared and the Pixel 9’s home screen appeared instead.
I had to restart the app and then press ‘Continue’ to carry on navigating.The Samsung A52, on the other hand, had no problems today.
In two weeks’ time, we’ll be back in the mountains for four days... I’ll report back then.
-
With regards to the blank screen on iOS, there are issues reported with other apps also, such as Waze, not displaying the map.
e.g. https://www.reddit.com/r/waze/comments/1tv8syv/waze_always_starts_on_a_blank_screen_in_carplay/
https://discussions.apple.com/thread/256152967I've had the same with Waze as well as MRA Navigation Next - but it might be an iIOS bug more than something MRA can fix.
-
Today (10.06.2026) I navigated a little over 4 hours from Stavanger to Bergen; there were two crashes, but I was able to restart and continue navigating. However, I was once again unable to save the tracklog at the end (not enough track points).
-
With regards to the blank screen on iOS, there are issues reported with other apps also, such as Waze, not displaying the map.
e.g. https://www.reddit.com/r/waze/comments/1tv8syv/waze_always_starts_on_a_blank_screen_in_carplay/
https://discussions.apple.com/thread/256152967I've had the same with Waze as well as MRA Navigation Next - but it might be an iIOS bug more than something MRA can fix.
@Kirsten-De-Weerd If it was an iOS bug, how come these problems weren't there before the update? I still have iOS 18, so I wouldn't say it depends on iOS...
-
Yesterday update to version 5.2
Today no problems at all - 280 km within 7h, no restarts and at the end save the tracklog was possibel
-
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.
-
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
-
Massimo Cardone referenced this topic on
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
-
0665
-
28506.6k
-
16241.2k
-
07277
-
-
