Display Accuracy

As I mentioned in my initial review, the OnePlus 3 targets the NTSC color gamut. I really feel the need to reiterate that this choice of gamut target makes absolutely no sense. The actual NTSC gamut was never really relevant, even back in the 1950s when it was created. This is because the phosphors used in CRT displays of the time simply could not produce such saturated colors with an adequate brightness level. In fact, most modern displays still cannot realize the original NTSC gamut. Because of this, it was assumed that content was created and should be displayed using the gamut defined by the SMPTE C specification, which is actually smaller than the sRGB gamut. SMPTE C also used CIE Illuminant D65 for the white point instead of CIE Standard Illuminant C which has a CCT of 6774K, making it more blue than the white point used in more modern color standards.

If the NTSC gamut is not a sensible target, a good question is what gamut would be? This gets back into the discussion of color management, which is something I've discussed in the past several times and don't want to tread over again in this article. In theory, it would make most sense for OnePlus to target the DCI-P3 gamut, because right now UltraHD Bluray content uses that color gamut in a Rec. 2020 container for future compatibility as displays actually move to Rec. 2020. That is why Apple is targeting the DCI-P3 gamut on their newest devices, and it's why all the high end UltraHD TVs launching this year use it as well.

Unfortunately, Android poses a problem here. Android has no color management at the system level, and so if you ship a wide gamut display you get oversaturation when viewing anything designed for sRGB, which for most people will include every single piece of content on their phone. Because of this, the only two reasonable options are to just constrain your Android smartphone to sRGB completely, or to include separate color modes that allow switching between sRGB and the wider gamut. This isn't the fault of the Android device makers, and it's clear that the inclusion of wider gamut displays is done with good intentions, but for now we have to wait on Google to bring color management to Android.

One thing I didn't do in my review was test the OnePlus 3 against the NTSC standard. Again, I feel this is mostly pointless because you will not be able to find any content anywhere that targets that gamut, but examining how well the display conforms to OnePlus's target gamut would have been an interesting exercise nonetheless. Unfortunately, OnePlus seems to have changed the white point in the normal display mode significantly with this update, which means any results I report won't be representative of how the phone was on its original firmware, or how it may be in the future. We ran into this same issue with the OnePlus One, where later updates completely changed the calibration and made it much less accurate. OnePlus has a bit of a track record of changing key device behavior after release, with another example being the browser detection on the OnePlus 2 which shut off the A57 cluster. I'm not a fan of publishing results that are subject to change with any update, and I'm not going to play the game of testing a phone again after every single update to see if things have changed, especially when changes are made but not documented at all in the update notes.

Display - Grayscale Accuracy


SpectraCal CalMAN

Greyscale accuracy with the sRGB mode enabled is a huge improvement over the standard display mode. The CCT average is slightly below target, but only by a tiny amount. My only complaint is that the RGB balance with the whitest shades is shifted too far toward red, and it would be good to tweak this a tiny bit to make sure 100% white is properly balanced so that the display doesn't have any sort of warm cast on webpages and in Material Design applications. Even with that, the error levels for each individual shade of grey are all at or below three, which is what we're targeting. With these changes the OnePlus 3 goes from being one of the worst displays on record to one of the best, and that's a great thing to see.

Display - Saturation Accuracy


SpectraCal CalMAN

I was originally concerned that it might be too late to properly fix the OnePlus 3's display once phones had shipped, as there's a degree of variance from display to display. However, it appears that the displays, while inaccurate, were defined well enough that OnePlus knew what to tweak to constrain them to sRGB. In the saturation sweep test you can see that only two error values go slightly above three, with the rest being comfortably below.

Display - GMB Accuracy


SpectraCal CalMAN

With great greyscale and saturation rendering you're usually set for accurate color mixture rendering. With its sRGB mode enabled the OnePlus 3 does a great job of rendering the colors that are part of the GretagMacbeth ColorChecker test. The error value is below our target value of three, and pushing accuracy much further doesn't bring many benefits as at this point you already can't discern the difference between the colors and their actual reference colors unless you have them sitting still beside one another.

To say that OnePlus's new sRGB mode provides a substantial improvement in display accuracy would be an understatement. The display has gone from being the most inaccurate display that I've seen in years, to being among the most accurate displays that we have on record. Gone is the ghastly blue shift, and even in the standard display mode OnePlus has toned that down significantly. The gamut matches sRGB very well, and both greyscale and color reproduction is right on target.

Introduction Final Words
POST A COMMENT

81 Comments

