Price Pony

High volume audio issue spotted on Google Pixel!

Google Pixel has been launched. Since then, the phone has received a lot of praise for its specs, particularly the camera. However, recently, people have spotted high volume audio issue with this phone!

High volume audio issue spotted on Google Pixel!

Normally, if anything can produce sounds, the audio will gets bad once it is overextended on the volume scale. That is why there are caps on the volumes, meaning the sounds of devices can only go up to a certain level. That is usually the case, and nothing more. However, recently, there are reports of high volume audio issue with Google’s two new phones, Pixel and Pixel XL in this aspect. Most phones only allow sound to go up to certain level, in order to prevent distortion of any kind to the sound. Users are reporting exactly these sorts of issue with Google phones.

Complaints come from Pixel owners, and they seem to persist through a lot of output devices. Be it a high-end Sennheiser headphone, or a Cast-enabled TV, the same issue happened. People also tested the same apps in different devices as well, then reached the inevitable conclusion that the Pixel and Pixel XL are the source of the problem. Reports also said that restarting the devices would not solve the issue. Some people have gone to Google Store over the issue and got their replacements.

On the other hand, the custom ROM community does not seem to suffer the same problem. There have been no topics or threads so far concerning the high volume audio issue for people who uses custom ROM. While it is no guarantee that Google’s software is the cause, it seems likely to be the case here. It could be because of the recent update from Google. For now, Google has been notified of the issue, and it is investigating. Once Google figures out the problem, they will get back to customers.

High volume audio issue: Don’t worry too much

Google has started investigation, so you should not worry too much. You can also go to the store to exchange for  new device. Hopefully this will be solved soon!

Exit mobile version