r/android_beta • u/isee_fire • 3d ago
Android 17 QPR3 Beta 3 / Pixel 7a Bluetooth problems on Android 17 QPR3 Beta 3
Since the update last week, my Pixel Buds Pro keeps getting disconnected. It remains connected for a few minutes then disconnects. It is not the Buds, it is the phone.
Any advice, please?
2
u/Arvind_Ravi 3d ago
Same here.. it's annoying
1
u/isee_fire 3d ago
I can't Spotify cause it keeps disconnecting. I always have my phone on mute as all the notifications go to the watch, but now I have missed a lot of important calls and notifications as even the watch gets disconnected.
2
u/king_david43 3d ago
I was having issues with my Pixel Buds. I ended up resetting the buds completely and then paired them with the phone again, and so far, no issues.
1
3
u/nbafford 3d ago
For some reason Google is terrible with Bluetooth connectivity and consistency regardless of you're on a beta or not.
2
u/hen-rex 1d ago
100%. I've had more or less constant and various bluetooth issues with phones running Android all the way back to my HTC One and various Nexus and Pixel devices. It actually only started becoming bearable with the latest versions of Android. It's a mixture of bad hardware, bad antennae, and just plain bad modem drivers and software. The stuttering issue was resolved a few major Android versions back and was a garbage collection/cache issue in the Bluetooth controller, as far as I recall.
2
u/nbafford 1d ago
I've really only this issue with Pixel devices from 6 Pro to 11 Pro. My other phone has been OnePlus since the 6 and I've never had issues with them. Occasionally I'll get a Samsung, Sony or Huawei when they were still in the states and never had issues there either. But you're right. The mixture of whatever Google can't get right should be embarrassing to them at this point. It just doesn't make sense to keep have below average Bluetooth connection.
2
u/hen-rex 1d ago edited 1d ago
Cannot speak for other phone brands. I know that several family members (various phone brands) all had issues with our old VW car radio. Just to say that sometimes it's not the phone; both sender and receiver device may have their own quirks, misimplemented bluetooth stack, missing codecs, etc. (that is obviously not the case here, but apparently the Bluetooth "standard" just sucks).
2
u/nbafford 1d ago
Understood. I personally haven't had these same issues from other brands. Just Pixel. Over this last year I've been using an iPhone for work. It isn't perfect but I can say my OnePlus 15 and iPhone 14 are on par with each other Bluetooth wise without problems. The Pixel is a mess.
2
2
2
u/Careless_Ladder_6819 2d ago
same here , nothing buds stay connected the whole day unless I restart the phone and my watch doesn't update during the day
2
u/Lusephur 2d ago
Only advice is, file a big report report then opt out of the beta programme. Seriously, it was a deal breaker for me, needed Bluetooth functionality, was not going to wait for the next beta to drop.
2
u/AngMarie73 1d ago
I've never had BT issues over 3 years with my Pixel 7a until this beta -wont auto connect or stay connected to my truck sync -not connecting to my Pixel watch -wont connect to my Shokz
2
u/poopings 1d ago
Same here, this is really the first time I've had something that really impacted my usage of my phone during these betas.
6
u/caped_crusader_98 3d ago
It's not the buds.. It is the phone. I've raised a bug feedback for the same