Slashdot Mirror
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.
Anyone who is willing to slash out a premium for a smartphone is getting an iPhone, or possibly a Samsung. I have a hard time believing Google is selling > 100k of these to actual customers who are not Google employees.
I don't know how similar the oleds are between the $10 hobby i2c modules ('maker stuff') and the oled big color screens; but I've built quite a few of the 1.13" i2c oled display projects and one of them has been a gps clock that has been on for at least 2 years now. its display cycles between calendar and some other modes but the display is always on. and its already showing 'lines' of fade, based on which pixels were lit the most.
on my diy projects, I put the oleds in sockets so they can be replaced later. of course, phones are so ANTI FIX-ME (hardware) that they'd never think of letting users replaced worn out screens. sigh...
--
"It is now safe to switch off your computer."
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.
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.