2022 Jeep Gladiator - Wifi & Bluetooth connect, no change on vehicle display
I have a 2022 Jeep Gladiator w/ their standard head unit running UConnect. Burned image to micro SD, connect phone to head unit via USB-C to let Android Auto start, then plug the Pi Zero 2W in. I see and connect to Bluetooth, phone then connects to Wifi and is "Looking for Android Auto", but never finds. There is no change in the head unit display indicating anything is connected.
I've pulled the /var/log/messages file and attached it to the ticket. My USB cable has the trident on it and I've tried a few others that seem to have 4-pin on both sides, all with the same outcome. Any assistance will be greatly appreaciated.
Do you have good quality USB cable with data (not only power) ?
And I assume you connect to OTG port in your RPi?
Much improved! I recalled I had a Wacom tablet that took MicroUSB, tested the cables I had used previously and they would not allow it to work, then found the cable that came with it and started getting "Device not supported" errors on the console. I found that setting AAWG_CONNECTION_STRATEGY=2 in the aawgd.conf file allowed it to work, mostly!
Now the only shortcoming is it seems not to recognize my vehicle's microphones. Any attempt at voice input and it not only does not recognize, but I can't tell that it is even receiving input based on the console interface.
Any ideas on how to get the vehicle microphones working? Will provide logs if that's a help.
Now the only shortcoming is it seems not to recognize my vehicle's microphones. Any attempt at voice input and it not only does not recognize, but I can't tell that it is even receiving input based on the console interface.
Any ideas on how to get the vehicle microphones working? Will provide logs if that's a help.
You're using a pass-through mode so generally the audio is working as AndroidAuto intended. The bluetooth audio is used for calls. If you want more sophisticated audio setting you might try my project with MITM mode, there you can eg disable media/TTS sink, etc. The MITM logs should also tell you more (eg what your HU is sending to the phone) but I doubt if it will help "recognizing your mic" magically if it is not working now...