New Beta! (v4.1.0) Android Auto / CarPlay revamp
-
@Jörgen good to know!
263 is indeed still processing for Android but should be available shortly.
People updating directly to that version should not get the white screen. -
Good weekend everyone!
It has been exactly a month since our last beta update.
Now this beta is something we are looking forward to very much. This update is completely focussed on stability of the app itself and more specifically Android Auto / CarPlay.Since the release of the app it is possible to use AA / CP. However, the stability has never been like we wanted it to be
Over the last months, Joost has been working extremely hard to improve the stability of Android Auto and CarPlay 
There are some minor new features, such as the possibility to change some navigation preferences directly from AA / CP, but there aren't any major new features.
As said, the focus of this beta is stability. The app itself should perform better but above all the AA / CP connectivity and usability will be greatly improved compared to previous versions
What to test?
Simply use the app! If you don't have a car with AA / CP or don't use it, we still want to know how the app itself functions on your device. If you do use AA / CP, we are excited to learn if you indeed experience a major increase in stability.What's next?
Coming week we will be working together with HERE directly to see if the battery drain issue can be resolved forever. Together with that, we will make some more changes to improve the GPS positioning.Enjoy your weekend and please let us know your experience with the app!
At the time of writing this post, it is already available for Android. iOS will be available shortly and those users will get a notification from TestFlight.Thanks again for being part of the beta community
Best,
Corjan@Corjan-Meijerink and Joost thnx for the hard work you both did
Build 263 is availible as we speek. -
Good weekend everyone!
It has been exactly a month since our last beta update.
Now this beta is something we are looking forward to very much. This update is completely focussed on stability of the app itself and more specifically Android Auto / CarPlay.Since the release of the app it is possible to use AA / CP. However, the stability has never been like we wanted it to be
Over the last months, Joost has been working extremely hard to improve the stability of Android Auto and CarPlay There are some minor new features, such as the possibility to change some navigation preferences directly from AA / CP, but there aren't any major new features.
As said, the focus of this beta is stability. The app itself should perform better but above all the AA / CP connectivity and usability will be greatly improved compared to previous versions
What to test?
Simply use the app! If you don't have a car with AA / CP or don't use it, we still want to know how the app itself functions on your device. If you do use AA / CP, we are excited to learn if you indeed experience a major increase in stability.What's next?
Coming week we will be working together with HERE directly to see if the battery drain issue can be resolved forever. Together with that, we will make some more changes to improve the GPS positioning.Enjoy your weekend and please let us know your experience with the app!
At the time of writing this post, it is already available for Android. iOS will be available shortly and those users will get a notification from TestFlight.Thanks again for being part of the beta community
Best,
Corjan@Corjan-Meijerink Well done!
🏍️ Motorcycle: DMD-T665 + SilverFox controller
🚗 Car: iPhone 15 Pro with wireless Apple CarPlay -
@Corjan-Meijerink Well done!
I just updated to 262 on an Android OnePlus 6T and had no problems. As far as I can see, everything works fine on the smartphone. Did not yet test Android Auto.
-
After reading the first posts. I made my precautions.
Deleted the "old" app en installed the new one.First of all big complements to the developers. Version 4.10 performed a lot beter than 4.0.8 (read my other post).
I did a short testride with 4.10. I made a route of 40 km. Riding went well. Some strange GPS behaviour. But i suspect the main issue for this is my phone. I was in a car and the phone was a bit hidden. This not good for the GPS reception.
Besides this. MRA did what is suppose to do.
Auto skipping shaping points went well also.There is one thing i would like to mention as an issue.
As long as the phone was connected to Android Auto is was not possible to start a route loaded from MRA webplanner on the phone.
I could select one. I got the overview with the setting choices. But when i push "Navigate" the wheel keeps turning and turning. No route appears on the screen (both screens).
I tried a again but this time disconnected from Android Auto. The route showed on my screen. After this i connect to Android Auto and worked well as said in the first part of this post.I tried it a few times and every the same result.
(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
I made sure to download the 263 version before starting the app. I still got the white screen. Clearing data and going through setup again fixed it.
2010 GL1800 Goldwing using Samsung Galaxy S20 5G Android 13.
-
I made sure to download the 263 version before starting the app. I still got the white screen. Clearing data and going through setup again fixed it.
@RetiredWingMan thanks for letting us know. We should now be able to see exactly what went wrong.
-
After reading the first posts. I made my precautions.
Deleted the "old" app en installed the new one.First of all big complements to the developers. Version 4.10 performed a lot beter than 4.0.8 (read my other post).
I did a short testride with 4.10. I made a route of 40 km. Riding went well. Some strange GPS behaviour. But i suspect the main issue for this is my phone. I was in a car and the phone was a bit hidden. This not good for the GPS reception.
Besides this. MRA did what is suppose to do.
Auto skipping shaping points went well also.There is one thing i would like to mention as an issue.
As long as the phone was connected to Android Auto is was not possible to start a route loaded from MRA webplanner on the phone.
I could select one. I got the overview with the setting choices. But when i push "Navigate" the wheel keeps turning and turning. No route appears on the screen (both screens).
I tried a again but this time disconnected from Android Auto. The route showed on my screen. After this i connect to Android Auto and worked well as said in the first part of this post.I tried it a few times and every the same result.
@M-Schrijver happy to hear that you are happy with the progress! We really put in a lot of effort to improve the stability.
Regarding the issue you encountered, we will check this out!
-
@RetiredWingMan thanks for letting us know. We should now be able to see exactly what went wrong.
@Corjan-Meijerink sorry, j was just checking all my options and noticed that the version is 262! I thought 263 was available but I guess not yet.
-
@RetiredWingMan thanks for letting us know. We should now be able to see exactly what went wrong.
@Corjan-Meijerink I did another update and 263 was loaded. Must have required two updates. The 263 update was much smaller.
-
Update from 262 to 263 went as usually. Connection to the account still there.
-
Good weekend everyone!
It has been exactly a month since our last beta update.
Now this beta is something we are looking forward to very much. This update is completely focussed on stability of the app itself and more specifically Android Auto / CarPlay.Since the release of the app it is possible to use AA / CP. However, the stability has never been like we wanted it to be
Over the last months, Joost has been working extremely hard to improve the stability of Android Auto and CarPlay There are some minor new features, such as the possibility to change some navigation preferences directly from AA / CP, but there aren't any major new features.
As said, the focus of this beta is stability. The app itself should perform better but above all the AA / CP connectivity and usability will be greatly improved compared to previous versions
What to test?
Simply use the app! If you don't have a car with AA / CP or don't use it, we still want to know how the app itself functions on your device. If you do use AA / CP, we are excited to learn if you indeed experience a major increase in stability.What's next?
Coming week we will be working together with HERE directly to see if the battery drain issue can be resolved forever. Together with that, we will make some more changes to improve the GPS positioning.Enjoy your weekend and please let us know your experience with the app!
At the time of writing this post, it is already available for Android. iOS will be available shortly and those users will get a notification from TestFlight.Thanks again for being part of the beta community
Best,
Corjan@Corjan-Meijerink
My App won't load after the update. Me too. Is the suggested app delete and reload the actual correct procedure to resolve this? Gary ClarkGary Clark
2018 R1200RS and 2001 MX-5 Miata
iPhone 15 iOS current. Wireless Carplay
IBA, MOA, Buckeye Miata Club
Dublin, Ohio USA -
@Corjan-Meijerink
My App won't load after the update. Me too. Is the suggested app delete and reload the actual correct procedure to resolve this? Gary ClarkiOS also a blanc screen after update. Delete the app and reinstall
Garmin Zumo XT2/XT/BMW Connected Ride Navigator/MyRouteapp (The App)
Een dag niet gelachen is een dag niet geleefd / Een route is net zo goed als deze uitgezet is. -
iOS also a blanc screen after update. Delete the app and reinstall
@Hans-van-de-Ven-MRA-Master
Deleted App and reInstalled. That worked. Thanks
Gary -
My guess is that anyone with the 262 update suffers from this, even after updating to 263. People who went from an earlier version directly to 263 should not have this problem.
Android: delete MRA app storage from the Android system menu
IOS: remove app and re-install from testflightI 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/ CAT S52 + MRA app -
My guess is that anyone with the 262 update suffers from this, even after updating to 263. People who went from an earlier version directly to 263 should not have this problem.
Android: delete MRA app storage from the Android system menu
IOS: remove app and re-install from testflight@Corjan-Meijerink : Nach dem Update jetzt 20:49 keine Funktion mehr,… als iOS Version bei mir
️
VG Hubert
Info zum Beta Test "Next App" dazu die Hardware ...
iPad 9. Generation iOS 18.5 / Handy iPhone Xr iOS 18.5 / PC mit MS Win11 / BMW Connected App mit Cradel.
❗️MyRoute-App im Cradel und Remotek-One❗️ -
@Corjan-Meijerink : Nach dem Update jetzt 20:49 keine Funktion mehr,… als iOS Version bei mir
️HERE: GPS-Positionirung zu verbessern, gut das das auf der Liste steht.
-
Good weekend everyone!
It has been exactly a month since our last beta update.
Now this beta is something we are looking forward to very much. This update is completely focussed on stability of the app itself and more specifically Android Auto / CarPlay.Since the release of the app it is possible to use AA / CP. However, the stability has never been like we wanted it to be
Over the last months, Joost has been working extremely hard to improve the stability of Android Auto and CarPlay There are some minor new features, such as the possibility to change some navigation preferences directly from AA / CP, but there aren't any major new features.
As said, the focus of this beta is stability. The app itself should perform better but above all the AA / CP connectivity and usability will be greatly improved compared to previous versions
What to test?
Simply use the app! If you don't have a car with AA / CP or don't use it, we still want to know how the app itself functions on your device. If you do use AA / CP, we are excited to learn if you indeed experience a major increase in stability.What's next?
Coming week we will be working together with HERE directly to see if the battery drain issue can be resolved forever. Together with that, we will make some more changes to improve the GPS positioning.Enjoy your weekend and please let us know your experience with the app!
At the time of writing this post, it is already available for Android. iOS will be available shortly and those users will get a notification from TestFlight.Thanks again for being part of the beta community
Best,
Corjan@Corjan-Meijerink Ik heb net de nieuwe versie gedownload en de app opent niet op mijn iphone 13 pro. Het scherm blijft blank bij openen van de App. Jammer…..
-
iOS also a blanc screen after update. Delete the app and reinstall
@Hans-van-de-Ven-MRA-Master said in New Beta! (v4.1.0) Android Auto / CarPlay revamp:
iOS also a blanc screen after update. Delete the app and reinstall
No blank screen for me on iOS from <2.0.8?> to 2.1.0 - 263. It went fine - no blank screen, no loss of data.
Still waiting for Android 263 and then I'll retest, and I'll try Production 2.0.8 to 2.1.0 - 263.
-
Update on iOS to 263 failed also, after start only white screen.
Delete App and reinstall, ok after new login.
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
