Issues since the 5.1.0-462 update / Crashes and lag

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

[Léon Hassing]

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

[Peter Zehentreiter]

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.

[M. Schrijver]

Pas few days similar with 5.2.
This is the 5.1 topic but I assume you ride with 5.2

[Peter Zehentreiter]

@M.-Schrijver Yes, of course, I’ve downloaded the latest update, 5.2.0-474