Reboot loop

[JosemyAB]

Hello!

First of all thank you for your this awesome project!

I'm trying to use it with this hardware:

• Rpi zero 2w
• Peugeot 5008 - 2018
• PIxel 7
• Version 0.12.0

LOGS
aa-proxy-rs-1.log
aa-proxy-rs-2.log
aa-proxy-rs-3.log
aa-proxy-rs-5.log
aa-proxy-rs-6.log

I start connecting the phone using a wire directly to the headunit and everything works as expected.
Then I connect the raspberry (with default options), I connect vía bluetooth to it and then the raspberry enters in a boot loop.

No matters what I change in the setup, it always enters in boot loop.

Let me share some logs (each one with different setups like legacy on/off, dongle mode on/off, etc) I don't know how to interpretate the logs, but in all of them I see this trace:

1970-01-01, 00:01:47.094 �[34m[INFO]�[0m �[3m�[90m proxy: �[0m 📂 Opening USB accessory device: �[4m/dev/usb_accessory�[24m
1970-01-01, 00:01:47.094 �[31m[ERROR]�[0m �[3m�[90m proxy: �[0m 🔴 Error opening USB accessory: Device or resource busy (os error 16)
1970-01-01, 00:01:47.094 �[34m[INFO]�[0m �[3m�[90m proxy: �[0m 💤 waiting for bluetooth handshake...
1970-01-01, 00:01:49.942 �[31m[ERROR]�[0m �[3m�[90m usb: �[0m 🔌 USB Manager: Timeout waiting for accessory start, trying to recover..

and

1970-01-01, 00:00:53.313 �[31m[ERROR]�[0m �[3m�[90m proxy: �[0m 🔴 Connection error: error:80000002:system library:file_ctrl:reason(2):crypto/bio/bss_file.c:288:calling fopen(/etc/aa-proxy-rs/md_cert.pem, r), error:10080002:BIO routines:file_ctrl:system lib:crypto/bio/bss_file.c:291:, error:0A080002:SSL routines:SSL_CTX_use_certificate_file:system lib:ssl/ssl_rsa.c:329:

Do you see what could be the problem? I have the same problem with the "WirelessAndroidAutoDongle" by the way.

Thanks in advance!

[manio]

Hi Jose,
I reviewed your logs - I can see a few different issues here...
In the first log I see Bluetooth errors - the phone connecting to the Raspberry. Those errors could simply be what it looks like sometimes - I get the same even with a completely ideal setup. The phone sometimes acts up or reports "connection busy" and you have to wait until it's OK (for me often helps unlocking the phone, disabling bluetooth+wifi and re-enabling, but there are corner cases)...

But the main problem I see is that your connection to the HU isn't working. Normally I'd suspect the cable (missing data pins, poor quality), but since it works with your phone that's probably not it...
The other errors (resource busy) are a consequence of that problem - btw I hope we've already fixed that in the latest beta releases...
I'd also ask you to try legacy mode on and off - but you said you already tried that...

MITM mode requires keys. Without the keys (or with wrong ones), you’ll get a similar error...
As for the keys - feel free to join the Discord.

Don’t enable the DHU mode in the aa-proxy options - that’s only for very specific cases, for testing without a real device. In the latest versions I deliberately moved that option all the way down into the developer section.

And honestly, I’m not sure what else I can suggest... To me it looks like a typical HU communication issue. Try a few more times, and also try the version that’s currently being built:
https://github.com/aa-proxy/buildroot/actions/runs/18799542870
Once it finishes building, it’ll be the freshest “beta” version before the next release. It’s a bit experimental, but maybe it’ll happen to work for you... Also, feel free to join the Discord — maybe we can solve it together there.