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

sjvudp commented 4 days ago

Description

Today I had two issues:

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.
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 commented 3 days ago

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 commented 3 days ago

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 https://github.com/osmandapp/OsmAnd/issues/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:

https://github.com/osmandapp/OsmAnd/issues/21363 https://github.com/osmandapp/OsmAnd/issues/21361 https://github.com/osmandapp/OsmAnd/issues/21259

osmandapp / OsmAnd