Advertisement
Singapore markets closed
  • Straits Times Index

    3,144.76
    -38.85 (-1.22%)
     
  • S&P 500

    5,047.23
    -14.59 (-0.29%)
     
  • Dow

    37,771.94
    +36.83 (+0.10%)
     
  • Nasdaq

    15,855.92
    -29.10 (-0.18%)
     
  • Bitcoin USD

    62,426.74
    -2,048.46 (-3.18%)
     
  • CMC Crypto 200

    885.54
    0.00 (0.00%)
     
  • FTSE 100

    7,810.64
    -154.89 (-1.94%)
     
  • Gold

    2,387.50
    +4.50 (+0.19%)
     
  • Crude Oil

    85.34
    -0.07 (-0.08%)
     
  • 10-Yr Bond

    4.6740
    +0.0460 (+0.99%)
     
  • Nikkei

    38,471.20
    -761.60 (-1.94%)
     
  • Hang Seng

    16,248.97
    -351.49 (-2.12%)
     
  • FTSE Bursa Malaysia

    1,535.00
    -7.53 (-0.49%)
     
  • Jakarta Composite Index

    7,164.81
    -122.07 (-1.68%)
     
  • PSE Index

    6,404.97
    -157.46 (-2.40%)
     
Engadget
Why you can trust us

Engadget has been testing and reviewing consumer tech since 2004. Our stories may include affiliate links; if you buy something through a link, we may earn a commission. Read more about how we evaluate products.

Some Pixel 2 phones are making strange noises

Google is testing its buyers' patience.

The Pixel 2 and Pixel 2 XL are Google's best-rated smartphones yet, but early quality-control and testing problems could ruin the sales party. On top of display color and burn-in issues that have prompted some to advise against buying the device for now, users are also reporting sound problems. According to around 100 buyers on Google's Pixel product forum, the Pixel 2, and to a lesser extent, Pixel 2 XL are emitting clicking and/or high frequency sounds from the call speaker.

Users describe the ticking problem as like the second-hand on a bad watch that runs continuously when the phone is unlocked. The high-pitched noise, on the other hand, happens only during calls. Turning off NFC often stops the clicking problem, and while that's obviously no fix, it points to where the issue may lie. The whining, on the other hand, seems to be unrelated. It's mostly Pixel 2 buyers reporting the issues, but several XL buyers also complained.

On the forums, Google told users that "if you are experiencing the issue, you should contact [tech] support to discuss RMA options." One user reported that Google agreed to send a replacement unit and test it ahead of time to confirm it doesn't have the same issue.

Minor QC issues on a new phone are to be expected, but multiple issues (on an otherwise excellent phone) isn't a good sign. As Samsung learned, Google would be best off to quickly fix the problems, tell buyers honestly what happened and apologize. Engadget has reached out to Google on the sound issue, but for now, all it's saying is that "Google has been made aware of the issue and is looking into it. We will keep you updated on this."