View All Comments

  • MrCommunistGen - Thursday, June 30, 2016 - link

    Oh, I didn't mean to only post that. I also wanted to thank you for your diligence in doing the additional testing and for your well written objective analysis as well as your personal commentary on the topic of color accuracy.

    I think that this is a topic that more people would care about if they knew about it, and articles like this are a step in that direction.
    Reply
  • Brandon Chester - Thursday, June 30, 2016 - link

    I do plan to do this. I'm just at work right now, will be updating both the display and conclusion sections of the original review around 5PM EST. Reply
  • MrCommunistGen - Thursday, June 30, 2016 - link

    Awesome! Reply
  • Stochastic - Thursday, June 30, 2016 - link

    OnePlus One owner here. My one big gripe with the OPO is that, at least on T-Mobile, reception is pretty terrible. In your experience does the OnePlus 3 have any issues receiving LTE? In your review you wrote that "I'm still unable to achieve a strong enough signal over LTE to get results that are comparable to those run by Josh and Matt" which concerned me. Reply
  • Brandon Chester - Thursday, June 30, 2016 - link

    That's not due to the phone. My apartment just has terrible cellular reception on both our major networks on all my devices. I'm only pulling -97dBm, so I've decided to stop directly comparing my results, at least until I move at the start of August where I'll have to investigate the signal again. Reply
  • Lolimaster - Thursday, June 30, 2016 - link

    Meanwhile I currently have my firefox with 200tabs and just 4GB of memory on my Athlon II X4 620, feels snappy. Reply
  • MrCommunistGen - Thursday, June 30, 2016 - link

    There are likely other factors involved as well. First one off the cuff is that modern desktop OSes like Windows manage memory differently than Android. I guess there's a chance things have changed, but AFAIK Android does not use a pagefile to help alleviate memory pressure.

    Also, on mobile devices, the VRAM is still allocated out of a chunk of RAM. If your desktop has a dGPU, that'd be extra memory available on desktop vs mobile.

    Unfortunately I'm not terribly well versed in this topic and can't really provide much specific insight.
    Reply
  • thek - Thursday, June 30, 2016 - link

    Hi, Look!
    It's a reviewer that clearly forgot what it was to be an average day to day consumer and only thinking like a reviewer - with only numbers in his mind .. (kind of like politicians these days..huh), and bashed an apparently really decent phone(..or a superb! if you take into account the cost of it which is half the cost of a new galaxy or Iphone) for nothing really. just because it wasn't amazing.

    I swear, I thought about not buying this phone just because of your earlier review and what you said about the display, but thank god there are other decent reviewers out there. Once no one(literally no one) even mentioned the display I knew it was probably because you were relying too much on the numbers instead of actually looking at the screen. Then I went into youtube to watch vid reviews (and display reviews between the OP3 and other flagships) and clearly the OP3 was not the worse, as you said...and surprisingly enough, just from eye-to-eye, it was sometimes the best.
    Reply
  • thek - Thursday, June 30, 2016 - link

    just adding, I started liking AnandTech less since your review. Reply
  • MrCommunistGen - Thursday, June 30, 2016 - link

    "Beauty is in the eye of the beholder" is an age old adage for a reason. As I think Brandon mentioned in the review, much of the consumer base actually prefers oversaturated colors. This is part of what won early AMOLED panels their consumer appeal.

    The point of an thorough and critical review is not to say the same thing as every other site. It is to push the boundaries of what is examined. To perhaps find things that a device does particularly well, or in this case something a device might not do well.

    Personally, I'd like to know there is a *potential* issue with a device and be able to make an educated decision based on that, rather than no one looking deep enough, me buying the device, and seeing something clearly different on the display than I was expecting.

    The point of color accuracy isn't necessarily to provide picture that looks the best, but rather to display the colors that were actually called for.

    My rather poor example is: Say you are helping a friend buy a used car. You take a picture of a car whose paint looks faded and send it to your friend. For the case of this example, lets say that the picture taken was perfect. The lighting, exposure, and color represented in the image are exactly as it looks in real life. When viewed on a device with an oversaturated display, that car might look better than it does in real life. It might not look faded.

    If the conversation you're having is: "Hey <your friend's name>, I think the car is in good shape but the paint looks faded" <insert picture>

    If your friend's phone has an oversaturated display, he might say: "Naw, it looks fine to me" when in fact the paint looks terrible. When he shows up to buy the car he's probably going to be disappointed.

    I understand this is a very narrow example, but I hope it illustrates the difference between making an image look "good" vs accurate.
    Reply

Log in

Don't have an account? Sign up now