LightBlog

mardi 9 juin 2020

Google will roll out an update to improve Pixel Buds Bluetooth stability and connectivity

The Google Pixel Buds launched a couple of months ago and received mostly glowing reviews. These truly wireless earbuds are what most people wanted back when the first Pixel Buds were announced. However, as good as the Pixel Buds may be, they aren’t without issues. One of those issues has been audio cutouts and pausing. Google will soon fix the problem with a software update.

Google addressed the situation in the support forums for a report that was created in early May. The Pixel Buds user says they experienced audio cutting in and out when moving their head. Re-pairing the headphones with their phone didn’t solve the issue. Google eventually sent the user a new pair of Pixel Buds and the problem persisted. Several other users in the thread reported the exact same issues with their Pixel Buds.

Earlier today, a Google employee addressed the issues and said a software update will “improve Bluetooth stability and connectivity” in the coming weeks.

I just wanted to let all of you know that we’ve heard you, and our team will be rolling out software updates in the coming weeks to improve Bluetooth stability and connectivity.

They later went on to elaborate that the update will decrease the instances of phone call cut-outs, improve auto-recovery when one or both earbuds lose connection, and improve media playback stability for phones with software audio encoding. This week, there will be an update (296) to decrease the audio hissing/static noise that some people have experienced.

Pixel Buds users are being asked to participate in the Help Community and send bug reports if they experience the issues. They can do this by going to the preferences page for Pixel Buds on their phone > More settings > Send feedback.


Via: 9to5Google

The post Google will roll out an update to improve Pixel Buds Bluetooth stability and connectivity appeared first on xda-developers.



from xda-developers https://ift.tt/3hdKUUf
via IFTTT

Aucun commentaire:

Enregistrer un commentaire