Update 5.1 - CarPlay / Android Auto improvements and more!

[Mzokk]

Run the new version today on an Android Phone. Offline 162 mile route with 32 waypoints. No issues at all. Will test again tomorrow on the Africa Twin AA screen. Good job.

[Corjan Meijerink]

@Mzokk thanks for sharing

[Corjan Meijerink]

So interesting how many people report how much better this version works while others still have problems.

Rest assured, we will continue this journey to further improve the app!

[Adrian Avram]

Hello all !
Used the 5.1 version from Romania to Hungary and back using Android Auto. Truly impressed that track recording was working even after a refuel stop, si thats perfect. The only thing I am not sure about is the route loading directly from Android Auto. Before I was able to select the route and start it, but now it only works from my phone ( on the display I get an message that loading routes while driving is not possible …but I was standing still while trying that )
So maybe there is a glitch or I am not doing something right ?
Thanks !

[Jörgen]

@Corjan-Meijerink said:

Can confirm HERE released their update yesterday.
Expecting to implement that tomorrow in the app and push towards a quick Alpha / Beta / release.

I'll even try to add POI management / persistent map items and road avoidance features
Hopefully their SDK works as expected with the fix for map spinning.

Which Version will this be?

[Robert Lamont]

Went on tour to Wales from Ireland and was pleasently surprised with the auto update and love the new features. CarPlay is much more resilient. The Compass is a brilliant addition. It's just simpler to use. I am pleased to say that MRA has become my default sat-nav in both my car and on moto.
Congratulations.
Looking forward to the next surprises. Thank-you

[Mzokk]

Follow up to yesterday's post using the app on an Android phone. I used the same phone today Motorola Edge Neo 40 (Offline) connected to the Android Auto screen of my Honda Africa twin. 82 mile route with 67 waypoints (its all backroads) no issues including missing some waypoints as one of the roads was closed due to roadworks. No high power use or other weird behaviour. Seems as stable as it was yesterday just using the phone.

[Corjan Meijerink]

@Mzokk thanks for sharing your experience

[Bart De Medts]

Tested the app again and everything works perfectly. What an amazing app it has become. In 3 weeks I’m heading to Norway, and the only navigation app coming with me is MyRoute-app

[Guido Rulof]

I just returned from 10 days in the Dolomites. I drove the majority of the journey with the previous 5.1 version of MRA and spent 2 days with this new version. I am completely won over. MRA surprised us very positively and guided us flawlessly through 3,000 km of Europe. Even at local road closures and detours, MRA had already devised a workaround before we even realized a blockage was imminent. MRA calculated perfect detours, no longer than necessary, and on excellent roads. It then brought us neatly back onto the route. I did experience a frozen screen with the latest version (AndroidCar), but this was easily resolved by simply unplugging the phone. In short, very satisfied.

[Corjan Meijerink]

@Guido-Rulof thanks for sharing your positive experience!

[peha]

I was out on a little trip today. At one point, I ran out of gas and wanted to find a gas station; to do this, I tapped the magnifying glass on the Android Auto unit while driving—somewhere between waypoint 3 and 4 or so—then tapped on gas stations and selected the top entry (the first suggested station). The screen immediately went black and I got an error message saying an unexpected error had occurred and the app was closed. When I restarted it afterwards (via the Android Auto unit), it froze ("App is not responding") for a while until it finally restarted. After that, the navigation seemed "messed up" (it wasn't clear to me if I was now navigating to the gas station or the original route—and whether it was starting "from the beginning" or picking up from where I actually was).

The gas station search still feels somewhat unintuitive to me (why am I shown a gas station "in 23 km (!) along the route" when I actually pass several on the way, or one just a street over—not directly on the route, but it would only be a detour of maybe 500 meters?), and it apparently isn't 100% stable/reliable yet. For example, what's the best way to proceed if I want to find the nearest gas station while navigating on the highway (where stations are rare and absurdly expensive): do I take the next possible exit and only then search for a nearby station using the AA display > magnifying glass > gas station?

Aside from the crash and the known "spinning while standing" problem, which will hopefully be fixed soon (I think that was also the main reason for the confusion when restarting the navigation), the user interface changes (altitude display, etc.) on Android Auto are very well done! Go, Corjan & team!