Update 5.1 - CarPlay / Android Auto improvements and more!

[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!

[M. Schrijver]

Finally the official 5.1 was there (Google found some time).
Did only one trip. Because of that just some simple comments from my side.

• Everything find fine
• Nice touch that enlarge next gas station icon
• Nice touch that compass in de altitudemeter.

[superg]

After the upgrade, mine phone (z fold 7) is getting hot ,
The rest is really fine, thanks.

[peha]

@corjan-meijerink Would it help to share the log file, regarding the crash (I don't know how tondo that, though)?

[Hubert Thoring]

@peha
In the account at the bottom, press the version number longer, then the protocols will be written.

[Cookie On Tour]

V5.1.0-462 iOS: Will the new fuel station indicator be improved? Sorry, if this already written, I did not read the entire thread here. But currently the indicator is somehow crazy, showing fuel station next, which are not there or even a distance of several kilometers away, even if I can see a fuel sign in the distance. Beyond that I don't find the symbol very helpful, I would expect that I can tip on it and the next fuel station would be added to the route to be the next routing point.

[Travellexxie]

For 2 months I struggled with the last version during my trip to Spain and Portugal. I am glad with the new version, no funny recalculations of the route I made in the planner and some other things. But last week I went for a trip with my car and after I returned, I got this weird tracklog, a straight line and a duration of 8:20 hours :

[Rob Verhoeff]

@Travellexxie Long time since I saw that one!

[Travellexxie]

And I didn't fly!

[peha]

@Corjan-Meijerink I seem to remember that you stated somewhere (I cannot find said comment right now) how the latest HERE update, yet again, still being problematic. Did they reapond to your "angry message" - is there an ETA when the fix might be in beta? It's very unlikely to see this in the next two weeks, I'm afraid?

[Corjan Meijerink]

@peha I’m afraid so too.

Will post a statement early next week after some final confirmations

[NigelT]

I'm just back from a 2 week trip in Europe and finally moved from Nav 5 to using MRA on a Chigee AIO5 (IOS and CarPlay).

The App worked fairly well, although still work to do and ran into bugs that required restart phone rather than just close app and restart.

The biggest problem for both myself and the other rider using the same unit is the size of the icons and text size choices on screen. Fine if you've got perfect eyesight but, if not, some text is so tiny as to be unreadable while riding. Have other people mentioned this and it can be addressed? Or do I just have to buy a bigger screen?!

[Aiello antonino]

There's been some discussion about this, and I've had some too, about the arrival data, mileage, etc., as well as the compass... with a CarPlay as large as the Garmin Zumo's screen, the data is very readable on the Zumo, but the same can't be said for the MRA, not to mention the altitude, which is really tiny... but I don't know if they'll address that... but honestly, I hope so, because it's not something you should ignore... at least I hope so...