Can't get AA to start up on RAV4

[adrwhong]

Hello,

Phone is a Pixel 5 running Lineage OS 23.2 and Samsung S9 running Android 10
Car is RAV4 2021
Tried different data usb cables in USB port, not PWR on Raspberry Pi Zero 2 W
Tried reflashing Rpi image
Tried clearing appdata/cache on AA
Both phones say on head unit occsaionally: device cannot be recognised.

On Pixel 5:
Phone seems to pair with dongle successfully via BT then disconnects, I see the wifi connection set up and connected. Nothing happens on head unit. Sometimes says "check your phone to set up AA when parked". Phone shows in notifications "Connecting to Android Auto" with a spinning progress bar

Samsung S9:
Seems to connect via BT fine, but nothing happens on phone nor the head unit

Any help would be greatly appreciated ! Thank you for all the work on this project 🥇

Here is the logs

aa-proxy-rs.log
messages.txt

[manio]

Hey 🙂

Unfortunately the logs look like they’re cut off right at the moment when the head unit (HU) connection result should appear… so it’s hard to see what actually happened there. You can also enable persistent logging, btw.

Anyway, I’d suggest checking a few things:

1. USB cable – yeah, I know you already tried different ones 😅 but if you have any other data cable lying around, it’s still worth another shot. Some cables just act weird with AA.
2. Try disabling the legacy option.
3. Maybe also try this: Unable to connect #72 (comment)
4. Finally, if you have a Linux machine, you could try using DHU (Desktop Head Unit) to test the connection outside the car.

Let me know how it goes...

[Snirpo]

@adrwhong

Does the device turn off when Android Auto starts connecting?

[adrwhong]

@manio
I've set up a linux machine w/ DHU to test.. so the best I got so far is the phone is in a loop of trying to make AA happen. It seems to be going in a loop. Multiple phones are doing the same thing. Attached dmesg output here and hopefully the logs are better this time. Tried legacy mode and no luck. Tried more cables and same result. Tried the steps in #3 as well, no luck

@Snirpo nope, rpi nor phone turn off during the entire process

dmesg_output.txt
aa-proxy-rs.log
messages.txt

Thank you for your help so far @manio and @Snirpo

[manio]

When you see this in your dmesg:

[ 6850.187623] usb 1-1: new high-speed USB device number 55 using xhci_hcd
[ 6850.312269] usb 1-1: New USB device found, idVendor=18d1, idProduct=2d00, bcdDevice= 6.12
[ 6850.312281] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6850.312286] usb 1-1: Product: aa-proxy (Raspberry Pi Zero 2 W Rev 1.0)
[ 6850.312291] usb 1-1: Manufacturer: aa-proxy
[ 6850.312295] usb 1-1: SerialNumber: 00000000704a35a6

then in this correct moment you need to launch (eg on another console) in your ubuntu:
desktop-head-unit --usb=00000000704a35a6
You did it like this? (try disable legacy as well if you have problems)

Maybe also try the following binary?
💻 Google Desktop Head Unit for Linux:
https://dl-ssl.google.com/android/repository/desktop-head-unit-linux-x64_r02.1.zip

[adrwhong]

@manio it seems its in some sort of loop of the usb device connecting then disconnecting. I see my phone gets the connected to AA notification then goes away. Yep, I tried legacy mode on and off. Also tried the 2.1 binaries. Gave the rpi a factory reset today and same thing.

$ ./desktop-head-unit --usb=00000000704a35a6
Android Auto - Desktop Head Unit
  Build: 2022-12-15-495552137
  Version: 2.1-linux

ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
[W]: No configuration specified - using default values.
[E]: Could not load configuration from '~/.android/headunit.ini'.
BoringSSL is the SSL implementation used in the receiver-lib.
Starting link. Requested protocol version: 1.7
[I]: Searching for compatible USB device with serial number '00000000704a35a6'...
[I]: Found 11 USB devices.
[I]: Device 'aa-proxy aa-proxy (Raspberry Pi Zero 2 W Rev 1.0) 00000000704a35a6' (vid=18d1, pid=4ee1) supports AOAPv2, starting accessory mode...
[I]: No device found ready yet, will retry shortly...
[I]: Found 11 USB devices.
[I]: No device found ready yet, will retry shortly...
[I]: Found 10 USB devices.
[I]: No device found ready yet, will retry shortly...
[I]: Found 10 USB devices.
[I]: No device found ready yet, will retry shortly...
[I]: Found 10 USB devices.
[I]: No device found ready yet, will retry shortly...
[I]: Found 11 USB devices.
[I]: No device found ready yet, will retry shortly...
[I]: Found 11 USB devices.
[I]: No device found ready yet, will retry shortly...
[I]: Found 11 USB devices.
[I]: No device found ready yet, will retry shortly...
[I]: Found 11 USB devices.
[E]: Couldn't find/access compatible USB device.
[E]: Failed to start Google Automotive Link.

