Latest Google Pixel Bug Messes With Your Audio Settings

Hotstar in UAE
Hotstar in UAE

There’s a new Google Pixel bug lurking around, and this one messes with your phone’s audio settings. To be more accurate, it impacts the phone’s ringtone, notification sound, and default alarm sounds. They seem to be randomly changing on Google’s phones.

Latest Google Pixel bug may mess up some of your audio settings

People have started noticing that the phone’s ringtone is different, without their input. The same goes for notification and alarm sounds. Needless to say, this is quite odd, and confusing for people.

I didn’t notice this happening on my Pixel 4a, but folks over at 9to5Google seem to be having this issue, along with a number of other people. In fact, it seems like Pixel phones set sounds that are not even selectable in the Sound picker, at least in some cases.

It seems like the issue started happening once the April security patch landed. The issue doesn’t seem to be affecting everyone, but there were some reports. The source only noticed it on one phone, and that device was running Android 12 QPR3 Beta 1.1 at the time.

Check to see if the bug affected your unit

If you own a Pixel smartphone, you may want to go to Sounds & vibration, to see if you’re affected. If one of the ringtones is set to something you don’t recognize, you’ll need to change it back manually. We’re not sure if the change will be reverted or not, but it hopefully will not.

As per usual, people have been reporting the issue via Reddit. This issue doesn’t seem to be isolated to one Pixel variant, as various Pixel smartphones seem to be having issues, including the Pixel 5, 6, and more.

Pixel smartphones are not exactly strangers to bugs. In fact, the Pixel 6 and 6 Pro had plenty of them at launch. Google patched up most of those, rather fast, but new ones do creep in from time to time. This is the perfect example of that.

This is an annoying bug, for sure, but it’s at least not something that impacts the core functionality of the device. Let’s hope Google will patch it up soon, so that it prevents something like this from happening moving forward.

2022-04-12 15:06:00