Slashdot Mirror


Google Confirms Small Number of Pixel Phones Have Broken Microphones (theverge.com)

An anonymous reader shares a report on The Verge: Google says that a small number of Pixel phones have broken microphones that need to be sent back for replacement. The issue is seemingly not that widespread. Google claims the issue is present on less than 1 percent of devices -- the company also announced that it would replace defective phones last month, and it went largely unnoticed until now. Google says the primary cause for Pixels having microphone issues is a "hairline crack in the solder connection on the audio codec," which causes all three of the device's mics to go out at once. The issue has apparently been known about for several months now. Google says it's been "taking additional steps to reinforce the connection" since January and that phones built or refurbished since then should be fine.

68 comments

  1. Uh oh by Motherfucking+Shit · · Score: 5, Funny

    The NSA and CIA are going to want a refund.

    --
    "BSD: Free as in speech. Linux: Free as in beer. Windows 10: Free as in herpes." --Man On Pink Corner in #52607549.
    1. Re:Uh oh by Phusion · · Score: 1

      -sigh- came in here to make this comment. Kudos to you sir.

      --
      640k ought to be enough for anyone.
    2. Re:Uh oh by Anonymous Coward · · Score: 0

      doesn't seem that off-topic

      Why THREE mics? Front, Back, Always on

    3. Re:Uh oh by Anonymous Coward · · Score: 0

      I understand an extra mike for noise cancellation reasons (don't believe it, but I can understand it). 3 can only be for in case the main mikes fail, the third can still eavesdrop on you via backdoors. Battery can't be removed, therefore it can always be turned on remotely. The world we live in has changed immensely in the last 20 years, not for the good.

  2. News? by Thelasko · · Score: 2

    Why is this news. Manufacturers have defects all of the time. It's a small number of phones. Who cares!

    It's not like they randomly bust into flames or anything.

    --
    One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
    1. Re:News? by Anonymous Coward · · Score: 0

      It's a sign o' the times, human interest piece.

      The story is not the broken microphone itself, but the fact that being on a phone you might think it somewhat important, but *no one noticed* because no one uses their phone for something as pedestrian as making a phone call any more.

    2. Re:News? by geek · · Score: 3, Informative

      Why is this news. Manufacturers have defects all of the time. It's a small number of phones. Who cares!

      It's not like they randomly bust into flames or anything.

      The Pixel phones have been plagued by issue after issue. For a "premium" device the QA has been pretty terrible.

    3. Re:News? by DontBeAMoran · · Score: 1

      For a "premium" device the QA has been pretty terrible.

      Yet another proof that Google are copying Apple.

      --
      #DeleteFacebook
    4. Re:News? by DaHat · · Score: 2

      Yup, the biggest issue being lack of availability.

      Just try getting a XL 128 GB without paying a scalper $1200-$1500 for a device which is supposed to retail for $869... and this 5 months since release.

    5. Re:News? by Anonymous Coward · · Score: 1

      The Pixel isn't just a premium phone, it is THE Android flagship: the one designed by Google that is supposed to showcase what the latest and greatest things about Android.

      Apparently sloppiness is what is "in" for Android right now.

    6. Re:News? by thegarbz · · Score: 1

      Why is this news. Manufacturers have defects all of the time.

      Because a manufacturer came out early and said they will honour replacements before it became an issue. That's about as Newsworthy as it news gets.

    7. Re:News? by Radish03 · · Score: 1

      Indeed. I'll replace my current phone (functional, but very much showing wear and age) with a 128gb Pixel XL the second google lists them for sale again, if I'm not too slow, but unless they've really ramped up manufacturing, I'm not totally sure I'll have that chance before the 2017 model is released. The stock tracker (http://www.nowinstock.net/electronics/mobilephones/unlocked/googlepixel/) says it's been in stock something like 9 days throughout the past two months.

    8. Re:News? by Anonymous Coward · · Score: 0

      The new Moto phone will be released soon with sdcard support, 32gb onboard memory, Nougat, and minimal bloat. $229. What more does anyone 'really' need?

    9. Re: News? by Anonymous Coward · · Score: 0

      Didn't think I needed an amazing camera. Then I got a Pixel.

      Suddenly everyone is asking me for high res copies of my photos for posters.

      It really makes day to day photos look like professional wedding pictures.

      The macro ability is amazing too - I got an amazing shot of the antennae of a wasp when it landed on me. Nobody seems to have reported on that.

    10. Re:News? by Coren22 · · Score: 1

      They could also be copying Samsung...

      I do love my Google phone though.

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
    11. Re:News? by Coren22 · · Score: 1

      Yeah, I can recall the last fault in another manufacturer's phone where they kept denying the problem and deleting forum threads about the issue. Then there was the other time where everyone was told they were holding their phones wrong to cover for a manufacturing defect.

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  3. This is a feature... by Anonymous Coward · · Score: 0

    to prevent wire tapping. Once perfected it will be rolled out to the wider user base.

  4. solder, huh? by Anonymous Coward · · Score: 0

    Must be a super fine pitch device, like .35mm, this means the paste stencil and solder paste and reflow need to be *just so* to work reliably.

    1. Re:solder, huh? by Anonymous Coward · · Score: 0

      You must not know how reflow soldering works. The parts literally align themselves from surface tension.

  5. Weird, a broken mic is why I replaced my Nexus by wiredog · · Score: 2

    With a Pixel. About 2 weeks ago, so hopefully it won't have this defect.

    1. Re:Weird, a broken mic is why I replaced my Nexus by Tx · · Score: 1

      Hmm, my Pixel's mic seems to be a bit crap, but I don't think it's this fault. It seems to sometimes completely ignore "ok Google", but when I manually hit the mic icon, it then responds fine to voice commands, so the mic itself seems to be working ok. Maybe I need to retrain the voice model. I tried to "ok Google" the other day, and the Pixel in my hand wouldn't respond, but the Sony tablet in the next room did!

      --
      Oh no... it's the future.
    2. Re:Weird, a broken mic is why I replaced my Nexus by Coren22 · · Score: 1

      According to The Fine Summary, you are in the clear as the problem was recognized and corrected in January.

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  6. Fail fail fail by JustAnotherOldGuy · · Score: 1

    "hairline crack in the solder connection on the audio codec,"

    A codec is software, who knew software could have a hairline crack in the solder?

    --
    Just cruising through this digital world at 33 1/3 rpm...
    1. Re:Fail fail fail by Stewie241 · · Score: 1

      I noticed that too, but assumed it meant they had a hardware codec chip. Something like: http://www.ebay.com/itm/AKM-AK...

    2. Re:Fail fail fail by scubamage · · Score: 1

      A codec can be hardware or software.

    3. Re: Fail fail fail by Anonymous Coward · · Score: 0

      Can somebody please mod down the parent comment? He clearly has no idea what he's talking about.

      "Codec" is a portmanteau of "coder-decoder". A codec can be implemented in hardware or in software, and sometimes using both approaches.

      The codecs in phones are often implemented in hardware due to tight latency tolerances, and to reduce power consumption.

      I know the quality of the comments here has really dropped off, but the parent comment is particularly ignorant and idiotic.

    4. Re:Fail fail fail by freeze128 · · Score: 1

      Haven't you ever heard of "cracking software"?

    5. Re:Fail fail fail by squiggleslash · · Score: 5, Informative

      A codec is simply something that converts audio/video/whatever from one format to another. It certainly can be hardware.

      I was confused too when I first used it heard to describe on-motherboard audio systems in the 1990s, but that's a legitimate use.

      Ironically, most who don't think it's suitable for hardware also are the people who use it to describe formats like H.264 or AAC. You can use a (hardware or software) codec to convert something into H.264, but H.264 isn't the actual codec, it's the format.

      --
      You are not alone. This is not normal. None of this is normal.
    6. Re:Fail fail fail by JustAnotherOldGuy · · Score: 1

      A codec is simply something that converts audio/video/whatever from one format to another. It certainly can be hardware.

      No. It can be implemented in hardware but it is not hardware. You can buy a codec, but you can't have a hairline crack in a piece of software.

      You may as well say "My mp3 has a hairline crack in it"

      --
      Just cruising through this digital world at 33 1/3 rpm...
    7. Re:Fail fail fail by JustAnotherOldGuy · · Score: 1

      Keyword, "chip".

      A codec can be implemented in hardware but it is not hardware. They may as well have said "My mp3 has a hairline crack in it".

      --
      Just cruising through this digital world at 33 1/3 rpm...
    8. Re:Fail fail fail by Anonymous Coward · · Score: 0

      My MP3 can't have a hairline crack in it, but my MP3 codec chip certainly can.

      And software implemented in hardware, by definition is hardware. If software implemented in hardware wasn't hardware, then there would be no such thing as hardware, since most hardware is synthesized from VHDL or Verilog.

    9. Re:Fail fail fail by spire3661 · · Score: 2

      Code/decoder implementations can be hardware or software.

      codec
      kdek/
      noun
      a device or program that compresses data to enable faster transmission and decompresses received data.

      --
      Good-bye
    10. Re:Fail fail fail by fuzzyfuzzyfungus · · Score: 1

      It may be a sloppy usage, or just unfamiliar to people used to dealing with the delights of 'codec packs' and getting oddball media to play back; but the term 'audio codec' appears to be what they use for the chip that handles talking to one or more mics and audio ins and outs and(possibly in addition to providing hardware accellerated processing of certain features) wraps that all up into a(fairly high speed; but conveniently low pin count and digital, I2S or similar inter-chip audio bus) for connection to the SoC.

      At least in the case of the Pixel XL; the part in question is a Qualcomm WCD9335. The usual joys of actually finding Qualcomm datasheets apply; but it's referred to as a "WCD9335 audio codec" in a variety of places it is mentioned.

      Given contemporary CPU power, I'm not sure if having the coding and decoding offboard is of much interest anymore; but using the offboard codec allows you to get away with supporting a wide variety of different audio capabilities(anywhere from just single mic and speaker to fancy array mics and zillions of audio ins and outs) with the same SoC implementing a relatively simple digital bus(no need to add a whole bunch of ADCs and DACs to every SoC just in case some high-end phone models want to use them); and allowing the designer to choose a codec chip based on how many mics and audio outs they need to support; whether they care about 'audiophile' DACs, etc.

      Somewhat analogous to 'Intel HD Audio' on the PC side: this specifies a fairly cheap and flexible interface with some amount of standardization of how you talk to various features; but doesn't require adding ADCs and DACs to the CPU or chipset; and allows motherboard vendors to use any support chip that speaks HDA depending on their desired budget, number of audio ins and outs, interest in audio quality, etc.

      They aren't the vendor used by the Pixel, to my knowledge; but take a look at Cirrus Logic's "'Codecs' page for a whole bunch of datasheets outlining the purpose and capabilities of chips referred to as 'audio codecs'.

    11. Re:Fail fail fail by 140Mandak262Jamuna · · Score: 2
      codec = compressor/decompressor

      serdes = serializer / deserializer

      modem = modulator / demodulator

      Most of these terms originated in hardward and migrated to software.

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    12. Re:Fail fail fail by Anonymous Coward · · Score: 0

      It's shorthand for: The dedicated integrated circuit that contains a codec state machine.

      The codec often reads the pulse-density modulated output of a MEMS microphone and converts it into pulse-code modulated data.

    13. Re:Fail fail fail by 140Mandak262Jamuna · · Score: 1

      So you are going to call the graphics card rendering OpenGL triangles software?

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    14. Re:Fail fail fail by GuB-42 · · Score: 2

      Hardware audio codecs are integrated ADC/DACs. Their main purpose is act as a bridge between the analog and the digital part of the audio system. Usually they don't know anything about digital audio formats.
      While they have the same name as software codecs, they operate on a different level. Software codecs convert a stream of bits into a different stream of bits, hardware codecs convert an electrical signal into a different electrical signal.
      To make things even more confusing, things like mp3 implemented in hardware can are also called a hardware codec. However, it is generally not people mean when they are talking about audio codecs on a motherboard.

    15. Re:Fail fail fail by thegarbz · · Score: 1

      A codec is software

      No a codec is a description of a process (coding and decoding). The way it is implemented is entirely up to the person creating it.

      Fun fact, codec was was used to describe hardware conversion of audio in both analogue and digital domains long before it was used to describe software compression, conversion, and other processes on your computer.

    16. Re:Fail fail fail by squiggleslash · · Score: 2

      No. It can be implemented in hardware but it is not hardware

      Yes, it can be in hardware. I'm wondering if you're one of the people (I was once too, there's no shame in it) that I'm discussing in the second half of my comment.

      Codecs convert from one format to another. They can be hardware or software. They are not to be confused with the formats themselves.

      --
      You are not alone. This is not normal. None of this is normal.
    17. Re:Fail fail fail by Anonymous Coward · · Score: 0

      Codec for hardware engineers is a combination of an ADC and DAC in a single chip. Most of the time it is 'encoded' as PCM.

      This may sound a bit weird because PCM is hardly encoding. However it is not as easy as you think, most modern ADC converters (and modern DAC as well) are delta-sigma converters with a 1 bit output at a very high sample rate. This 1 bit output is then passed through several digital low-pass filters to convert this to 24 bit PCM.

      In very special cases you can also find ADC/DACs that uses this 1 bit signal, so another chip can process this. Most of the time however the Codec will do this processing for you and you can simply get a nice PCM encoded signal into your processor.

    18. Re:Fail fail fail by JustAnotherOldGuy · · Score: 1

      No a codec is a description of a process (coding and decoding). The way it is implemented is entirely up to the person creating it.

      Fun fact, codec was was used to describe hardware conversion of audio in both analogue and digital domains long before it was used to describe software compression, conversion, and other processes on your computer.

      I reject your reality and substitute my own! ;)

      --
      Just cruising through this digital world at 33 1/3 rpm...
    19. Re:Fail fail fail by JustAnotherOldGuy · · Score: 1

      Despite people far more knowledgeable than I correcting me, I will stick to my outmoded and almost certainly erroneous mode of thinking!

      You'll not sway my thinking with your tricky, underhanded facts! lol

      --
      Just cruising through this digital world at 33 1/3 rpm...
    20. Re:Fail fail fail by JustAnotherOldGuy · · Score: 1

      So you are going to call the graphics card rendering OpenGL triangles software?

      Yes, no matter how wonderfully pointy and triangular they are.

      grumble grumble firmware grumble grumble

      --
      Just cruising through this digital world at 33 1/3 rpm...
    21. Re:Fail fail fail by Anonymous Coward · · Score: 0

      Codecs enCode and Decode. It is inherently a mathmatic function. That function can be implemented in either HW or SW but is not HW itself. Come on man. It's one step up the logical hierarchy. Like a dove is a bird but not all birds are doves. The codec can be implemented in various ways but it is a mathematical definition.

      Reread justanotheroldguy's point because you missed what he is saying. There is the format the codex and the implementation youre conducting the codes with the implementation of the codec and saying that they are interchangeable.

    22. Re:Fail fail fail by JustAnotherOldGuy · · Score: 1

      codec = compressor/decompressor
      serdes = serializer / deserializer
      modem = modulator / demodulator
      Most of these terms originated in hardward and migrated to software.

      And that's when you youngn's went off the track and sullied my ossified view of this here world, dangnabbit! ;)

      --
      Just cruising through this digital world at 33 1/3 rpm...
    23. Re:Fail fail fail by JustAnotherOldGuy · · Score: 1

      Your unassailable logic and first-hand knowledge is no match for my stubborn dismissal of the facts! ;)

      grumble grumble grumble grumble

      --
      Just cruising through this digital world at 33 1/3 rpm...
    24. Re:Fail fail fail by kevmeister · · Score: 1

      First, CODEC is short for coder-decoder. Whether it is done in hardware or software, any tool which performs the function of accepting a digital stream in a specified format and outputting it in a different digital format is a CODEC. H.264 is not quite a codec, but any software or hardware that accepts a data stream in a digital format and outputs it into another is a codec and H.264 is usually called a codec because it describes a a standard for taking a raw video data stream and compressing it into well known encoding. The actual input my be any most anything as long as the decode part of the codec can understand it.

      Actually, CODEC took the old, analog/digital domain term "modem" (modulator/demodulator) and moved it into the all digital domain, keeping the order the same.

      Not too long ago software was too slow to implement a real-time audio codec at a reasonable price, so most people assumed hardware when you talked about a codec. By not long ago, I mean beck in the 1980s. (Yes, I'm old.)

      --
      Kevin Oberman, Network Engineer, Retired
  7. please clarify the term? by Anonymous Coward · · Score: 0

    I was under the impression that the "codec" was software used to control/parse/interpret the data gained from hardware. Something to download like video codecs to play various different video files.

    Does the term Codec now cover the hardware component as well?

    1. Re:please clarify the term? by Stewie241 · · Score: 1

      Codec is short for encode/decode. So a hardware codec would be a chip that performs encoding and decoding of an audio stream. They probably could have used a software codec and ran it on the CPU, but seemingly instead opted to use a hardware codec that would be more optimized for the particular algorithm they were using.

    2. Re:please clarify the term? by TechyImmigrant · · Score: 1

      Codecs can be implemented both in hardware and software.

      Codecs for high quality compressed speech codes can be computationally intensive and so may be better done in hardware.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
    3. Re:please clarify the term? by fuzzyfuzzyfungus · · Score: 1

      It does. The part in the Pixel is(I think) a Qualcomm; but they are annoying as hell to get datasheets for; so these examples are Realtek:

      Here are their I2S codecs(what you'd likely find in a cellphone or similar device); and here are the Intel HDA ones; as you'd see in a PC. Unless you are doing something particularly fancy(in which case the an offboard DSP might actually be worth the trouble); the main purpose appears to be allowing you to decouple the ADCs and DACs(which aren't necessarily well suited to being fabbed on the process that makes the most sense for a SoC or PC chipset; and which can vary widely in number and quality depending on the desired features of the product, which would lead to nasty SKU proliferation) from the SoC or chipset; with just a simple, versatile, digital data link between the two chips, allowing the SoC or chipset to support a wide variety of audio configurations with just one design; and allowing the device vendor to get their choice of features and performance(anywhere from a single mic, single audio out, lousy ADC and DAC quality; up to zillions-of-peripherals-and-golden-eared-audiophile-DACs) just by attaching a different codec chip.

      The most spartan designs might not need a 'codec' at all(you can get MEMs mics that speak I2S directly, with the analog support circutry integrated into the package; and you can also get audio amps/speaker/headphone drivers that speak I2S directly and have a DAC onboard, rather than accepting a low voltage analog audio input); but if you've got a mic array, a speaker, headphone/mic jack, line out, etc. a codec can bundle up all the support for the various analog interfaces and allow you to attach them all to the SoC/chipset with a single digital bus.

      In this case, the fact that it's a codec soldering issue is presumably why all three mics die at once. That would be seriously unlikely if the mics themselves failed; but the codec handles all the mics, so a failure there knocks out the mics in roughly the same way that just yanking out a soundcard would.

    4. Re:please clarify the term? by tlhIngan · · Score: 1

      The most spartan designs might not need a 'codec' at all(you can get MEMs mics that speak I2S directly, with the analog support circutry integrated into the package; and you can also get audio amps/speaker/headphone drivers that speak I2S directly and have a DAC onboard, rather than accepting a low voltage analog audio input); but if you've got a mic array, a speaker, headphone/mic jack, line out, etc. a codec can bundle up all the support for the various analog interfaces and allow you to attach them all to the SoC/chipset with a single digital bus.

      In this case, the fact that it's a codec soldering issue is presumably why all three mics die at once. That would be seriously unlikely if the mics themselves failed; but the codec handles all the mics, so a failure there knocks out the mics in roughly the same way that just yanking out a soundcard would.

      Actually, for microphones, you don't usually use analog ones hooked to a codec providing the data via I2S in modern phones.

      You use "digital microphones" that output PDM coded audio directly (PDM = pulse density modulation - the higher the signal value, the closer the pulses are together). PDM has a trade name of DSD (Direct Stream Digital) as it's the format used by Soper Audio CD and "1-bit DACs". (They only output 1s and 0s, the density of 1s describes the signal level).

      This lets you connect up an array of microphones (usually at least 3 on modern phones) using minimal pins and support electronics - a PDM microphone takes just 2 wires - clock (in) and data (out), and if you have an array, they can share a clock line so your 3 microphones use just 4 lines.

      A crack on the clock line would easily disable all the microphones.

  8. You'd care if it were your phone. by Anonymous Coward · · Score: 0

    It's a small number of phones. Who cares!

    You'd probably care a lot if it were your phone that suddenly stopped working because of a busted microphone, especially if it happened when you needed to make a critical call (like to the police, firefighters or paramedics).

    When somebody is paying $600 or more for a phone, it's perfectly reasonable for them to expect that something as essential as the microphone works reliably and does not break unexpectedly.

    Given that phones are commonly used to make emergency calls, people with these devices should be made aware of this flaw as quickly as possible so that they can protect themselves from unexpected failures.

    Downplaying this serious problem is a dumb thing to do when we consider how critical phones can be.

    1. Re:You'd care if it were your phone. by CannonballHead · · Score: 1

      when you needed to make a critical call

      Wait, what? You use your phone to do what? What's a "call?" Is it free in the app store?

  9. RoHS FTW! by TechyImmigrant · · Score: 1, Insightful

    "hairline crack in the solder connection on the audio codec"

    This is what happens when you ban lead in solder.
    A slight miscalibration or unaccounted for solder shadowing and the joint will form brittle then pull itself apart.

    --
    I should use this sig to advertise my book ISBN-13 : 978-1501515132.
  10. are you saying... by ooloorie · · Score: 1

    You can make phone calls on the Pixel Phones as well?

    1. Re:are you saying... by Anonymous Coward · · Score: 0

      You can make phone calls on the Pixel Phones as well?

      Apparently with this flaw, not successfully.

  11. And Apple is confirming by Anonymous Coward · · Score: 0

    a large number of iPhones lack a headphone jack,

  12. Can you hear me now? by Anonymous Coward · · Score: 0

    .....

  13. They have been called Audio Codec Chips since... by Anonymous Coward · · Score: 0

    AC97. 'nuff said.

  14. Simple math. by ckatko · · Score: 1

    1% of 3,000,000 = 30,000 really pissed off customers.

    If it was far less than 1%, they would have told us it was "less than .01%" or something like that.

    Source for sold numbers:

    http://www.pcworld.com/article...

    1. Re:Simple math. by TechyImmigrant · · Score: 1

      1% is a pretty serious flaw. If it was my product I would be concerned as to whether or not it was a progressive failure and they're all going to fail in the end.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
  15. Secure Mode by Anonymous Coward · · Score: 0

    This would actually make a great feature, wherein there was no microphone at all and only a headset, easily disconnected when not actually in use.

  16. Google confirms 60++% adview decrease by Anonymous Coward · · Score: 0

    I help it happen via APK Hosts File Engine 9.0++ SR-7 32/64-bit https://www.google.com/search?hl=en&source=hp&biw=&bih=&q=%22APK+Hosts+File+Engine%22+and+%22start64%22&btnG=Google+Search&gbv=1/

    Ads & malware rob speed/security/privacy

    Hosts add speed (via hardcodes/adblocks), security (vs. bad sites/malware/poisoned dns), reliability (vs. dns down), & anonymity (vs. dns requestlogs/trackers).

    Less power/cpu/ram + IO use vs. DNS/routers/addons/antivirus + less security bugs/complexity & faster vs. addons/routers/remote dns!

    Avoids DNSChangers in routers/IP settings & dns redirects (99.999% of ISP DNS != patched vs. it) + lightens DNS load & resolves faster from local system RAM!

    * Via what u NATIVELY have built into the IP stack in FASTER kernelmode!

    APK

    P.S. - Safe https://www.virustotal.com/en/file/e01211ca36aa02e923f20adee0a3c4f5d5187dc65bdf1c997b3da3c2b0745425/analysis/1433430542/

  17. A "small" number... by Anonymous Coward · · Score: 0

    Maybe it's just stuck at 301 while it waits for validation.