Wireless Android Auto not working since A17

Norman

trickywinter I recommend also showing the github issue some love if possible, so we can help the devs pinpoint the issue

Norman

An update for everyone involved, there seems to be some progress on (hopefully) fixing this issue: https://github.com/GrapheneOS/platform_packages_modules_Bluetooth/pull/74

Norman

Another update: the PR to fix this issue got merged so the fix will be available in the next OS release! 🎉

trickywinter

Norman while testing I changed to the beta branch for AA. Still busted there but works for 10 min at a time instead of every 60 seconds.
Should this be rolled back to official for the OS update?

Norman

trickywinter the fix will come in the next OS release, the version of the AA mirror has nothing to do with it.

Obasav

Just updated to the new version of GrapheneOS and it doesn't appear to fix the issue. I have a better time maintaining my connection to the AAWirelessTwo+ now, but it doesn't launch AA.

Norman

Obasav That's a shame, I hope I don't run into the same issues. Maybe then we need to create another issue...

Obasav

Norman Did you get an opportunity to test it?

Norman

Obasav No I won't for a while due to some personal circumstances

Arcanis

I tried it out and it looks like the Bluetooth keeps randomly disconnecting and stopping music playback. I think the one positive is I didn't see AA flashing in and out and an AA VPN error screen. So Babysteps. Another thing that may have been tied to this problem is that since the update, WzSabre is finally able to connect correctly, so apps like HwR and JBV1 now have crowd source alerts again. Since the whole AA issue has been happening, WzSabre stopped working, which makes the whole problem a mobile connection issue. At least I know they are getting close to finding the bug.

trickywinter

Norman OS updated today. Same issues with AA. Only difference is it reconnects quicker but still constant on/off with AA. Unusable.

muhomorr

@Arcanis @trickywinter The fix in the current OS release was for Android Auto auto-connect not working in private space and in work profile. The issue that you describe is separate. Capture full system logs from Settings > System > View logs immediately after unexpected Android Auto disconnect and send them to logs@grapheneos.org

Norman

I'll be able to provide my feedback/account by Friday probably.

Norman

muhomorr @trickywinter

Update from my end.

I've used Android Auto for the past few days with my car. Wirelessly, in Private Space. I unlock Private Space before entering my car, and enable Bluetooth.

My car connects to my phone after about 10 seconds, then after another 10 it will boot up Android Auto.

I did a 3+ hour drive with a break, which disconnected my phone, and then reconnected it. Also did a bunch of smaller drives.
Thus far I've not run into any issues! No disconnections, and Android Auto connects just fine every time.

Huge props to you Muhomorr for getting this fixed. I hope it stays as consistent in the future. If there are any issues, I'll be sure to post them.

« Previous Page