Display Measurement

The Pixel 3’s screen is an extremely important aspect of the phone, not just because it’s the centre-piece of a device, but also because Google’s choice of panel manufacturer. Last year’s Pixel 2 XL suffered from a compromising display made by LG, which in particular had very large issues regarding gamma as well as black clipping at low brightness levels.

This year, Google opted to swap display suppliers around, with the small Pixel 3 now featuring an LG panel while the bigger Pixel 3 XL uses a Samsung unit. Again unfortunately we don’t have the 3 XL at hand, but we can investigate the Pixel 3’s LG panel and make comparisons on the issue points that plagued last year’s 2 XL.

One thing of note that is a first for Google is the introduction of different display colour modes. This was introduced in Android P / 9 and was backported to last year’s Pixel 2. Google now offers a “Natural” mode which represents accurate sRGB and Display P3 D65 targets, a “Boosted” mode which increases the colour saturations, as well as an “Adaptive” mode which is a bit of a mess but shouldn’t be of any concern to people who don’t care too much about colour accuracy.

As always, we thank X-Rite and SpecraCal, as measurements are performed with an X-Rite i1Pro 2 spectrophotometer, with the exception of black levels which are measured with an i1Display Pro colorimeter. Data is collected and examined using SpectraCal's CalMAN software.

SpectraCal CalMAN

SpectraCal CalMAN

Starting off with the greyscale measurements, I decided to switch over to full scale 256 level measurements to better showcase some of the characteristics of the panels, we’ll get back to this at the end of this page.

In “Natural mode”, the Pixel 3 is very accurate and manages to showcase a DeltaE2000 of 1.36, along with an average colour temperature of 6576K, which is very near the target D65 illuminant.

The phone has a maximum brightness of 407 nits – which is average of an OLED, as recent generation Apple and Samsung devices reach levels above 600nits. Google isn’t employing any auto-brightness boost mode, so sunlight legibility might be less than that of other devices, however I wasn’t able to test this directly in the cloudy weather.

Gamma came in at 2.18 – however looking at the curve it’s notable that for most levels it’s at around 2.3, and the average is brought down by being too bright in the last 5% of levels.

  SpectraCal CalMAN
sRGB in "Natural" and in "Boosted" (Against Display P3 Gamut)

When in “Natural” mode, all non-colour managed content targets the sRGB colour-space. Here the Pixel 3’s screen is very accurate with a dE2000 of 1.1, among the best in terms of colour accuracy.

Selecting the “Boosted” mode linearly increases the saturations within the sRGB space – the resulting gamut doesn’t adhere to any standard. The adaptive mode is a complete mess in terms of colour gamut as well as targeting a high gamma of 2.5 – we’ll get back to that into a bit.

Google introduced OS level colour management support in Android 8, however the implementation on the Pixel 2 wasn’t finalised and there wasn’t any application support as of last year. With the Pixel 3 I had hoped that Google would progress on this, however to my great disappointment I didn’t find a single out-of-the box application which would support wide-gamut content.

To demonstrate the issue, you see the Pixel 2, Pixel 3 and an iPhone XS showcasing sRGB and Display P3 images alongside each other in the above photo. By default on Chrome, both sRGB and P3 images are equal, while the XS correctly showcases the higher saturation of the full-level red of the P3 image.

There is one way to bypass this issue, and that is to explicitly tell Chrome to override the default provided system colour profile and just tell it the display is Display P3. This enables colour management in the app, and short of writing a custom application, is the only way to get wide colour gamut content to work on the Pixel 3.

  SpectraCal CalMAN
Display P3 in "Natural" and in "Boosted"

Now one of the big questions I’ve had this year is how the CMS would interact with the actual display colour profiles in the settings. Fortunately, it’s pretty straightforward: The “Natural” mode isn’t per se a colour gamut selection, is just an actual category which has both accurate sRGB and P3 display modes via the CMS.