[manio]

This might be a permission problems, look also here:
#72 (comment)

[manio]

One more thing I forgot to mention - I see you pointed out the loop.

If it wasn’t there, the first time there was a connection issue, nothing else would happen. And here we have quite a few things that can fail - for example, the phone might stop connecting, the HU might stop responding, or the connection itself might stop transferring data.

In all those cases there are built-in “safety nets” that make the device keep retrying the connection. That’s intentional and by design. It’s normal.
I know it can be annoying - you’re trying to set something up or figure things out, and the phone keeps going beep-beep and relaunching AA.

But without that behavior, the whole thing would be useless whenever there’s a problem. We can’t assume that every time you get into the car everything will start perfectly on the first try and stay connected until you get out ;)

[adrwhong]

@manio ok I'm getting somewhere..!! so I factory reset it then reboot and re-pair the phone via BT and it's working on 2 phones I have! The pixel 5 pairs but disconnects instantly (this is the phone I ultimately want to work) - same result in legacy mode. I can't seem to get devices to consistently work when using multiple phones..

$ sudo LD_LIBRARY_PATH=/home/adrwhong/Android/Sdk/build-tools/36.1.0/lib64:/snap/android-studio/209/plugins/android-ndk/resources/lldb/lib64:$LD_LIBRARY_PATH ./desktop-head-unit --usb=00000000704a35a6
Android Auto - Desktop Head Unit
Build: 2022-12-15-495552137
Version: 2.1-linux

ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
[W]: No configuration specified - using default values.
[E]: Could not load configuration from '~/.android/headunit.ini'.
BoringSSL is the SSL implementation used in the receiver-lib.
Starting link. Requested protocol version: 1.7
[I]: Searching for compatible USB device with serial number '00000000704a35a6'...
[I]: Found 11 USB devices.
[I]: Ignoring device '0000:3c:00.0' while searching for '00000000704a35a6'.
[I]: Ignoring device '0000:3c:00.0' while searching for '00000000704a35a6'.
[I]: Ignoring device '20120501030900000' while searching for '00000000704a35a6'.
[I]: Ignoring device '0000:00:14.0' while searching for '00000000704a35a6'.
[I]: Ignoring device 'ba20b486d7e7' while searching for '00000000704a35a6'.
[I]: Ignoring device '200901010001' while searching for '00000000704a35a6'.
[I]: Found device 'aa-proxy aa-proxy (Raspberry Pi Zero 2 W Rev 1.0) 00000000704a35a6' in accessory mode (vid=18d1, pid=2d00).
[I]: Found accessory: ifnum: 0, rd_ep: 129, wr_ep: 1
[I]: Attaching to USB device...
[I]: Attached!

Phone reported protocol version 1.7
ssl state=TLS client read_server_hello -1
ssl state=TLS client process_change_cipher_spec -1
ssl state=SSL negotiation finished successfully 1
SSL version=TLSv1.2 Cipher name=ECDHE-RSA-AES128-GCM-SHA256
Verify returned: ok
[I]: Received ByeBye 4 from phone.

aa-proxy-rs (1).log
messages-2.txt

[manio]

Nice you have it working (at least it started)...
I can see that it doesn't start USB transfer (and you are using legacy mode). What if you disable it, and please also set stats_interval to 1 second so it would be easier to see if there are any bytes.

[adrwhong]

I feel we're getting close..

With legacy mode enabled, it stays connected with the phone, DHU says "Waiting for phone..." but nothing pops up on my phone. Tried clearing storage and cache of AA app and restarted. Same result:

