Google acknowledges the audio issues affecting the Pixel and Pixel XL

posted by Milen Y. / Dec 20, 2016, 9:08 AM

Google acknowledges the audio issues affecting the Pixel and Pixel XL

Yesterday, a Redditor by the name of “Badmark” claimed he was on his fourth Google Pixel replacement due to a strange audio issue. Other Pixel and Pixel XL owners also chimed in the thread to share that they are experiencing the same issue where their phones produce a lot of distortion when playing back audio at the three highest volume levels.

A bug report regarding the problem was submitted to Google's Pixel User Community on Oct. 24, but it is only now that the problem became more widely documented, that Google has acknowledged it officially.

The Google rep in charge of the Pixel User Community has replied to the original post, saying that the issue is being investigated:

Hey Everyone,

Thanks for continuing to report examples here. The team is aware and continuing to investigate. I'll post an update as soon as there is some meaningful info for you all.

– Orrin, Pixel Community Manager

It is currently unknown whether the audio distortion is caused by a hardware issue in the Pixel and Pixel XL or if its rooted in software. If you are currently experiencing similar problems on your Pixel device, you are likely eligible for a replacement. However, judging by the various user reports on Reddit and Google's official Pixel Community page, even replacement units may exhibit similar problems so your best course of action for the moment may be to wait until Google issues an official statement on the matter. We will keep you updated.

PhoneArena is on Instagram. Follow us to stay updated with fresh news and flashy media from the world of mobile!

sources: Reddit (1), (2), Google

Options

13 Comments

1. Babadook

Posts: 230; Member since: May 24, 2016

So this is 100% fixable with a software update?

posted on Dec 20, 2016, 9:34 AM 0

2. Awalker

Posts: 1973; Member since: Aug 15, 2013

If it's a software issue.

posted on Dec 20, 2016, 9:37 AM 1

5. vincelongman

Posts: 5677; Member since: Feb 10, 2013

I think it is since its usually only happens at max volume with a specific app (perfect piano) or the mummy trailer Also people have found its happening on other devices too

posted on Dec 20, 2016, 10:43 AM 1

9. Well-Manicured-Man

Posts: 673; Member since: Jun 16, 2015

It is not a Software issue it is a Hardware issue that can be controlled by software. The noise you hear seems to be of electrical origin. It is electrical noise that makes its way to the speaker. Why only at full volume? At full volume the electrical signal becomes stronger so that the filter on the PCB cannot filter it out anymore. Basically, Google has equipped the PCB with an inadequate filter. You usually use a coil or a capacitor or a combination of both for filtering out electrical noise. Google has either sourced a component that does not cover the complete bandwidth of electrical noise within the pixel or the supplier or one of the multiple sourced suppliers does not deliver according to specification.

posted on Dec 20, 2016, 12:20 PM 0

10. vincelongman

It could still be a software issue IMO if it was a hardware it would have been more common and noticed within a few days of usage by all reviewers and users There's people saying they also experience it on other devices including iPhones and MacBooks Also apparently Pixels with Viper4Android don't have the issuehttps://www.reddit.com/r/GooglePixel/comments/5jdteg/i_believe_the_audio_poppingcrackling_may_be_a/ Its too early to tell could be either, but IMO its more likely to be a software issue IMO most likely that Google broken something in one of their updates

posted on Dec 20, 2016, 12:29 PM 1

11. marorun

Posts: 5029; Member since: Mar 30, 2015

Funny first i have no client thats came back with this issue. Second go see the thread its only happen in specific app and not in everything like you can play spotify music full blast whitout the issue. If its was hardware its would affect EVERY APP.

posted on Dec 20, 2016, 1:02 PM 1

3. palmguy

Posts: 979; Member since: Mar 22, 2011

I major tech company takes responsibility...... Unheard of.

posted on Dec 20, 2016, 9:48 AM 3

7. NarutoKage14

Posts: 1318; Member since: Aug 31, 2016

I know right!

posted on Dec 20, 2016, 11:43 AM 0

4. KingSam

Posts: 1425; Member since: Mar 13, 2016

The bugs are approaching iPhone levels. No offense to anyone but its true. Google better test the pixel 2 thoroughly

posted on Dec 20, 2016, 10:23 AM 1

6. NarutoKage14

Not gonna happen because no company can afford to hire enough testers for the time that's necessary to thoroughly test a phone. Besides, that's what early adopters are for I guess.

posted on Dec 20, 2016, 11:42 AM 1

8. Scott93274

Posts: 6032; Member since: Aug 06, 2013

Well, they have had a few issues thus far with the lens flare and the minor audio bug, hopefully, they can all be addressed with software updates... hopefully. And you have to remember that they rushed this device to market, hopefully with a full development cycle, the Pixel II will be that much better. I personally hope that it comes with wireless charging, that would make me a happy camper as I have yet to own a phone with this feature.

posted on Dec 20, 2016, 11:44 AM 1

12. marorun

IPhone level really? Two small bug? IPhone has a tendency to freeze completely , phone close at 30% battery and load more issues.. Pixel is by far the phone i have the least return where i work.. ( if you take a ratio of how many return out of 20 sold by example iPhone and Samsung are easily between 5 and 6 out of 20 sold thats return compared to maybe 1 out of 20 sold with pixel lol )

posted on Dec 20, 2016, 1:17 PM 1

13. The_Innovation

Posts: 648; Member since: Jul 18, 2012

Shouldn't be a tough fix if it's a software issue. It's not the first phone to have such problems/bugs. It can't be a hardware issue because the speaker itself is fine, think about it? You can watch countless videos on max volume and everything is fine. I play music on max volume and everything works as it should.