Testing out the Display P3 targets, the Pixel 3 showcases a good dE2000 result of 1.6. The display didn’t score better because seemingly the blue spectrum isn’t fully hitting the target saturations, something that also happened in the sRGB targets. Testing the P3 targets in the “Boosted” mode, we see again what is happening is that this mode just linearly increases the saturations. The blues are nearer to the P3 targets but all other colours overshoot the P3 target now.

  SpectraCal CalMAN
sRGB and Display P3 Targets in "Adaptive"

Now the fun thing is testing what happens with the sRGB and Display P3 images when you’re in “Adaptive” mode. sRGB obviously is quite a disaster – I didn’t manage to match this resulting gamut to any existing standard so there’s no real point in measuring an error rate. Now what is really interesting is to see the CMS expand the resulting visible gamut with the P3 images – here we’re seeing something that is far wider than Display P3, especially in the blues. Again this doesn’t really match any standard gamut, so there’s no point in making direct comparisons.


SpectraCal CalMAN
GretagMacBeth in "Natural"

SpectraCal CalMAN

The GretagMacBeth colour test in natural mode results in accurate colours with a dE2000 of 1.28.

Gamma curves under magnifying glass

One of the reasons I want to switch to full 256 level greyscale testing is to better show case the luminance behaviour, specifically highlighting the issue of “black clipping”.

The Pixel 2 XL, along with the LG V30, suffered very badly from black clipping at low brightness levels. I generally attribute this to the fact that those generation panels just used the DDIC’s ADC bit-depth for both colour representation as well as brightness control. Samsung OLEDs use PWM on top to control brightness by just adjusting the duty level – with voltage of the pixels determining the colour intensity. The Pixel 2 XL and V30 seemed to lack sufficient range to cover the level-spectrum at the low-end, and this resulted in notorious black clipping.


SpectraCal CalMAN
Pixel 2 XL
SpectraCal CalMAN
Pixel 3

At minimum brightness, the Pixel 3 improves over the Pixel 2 XL in this regard, but it’s still pretty terrible as it’s clipping 15% of levels to black, as opposed to 25% of the Pixel 2 XL.

The higher the brightness, the less pronounced the issue is. At 200 nits compared across the Pixel 3, Pixel 2 XL, S9+ and an iPhone XS, we see that all of the Android phones are clipping the first few greyscale levels to black, with Apple being the only manufacturer able to perform excellently in this regard.

SpectraCal CalMAN

Also one thing that becomes evident when doing full-scale 256 level measurements is the fact that the Pixel 3 colour balance across levels is very haphazard, and we see quite a zig-zagging behaviour between the intensities at different levels, also represented by the dE2000 results. In absolute terms, this shouldn’t be an issue as overall the error rate is acceptable, however it’s a stark behavioural contrast to any other phone I’ve measured before.

Overall, the Pixel 3’s screen is an improvement over the Pixel 2 XL, however it doesn’t fully solve the low-brightness issues that are plaguing LG’s OLED panels, and Samsung panels such as on the Pixel 2 are still better this this regard.

In terms of colour accuracy, the Pixel 3 performs well. Here I would have hoped that Google would have gotten wide colour gamut support fully working within its applications – currently the only way to get this to work is to change a Chrome settings flag, and this only solves the problem for Chrome, and no other app.

Lastly, the display brightness is good, however again it’s just adequate at up to 400 nits, and fails to compete with super bright displays from competing flagships.

GPU Performance Battery Life
Comments Locked

135 Comments

