From the Google Forums:
> Since launch, we’ve also received reports of suspected issues related to the Pixel 2 XL display. We take these reports very seriously and wanted to provide an update. First, there’s been some feedback about the Pixel 2 XL displays not appearing as vibrant as other phones, and in the past few days, there have been a small number of reports of differential aging (also referred to as “burn-in”) on the Pixel 2 XL’s pOLED screen.
And:
> Regarding differential aging, we put all of our products through extensive quality assurance before launch and in the manufacturing of every unit. Thorough testing of the Pixel 2 XL display shows that its decay characteristics are similar to OLED panels used in comparable products. Our current investigation of burn-in, which started as soon as we received the first user report on October 22, confirms that the differential aging is in line with that of other premium smartphones and should not affect the normal, day-to-day user experience of the Pixel 2 XL. Regardless, we use software to safeguard the user experience and maximize the life of the OLED display, and we’ll make ongoing software updates to optimize further.
And:
> We’re very confident that the Pixel 2 delivers an exceptional smartphone experience, and to give users peace of mind, every Pixel 2 and Pixel 2 XL will now come with a 2-year warranty worldwide.
Hard to know how to react to this. The way I read it, the burn-in is being sold as normal, nothing to see here, move along. If this is the case, there should be reports of burn-in on all OLED displays, no?
As to the Pixel 2 color issues, there’s a detailed explanation in this Google Forums post. It focuses on the Pixel 2 XL using wide Display P3 color gamut, white point temperature settings, and old school sRGB being translated into that space.
Lots to process, props to Google for doubling the warranty.
The complaints I’ve seen about the XL display have nothing to do with color space issues (iPhones and iPads are P3. sRGB content looks fine as long at it’s properly tagged as sRGB, this ain’t new stuff). The XL display is unable to do things as simple as display the plain black and white logo of the NY Times as black. I mean, this is an OLED display. The one thing they do better than ANY OTHER display is black.
The standard Pixel 2 is great from what I’ve gathered, it’s only the XL that has the issues. Too many people who are very familiar with display technology, color gamut, and color spaces are reporting very real issues with the XL. I don’t think Google is going to get a pass with a “nothing to see here” press release.
The 2 year warranty is only worthwhile if Google admits the displays have real issues and replaces them. What the hell good is it if they maintain it’s operating as intended?
Luckily this doesn’t affect me since I will never buy Google products. Never did, and never will. 🙂
“It’s not a flaw, it’s a feature.”
How does converting an image using sRGB make it have a blue bias, if the viewer is seeing the screen at a tiny, little itty bitty angle off of perpendicular? That’s not how color space works.
So their answer must be, “You’re holding it wrong!”
Doubling the warranty because the displays have issues, while claiming the issues are normal is nothing but PR. That can of tuna making you sick? We’ll give you another can for free.
Yeah, it’s stupid. Yes, sRGB content that is not tagged as sRGB will display poorly in P3. Same holds true for any other color space that’s not properly tagged (Rec, Adobe, etc.). That’s why it’s drilled in our heads from our first days of creating media to tag our images.
That’s not the problem here. Almost everything on the web is properly tagged sRGB. If it were, the same content would look just as bad on iPhones, iPads, and the latest MacBook Pro computers as they too are also P3.
Also, isn’t the standard Pixel 2 also P3? It doesn’t have this issue either.