Pixel 2 News: Some Users Report Hearing 'Clicking' Noises on New Google Handset
Some users of the newly-launched Google Pixel 2 smartphone recently reported experiencing a persistent clicking noise created by their mobile devices.
An owner of the Pixel 2 recently started a thread on the Pixel User Community page to share that he was having noise issues with the new smartphone. According to his report, the device was making a "high pitch frequency sound" as well as clicking noises whenever the screen was active or unlocked.
According to the same user, he still experienced the clicking noise issues despite rebooting the device or even after putting the smartphone on safe or airplane modes. Not even a factory reset fixed the problem, the Pixel 2 user added.
Get Our Latest News for FREE
About a week from when the thread was started, hundreds of other Pixel 2 users commented on the report and confirmed that they were experiencing the same issues. Added to that, reports from other websites shared hearing the same clicking noise on the Pixel 2.
Meanwhile, a community manager from Google named Orrin responded on the thread and said the company was already investigating the issues on Pixel 2.
"We are investigating a faint, low-frequency 'clicking' or 'ticking' noise that a small number of Pixel 2 users have reported. This clicking noise does not affect the performance of your device beyond the audible noise," the Google staff member explained.
While a permanent fix seems unavailable at the moment, Orrin suggested that Pixel 2 users experiencing the noise issues can temporarily disable the Near-Field Communication feature which is commonly used for apps like Android Pay.
The same Google employee promised to provide a more definitive explanation on the matter soon.
Also, very recently, some users complained about experiencing screen burn-in issues on the Pixel 2 XL
As explained by Android Central, the burn-in issue was quite a tendency for OLED panels. This problem was more likely to happen if images for on-screen buttons were projected too long, which then left shadows on the display even when the user had already switched to a new window.
