Display

For those that are uninitiated to the world of displays, a display seems relatively simple. After all, it just needs to have high resolution, pretty colors, high brightness, and high contrast. However, there’s a great deal of complexity to this issue. Even excluding the actual structure of a display, the characteristics of a display can strongly affect perception. Poor display calibration, low brightness, high reflectance, and low contrast can all affect the experience. In addition, something as simple as subpixel arrangement and the thin-film transistor design can have significant impacts on viewing angles and battery life.

In order to test these things, we use SpectraCal’s CalMAN 5 Ultimate and X-Rite’s i1pro2 spectrophotometer to ensure accuracy in our testing, in conjunction with subjective testing to get a good idea of overall display performance. As always, we target sRGB gamut and 2.2 gamma as these are the industry standard. While there are many arguments for larger gamuts and different gamma curves, the goal of our display calibration testing is to make sure that a display will be reasonably accurate in its reproduction of content as an artist intended. Without this calibration, videos, photos, and other content can appear "off".

While we still don’t have an accurate reflectance test, I spent a great deal of time wondering why the display on the Nexus 9 seemed to have more distracting glare than most. This was strange to me as the display was obviously laminated with no perceivable viewing angle degradation that comes with non-laminated displays. It seems that whatever material HTC has used to laminate the display isn’t quite ideal in this case, as at some point in the display stack there’s an obvious secondary reflection. This is an issue relating to a lower index of refraction, so it’s likely that some other characteristic was valued over reflectance.

Other than this, the only other immediately noticeable flaw is the display’s backlight bleed. To me, it’s quite obvious that the display gets lighter at the edges much like what I’ve seen on the Nexus 5. It seems that this is related to the backlight configuration, although given the high brightness of the panel I'm not sure that this can be avoided.

Before we get into the objective testing, I also wanted to mention that this display has “dual-domain pixels” similar to the iPad Air 2 and iPhone 6. The level of angling seems to be much more significant though, which seems to make the purple blacks much more obvious, but outside of this shift in black point it’s almost impossible to see shifts in color with changes in viewing angle. The microscope photo combined with some casual examination under sunlight suggests that the digitizer has been integrated into the display for improved clarity. The resolution is also quite high for a tablet, and while I can obviously pick out aliasing when closely examining the display, at a normal viewing distance I don’t really see any of these problems.

Display - Max Brightness

Display - Black Levels

Display - Contrast Ratio

The brightness of the Nexus 9's display ends up higher than what we see with the iPad Air 2. Contrast is approximately equal to what we see in the iPad Air 2, which is good but definitely not the perfect inky blacks that one might be used to from AMOLED.

Display - White Point

Display - Grayscale Accuracy

The next aspect of our display test suite is the grayscale test, which looks at the color balance and brightness of various shades of grayscale from black to white. Here, the Nexus 9 really does a great job across the board. If I were to nitpick, there is a bit of extra blue in the display but it’s really nothing worth talking about. Google does seem to consistently favor a lower contrast look when the gamma curve is dead on the mark, but on average it’s close enough to a power 2.2 curve that it doesn’t make a difference when viewing the display.

Display - Saturation Accuracy

While grayscale is important, colors are really the hardest part to get right in a display. Here, the Nexus 9 does an amazing job in our saturation test. I really don’t have anything else to say here as pretty much everything is on the mark. At this point, it’s pretty clear that most Nexus devices have a strong focus on display quality, and the Nexus 9 is no exception.

Display - GMB Accuracy

Finally, the Gretag MacBeth test shows that the Nexus 9 is quite accurate with color even outside of the basic primary and secondary colors. There shouldn’t be any issues with viewing content that has high requirements for color accuracy. Overall, the Nexus 9 display is great with only two real issues of note, namely the reflectance issue and the backlight bleed. While neither are deal-breakers, fixing these issues would make this display fall under a short list of the best mobile displays I’ve seen all year. For now, it sits just shy of that list. I definitely have to applaud Google in this case as they haven’t fallen into the trap of wider gamuts, bluer white points, dynamic contrast, and other “features” for the sake of showroom appeal.

