Open miguel7501 opened 2 months ago
It's either a bug in the upstream Bluetooth code or an issue with the device which happens to get handled better by the older Bluetooth code and other platforms. Looks a lot like the current Bluetooth device not following the protocol properly which causes a disconnection. It might have stricter handling of this specific case.
I'll have access to a stock Pixel 8 in 2 weeks and will test it with that to narrow it down.
The logs should be directly comparable, the code in the GOS log viewer is pretty clear even without knowing much java so I can avoid reading the logcat docs once more.
Is it resolved with the current stable release?
The issue still occurs on 2024102400
.
I did do some testing on the stock Pixel 8 and listened to music for about 45 minutes with logcat running, then when I started writing my reply and didn't have logcat running, the headset disconnected. I didn't have time to do more testing, but I did notice that the stock pixel 8 has the com.android.bluetooth
package listed as 'Bluetooth legacy' and there's also com.google.android.bluetooth
listed as 'Bluetooth'. I plan on doing some more testing if I get the chance, are both of those relevant or just com.android.bluetooth
?
Both of those are relevant but also more than that.
Hi,
I recently got a Pixel 8 pro with GOS and this headset disconnects after a bit for no apparent reason. It works perfectly with other android, linux and windows devices over bluetooth and the phone works perfectly with other BT headphones (I tested Sony WH-1000XM4 and Sony MDR-1000X).
Here's the logcat of the bluetooth system app when reproducing the issue. No other BT devices were conneted this time, but that appears to not matter.
The log starts with connecting the device at 9:43 and it disconnected at 9:47:51
These lines in particular look interesting to me:
I have "always show crash dialog" enabled and got no crashes, the screen was not turned off for this test and I used spotify for playback. None of that seems to make a difference to the disconnects in my experience, so this is likely separate from other issues on bluetooth. The audeze HQ app for managing the headset is installed atm, but removing it didn't make any difference in the past. I also fiddled around in the dev settings (disabled BT LE audio, disabled A2DP HW offloading and switching codecs from LDAC to AAC and SBC) without any success.
I've also taken an unfiltered HCI snoop, but I don't know what PII that contains so I'm hesitant on posting it publicly. I can gather more data if needed.