Description: Music goes silent on LHDC v5 earbuds after a second Bluetooth device disconnects from a Pixel. Check the exact trigger, safe workarounds, Google's October 2 fix and beta data risks.
On some Android 17 setups, audio playing through LHDC v5 earbuds can fall silent the moment a second connected Bluetooth audio device disconnects, even though the earbuds still appear connected. Google lists issue #554992287 as fixed in Android 17 QPR3 Beta 1, released October 2, 2026. For immediate recovery, try turning Bluetooth off and back on when it is safe to interrupt your other connections.
The unusually specific trigger
The public report documents a Pixel 7 on stable Android 17 build CP2A.260705.006. The reporter streamed to OPPO Enco X3 earbuds using LHDC v5 while a JBL Flip 4 speaker was also connected. Turning off the inactive speaker silenced the active earbuds. Android still displayed the earbuds as connected and selected. A control run using AAC continued playing. These are one reporter's repeatable tests, not an estimate of how many Pixel owners are affected.
| What you see | How to interpret it |
|---|---|
| LHDC v5 music stops exactly when the other connected speaker powers off | Matches the documented trigger |
| Earbuds disconnect completely | Check ordinary pairing and radio issues too |
| One AAC/SBC device is connected and audio never starts | Likely a different problem |
| Calls fail but music works | Inspect call-audio settings separately |
Safe checks and temporary fixes
- Check your build: Settings → About phone → Android version. The Android 17 label alone does not identify the fix.
- Check media output and volume carefully: Make sure your earbuds remain the selected output before changing volume; avoid a sudden loud blast when sound returns.
- Toggle Bluetooth off and on: Google's Pixel troubleshooting guide recommends this basic reset. Do it only when disconnecting calls, car systems or accessories is safe.
- Avoid the two-device trigger: Disconnect the spare speaker before connecting and playing through the LHDC v5 earbuds. This is a practical workaround, not a guaranteed permanent repair.
- Try AAC temporarily where supported: The reporter's AAC comparison kept playing. Codec menus vary by accessory and phone; if you use Developer options, note the original setting and restore it afterward. Do not factory-reset the earbuds for this test.
- Check the official update path: If your compatible Pixel is already enrolled in the beta, use Settings → System → Software updates to see whether QPR3 Beta 1 or a later build is offered.
What is confirmed, and what is analysis?
Google's release notes confirm the fix listing. In the public issue, the reporter captured a lost LHDC v5 encoder handle and repeated error logs; a Google engineer identified encoder-state clearing during codec initialization as the likely underlying fault. That technical discussion is stronger evidence than a generic 'Bluetooth bug' claim, but it does not establish that every headset or Pixel model fails. The reporter suggested the busy loop might cost CPU and battery; no population-wide battery-drain measurement was published.
Version and data-loss caution
As checked October 17, 2026, Google's fix is documented for QPR3 Beta 1 (DP11.260918.005 / DP11.260918.006), released October 2. Availability depends on the device and enrollment. The cited release note does not establish that all stable Android 17 devices already have the fix. Do not join a beta solely to troubleshoot a pair of earbuds without accepting beta risks. Leaving the beta for a stable build normally wipes local data, except during specified no-wipe transition windows. Avoid network resets, removing every pairing, or a factory reset as first steps.
Bottom line
If LHDC v5 playback dies when a second Bluetooth device disconnects, toggle Bluetooth, avoid simultaneous connections, or test AAC. The QPR3 Beta 1 fix is official; whether it has reached your stable build is a separate question. Verify both the connection indicator and actual audio.
References (5)
- Google Android Developers, Android 17 QPR3 Beta 1 release notes (2 October 2026): https://developer.android.com/about/versions/17/qpr3/release-notes
- Google Issue Tracker #554992287 (31 August–3 September 2026; reporter tests and engineer comments): https://issuetracker.google.com/issues/554992287
- Google Pixel Help, Bluetooth troubleshooting: https://support.google.com/pixelphone/answer/7334382
- Google Pixel Help, Android version and updates: https://support.google.com/pixelphone/answer/7680439
- Google Android Beta Program, opt-out and data-wipe conditions: https://www.google.com/android/beta
