Google Pixel buds A keep disconnecting. [317798832]

Fixed

Bug

Platform

Status Update

No update yet.

Description

ro...@gmail.com

created issue #1

Dec 26, 2023 07:34PM

Originating component:
- Build Number: google/oriole_beta/oriole:14/AP11.231117.006/11174680:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

What type of Android issue is this? Bluetooth

When did this happen?
Dec 26, 2023 2:29 PM GMT+05:30

What steps would let us observe this issue?
1. Connect Google Pixel buds A.
2. Play any media eg. YT music, Youtube, Google podcast, Amazon prime video etc.
3. Audio gets disconnected after some time but media keeps playing.

What did you expect to happen?
Audio must be available.

What actually happened?
No audio.

How often has this happened?
Every time

What was the effect of this issue on your device usage, such as lost time or work?
Moderate

Additional comments
Have to disconnect and reconnect bluetooth all the time to use Pixel buds. The issue happens in other wireless earphones (Nothing ear 1) as well but the audio gets started after 10 seconds automatically.

Debugging information
Google Play services
com.google.android.gms
Version 234816038 (23.48.16 (190400-590025996))
System App (Updated)

Android System WebView
com.google.android.webview
Version 609914433 (120.0.6099.144)
System App (Updated)

Network operator: Vi India
SIM operator: Vodafone IN

Filed by Android Beta Feedback. Version (Updated): 2.39-betterbug.external_20231115_RC02 (DOGFOOD)
To learn more about our feedback process, please visit

https://developer.android.com/preview/feedback#feedback-app.

Comments

ro...@gmail.com <ro...@gmail.com> #2Dec 26, 2023 07:35PM

Information redacted by Android Beta Feedback.

bugreport-oriole_beta-AP11.231117.006-2023-12-26-14-29-46_GMT+05:30.zip

Restricted+

25 MB

Download

bugreport-oriole_beta-AP11.231117.006-2023-12-26-14-29-46_GMT+05:30_REDACTED.zip

Restricted

19 MB

Download

so...@google.com <so...@google.com> Dec 27, 2023 12:54AM

Assigned to so...@google.com.

so...@google.com <so...@google.com> #3Dec 27, 2023 03:21AM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

so...@google.com <so...@google.com> #4Jan 5, 2024 12:51PM

Marked as fixed.

The issue has been fixed and it will become available in a future Android release. Please keep an eye on the release notes(https://developer.android.com/preview/release-notes.html).

da...@gmail.com <da...@gmail.com> #5Jan 19, 2024 05:24PM

How long till this hit stable?

The issue is really annoying. Pixel 8 Pro + Pixel Buds A-Series + Pixel Watch. This should work without any issue and instead we have to manually disable Bluetooth on the watch whenever we use the buds. Don't you have quality controls on your products interactions?

da...@gmail.com <da...@gmail.com> #6Feb 17, 2024 04:40AM

Have the same issue. Pixel buds disconnect constantly. Works without issue on Pixel 6 with Pixel Watch.

-Pixel 8, Pixel Buds A, Pixel Watch-

de...@gmail.com <de...@gmail.com> #7Feb 27, 2024 07:17PM

I have the same issue. Pixel Buds A, Pixel Watch, and Pixel 8 Pro. If I turn off my Pixel Watch my buds no longer disconnect.

ty...@gmail.com <ty...@gmail.com> #8Mar 3, 2024 07:08PM

Same issue. Upgraded to Pixel 8 Pro and did not have similar issue with older Pixel 4. Poor service from Google

cr...@gmail.com <cr...@gmail.com> #9Mar 4, 2024 07:18PM

Yep both of my pair of buds are doing the same on my pixel 6 pro while google watch is connected I have my watch on aeroplane mode to stop it but shorely that can't be the only answer.

te...@gmail.com <te...@gmail.com> #10Mar 5, 2024 06:21AM

We have been waiting for a fix since October 2023. But this is still not fixed in the March update!

jo...@gmail.com <jo...@gmail.com> #11Mar 5, 2024 10:23PM

Any updates here? This is infuriating

st...@bsg23.net <st...@bsg23.net> #12Mar 6, 2024 06:24AM

Google, Status-Update?!

ge...@gmail.com <ge...@gmail.com> #13Mar 9, 2024 07:40PM

Same issue here. Pixel 8 Pro + Buds A + Watch. Buds either constantly disconnecting or nor playing audio while connected after some time (usually around 5 to 10 minutes). Buds worked flawlessly with Pixel 6a and same Watch. Would appreciate to get some information when this will be fixed. Cannot use Buds with my brand new 1000+ Pixel 8 Pro and my Pixel Watch. That's really a shame.

te...@gmail.com <te...@gmail.com> #14Mar 12, 2024 05:23PM

#13
This should have been fixed for QPR2 and Pixel Buds A

s....@gmail.com <s....@gmail.com> #15May 11, 2024 06:03PM

The issue is still there. Its really annoying to have the buds disconnected while on a call. I am using a buds a series and a 6-pro. Really really really frustrated.

da...@gmail.com <da...@gmail.com> #16May 21, 2024 06:46AM

Just a feedback for Google.

The bug was reported on the 26th of December 2023. It was fixed on the 5th of January 2024 (comment #4), very fast considering the Xmas holidays in the middle.

What is inaccettabile is that the fix, hasn't been released to devices after 6 months. It is still in the Android 15 beta.

This is a but affecting 2 of your flagship products. You need to have some way to expedite the release of this kind of thing.

It should have been released in Android 14 as an hotfix in January.

Please fix your process.

lc...@gmail.com <lc...@gmail.com> #17Jun 21, 2024 10:52PM

Yeah ive been putting up with it, but I'm not going to buy google hardware again. I'm thinking of detatching from google entirely. I've lost my trust in them.

sa...@gmail.com <sa...@gmail.com> #18Nov 30, 2024 11:51AM

Also been impacted by this and had the buds replaced by Google originally. This is brand damaging and must be costing a fortune as well - surprised they've let this bug get so far..

pg...@gmail.com <pg...@gmail.com> #19Apr 3, 2025 05:13PM

still having this problem. All firmware updated. Pixel7

am...@google.com <am...@google.com> #20Apr 7, 2025 06:36AM

comment#19

,

Even though the issue sounds similar, the internal root cause would be different, so please raise a separate ticket along with the bugreport from your device.

Thanks.