AA just isn't usable
-
@Corjan-Meijerink Hi. I know there is some work on AA in the pipeline, but do we have any timescales? I bought the lifetime licence for Navigation Next and a Chigee AA/CP unit for use with MRA, but at the moment it's not even beta stability.
I don't care about the zoom, or the map layout, or even the fact that roundabouts show as the wrong junction type, often indicating the wrong direction. I'd just like it to not crash every single time.
Today's use was typical. I started the bike, switched the Chigee to AA, opened MRA via the Chigee and selected my 95-mile route. I clicked to start navigation and rode out of my drive. Within seconds I could tell that the display wasn't updating. Nothing. Totally static. Luckily one of my first stops was a fuel station. I pulled over and opened MRA on my phone and chose the next waypoint manually. The map updated on the Chigee, so I set off. Again, the map stayed static, but this time the instruction box just turned to a spinning circle and stayed like that. I opened Maps and Waze and they were both updating fine, but MRA was frozen apart form the spinning circle. When I next had the opportunity to pull over again I had to manually force stop the MRA app on the phone and give up. I just rode the route by memory with a bit of help from Sygic showing the roads.
I love the planner, and the phone app works great too. But AA isn't even pre-release. It literally goes wrong every single time, if not before I even leave my drive then as soon as I make a stop and try to resume navigation.
Sorry for the rant, but this is so frustrating.
I hope some time for AA development is scheduled for 2024.
-
I just sat down to post about my experience today but I think I'll just tag onto yours, @Tim-Watson.
I was riding a similar route using a Pixel 6 Pro phone an inexpensive "Weuaste" running Android Auto. Worked fine until I needed to make a bathroom break. I pulled into a gas station on my route, so I was maybe 10 meters away from the road, if that. I turned off the ignition which powered down the AA unit, but not the phone. I started back up and it became clear that the display was stuck where I pulled over. MRA was frozen on the phone, so the Weusate was accurately reflecting that.
I tried stopping and restarting navigation and exiting MRA and starting it over. Same thing. The only thing that fixed it was reboot the phone. Then everything came back. (This troubleshooting by the side of the road is not enjoyable!)
Maybe it's not related to AA, but I suspect it is because I haven't had that problem when just using the phone for navigation without the AA unit.
I may have seen another post or two about this. It happened to me today.
Vinnie
-
Just to add a little more to this frozen AA scenario - when MRA stops responding on the head unit after pressing Navigate, often the phone app still has the Navigate button available to press, which sorts MRA. So if you're happy to get the phone out of your pocket each time, that can help. The problem with this is that often clicking Navigate on the phone app actually brings up a solid grey screen for MRA and the phone needs rebooting or the app force stopping.
-
Sadly I too have been having the same problems with AA. The app says go left, and AA says go right. Then the circle going round and round, and nothing happening at all.
The App on it's own ( apart from a 5% drop in battery power in less than 15 miles, which is plugged in via a USB in my Mitsubishi car, which rather renders the app use, a bit problematic to use over a long period of time ) is brilliant.
I love MRA, it's the perfect planning tool to use. For me nothing comes close. Basecamp, which I can also use without any problems, is OK but the various maps that MRA offers is light years ahead of Basecamp. I too wish that this ongoing problem would be sorted out soon. But having said that I firmly believe that the MRA team will get there in the end, of that I've no doubt.
