[Android Auto General] lastimpression:
some quick feedback on the 2.0.0 firmware update for @Snirpo.

TL;DR bug report - it appears 2.0.0 has some problematic interaction between Start/Stop mode and the new WiFi Client feature settings that become apparent for me when i tried to disable Client mode and switch back to Hotspot mode and got stuck with Start/Stop mode being enabled.

details if interested:

i have two AAW units: unit-1 connected to a Sony XAV-AX5500 in a car with pretty basic setup needs (original firmware worked well but did see reboots attributable to the interference issue well discussed here); unit-2 connected to a Sony XAV-AX5000 in a small RV which i was intending to use with a self-installed WiFI system.

phone is a pixel 6 with AAwireless app v2.6.0 and current Android 12 firmware. both XAV-AX5500 (v1.13) and XAV-AX5000 (v1.06) are on the latest firmware available for them.

unit-1 (id SM1Rz3aA) experience: after upgrading to 2.0.0 today unit-1 continues to work very well. used it first without any configuration changes and it was solid where previous firmware was solid, garbled/dropped/rebooted where the previous firmware did the same. changed the WiFi settings to use channel 165 and the garbled/dropped/reboot issues stopped in all the locations i normally and regularly saw them.

i plan to play with the "dongle mode" to see if a separate problem specific to the XAV-AX5500 lingering on my pixel 6 after all devices are turned off - i don't think that problem is attributable to AAW since it started with Android 12 and only presents with the XAV-AX5500 but figured it doesn't hurt to see if it might help.

unit-2 (id 8DkP1jEm) experience: upgraded to 2.0.0 and in normal use (original WiFi Hotspot mode, no special settings in AAW, pass-through is required for both Sony units) works well as before with same caveats for interference related reboots.

i then configured and experimented with the Start/Stop mode on the new firmware and then turned it off (i'll get to why in a later note).

then i configured unit-2 to use WiFi in Client mode and saved the settings. unit-2 rebooted, connected to the intended WiFi SSID, phone connected, AAW came up and worked as expected. played music, podcasts, used Maps, etc - all worked well. opened AAwireless app and noticed Start/Stop mode was enabled. click on the button to turn it off but it shows a popup saying the Start/Stop cannot be used in Client mode. reconfigured unit-2 to use Hotspot mode and saved settings. unit-2 rebooted but then phone couldn't connect to it at all while it was plugged into the XAV. unit-2 had white LED showing so i suspected the Start/Stop mode was involved. AAwireless app phone notification noted it couldn't connect, opened app and it timed out trying to connect. unplugged it from the XAV and plugged into a power-only jack and connected with AAwireless app and see the Start/Stop mode is still enabled - disabled it, saved settings, connected unit-2 to the XAV and all came back up in normal mode.

in my short testing with the WiFi Client mode there were a couple of times when i couldn't figure out how to get the AAW device and phone to connect together. the XAV headunit doesn't have a button to press to initiate AA mode unless it has a AA-capable phone connected. i'll play with it more when i have more time and report back.

it is unclear to me what function the AAwireless app notification's "Stop" and "Restart" action buttons are supposed to have. the notification appears to be the same one whether in WiFi Client mode or in the Start/Stop mode. "Stop" appears to just disconnect the app from the AAW device and the notification goes away and AA/AAW continue working. i don't remember what the "Restart" button did or if i tried it in this round.