View All Comments

  • Rmrx8 - Saturday, November 3, 2018 - link

    I actually like the ear buds. I bought them for my pixel 2 and I enjoy them just as much as Apple EarPods. Too bad more time wasn't spent on this on the review. Reviews of these have been mixed with people either loving them or hating them. I do lots of recording and the cut in on the mic is much less aggressive than the apple buds, which is a good thing for me. The higher frequencies on googles buds are attenuated a bit. But otherwise I like them and they don't fall out. Also age matters. I'm 51. Undoubtedly a younger person will have better hearing and maybe find more problems, as you age the differences start to disappear.
  • TidalWaveOne - Friday, November 2, 2018 - link

    My Pixel 2 will do just fine... hopefully the Pixel 4 will be good enough to justify an upgrade.
  • Genspirit - Friday, November 2, 2018 - link

    Also did i just miss it or was there no mention of the selfie camera or numerous camera features like top shot? Or live google lens integration. I love the in-depth testing on performance and the camera but I do feel like a lot of what makes the pixel a pixel was left out.
  • BNSFguy - Friday, November 2, 2018 - link

    " I would easily choose USB-C earbuds from any other primary smartphone vendor."

    That's pretty comical statement seeing that there are very, very, few choices for "USB - C" headphones, and most, if not all, are significantly more expensive than the $30.00 Google USB-C Headphones included for FREE with the phone. I mean, just go shopping for a pair of USB-C headphones. You won't find a single pair at any retail store such as Best Buy, and very few online anywhere.
  • imaheadcase - Saturday, November 3, 2018 - link

    THat is why most people use bluetooth
  • papoose34328 - Friday, November 2, 2018 - link

    Hi Andrei,

    Thank you for your very thorough review! Very informative
  • cfenton - Friday, November 2, 2018 - link

    My take away from this review is that it's probably better to try to get a cheap used Pixel 2. Google have lost their edge in daylight photo quality, and the Pixel 2 looks almost as good using Night Shift.

    Also, since Night Shift seems to be mostly a software feature, is there any reason it couldn't be ported to other Android phones? Obviously Google won't do it, but is there any hope that some clever XDA person will. I remember the Pixel camera was ported to other S820 devices, with varying degrees of success.
  • arayoflight - Friday, November 2, 2018 - link

    It's already been ported to many Nokia and Xiaomi devices, and active work is being done to make it work on OnePlus devices as well.
  • bull2760 - Friday, November 2, 2018 - link

    I made the switch to the PIXEL 3 from Apple iPhones. It's very interesting to see that a hardware testing site has not mentioned any of the cellular signal issues that are plaguing iPhone XS and XS Max users. I had the iPhone 10SX Max for 4 days and returned it due to extremely poor cellular service I was getting. From my research it is due to the 4x4 antennas that are being used. FCC testing shows that the new iPhones have signal issues when not in a strong signal area. I experienced this with the short time I had the phone. 4 dropped calls/call failed within minutes of each other. I'd be sitting next to my wife her on her iPhone 7 me on my MAX and my phone would have no service. I looked at her phone and she is pulling almost 3/4 antenna signal. Why is Tom's not diving into this? Anyway I got tired of Apple's crap and decided it was time to try my first Android phone. I looked at the Galaxy Note, and while I like the phone I'm not a fan of the curved edge screen. Plus the key point for me with buying the Pixel 3 is pure Android no UI installed on top of it so as Google roles out the next version of Android my phone will get the update automatically. So far so good, I'm really liking the Pixel 3. I should mention I am not a heavy gamer, I didn't buy a cell phone to game. I use it primarily for business answering email on the fly and calling customers.
  • pjcamp - Friday, November 2, 2018 - link

    "In order to combat this low memory, one new hardware/software feature is an application memory management 'lowmmemorykiller' background application/daemon which applies various settings to keep certain software in memory for fast app loading times. Whilst in general I don’t put as much value into this as some other people do, I did however notice that in everyday use the phones did need to reload applications more often. There have been user reports already that the phones are struggling to keep things open and alive in memory. "

    That's because software never compensates for skimping on the hardware. They could include more memory, but Google wants to push you into the cloud for everything. They could include removable storage but Google thinks people who use USB sticks every day will be confused.

    If it weren't for the fact that every other vendor seems to be dumber than a sack of doorknobs, Pixels would be going nowhere fast, but that isn't saying much. Lenovo essentially killed Motorola, Nokia won't sell anything of significance in the US, and everyone else can't resist product positioning by skinning the life out of Android.

Log in

Don't have an account? Sign up now