After coffee, MRA does not continue from where we left off.

[Frank Hosper]

When going for a coffe and powering the bike (and my 7"RiderNav R7M) down, MRA is kept alive on my phone,but when starting up the bike the navigation does not continue by joining the nearest point on the route, but it tries to send me back to where the biginning of the track was.

I need to change any MRA setting on my phone, or what?

Regards,
Frank Koster

[nomko]

Hi Frank,
That's a known error/bug/inconvenience of MRA.
If you use the search bar you can find similar topics. Perhaps you can find the solution in 1 of those topics.

[b0hd1]

@Frank-Hosper The simplest solution is to check the next point before starting the route, and if it tries to send you back to the previous point, skip it manually. It's simple, practical, and fast. Sometimes algorithms can be a bit unpredictable.

Regards

[white.mouse]

The simple solution is to when you leave your bike and your AA connection with the phone is lost, just close down AA. When you will continue your ride just start AA again. In my case this did the trick!
The problem is de lost connection. It will not connect in the right way when you return to your bike.
Another solution will be to leave your phone at your bike. Than the connection does not get lost!

[Frank Hosper]

what do you mean by AA connection?

[Nick Carthew]

@Frank-Hosper AndroidAuto

[Mzokk]

I take my phone away from my Africa Twin AA screen to get coffee/lunch and when I reconnect it to the phone I say yes to "Resume Navigation" on the screen. I don't close the app when the phone is no longer connected to the bike. Seems to work fine for me?

[Frank Hosper]

Hi Mzokk. Your fix does not work for me, because AA is connected via a switched positive lead to the BMW canbus. With other words, when stopping the running engine and going off contact, the AA will also power down.

[white.mouse]

Well I found out that disconnecting Android Auto for me the best solution was.
And yes, sometimes forgetting to disconnect, it also worked! But not allways.
After closing Android Auto and a fresh restart and then resume navigation, it always went good!