Issue with Raspberry Pi Zero 2W Connection

[liamfleming26]

Description

Hi Folks,

Thanks for this fantastic project! I've been using it on a Raspberry Pi 4, and it has been working flawlessly. However, I've encountered an issue when trying to use the same setup with a Raspberry Pi Zero 2W.

Details

I've flashed the appropriate image for the Zero 2W (manio/aa-proxy-rs/releases/download/v0.3.0/raspberrypizero2w-sdcard.img.xz) using Balena Etcher v1.19.25. Unfortunately, I've only been able to successfully connect once, and subsequent attempts have failed.

What I've Tried

• SD Cards: Tested multiple SD cards, including the one that worked perfectly with the Raspberry Pi 4.
• Cables: I tested several micro-USB cables to ensure they support data transfer, using an Android phone to verify them.
• Image Redownload: Redownloaded the image file to ensure no errors during the download process.
• Reflashing: Reflashed the SD cards with the freshly downloaded image to eliminate potential issues with the original flash.

Despite these efforts, the only result I can achieve is that the Android Auto icon appears on my car's head unit when using the Raspberry Pi Zero 2W. Conversely, the Raspberry Pi 4 boots in around 7 seconds and successfully connects with the head unit and phone.

Steps to Reproduce

1. Download the Raspberry Pi Zero 2W image and flash it using Balena Etcher.
2. Insert the SD card into the Raspberry Pi Zero 2W.
3. Connect the device to the car's head unit using a verified micro-USB cable.
4. Attempt to establish a connection.

Expected Behaviour

The Raspberry Pi Zero 2W should function similarly to the Raspberry Pi 4, enabling a full connection and seamless operation.

Actual Behaviour

The only observable behaviour is the appearance of the Android Auto icon on the car's head unit.

Additional Information

• Phone Model: Samsung Galaxy S22 Ultra
• Device: Raspberry Pi Zero 2W
• Flashing Tool: Balena Etcher
• Car Make: Ford
• Car Model: Focus
• Car Year: 2020
• Car Head Unit: Ford Sync 3

I'll gather some logs from the Raspberry Pi Zero 2W and share them here as soon as possible. Please let me know if you need any specific details or tests to help identify the issue!

Thanks again for your hard work on this project—it's much appreciated.

[liamfleming26]

As a follow-up to my initial issue, I've tested using the --legacy flag as documented in the README. Unfortunately, this worsened things, as I couldn't even get the Android Auto logo to display on the head unit.

I'm now planning to experiment with the --timeout flag and try setting it to 10 seconds and 15 seconds to see if this helps maintain a successful connection. Once I've had a chance to test this, I'll report back with my findings. It appears as though I invented the --timeout option in my head. Though I'm sure I saw @manio reference a -t option in #11, I'm hoping this may allow me to increase the amount of time it takes for the vehicle and pi02w to make a successful connection.

[manio]

Liam,
The timeout option indeed has been added but it is in not-yet-released tree. If you want to test it, just head to the recent build artifact for the moment, which is here.
Inside the archive should be a working image for pi zero 2 w.

Test it with some varying timeout values and reply back. And as always - I cannot help you further with this if you will not provide me the aa-proxy-ls logs :)