Issues since the 5.1.0-462 update / Crashes and lag

[Roland Busenhart]

On June 5, navigated for 6.5 hours and 520 km without any issues.
Today, June 6, navigated for 10 hours and 870 km, with 3 crashes after approximately 3, 3.5, and 6 hours. A restart was possible each time, but after the last crash, the map was no longer displayed on CarPlay. Another issue was constant zooming in and out on the map in CarPlay.

[Peter Zehentreiter]

Here is the report for Day 2 of our South Tyrol tour.

Start: 08:19
Arrival: 18:00

We followed a planned route until 15:00

From 15:00 we finished the existing route and then started a new one (a shortened route was loaded).

The track was not recorded on any of the devices.

Dry weather, temperatures ranging from 15°C to 24°C.

1x iOS offline: no issues or problems encountered

1x iOS online: no problems

2x Android: no problems whatsoever

[Marinus van Deudekom]

@Peter-Zehentreiter Did you see the yellow line following your position indicator at all. I assume that you've either set the track recording manualy or automaticly

[Peter Zehentreiter]

@Marinus-van-Deudekom I suppose I didn't make myself quite clear...
Track recording wasn't activated!

[MarcM]

Same for me, since 23/05 after latest update and also region Lake Como/Lake Garda ….

[Marinus van Deudekom]

@Peter-Zehentreiter so it worked ok

[M. Schrijver]

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.

[Peter Zehentreiter]

Day 3 of our South Tyrol tour

Departure 08:15
Return 16:45

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

[Aiello antonino]

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

[Massimo Cardone]

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)

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