Android Auto bugs and improvements
-
Hi, I'm an MRa user (Next 4.3.7 + Gold Planner). I have been on a motorcycle trip around England and France, covering approximately 4,000 km. On previous trips, I've used an Android tablet with the navigation app installed. On this trip, I had to change my system and traveled using a Carpuride w702bs and MRa for Android Auto. The system performed acceptably well, but I think there are improvements to be made to the app when running in Android Auto mode.
The most important thing is that we need to improve the app's stability, as it has crashed several times. The phone running the app was a Samsung S24 Ultra. Another issue I've detected is that the Exit button on the app screen in Android Auto covers the road speed signal displayed on the screen, so it would be necessary to move that button in future updates.
As for improvements, I think there are two important ones to implement in future versions.
One of them relates to waypoints. Android Auto doesn't display waypoint names even when you're at the location where the waypoint is located, and I think this is a major flaw. In fact, it would be important if the name of the next waypoint always appeared on the screen until you reach it. We already have the time and distance information to the next waypoint, but it's necessary to know the name of that waypoint.
Finally, it would be a great improvement to have a menu in Android Auto where we could view the list of waypoints in the current route and be able to select any route from our library and start navigation.Thank you.
-
Hi, I'm an MRa user (Next 4.3.7 + Gold Planner). I have been on a motorcycle trip around England and France, covering approximately 4,000 km. On previous trips, I've used an Android tablet with the navigation app installed. On this trip, I had to change my system and traveled using a Carpuride w702bs and MRa for Android Auto. The system performed acceptably well, but I think there are improvements to be made to the app when running in Android Auto mode.
The most important thing is that we need to improve the app's stability, as it has crashed several times. The phone running the app was a Samsung S24 Ultra. Another issue I've detected is that the Exit button on the app screen in Android Auto covers the road speed signal displayed on the screen, so it would be necessary to move that button in future updates.
As for improvements, I think there are two important ones to implement in future versions.
One of them relates to waypoints. Android Auto doesn't display waypoint names even when you're at the location where the waypoint is located, and I think this is a major flaw. In fact, it would be important if the name of the next waypoint always appeared on the screen until you reach it. We already have the time and distance information to the next waypoint, but it's necessary to know the name of that waypoint.
Finally, it would be a great improvement to have a menu in Android Auto where we could view the list of waypoints in the current route and be able to select any route from our library and start navigation.Thank you.
@bluetuz said in Android Auto bugs and improvements:
Hi, I'm an MRa user (Next 4.3.7 + Gold Planner). I have been on a motorcycle trip around England and France, covering approximately 4,000 km. On previous trips, I've used an Android tablet with the navigation app installed. On this trip, I had to change my system and traveled using a Carpuride w702bs and MRa for Android Auto. The system performed acceptably well, but I think there are improvements to be made to the app when running in Android Auto mode.
The most important thing is that we need to improve the app's stability, as it has crashed several times. The phone running the app was a Samsung S24 Ultra. Another issue I've detected is that the Exit button on the app screen in Android Auto covers the road speed signal displayed on the screen, so it would be necessary to move that button in future updates.
As for improvements, I think there are two important ones to implement in future versions.
One of them relates to waypoints. Android Auto doesn't display waypoint names even when you're at the location where the waypoint is located, and I think this is a major flaw. In fact, it would be important if the name of the next waypoint always appeared on the screen until you reach it. We already have the time and distance information to the next waypoint, but it's necessary to know the name of that waypoint.
Finally, it would be a great improvement to have a menu in Android Auto where we could view the list of waypoints in the current route and be able to select any route from our library and start navigation.Thank you.
-
Hi, I'm an MRa user (Next 4.3.7 + Gold Planner). I have been on a motorcycle trip around England and France, covering approximately 4,000 km. On previous trips, I've used an Android tablet with the navigation app installed. On this trip, I had to change my system and traveled using a Carpuride w702bs and MRa for Android Auto. The system performed acceptably well, but I think there are improvements to be made to the app when running in Android Auto mode.
The most important thing is that we need to improve the app's stability, as it has crashed several times. The phone running the app was a Samsung S24 Ultra. Another issue I've detected is that the Exit button on the app screen in Android Auto covers the road speed signal displayed on the screen, so it would be necessary to move that button in future updates.
As for improvements, I think there are two important ones to implement in future versions.
One of them relates to waypoints. Android Auto doesn't display waypoint names even when you're at the location where the waypoint is located, and I think this is a major flaw. In fact, it would be important if the name of the next waypoint always appeared on the screen until you reach it. We already have the time and distance information to the next waypoint, but it's necessary to know the name of that waypoint.
Finally, it would be a great improvement to have a menu in Android Auto where we could view the list of waypoints in the current route and be able to select any route from our library and start navigation.Thank you.
@bluetuz, what can and may be displayed by AA/CP devices is not up to MRA but to Google and Apple. They simply do not allow what they consider distracting information or UI elements. That's also the reason why most navigation apps on AA/CP look quite similar concerning the UI.
-
Hi @Corjan-Meijerink, I started this thread with the intention of contributing ideas and reflecting on the issues the app is experiencing after a long trip and many kilometers with MRa in its Android Auto mode.
I sincerely and humbly believe that my contributions should be taken into consideration, as they come from experience and many hours of testing (I bought Next when it was in beta).I think it's very important to improve the app's stability, and I'm aware that it's complicated and requires dedication and work, but it's an essential feature.
I think the Exit button on the speed sign is easy to fix and should be resolved in the next version.
I know Android Auto has certain limitations and restrictions, as has been mentioned here, but in the case of the next waypoint name indications, it wouldn't be a problem because, for example, Waze displays a lot of information on the screen and in a very dynamic way. Knowing the name of the next waypoint is very relevant and important information for the driver. Knowing the distance and the time is important, but you must know that time and the distance to where they're taking you (to restaurant X, gas station Y, viewpoint Z, etc.).
The app would be a huge boost if we were able to see the list of waypoints within the Android Auto menu. It would be incredible if we could choose which waypoint to jump to from that list. This would give the app a significant leap in quality.
Another very interesting feature to integrate would be the ability to choose a route from our library in Android Auto.I know you're developing and changing a lot of things for the new version, and I'm eagerly awaiting these improvements.
Finally, I'd like to tell you that it's becoming more and more common to have Android Auto or CarPlay on a motorcycle, either natively, as some brands already integrate, or with a device like the Carpuride or Chigee, which is so popular and so present on so many motorcycles now. Therefore, I think it's very important to improve the app for this system, enhancing it with new features and making it functional and stable. Many motorcycles can already control Android Auto or CarPlay from the handlebars, and integrating new features into the app for these systems would open the door to new partners.
Thank you for your tremendous work and dedication.
I hope my comments are helpful and are taken into consideration. -
Hi @Corjan-Meijerink, I started this thread with the intention of contributing ideas and reflecting on the issues the app is experiencing after a long trip and many kilometers with MRa in its Android Auto mode.
I sincerely and humbly believe that my contributions should be taken into consideration, as they come from experience and many hours of testing (I bought Next when it was in beta).I think it's very important to improve the app's stability, and I'm aware that it's complicated and requires dedication and work, but it's an essential feature.
I think the Exit button on the speed sign is easy to fix and should be resolved in the next version.
I know Android Auto has certain limitations and restrictions, as has been mentioned here, but in the case of the next waypoint name indications, it wouldn't be a problem because, for example, Waze displays a lot of information on the screen and in a very dynamic way. Knowing the name of the next waypoint is very relevant and important information for the driver. Knowing the distance and the time is important, but you must know that time and the distance to where they're taking you (to restaurant X, gas station Y, viewpoint Z, etc.).
The app would be a huge boost if we were able to see the list of waypoints within the Android Auto menu. It would be incredible if we could choose which waypoint to jump to from that list. This would give the app a significant leap in quality.
Another very interesting feature to integrate would be the ability to choose a route from our library in Android Auto.I know you're developing and changing a lot of things for the new version, and I'm eagerly awaiting these improvements.
Finally, I'd like to tell you that it's becoming more and more common to have Android Auto or CarPlay on a motorcycle, either natively, as some brands already integrate, or with a device like the Carpuride or Chigee, which is so popular and so present on so many motorcycles now. Therefore, I think it's very important to improve the app for this system, enhancing it with new features and making it functional and stable. Many motorcycles can already control Android Auto or CarPlay from the handlebars, and integrating new features into the app for these systems would open the door to new partners.
Thank you for your tremendous work and dedication.
I hope my comments are helpful and are taken into consideration.@bluetuz, You can be sure your suggestions are read, also without reminding again.
The team is continuously improving the AA/CP functions, but you must realize it will never be as smooth, easy and function complete as the native app. That is simply not possible under restrictions from Google and Apple.Another very interesting feature to integrate would be the ability to choose a route from our library in Android Auto.
This is of course possible from the menu as it is.
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/ CAT S52 + MRA app -
@bluetuz, You can be sure your suggestions are read, also without reminding again.
The team is continuously improving the AA/CP functions, but you must realize it will never be as smooth, easy and function complete as the native app. That is simply not possible under restrictions from Google and Apple.Another very interesting feature to integrate would be the ability to choose a route from our library in Android Auto.
This is of course possible from the menu as it is.
@Con-Hennekens I know the Android Auto version may not be exactly the same as the original version, but the stability and improvements I'm proposing are perfectly implementable.
