Issues since the 5.1.0-462 update / Crashes and lag

[ginogino]

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.

[Peter Zehentreiter]

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 degrees

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

[Kirsten De Weerd]

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/256152967

I'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.

[Roland Busenhart]

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

[Aiello antonino]

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

[Roland Busenhart]

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

[Roland Busenhart]

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]

Today 480 km and over 9h without any problems, at the end the trackroute was able to save

[Roland Busenhart]

Same situation like yesterday, no problems at all - 200 km in 5 hours, was able to save the tracklog

[Peter Zehentreiter]

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.