MRA lagging and freezing on AA
-
After some troubleshooting — including installing the app on another factory-reset phone, which worked fine — I finally figured out what was causing the issue on my device. I’m sharing this in case it helps anyone else who runs into the same problem.
In my case, the lag was actually caused by Android Auto itself. After the most recent update, it seems the location permission was automatically enabled for the Android Auto app, and this was causing MyRoute App to freeze and lag.
Interestingly, MyRoute App was the only app affected. I tested OsmAnd, TomTom, Sygic, Maps, and Waze, and none of them had this behavior.
Once I changed the Android Auto location permission to “Don’t allow,” everything started working smoothly again.
Sorry for the confusion in my earlier post, and I’m glad I can enjoy the app properly again.
@Adrian-Avram Thank you so much for your contribution. Any ideas for those of us who are experiencing or have experienced problems with AA wireless are very welcome!
-
After some troubleshooting — including installing the app on another factory-reset phone, which worked fine — I finally figured out what was causing the issue on my device. I’m sharing this in case it helps anyone else who runs into the same problem.
In my case, the lag was actually caused by Android Auto itself. After the most recent update, it seems the location permission was automatically enabled for the Android Auto app, and this was causing MyRoute App to freeze and lag.
Interestingly, MyRoute App was the only app affected. I tested OsmAnd, TomTom, Sygic, Maps, and Waze, and none of them had this behavior.
Once I changed the Android Auto location permission to “Don’t allow,” everything started working smoothly again.
Sorry for the confusion in my earlier post, and I’m glad I can enjoy the app properly again.
@Adrian-Avram hi Adrian.
This is indeed interesting. Do you meen that you’ve installed, or updates Android Auto in your car.
I would have to check if setting thé location permission on my AA is possible. I can’t remember setting that at all. Even stranger that it worked fine while using you IPhone. Basicly it’s the same screen.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 -
Hello everyone,
After testing the latest version of the app today (following a clean reinstall and downloading only the current map for my country), I noticed that the app is lagging and frequently freezing on Android Auto.
I am using a Samsung Galaxy S25 Ultra connected to the car display. While the app freezes and lags on Android Auto, it works perfectly fine when opened directly on the phone at the same time.
For comparison, I also tested it with my iPhone 13 using CarPlay, and everything works smooth as butter, both on the car display and on the phone itself.
I have attached a video recorded with my iPhone while Android Auto was running from my Samsung device.
Thank you!
https://drive.google.com/file/d/1KUhaO5VDmIPNKSdHYe273PTgQGAhWv6f/view?usp=drive_link
@Adrian-Avram, my theory about this is that big tech companies can spare developers to program all kinds of workarounds for "not nice functioning" AA/CP devices. It could be as simple as maintaining a list of problematic devices, for which the use of the phones internal GPS is being forced, instead of the GPS built into the AA/CP device. For the MRA app we will have to do this manually I am afraid.
@Marinus-van-Deudekom said in MRA lagging and freezing on AA:
I can’t remember setting that at all.
Usually you do not need to set that. Android Auto is a system app on your Android phone that by default has location permissions. Normally when you connect to a AA device, the GPS of that device is being switched to, if it has one (some don't, some do). If it does not have a GPS onboard, it falls back to the phones GPS. Also when you deny the Android Auto location permissions, the MRA app will fall back to the Phones own GPS.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ Motorola Thinkphone + MRA app -
@Adrian-Avram hi Adrian.
This is indeed interesting. Do you meen that you’ve installed, or updates Android Auto in your car.
I would have to check if setting thé location permission on my AA is possible. I can’t remember setting that at all. Even stranger that it worked fine while using you IPhone. Basicly it’s the same screen.@Marinus-van-Deudekom said in MRA lagging and freezing on AA:
Do you meen that you’ve installed, or updates Android Auto in your car.
Hi @Marinus-van-Deudekom this happened after a Android Auto update on my phone, as in the Android Auto app, from Play Store.
-
@Adrian-Avram, my theory about this is that big tech companies can spare developers to program all kinds of workarounds for "not nice functioning" AA/CP devices. It could be as simple as maintaining a list of problematic devices, for which the use of the phones internal GPS is being forced, instead of the GPS built into the AA/CP device. For the MRA app we will have to do this manually I am afraid.
@Marinus-van-Deudekom said in MRA lagging and freezing on AA:
I can’t remember setting that at all.
Usually you do not need to set that. Android Auto is a system app on your Android phone that by default has location permissions. Normally when you connect to a AA device, the GPS of that device is being switched to, if it has one (some don't, some do). If it does not have a GPS onboard, it falls back to the phones GPS. Also when you deny the Android Auto location permissions, the MRA app will fall back to the Phones own GPS.
@Con-Hennekens said in MRA lagging and freezing on AA:
For the MRA app we will have to do this manually I am afraid.
@Con-Hennekens I totally agree ! Just one setting can really mess things up !
-
@Adrian-Avram, my theory about this is that big tech companies can spare developers to program all kinds of workarounds for "not nice functioning" AA/CP devices. It could be as simple as maintaining a list of problematic devices, for which the use of the phones internal GPS is being forced, instead of the GPS built into the AA/CP device. For the MRA app we will have to do this manually I am afraid.
@Marinus-van-Deudekom said in MRA lagging and freezing on AA:
I can’t remember setting that at all.
Usually you do not need to set that. Android Auto is a system app on your Android phone that by default has location permissions. Normally when you connect to a AA device, the GPS of that device is being switched to, if it has one (some don't, some do). If it does not have a GPS onboard, it falls back to the phones GPS. Also when you deny the Android Auto location permissions, the MRA app will fall back to the Phones own GPS.
@Con-Hennekens That's what I suspected. I've got the idea that @Adrian-Avram would have set something in the AA device itself. Thats explains why it works with the Iphone and didn'twork on his Android phone.
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 -
undefined Adrian Avram referenced this topic
-
@Con-Hennekens That's what I suspected. I've got the idea that @Adrian-Avram would have set something in the AA device itself. Thats explains why it works with the Iphone and didn'twork on his Android phone.
@Marinus-van-Deudekom Anyway, it's not normal that it only affects MRa. These issues will surely be resolved with version 5.1.
Creator and administrator of the largest MRA groups.
- https://t.me/MRa_by_b0hd1
- https://www.myrouteapp.com/group/messages/7007
- YouTube: @demco17
- Ex-routeexpert, current beta tester and MRA expert. Creator of tutorials, manuals, and MRA user trainer
-
@Marinus-van-Deudekom Anyway, it's not normal that it only affects MRa. These issues will surely be resolved with version 5.1.
@b0hd1 said in MRA lagging and freezing on AA:
Anyway, it's not normal that it only affects MRa. These issues will surely be resolved with version 5.1.
From the tests I performed with other apps, my best guess is that they are all using the phone’s internal GPS sensor rather than the external GPS from the Android Auto device.
I also checked my iPhone settings and there is no specific option for CarPlay to control location access, unlike Android Auto, which does provide such a setting.
So I think this is not a MRA issue but an Android Auto one (the app itself).
Best regards,
AdrianSamsung S24 Ultra and Motorola Thinkphone with Android Auto
MyRoute-APP (Planner+Navigation, GOLD Lifetime)
Honda NC750X (2021) with CHIGEE Aio-5 Play -
Hi, a very interesting post. Are you saying that if you turn location permissions off in the AA app on your phone that the system reverts to the GPS built into the Car Play device you are using, rather than the phone? I ask this because I have a Car Play device for my motorcycle that has a built in GPS.
-
Hi, a very interesting post. Are you saying that if you turn location permissions off in the AA app on your phone that the system reverts to the GPS built into the Car Play device you are using, rather than the phone? I ask this because I have a Car Play device for my motorcycle that has a built in GPS.
@nathan-eason-0 said in MRA lagging and freezing on AA:
Hi, a very interesting post. Are you saying that if you turn location permissions off in the AA app on your phone that the system reverts to the GPS built into the Car Play device you are using, rather than the phone? I ask this because I have a Car Play device for my motorcycle that has a built in GPS.
Nope, its the other way around. If you turn off location permissions for Android Auto, the app reverts to the phone's built-in GPS sensor, rather using the built-in GPS sensor of the car / mirroring device !
-
@b0hd1 said in MRA lagging and freezing on AA:
Anyway, it's not normal that it only affects MRa. These issues will surely be resolved with version 5.1.
From the tests I performed with other apps, my best guess is that they are all using the phone’s internal GPS sensor rather than the external GPS from the Android Auto device.
I also checked my iPhone settings and there is no specific option for CarPlay to control location access, unlike Android Auto, which does provide such a setting.
So I think this is not a MRA issue but an Android Auto one (the app itself).
@Adrian-Avram said in MRA lagging and freezing on AA:
From the tests I performed with other apps, my best guess is that they are all using the phone’s internal GPS sensor rather than the external GPS from the Android Auto device.
I'm not sure if you are on the right track with that guess.
The basic idea of AA and ACP that it takes care of it all. AA and ACP by default uses as much vehicle sensors and info as possible. At least as much as the vehicle manufacturer allows AA and ACP to use.
The idea is that AA and ACP can be more "intelligent" than the normal phone apps. Because AA and ACP can have access to the vehicle which your phone doesn't have. But that is the idea.I also noticed that MRA has diffuclties to use the vehicles GPS data in their app. This is a problem onwards from day one. And yes it seems only MRA is affected by this issue. Compared to other navigation apps. which i've tried.
Because of the GPS problem with MRA i bought a separate GPS receiver to test things. This was a few years ago. The idea was that a special GPS receiver is more accurrate compare to one in the Phone. At that time i had also a GPS logger running in the background to record my movements and upload them to my Google Drive. Because TomTom Go (Expert nowadays) doesn't have this abillity.
After some testing i noticed MRA behaves exactly the same and the GPS logger shows the same shaped tracklogs. So the special GPS receiver did not do anything. This was the moment i learned, the GPS data comes from the vehicle and from the phone.@Con-Hennekens could be right that the size of the development team has something to with this. But it can also be a choice of the development software itself which causes this. Why it think this?
Besides this GPS issue. There is still an issue with volume of navigation directions. MRA is the only navigation app, i found, which can not separate the navigation volume from the media volume (if your AA/ACP device supports it).
MRA is based on the Here dev kit.
The Here navigation app itself does not have any problems with both issues mention above. So i can only assume the problems are not in the Here dev kit. And therefore the software which the development team uses to built MRA is causing this.