GPU and NAND Performance Battery Life and Charge Time
Comments Locked

169 Comments

View All Comments

  • PC Perv - Wednesday, February 4, 2015 - link

    It is clear, even though you did not say, why no one other than NV and Google will use Denver in their products. Thank you for the coherent review, Ryan.

    P.S. I can't wait for the day SunSpider, Basemark, and WebXPRT disappear from your benchmark suit.
  • jjj - Wednesday, February 4, 2015 - link

    You always make those kind of claims about dual core vs more cores but you have never attempted to back them up with real world perf and power testing.
    In real use there are alerts and chats and maybe music playing and so on. While your hypothesis could be valid or partially valid you absolutely need to first verify it before heavily insisting on it and accepting it as true. Subjective conclusions are just not your style is it, you test things to get to objective results.
    And it wold be easy you already have "clean"numbers and you would just need to run the same benchmarks for perf and power with some simulated background activity to be able to compare the differences in gains/loses.
  • PC Perv - Wednesday, February 4, 2015 - link

    Where would you put the performance of "backup" ARM-only part of Denver? Cortex-A7? Is it measurable at all?

    Also, why don't Samsung use F2FS for their devices? I thought it was developed by them.
  • abufrejoval - Wednesday, February 4, 2015 - link

    While the principal designer seems to be a Korean, I'm not sure he works for Samsung, who typically used Yet Another Flash File System (YAFFS).
  • Ryan Smith - Wednesday, February 4, 2015 - link

    It's not measurable in a traditional sense, as the DCO will kick in at some point. However I'd say it's somewhere along the lines of A53, though overall a bit better.
  • Shadowmaster625 - Wednesday, February 4, 2015 - link

    The design philosophy of the DCO does make a lot of sense. When your mobile device starts to bog down and you start cursing at it, what is it usually doing? It is usually looping or iterating through something. The DCO wont help with small blocks of code that execute in 500uS, but you dont need help with that sort of code anyway. What you want to improve is exactly the type of code the DCO can improve: the kind of code that takes several dozen milliseconds (or more) to execute. That is when you begin to notice the lag in your cpu.
  • mpokwsths - Wednesday, February 4, 2015 - link

    Joshua & Ryan,

    please update the charts with the bench results of the newer version of Androbench 4: https://play.google.com/store/apps/details?id=com....
    (I had previously commented on the fact that you can't safely compare the i/o results of different OS AND different bench apps).

    Androbench 4 is redesigned it to use multiple i/o threads (as a proper i/o bench app should have) and produces vastly improved results on both Lollipop and earlier Android devices.

    You will not be able to compare the newer results with older ones, but at least it will put an end to this ridiculus ι/ο performance difference between iOS and Android, the one you persistently -but falsly- keep projecting.
  • Andrei Frumusanu - Wednesday, February 4, 2015 - link

    I tested this out on several of my devices and could see only minor improvements, all within 10%. The performance difference to iOS devices does not seem to be a dupe at all.
  • mpokwsths - Wednesday, February 4, 2015 - link

    My results strongly disagree with you:
    Nexus 5: Seq Write: 19MB/s --> 55 MB/s
    Rand Write: 0.9 --> 2.9 MB/s

    Sony Z3 Tablet: Seq Write: 21 MB/s --> 53 MB/s
    Rand Write: 1,6 MB/s --> 8MB/s
    Seq Read: 135 MB/s --> 200MB/s

    I can upload pics showing my findings.
  • mpokwsths - Wednesday, February 4, 2015 - link

    Meet the fastest Nexus 5 in the world:https://www.dropbox.com/s/zkhn073xy8l28ry/Screensh...

    ;)

Log in

Don't have an account? Sign up now