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.
But itâ(TM)s more prettier
How do you turn off tracking and disable the government backdoor?
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.
This sounds more like something that was tested as a "feature", not chosen as #1 by the consumer group that tested it, and now played back to the people as though this were a fix.
--
"It's a sign" - E. Corp
Will promise you the perfect device then make it worst with update (like otherOS per example).
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
What is NFC, and why is that related to clicking noises?
Enough with the TLAs, ok?
There seems to be a discrepancy between the title of the story, and the summary... The title says Google addressed, and the summary says Google plans to release. To me it sounds like they haven't addressed anything yet. Shouldn't we wait to see if their software "fix" fixes anything before claiming they've addressed the issue...
And the missing MicroSD slot? And the lack of a close app feature on apps? And the "we have shut two apps to save power" for apps I wanted to close days ago when I finished with them, but couldn't because you won't let users close apps? And the lack of features compared to the OEM phones? And the missing audio jack? And the annoying way it closes apps in the background I want to keep running?
These masturbation phones from Google do not sell in large quantities and until they decide to make phones to suite customers, rather than Google own agendas they really won't sell.
Look at the lack of excitement over the Chromebook Pixel coming out.... you Google lot merged Chrome OS and Android, Android users want a big Android tablet suitable for touch, not a WIMP interface. ChromeOS users wanted a locked down OS that grandma wouldn't break. You merged them because they're both Google projects, and Pinchai was ChromeOS lead. Not because customers were crying out for a merge. So Android was crippled in the tablet market to make way for FrankenOS. Instead of addressing Android's shortcomings on large tablets, you made a system more suited to a mouse, with a 90's style trackpad to boot than fix the actual problems users and reviewers report with these large tablets.
Shark+jump+Google.
Only a fucking moron would buy anything but an iPhone 8 or X at this point. The Pixel/2 is a P.O.S. that Google will only use to invade your privacy and hand over all your personal details to the fucking retard democrat party.
There seems to be a discrepancy between the title of the story, and the summary... The title says Google addressed, and the summary says Google plans to release. To me it sounds like they haven't addressed anything yet. Shouldn't we wait to see if their software "fix" fixes anything before claiming they've addressed the issue...
"Addressed" means "spoke about". As opposed to, "released fix for", which is what you seem to be looking for.
Apparently, the new Pixel 2 XL screens made by LG have a blue tint. No comments from Google about that problem.
In a time of universal deceit, telling the truth is a revolutionary act. George Orwell
The stark white background. Try a pale shade of blue,or gray. Not rocket science;using an extension to do this, however gives the browser unnecessary excess baggage and too many options or settings that remind one of KDE. I'm not saying this fixes the problem; but it does buy Google engineers some time to craft a hardware solution; the bean counters will cream their knickers at the phrase authorized repair; legal will carefully word an announcement that avoids use of the word recall.
TSA will add another item to their list of banned items, Google Pixel appearing right above Laptops and Lithium Ion batteries and canned hairspray
Their hardware is clearly faulty, and they pretend to resolve it through software. You can't solve burn in and messed up inverters with software, and considering the selling point for these devices is supposed to be the "high quality" of the very same hardware, they aren't going to get away with this because they don't posses a reality distortion field of cult glitz with the associated audience like Apple.
When the iPhone X launched and they showed how you swipe up from the bottom of the screen to get back to home, I thought it was a bit odd, but their decision to avoid onscreen buttons does look smart now they've switched to OLED. Will Android follow suit now that phones are converging on an all-screen front with no hardware buttons?
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.
Ooh! I really really want to implement TCP/IP Over Bongo Drums, but I don't think that's supported on Red Hat. If I install Ubuntu, are there third party bongo providers?
You take a time machine to the 1800s and bask in the knowledge that your phone can't be tapped because phones have not been invented yet...
I guess we are just looking at it wrong?
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.
Giving a workaround for the clicking, they could simply said that it's a nonexisting problem but instead they accepted it and gave us a very easy fix by turning of a feature that nearly anyone uses anyway.