Issues since the 5.1.0-462 update / Crashes and lag
-
Hello
It’s interesting that no one else is experiencing these issues. If I were the only one affected, then—as I mentioned earlier—it would be either a local issue with my phone or a general problem with Android phones.
But since my two friends also had the exact same issues with their iPhones after the update, I believe there must be a problem with the update itself.
@Rob Verhoeff: You wrote that you don’t have these issues, okay. How long was your last trip since the update to 5.1.0-462?
On our last two trips to Lake Como (the week before last) and Lake Garda (last week), we were on the go for between 9 and 12 hours (including breaks) each time.
And the problems never or rarely occurred in the morning, but only in the afternoon or toward the end of the tour. That means that if you’ve only used MyRouteapp for a few hours since the last update, you may not have had any problems with it at all.
It can’t be that we’re the only ones having these issues, because we use different smartphones with different operating systems: an iPhone 13 Pro with a slightly outdated version, an iPhone 15 Pro with the latest iOS version, and an Android smartphone running version 16.
Best regards,
Massimo
Translated with DeepL.com (free version)
-
Hello
It’s interesting that no one else is experiencing these issues. If I were the only one affected, then—as I mentioned earlier—it would be either a local issue with my phone or a general problem with Android phones.
But since my two friends also had the exact same issues with their iPhones after the update, I believe there must be a problem with the update itself.
@Rob Verhoeff: You wrote that you don’t have these issues, okay. How long was your last trip since the update to 5.1.0-462?
On our last two trips to Lake Como (the week before last) and Lake Garda (last week), we were on the go for between 9 and 12 hours (including breaks) each time.
And the problems never or rarely occurred in the morning, but only in the afternoon or toward the end of the tour. That means that if you’ve only used MyRouteapp for a few hours since the last update, you may not have had any problems with it at all.
It can’t be that we’re the only ones having these issues, because we use different smartphones with different operating systems: an iPhone 13 Pro with a slightly outdated version, an iPhone 15 Pro with the latest iOS version, and an Android smartphone running version 16.
Best regards,
Massimo
Translated with DeepL.com (free version)
@Massimo-Cardone My last trip was to Switzerland in May, using version 5.1.0-462 (still in alpha testing). While in Switzerland, I also made another trip there (about half a day). Back in the Netherlands, I made two more day trips. Apart from that, I use it daily whenever I’m driving, whether for errands or commuting to and from work.
I haven’t experienced any of the issues you’re describing on my side.
-
Hello
It’s interesting that no one else is experiencing these issues. If I were the only one affected, then—as I mentioned earlier—it would be either a local issue with my phone or a general problem with Android phones.
But since my two friends also had the exact same issues with their iPhones after the update, I believe there must be a problem with the update itself.
@Rob Verhoeff: You wrote that you don’t have these issues, okay. How long was your last trip since the update to 5.1.0-462?
On our last two trips to Lake Como (the week before last) and Lake Garda (last week), we were on the go for between 9 and 12 hours (including breaks) each time.
And the problems never or rarely occurred in the morning, but only in the afternoon or toward the end of the tour. That means that if you’ve only used MyRouteapp for a few hours since the last update, you may not have had any problems with it at all.
It can’t be that we’re the only ones having these issues, because we use different smartphones with different operating systems: an iPhone 13 Pro with a slightly outdated version, an iPhone 15 Pro with the latest iOS version, and an Android smartphone running version 16.
Best regards,
Massimo
Translated with DeepL.com (free version)
@Massimo-Cardone From tomorrow until Monday, we’ll be heading to South Tyrol as part of a larger group.
Four of us will also be using MRA for navigation.
2x iPhone
2x AndroidThe tours start daily at 8.00 am and last until around 6.00 pm.
I’ll be paying particular attention to how MRA performs and will post daily updates here.
-
I experienced the same issue as well. At first everything seemed to run smoothly, but over time it started to stutter and the navigation began lagging behind my actual position. Eventually, the display stopped refreshing altogether, and I even ended up with a white screen showing only the instructions in the top-left corner. The voice guidance, however, continued to work correctly and on time.
I have also previously reported this issue to MyRouteApp. -
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 -
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.
-
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. -
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. -
Here is the report for Day 2 of our South Tyrol tour.
Start: 08:19
Arrival: 18:00We 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
BMW R 1250 GS
MRA Navigation & SilverFox C1 Controller
BMW Connected Ride Cradle
Wunderlich USB Ladebox mit Quadlock
Pixel 9 "online"
SPC Universal mount
Motorola Edge 40 "offline"
Sena SLR 3
Sena 50 R -
Here is the report for Day 2 of our South Tyrol tour.
Start: 08:19
Arrival: 18:00We 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
@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
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT sold
Samsung S24FE mounted on a Quadlock and using Android Auto in my car -
@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
@Marinus-van-Deudekom I suppose I didn't make myself quite clear...
Track recording wasn't activated!
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
-
0871
-
09178
-
07159
-
115407
-
0443
-
2381.0k
-
0497
-
1425