sudo LD_LIBRARY_PATH=/home/adrwhong/Android/Sdk/build-tools/36.1.0/lib64:/snap/android-studio/209/plugins/android-ndk/resources/lldb/lib64:$LD_LIBRARY_PATH ./desktop-head-unit --usb=00000000704a35a6
Android Auto - Desktop Head Unit
 Build: 2022-12-15-495552137
 Version: 2.1-linux

ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:878:(find_matching_chmap) Found no matching channel map
[W]: No configuration specified - using default values.
[E]: Could not load configuration from '~/.android/headunit.ini'.
BoringSSL is the SSL implementation used in the receiver-lib.
Starting link. Requested protocol version: 1.7
[I]: Searching for compatible USB device with serial number '00000000704a35a6'...
[I]: Found 11 USB devices.
[I]: Ignoring device '0000:3c:00.0' while searching for '00000000704a35a6'.
[I]: Ignoring device '0000:3c:00.0' while searching for '00000000704a35a6'.
[I]: Ignoring device '20120501030900000' while searching for '00000000704a35a6'.
[I]: Ignoring device '0000:00:14.0' while searching for '00000000704a35a6'.
[I]: Ignoring device 'ba20b486d7e7' while searching for '00000000704a35a6'.
[I]: Ignoring device '200901010001' while searching for '00000000704a35a6'.
[I]: Found device 'aa-proxy aa-proxy (Raspberry Pi Zero 2 W Rev 1.0) 00000000704a35a6' in accessory mode (vid=18d1, pid=2d00).
[I]: Found accessory: ifnum: 0, rd_ep: 129, wr_ep: 1
[I]: Attaching to USB device...
[I]: Attached!
> Phone reported protocol version 1.7
ssl state=TLS client read_server_hello -1
ssl state=TLS client process_change_cipher_spec -1
ssl state=SSL negotiation finished successfully 1
SSL version=TLSv1.2 Cipher name=ECDHE-RSA-AES128-GCM-SHA256
Verify returned: ok

aa-proxy-rslegacymodeon.log
messages-legacymodeON.txt

With legacy mode disabled: (same terminal output [I]: Received ByeBye 4 from phone.)
aa-proxy-rs-legacymodedisabled.log
messages-legacymodedisabled.txt

[manio]

https://github.com/aa-proxy/aa-proxy-rs/blob/main/static/config.json#L220
Why are you enabling this option? It's a developer option for quite different purposes.
Please disable it.

[j4ckp0t85]

Hi. Maybe it's not your situation, but i had a similar problem when i tried to use a rpi4 with a 2018 golf.

There is a setting in aaproxy (don't recon exactly the name) to invert the order of connections (first connect the rpi to dhu, then connect phone to rpi).

Try to switch this toggle.

Remember to reboot the device

[manio]

Hi. Maybe it's not your situation, but i had a similar problem when i tried to use a rpi4 with a 2018 golf.

There is a setting in aaproxy (don't recon exactly the name) to invert the order of connections (first connect the rpi to dhu, then connect phone to rpi).

Try to switch this toggle.

Remember to reboot the device

Thanks. You probably referring to change_usb_order. So it's not working with this option in your golf?

[j4ckp0t85]

Hi. Maybe it's not your situation, but i had a similar problem when i tried to use a rpi4 with a 2018 golf.
There is a setting in aaproxy (don't recon exactly the name) to invert the order of connections (first connect the rpi to dhu, then connect phone to rpi).
Try to switch this toggle.
Remember to reboot the device

Thanks. You probably referring to change_usb_order. So it's not working with this option in your golf?

In my case it worked. Now i'm using a milkv duo (no need to change order)

[adrwhong]

I think also to add.. I'm not sure what's going on with this Pixel 5 but it is the only phone I have that has problems connecting to my car for wired AA. Tried different cables and different cars, same result. Tried stock and LineageOS, same thing. Port has been cleaned. Maybe something wrong with one of the data pins in the port but I don't think it should affect wireless AA..

https://github.com/aa-proxy/aa-proxy-rs/blob/main/static/config.json#L220 Why are you enabling this option? It's a developer option for quite different purposes. Please disable it.

Hm, I toggled it on and off but dhu option was disabled already.. I checked the config via ssh too. Same result: "Waiting for phone" or I get the ByeBye 4 message in terminal

Hi. Maybe it's not your situation, but i had a similar problem when i tried to use a rpi4 with a 2018 golf.

There is a setting in aaproxy (don't recon exactly the name) to invert the order of connections (first connect the rpi to dhu, then connect phone to rpi).

Try to switch this toggle.

Remember to reboot the device

Same result "Waiting for phone".. doesn't seem to make it better or worse atleast