Don’t Buy The Pixel 2 XL Until Google Sorts Out Its Display Problems

Don’t Buy The Pixel 2 XL Until Google Sorts Out Its Display Problems


If you’re mulling the Pixel 2 XL for your next smartphone upgrade, you may want to think twice, or at least put your decision on hold for a few days.

Early versions of the device could have a hardware flaw that causes permanent damage to the screen. Multiple people have reported cases of “burn-in”, meaningthe display may be permanently damaged in areas where a recurring image (such as the Android navigation buttons) discolours the screen.

Yesterday, Google confirmed that it's looking into issues surrounding the Pixel 2 XL display in a statement to The Verge:

The Pixel 2 XL screen has been designed with an advanced POLED technology, including QHD+ resolution, wide colour gamut, and high contrast ratio for natural and beautiful colours and renderings. We put all of our products through extensive quality testing before launch and in the manufacturing of every unit. We are actively investigating this report.

What You Need to Know About Burn-In On the Pixel 2 XL Display

Burn-in isn't that uncommon of an issue on modern displays, but it typically takes months or even years for even the faintest discoloration to show up. So the fact that people are already seeing it happen on the Pixel 2 XL definitely isn't a good sign.

Here's what burn-in looks like on the Pixel 2 XL, courtesy of Android Central executive editor Alex Dobie. (Look for the faint navigation icons at the bottom of what should be a plain grey screen.)

It's possible the issue could actually be image retention, which would be an easier fix, but if burn-in is the culprit Google may need to replace a ton of devices or even recall the Pixel 2 XL entirely.

For now, you should probably wait to see what the company uncovers, or just opt for the smaller Pixel 2 (which doesn't seem to have any major issues) instead.


  • Shame, I’m really looking forward to swapping my Google Pixel XL for the Pixel 2. They’re great simple phones. It’s awesome being with Google since we get all the updates first xP

  • I mean, Samsung and Apple people like to take the piss out of each other… but *that* is
    whole other level of disgusting. There’s no way that wasn’t picked up during quality testing?

    • Maybe it’s just a bad batch or something? If it’s showing up so soon you’d think it’s something that would have come up in testing if it was an inherent fault in all units.

      Oh well, at least it isn’t catching fire or exploding etc 😛

      • Forgot about the explosions! lol.

        But yeah undoubtedly it’s a bad batch, but that’s still down to faulty/bad hardware that should’ve been picked up. Sounds like shoddy workmanship. No doubt it’s an issue that can be rectified quicksmart.

Show more comments

Log in to comment on this story!