Bug in latest release - bluetooth disconnects

shuteye

Morning, I got a system update Nov 23, installed it and now my bluetooth audio periodicly goes silent. I'm a blind screen reader user and use my phone exclusively connected to a bone conduction headset, and now even though the headset stays connected, the audio stops, and the only way to fix is to turn off the headset and turn it back on again. There's no rhyme or reason as to when it happens, sometimes the headset stays stable for hours, sometimes it drops out after only seconds. This seems to be the first stable release (I'm on stable channel) that contains the stuff for shared bluetooth audio, can anyone suggest how I might fix the issue?

shuteye

To add some more info here: my installed release according to the "info app" is: 2025112100 and I've noticed the above behaviour with a set of Suunto Wing headphones as well as both Soundpeats Air5 and Air5 pro models. All are using the apt-x protocol as per their bluetooth settings as I need apt-x adaptive to reduce latency for the screen reader. Its early testing, but the headsets most often cut out if I'm doing something screen reader intensive e.g. scrolling with two fingers through a big apps list or web page, at that point audio will cut out in seconds while the set might stay uneffected for some hours if I don't do much on the phone. I tried turning off apt-x as per a headset's bluetooth connection settings via the "connected devices" area in settings, and have not yet had bluetooth audio cut out... perhaps this is an issue with the most recent update and the Apt-X implementation on the Pixel 8? Can someone point me to where I might be able to get phone logs or other data that would assist in narrowing down the issue? My screen reader is so laggy w/out apt-x!

de0u

shuteye I'm sorry to hear that you're running into trouble with this. Hopefully a member of the team will be able to provide some input.

de0u

shuteye Do you have a GitHub account? I'm thinking it might be time to think about filing an issue on the GrapheneOS issue tracker.

nandohyphen1

I'm having a similar problem as @shuteye regarding Bluetooth. I usually keep Bluetooth turned on (so that it will auto connect to my saved devices). I have a BT stereo in my house that doesn't actually turn off (its an old car stereo, so to turn it right 'off' I'd have to turn off power completely). Since updating to QPR1 Bluetooth always tries to pair with the stereo and is usually successful, meaning all my notifications are silent, since they are going through the stereo (which is 'off'). So I always need to disconnect from the stereo, keep BT off, or forget the stereo for now. Before updating to QPR1 BT never did this. It stayed disconnected when I disconnected it from the stereo.

nandohyphen1

I just had Bluetooth crash out of the blue. I wasn't using it or anything. It gave me a crash log but I was in a different profile which I forgot I have set to not allow running in the background so when I tried to use inter profile sharing, I lost the crash log since the Profile ended itself when I switched to my owner profile to retrieve the log. If it happens again I'll try and grab the log and post it

shuteye

I don't have a git hub account but will make one for this! Screen reader lag from using the SBC codec is frustrating beyond compare - I want my apt-x back lol! re: stereo issue, I'm glad someone else is seeing BT issues as well!

shuteye

Issue 6606 created and linked to this thread so others observing issues please feel free to continue to post here.