I did see similar disconnect / connect looping issues when connecting from GrapheneOS (A15 base) to a 2021(?) Ford F-150. But at that time I didn’t have iodéOS 6.x rooted so just got the red screen “22” error with it, and I don’t think I got to test it with iodéOS 5.x either. It will be months before that truck would be available again for testing. But what I am wondering is if different manufacturers are more or less compatible.
It was a bluetooth issue. It was solved by removing any pairing from both car and phone after AA wired setup and re-paring as wireless AA instead of regular Bluetooth.
It must still be somehow specific to this patch as I never had issues on stock where it seamlessly transitions between wireless AA and regular bluetooth.
Thanks for the help !
1 Like
I had the same issue. I had first set up AA via a usb cable (and it auto-paired the bluetooth as part of this). Then to try AA wireless, it would not pair etc. until I deleted the BT pairing from the phone (I had also removed the device from the vehicle saved devices in my case, not sure if necessary), and did not connect explicitly from BT, but rather through the AA prompts of using the device.
So I think we can confirm for this thread that “for iodé 6.x, to get AA functionality you need to root with Magisk and add the aa4mg magisk module”. Does that sound right? Hopefully this is not always the case, maybe the devs (LOS, microG, and or iodé) will be able to crack this particular nut in the future.
1 Like
Is this of any use? Android Auto crashes on startup (#26) · Issues · MindTheGapps / vendor_gapps · GitLab
I’m hoping to recover AA on iodé as soon as possible.
Thanks all