Issues since the 5.1.0-462 update / Crashes and lag

[Marinus van Deudekom]

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

[Roland Busenhart]

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.

[Peter Zehentreiter]

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.

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