Google Addresses Pixel 2 XL Display Issues, Pixel 2 Clicking Sounds With Software Updates (phonedog.com)
An anonymous reader quotes a report from PhoneDog: Google explains that it's been investigating reports about the Pixel 2 XL's display and that this has given it "confidence that [its] displays are as great as [it] hoped they would be". Still, Google will be taking steps to respond to consumer complaints about the screen. Google plans to issue a software update that'll add a "saturated" color mode that will make the colors more saturated and vibrant, but less accurate. This way, consumers that feel the Pixel 2 XL's screen is too muted can punch up the color saturation themselves.
When it comes to burn-in, Google says that its investigations of the Pixel 2 XL's display found that its "decay characteristics are comparable to OLED panels used in other premium smartphones." Google does plan to take further steps to fight burn-in, though, and it's testing an update that'll add a new fade-out of the navigation bar buttons after a short period of inactivity. Google is also working with more apps to use a light navigation bar to match the app's color scheme. Additionally, the update will reduce the maximum brightness of the Pixel 2 XL's screen by 50 nits, which Google says will be "virtually imperceptible". This will reduce load on the display with very little change on its observed brightness. This update will roll out to the Pixel 2 XL "in the next few weeks." Google also touched on the reports that some Pixel 2 phones are emitting some clicking sounds. The company plans to release an update in the coming weeks to address the issue, but until then, it says that Pixel 2 owners can turn off NFC by going into Settings > Connected Devices > NFC.
When it comes to burn-in, Google says that its investigations of the Pixel 2 XL's display found that its "decay characteristics are comparable to OLED panels used in other premium smartphones." Google does plan to take further steps to fight burn-in, though, and it's testing an update that'll add a new fade-out of the navigation bar buttons after a short period of inactivity. Google is also working with more apps to use a light navigation bar to match the app's color scheme. Additionally, the update will reduce the maximum brightness of the Pixel 2 XL's screen by 50 nits, which Google says will be "virtually imperceptible". This will reduce load on the display with very little change on its observed brightness. This update will roll out to the Pixel 2 XL "in the next few weeks." Google also touched on the reports that some Pixel 2 phones are emitting some clicking sounds. The company plans to release an update in the coming weeks to address the issue, but until then, it says that Pixel 2 owners can turn off NFC by going into Settings > Connected Devices > NFC.
The original Pixel sold very well and was deemed the best premium smartphone of 2016 by many.
It would seem that the newer OLED panels suffer more from burn-in than LED. I'm glad this was brought up. I'll be refraining from upgrading to OLED until this sort of thing is made better or a newer technology supersedes it. More details here for those who are interested. The burn-in is not permanent but can occur when a static image is present in as little as 45 minutes. The ghosting is not permanent like older CRT and Plasma screens but it's annoying to have to run through steps to clear it up periodically.
We'll make great pets
Near field communication is what it is; and wikipedia knows more about it than I do: https://en.wikipedia.org/wiki/...
If you don't want to read that: It's a wireless communication protocol that requires very close proximity, used for mobile payment, and sometimes to transfer settings to new phones.
Why is that related to the clicking noise? Well my first guess of interference is thrown out by the fact that they can fix it in software; maybe someone can shed light on this?
The clicking noises are probably noise leaking into the audio amplifier from the modulation of the NFC radio. The frequency of the radio is out of hearing range but the modulation is not, and intermodulation can appear as low frequency noise. My iPhone lte radio has done the same thing to land lines on several occasions.
Apparently Google judged the burn-in on their displays in line with the industry despite problems being reported in the first few weeks where as industry standard is for the situation to be unnoticeable for several years.
Apparently the screen is fine but we'll make software changes to make the totally not problematic screen less likely to cause a problem which totally doesn't exist in the first place.
Apparently Google's answer to problems with display colours changing with viewing angles are a software update to make them more saturated?
Like what the heck? Why not just give customers the middle finger? At least there would be less reading involved.
Oh, i dunno: https://arstechnica.com/gadget...
WTF?
After another power cycle failed to clear it, I called Google, who immediately arranged for a replacement to be shipped (Thanks Google!). I really expected to hear something about some process I should go through to 'fix it' in some way. After another day of use, the problem HAS been reduced. In fact, if it were no worse that this in the first place I would likely not have called at all. Meanwhile, I'm charging it with power off to be safe.
Bottom line, I still like this phone very much. It's wonderfully fast, and easier on the hand than my Nexus 6 was. The prompt replacement just reinforces my already long and happy relationship with Google hardware.