Unfinished navigation in Android Auto prevents startup of Android Auto when re-connecting

[sjvudp]

Description

Today I had two issues:

1. When turning on the car, the Android Auto screen had appeared. Then I had used the reverse gear to leave the garage (when using the reverse gear my car switches to the backwards sensors screen). When switching back to the forward gear, the display in the car claimed the phone would be incompatible with Android Auto. OK, that might be an issue of the car (or Android Auto), because re-plugging the phone fixed the issue.
2. After managing to activate navigation mode, I was "0 meters" from the destination when parking the car. I stopped the engine, unplugged the phone, and went for a meal. When returning, connecting the phone and starting the engine, the car did not display the Android Auto screen, but just connected in "headset mode" (hands-free profile). After arriving at home, I stopped the car, disconnected the phone, and opened OsmAnd. There the screen asked whether to terminate navigation or to continue it. Obviously it had not terminated navigation automatically when disconnecting the phone.

The issue seems to be that Android Auto is blocked from working when the phone is disconnected while in navigation mode.
Specifically, here was no such prompt on the Android Auto screen (terminate navigation). In an ideal world, disconnecting the phone from Android Auto would save the car's position even (it's offered on the phone's screen when not using Android Auto).

What makes matters worse is the fact that you cannot fix the problem from the Android Auto screen, and opposed to the issue listed as item 1, re-plugging the phone did not fix the problem.

Steps to reproduce

• Start "navigation" (enter destination).
• Arrive at destination more or less
• Disconnect the phone
• (Pause)
• Reconnect the phone

Actual result

Android Auto does not start up, but phone is only in "hands-free mode" and charging (when being connected via Bluetooth and USB cable).

Expected result

Android Auto screen should display

Your Environment (required)

WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!

OsmAnd Version: 4.8.6
Android/iOS version: 13
Device model: CPH2371, Opel Corsa (Stellantis) from 2023
Crash-Logs: ?

[yuriiurshuliak]

Regarding the reverse gear issue: This issue was resolved in OsmAnd version 4.9.6. Please try updating to the latest version, as it should resolve this problem.

Regarding the unfinished navigation issue: This appears to be a duplicate of #21361, which is already being tracked. The developers are aware of this behavior and will likely address it in an upcoming release.

[vshcherb]

This is tricky situation as we have ongoing several issues, they are better documented and more specific. I have the issue with reverse gear which sometimes leads to ANR or crashes, it's related to slow reinitialization after switch back which we are working on.

If you have ongoing navigation you should see #21363 Continue navigation button.

However none of the issues describe that AA is blocked, so we will need to see the video and think how to reporduce or probably retest after these issues are fixed:

#21363
#21361
#21259

[sjvudp]

Today I discovered another potential reason that may prevent Andoid Auto connection; however it seems to be different from the past (both, OsmAnd and Android Auto were updated since then):
In the past I thought that Bluetooth connection alone might be sufficient to make the connection work, and USB i jut needed for power (or some other undocumented magic).
But today I found out that I have to activate the option t"exchange files / Android Auto" when connecting the phone.
This is somewhat annoying, because I have to grab the phone, unlock it, then make the selection on the menu (well I could configure the phone to always enable file exchange when connecting USB, but I think that is a security problem).
OsmAnd version was 4.9.7 (BTW: Why does the version of OsmAnd display near the end of the "Help" menu instead of the start of it?) , and Android Auto was 13.2.64464-release.

Android Auto makes it very hard to do any type of quality checking, because they (Google) never state what has been changed in the current version. As it is now using Android Auto is a kind of lottery: It might work, or it won't, and what works today may not work in the future, because of steady changes and lack of documentation (as seem from the end-user's perspective).

[vshcherb]

Android Auto requires either Wifi or USB-data connection but usually Android switches to the right connection itself while it's cable connected.

[sjvudp]

OK, 4.9.7 seems to behave better: I made the following test today:

1. Navigate to the first supermarket, take the phone with me
2. Navigate to the next supermarket: When I had unplugged the phone I saw a read screen from Android Auto saying something went wrong (I can't remember the exact words), and I should unplug and re-plug the phone.
3. Navigate back home, taking the phone with me.

On all three legs the navigation screen actually worked (which was not the case in the past), but to my surprise OsmAnd had a dialog at the end of the tour asking whether I want to find a parking lot, or whether to terminate navigation. This is remarkable, because on the car's display the navigation displayed as finished.

(And as an unrelated side-note: When following a main road with several turns and crossings, the "turn arrow" ("tun left in 500 meters") only indicates where I have to leave the main road, but does not assist how to follow it: In contrast TomTom also suggests turns to take while following the main road. I know that Google maps also works like OsmAnd, but maybe it's because American roads are more straight than German ones ;-))

[sjvudp]

Android Auto 13.4.645054, OsmAnd 4.9.10, Android 13 (ColorOS 13.1):
Used Navigation to go to supermarket, disconnected the phone on arrival (took it with me), returned to the car, re-connected the phone (USB cable+Bluetooth): Car display said the device isn't compatible.
Arrived at the next supermarket, same procedure as above.
When back at the car and reconnected the phone, the car's display still said the device isn't compatible.
Arrived back at home, disconnected the phone, made a walk with the phone.
Back at home opened OsmAnd to see a menu with three items (like "find parking spot, finish navigation).

So my guess is that display of that menu (that wasn't displayed in the car's display) prevented OsmAnd to reconnect to the car, and Android Auto concluded from that that the phone is not compatible. I think this should be fixed!

[DmitryAlexei]

@sjvudp do you have active Maps+ or OsmAnd Pro subscription?
Android Auto only available in paid versions of the app