New update! (4.3.5) Very minor changes
-
Hi everyone
A very small update is coming your way!
The main reason for this release is to resolve a very annoying issue for Android Auto users.Android Auto
Resolved issue where Android Auto would sometimes stop displaying the updated location while driving. The instructions would update but your position would remain stationary on the display. This issue should now be resolved.HERE version
We update the core SDK of the app.
Should result in some minor stability improvements that are not our direct responsability.That's it
Cheers,
Corjan -
The update is already live for Android!
-
Hi everyone
A very small update is coming your way!
The main reason for this release is to resolve a very annoying issue for Android Auto users.Android Auto
Resolved issue where Android Auto would sometimes stop displaying the updated location while driving. The instructions would update but your position would remain stationary on the display. This issue should now be resolved.HERE version
We update the core SDK of the app.
Should result in some minor stability improvements that are not our direct responsability.That's it
Cheers,
Corjanwrote on 14 Jan 2025, 17:20 last edited by@Corjan-Meijerink yes I can confirm that it works fine now. Just tested the new version !
-
@Corjan-Meijerink yes I can confirm that it works fine now. Just tested the new version !
@Adrian-Avram Great!
-
The update is already live for Android!
wrote on 15 Jan 2025, 23:46 last edited by peha@Corjan-Meijerink I have tried the updated app. For me, on the Android Auto display when just driving (no navigation ongoing), the position still doesn't update until I unlock my phone once. As soon as I do that, it updates my position on the map correctly, and it stays that way even if I then lock my phone again. But it seems that the initial unlocking is crucial, otherwise it doesn't update. I didn't have time to test while routing.
-
@Corjan-Meijerink I have tried the updated app. For me, on the Android Auto display when just driving (no navigation ongoing), the position still doesn't update until I unlock my phone once. As soon as I do that, it updates my position on the map correctly, and it stays that way even if I then lock my phone again. But it seems that the initial unlocking is crucial, otherwise it doesn't update. I didn't have time to test while routing.
@peha Interesting!
-
@Corjan-Meijerink I have tried the updated app. For me, on the Android Auto display when just driving (no navigation ongoing), the position still doesn't update until I unlock my phone once. As soon as I do that, it updates my position on the map correctly, and it stays that way even if I then lock my phone again. But it seems that the initial unlocking is crucial, otherwise it doesn't update. I didn't have time to test while routing.
Alpha testerwrote on 16 Jan 2025, 14:45 last edited by Con Hennekens@peha, could it be that the MRA app has permission to use location services ONLY when in use? I think running no navigation with the screen locked might not qualify as "in use".
You can check that in the Android System - Apps settings of your device.
-
@peha, could it be that the MRA app has permission to use location services ONLY when in use? I think running no navigation with the screen locked might not qualify as "in use".
You can check that in the Android System - Apps settings of your device.
wrote on 16 Jan 2025, 18:27 last edited by@Con-Hennekens Wow, you're absolutely right - this has been the problem apparently! I didn't realize it was set like this, and since I've switched the location permission to always, it works perfectly! It even handles the situation that I start a navigation on the smartphone while the Android Auto device is off, then starting the vehicle (thus turning on the Android Auto device) - and it just takes over both navigation instruction display and voice instructions (to the correct sound device rather than the smartphone's speakers. Thanks a lot!
-
You humble me @Con-Hennekens
Thanks for thinking along!I will check if the app can check this permission and warn about potential issues like this.
-
You humble me @Con-Hennekens
Thanks for thinking along!I will check if the app can check this permission and warn about potential issues like this.
Valued contributorwrote on 17 Jan 2025, 08:38 last edited by@Corjan-Meijerink yesterday was another test dat using AA. Just to see what’s happening with the location pointer. First a drive whitout a route active. No problem. Phone wasn’t activated,Just the screen of AA.
Then tried a route and deviaties from the route a couple of times. No problem at all. The pointer mept the wright location all the times. Alternative was presented fast. D’urine the ride the daylight shifted to nightvidion.
No problems at all
Conclusion everything is working OK
Thnkx team -
@Con-Hennekens Wow, you're absolutely right - this has been the problem apparently! I didn't realize it was set like this, and since I've switched the location permission to always, it works perfectly! It even handles the situation that I start a navigation on the smartphone while the Android Auto device is off, then starting the vehicle (thus turning on the Android Auto device) - and it just takes over both navigation instruction display and voice instructions (to the correct sound device rather than the smartphone's speakers. Thanks a lot!
@peha, You are most welcome!
@Corjan-Meijerink, I know you will make up for this sooner or later...
-
@Corjan-Meijerink yesterday was another test dat using AA. Just to see what’s happening with the location pointer. First a drive whitout a route active. No problem. Phone wasn’t activated,Just the screen of AA.
Then tried a route and deviaties from the route a couple of times. No problem at all. The pointer mept the wright location all the times. Alternative was presented fast. D’urine the ride the daylight shifted to nightvidion.
No problems at all
Conclusion everything is working OK
Thnkx team@Marinus-van-Deudekom awesome!