Updated beta! 4.3.4 (374)
-
Hi everyone!
This update contains some fixes to your feedback and minor improvements
- Fixed issue where route would not recalculate after deviating.
- Fixed issue where section of track would be skipped after deviating.
- Fixed issue where not all user defined waypoints would be used in track navigation causing the displayed upcoming waypoint to be incorrect
- Minor improvements to nearby fuel suggestions. Regarding searching them and the animation / way of adding them. Suggestions are also shown in track navigation but suggestions cannot be added.
- Enhanced voice instructions. They now include lane assist (when also enabled by user) and more detailed highway information.
- Displaying recent searches on map while navigating and searching for a stop.
- Better determination of nearest waypoint when starting a route (or track).
- Moved screen lock up in menu, can also be activated by long pressing the menu button.
- When generating AB route in the home screen fails, we will use a fallback
This version is intended for public release
Looking forward to any feedback from you all!Cheers,
Corjan -
@Corjan-Meijerink These look like great improvements! Looking forward to trying them!
Vinnie
-
@Corjan-Meijerink I hope the Android version will comes soon because tomorrow I have a motorbike ride planned! Then I can immediately see how it goes.
Fantastic that speed with you! -
this app just gets better and better well done MRA gang, and to be fair all the beta testers too, as it is us who put forward the legitimate issues.
posted originally in wrong thread
-
@Corjan-Meijerink Still no Android version yet. It's a pitty!
met een R1250RT met TFT en BMW Connected Ride App; de Garmin Zumo XT en My Route App in combinatie met de Carpuride W702 (voor Android op de Motor!)
-
@white-mouse-on-the-motorbike it’s there now!
-
Just did an Android update... 4.3.4 375!
-
The improvements in recent updates, specifically concerning track-based navigation, have tempted me to reinstall MRA Navigation again after a long time. In theory, this is exactly what I was hoping for when MRA Next was first announced way back when and for the most part, it works quite nicely. Good stuff!
I've tested it over the weekend on a route I know quite well, where I made a couple "mistakes" on purpose to see how the system would handle it. The basics went quite well, but I did encounter a few issues.
The first issue I encountered is that the route I had planned (using the web planner, on the TomTom map) had already changed when I viewed it in the app, because of a ferry crossing (which we know HERE doesn't handle correctly, it tried to send me around adding 30 minutes and 20 kms to my trip; yes, I know there's a work-around, no, I'm not going to use it). So, sadly, it seems I'm still not able to trust that my planned route will not be touched when using it for navigation, even with track navigation, which is one of the main reasons I don't want to use route-based navigation for planned routes (simple A-B is fine, of course, but that's not what I use MRA products for).
The second issue was that I (on purpose) put a Via-point on one road and then (again, on purpose) used a different road. The good thing is that the system (with recalculations enabled) handled my deviation quite nicely: recalculation was quick and suggested a reasonable alternative route. Obviously, it tried to send me back to the missed Via-point (as expected). What I did not expect, was that I had to skip multiple waypoints to get rid of that. As I did this while driving (yes, I know I shouldn't have), I didn't notice which point(s) I actually needed to skip manually (automatically skipping waypoints is enabled in the app, not sure if it affects track-based navigation?). I got the impression that it may have been asking me to skip all points (including shaping points) from the start of the route and not just the via-point I missed, but it could also be that it somehow didn't correctly register that I wanted to skip the via-point and just kept asking me about the same point multiple times.
A third, completely separate, issue I've noticed on a few occasions, is that I get a notification that the app has crashed after I've used CarPlay, but I haven't used MRA itself). I'm using the latest iOS version (just updated to 18.2, but also noticed it with 18.1) and the latest beta (haven't tried it with the official release yet). I've had this before as well (with way older versions). I've mostly been using the betas, so it could be a beta-only/TestFlight issue.
