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!

[Frank Hosper]

Hi White.Mouse

I am not sure how I am supposed to disconnect Android Auto. For this to happen I do not have to take any action (as I see it). When I stop the bike the TFT screen goes black and the AA screen also powers down after some 6- 7 seconds. I.e. the canbus switched all of the bike electrics off. So physical disconnection of AA is already a fact. So I lso cannot as you mention "forget to disconnect the AA", since this is already an automatic process aided by the Canbus.

So after locking my bike I walk away for a coffee with my handphone in my pocket, while leaving the AA (powered down) in the BMW navigation cradle on the bike.

The "fresh restart"you talk of is, I imagine, achieved by pushing the start button (or turning the start switch) whereby the TFT screen comes alive, and shortly thereafter automatically followed by the AA screen (since the AA trigger wire observed the canbus coming "alive"). At that moment accepting the command "Resume Navigation" did not allow me to continue my intended route from.

The above is a bit of an elaborate write-up, but I was afraid my initial write-up was maybe not clear.

If anybody got a work-around, than please be specific in the actions to be taken. Rather than use generic statements. I am new to this and may need "baby speak" instructions.

If this ios a known bug, is anybody than at least trying to resolve this?

Regards
Frank

[Leike Lodiers]

I have a samsung phone and they've got i made a routine in the setup under routines. That if bluetooth dive turns on and the aa in use to start the mra app and set volume to max. And one routine that if bluetooth device turns of to automaticly tirm of the mra app en turn volume bach to normal. Now if i turn on the beemer my android turn on an mare start and ask if i want te navigate further with my route...... And it works fine until now. And i don't need to take out my phone.