Toyota Aygo (Pioneer) Bluetooth connects and disconnect

[toffyjan]

I’ve tried different USB cables and flashed multiple versions, but the Bluetooth keeps connecting and disconnecting. It stays on 'Waiting for Android Auto'. I'm experiencing the same issue with the latest WirelessAndroidAutoDongle v0.5.0 (https://github.com/nisargjhaveri/WirelessAndroidAutoDongle)

I tried in Toyota Aygo. Android Auto works fine with usb cable. I know you can't help much without logs, but maybe you've encountered this kind of issue before.
The attached image is a combination of two screenshots. Bluetooth keeps connecting and disconnecting continuously.
I'm able to connect to the AAWireless Wi-Fi by entering the password ConnectAAWirelessDongle, even though it shouldn't be necessary—it should all happen automatically after the Bluetooth connection.

I really appreciate your work.

[manio]

I know you can't help much without logs, but maybe you've encountered this kind of issue before.

The problem is that this 'Waiting for Android Auto' is very common and doesn't specify the exact problem. So really can't tell you more without the logs. Your screenshots doesn't help either :(

I'm able to connect to the AAWireless Wi-Fi by entering the password ConnectAAWirelessDongle, even though it shouldn't be necessary—it should all happen automatically after the Bluetooth connection.

That's good, so it would be easier for you to get the logs :)
Exactly as you said - directly connecting to WiFi is not necessary at all in the "normally working" process.
If you're not in a hurry I am planning to add option for fetching logs via webserver which I added recently...
Please also consider joining us on Discord so it will be more direct help :)

[toffyjan]

I know you can't help much without logs, but maybe you've encountered this kind of issue before.

The problem is that this 'Waiting for Android Auto' is very common and doesn't specify the exact problem. So really can't tell you more without the logs. Your screenshots doesn't help either :(

I'm able to connect to the AAWireless Wi-Fi by entering the password ConnectAAWirelessDongle, even though it shouldn't be necessary—it should all happen automatically after the Bluetooth connection.

That's good, so it would be easier for you to get the logs :) Exactly as you said - directly connecting to WiFi is not necessary at all in the "normally working" process. If you're not in a hurry I am planning to add option for fetching logs via webserver which I added recently... Please also consider joining us on Discord so it will be more direct help :)

Thank you for your time. I can wait for the option to fetch logs via the web server. In the meantime, I'm trying to gather some logs, but it's a bit of a headache in this case. Could you please point me in the right direction regarding how to join the Discord.

Another thing I'm considering is that maybe the USB port in the car doesn't provide enough power to run the Raspberry Pi 2 W (enough power need for raspberry pi 2W, Bluetooth and wifi)

[manio]

Thank you for your time. I can wait for the option to fetch logs via the web server. In the meantime, I'm trying to gather some logs, but it's a bit of a headache in this case.

OK... here is the most recent version with webserver and Download log option:
https://github.com/manio/aa-proxy-rs/actions/runs/16186975037/artifacts/3501467051

What you need to do:

1. Flash the proper image to your raspberry
2. Try several times to connect to dongle bluetooth from your phone
3. If it is still not working, connect to the dongle WiFi (you need to set a password for this, but you're probably aware as you was doing it before)
4. Enter your PI address in the browser to access embedded webserver

Then you should have this blue button to fetch the logs:

5. Give me the logs so I could see why it is not working

Could you please point me in the right direction regarding how to join the Discord.

Just click here.

Another thing I'm considering is that maybe the USB port in the car doesn't provide enough power to run the Raspberry Pi 2 W (enough power need for raspberry pi 2W, Bluetooth and wifi)

I don't think so... Pi02W is the most power efficient device from the supported Pi's.
I hope you have a proper cable with USB Data+power (there are sometimes power-only for charging, but not for data).

[toffyjan]

I don't think so... Pi02W is the most power efficient device from the supported Pi's. I hope you have a proper cable with USB Data+power (there are sometimes power-only for charging, but not for data).

I am using this cable https://www.amazon.de/-/en/Android-Mobile-Charging-Samsung-Motorola/dp/B0D41NKZ9R

[manio]

I am using this cable https://www.amazon.de/-/en/Android-Mobile-Charging-Samsung-Motorola/dp/B0D41NKZ9R

Should be fine:

[toffyjan]

I collected various logs and zipped them all. I hope they will be helpful.

aa-proxy-rs-logs.zip

[manio]

Thanks for the logs... Indeed same problem as reported in Nisarg's project.

In the mean time: does it help if you clear the cache?

[toffyjan]

Thanks for the logs... Indeed same problem as reported in Nisarg's project.

In the mean time: does it help if you clear the cache?

I used the 'Clear All Data' option in Android Auto's developer settings, but it didn't help. I'm going to try with an older Samsung Galaxy running Android 11 and see what happens. I haven't cleared the cache in the Android Auto app yet — I might try that and see if it helps.

[manio]

@toffyjan
This is somehow shot in the dark, but please try this:
https://github.com/manio/aa-proxy-rs/actions/runs/16234601041/artifacts/3517959707

Edit: fixed url, the old one was probably bad

[toffyjan]

@toffyjan This is somehow shot in the dark, but please try this: https://github.com/manio/aa-proxy-rs/actions/runs/16212730982/artifacts/3510480501

Edit: fixed url, the old one was probably bad

I can confirm that this works fine with the Google Pixel 9 Pro running Android 16 and Android Auto version 14.8.152744-release.daily. I cleared both the cache and storage. Now it's time to play with Docker. Thank you and appreciate your work. I will shortly join Discord for further help.