Display

By now, it generally goes without saying that a high end smartphone needs to have an amazing display. However, defining what an amazing display is can often be quite difficult. We can all agree that a display should get as bright as possible and that black pixels should be as dark as possible, but some characteristics are often subject to personal biases. Something as simple as white point can divisive because some people prefer warmer colors, but others prefer a colder color balance. Color in general can be a subjective preference, as some prefer wide color gamuts and saturation compression to achieve a vivid look, but others prefer more muted and subtle colors.

However, despite subjective preference we have to all have a common standard for color rendition. After all, if pink on one screen looks like magenta on another, this could easily result in a number of problems when sharing content. Something as simple as taking a photo can be difficult with an inaccurate display, as white balance on a photo could easily appear to be incorrect for a scene even if it isn’t. As a result, in addition to judging simple characteristics such as brightness and contrast, we also test how well a display matches against the sRGB color standard with a gamma target of 2.2. In order to do this, we use our usual test suite which includes X-Rite’s i1Pro2 for accurate color and brightness measurements, along with X-Rite’s i1Display Pro for accurate contrast measurements. In order to fully utilize this hardware, we use SpectraCal’s CalMAN 5 Ultimate with a custom workflow for mobile devices.

Display - Max Brightness

Display - Black Levels

Display - Contrast Ratio

Our first test is focused on some of the basic aspects of the display, namely brightness and contrast. In this regard, the M9 seems to effectively identical to the M8. Both have some level of content-adaptive backlight control, which means that static contrast is lower than the value that we’ve tested it for.

Outside of this basic test, I noticed that the display has worse viewing angles than the M7 and M8. Although the off-angle glow isn’t visibly different when shifting the display along the horizontal and vertical axes, anything in between dramatically decreases contrast as seen in the photos below. It’s likely that this is related to the polarizers used, as the IPS glow effect is strongly angle-dependent. In practice, this really does reduce the effective contrast of the display. The brightness of the display could be higher, but it’s likely that at this point it makes more sense to target lower reflectance with improved coatings rather than driving brightness.

Display - Grayscale Accuracy

Display - White Point

Moving on to grayscale calibration, we can see a dramatic reduction in accuracy when compared to the M7 and M8. Although gamma is generally correct, the white balance ends up far too green and blue. The next most notable issue seems to be related to CABC, as there’s a dramatic increase to gamma from 70% to 100% white. In practice, everything looks excessively cold and with a strange green tint to a lot of content, which really hurts the viewing experience. In order to get an idea for whether this is just a single point or a general trend, we can look at the saturation test which introduces multiple colors.

Display - Saturation Accuracy

Display - Gamut Accuracy

As we can see, in the saturation test this excess of green and blue in colors is not an isolated case of white balance. Colors like magenta are significantly skewed towards blue, yellow tends to skew towards green, and colors like blue and green have noticeable saturation compression. As a result, the color accuracy will be noticeably different from a monitor that follows the sRGB standard. The only positive aspect of this color calibration is that HTC has managed to constrain the gamut of the display to sRGB, unlike the M8 which noticeably exceeded sRGB.

Display - GMB Accuracy

In the Gretag MacBeth ColorChecker, we can get a holistic view of color accuracy within the sRGB space which tests hue, saturation, and gamma to see display calibration as a whole. Somewhat predictably, the M9 also falls short in this scenario. Given how significant the deviations are, it would be difficult to use the M9 in any case where color accuracy is needed.

Overall, the display of the M9 is disappointing. At some point, it was clear that HTC was integrating some of the best mobile displays possible into smartphones, but starting with the M8 it seems that we’ve seen HTC slip in this area. The M9 continues this trend, which is somewhat concerning as the display of a slate smartphone tends to be a critical part of the experience. Some may be eager to point to AMOLED as an alternative, but the problem is that HTC has failed to integrate a high quality LCD into the M9. In the near future though it seems that it may make sense for HTC to move to AMOLED. However, it’s unlikely that such a move would result in any reduction of bezel size as all current displays require a display driver that must be placed directly next to the display.

HTC’s Last Minute Software Update, Battery Life, & Charge Time System Performance: Snapdragon 810
POST A COMMENT

132 Comments

View All Comments

  • flyingpants1 - Monday, March 23, 2015 - link

    Those are the dumbest reasons I have ever seen. One front speaker is infinitely better than one rear speaker. IR blaster is a gimmick feature. Amoled.. You're blaming Amoled for lollipop being white.. Jesus. Reply
  • hughlle - Tuesday, March 24, 2015 - link

    One front speaker is worse than 2 front speakers. You call it a gimmick, others call it a great feature; I certainly wouldn't buy a new phone if it didn't have an IR blaster. And no, where did he blame amoled? He said that because lollipop is so white then the power saving ability of amoled is not really relevant in lollipop.

    Nice try and trying to spin everything though.
    Reply
  • flyingpants1 - Monday, March 23, 2015 - link

    Lol.. You can get used to having no buttons. You know like LG, Sony, Nexus 4,5,6, Motorola..

    You can't get used to having no front speakers.

    Also the M9 has mSD which allows me to dump 128gb of music on there, or record 1080p videos continuously and switch out cards.
    Reply
  • Black Obsidian - Tuesday, March 24, 2015 - link

    Of course you can get used to having no front speakers. It's not as though rear-facing speakers don't work at all.

    Presumably the M9 also comes with a headphone jack and Bluetooth audio functionality, both of which offer listening options incomparably better than crappy phone speakers, whatever their orientation.
    Reply
  • Notmyusualid - Wednesday, March 25, 2015 - link

    I must humbly disagree with you Sir.

    Whatever 'other' audio connectivity exists, that will not suffice if I lean over to the phone in the car whilst in its holder, and choose to answer with 'speaker'. My GS5 can barely be heard, so bad to the point that I end the call and dial back when I stop.

    I drive many company / rental cars, I'm not bluetoothing to each and every one, and I'm not the greatest fan of bluetooth headsets.
    Reply
  • Notmyusualid - Wednesday, March 25, 2015 - link

    No Sir. I can't get used to having no physical buttons, or M9 it would be for me.

    It matters not how many devices in existance have them, for I simply find them too buggy to use, they take up valuable screen space, and their nature of appearing / dissappearing gives me chest pains, for want of a better description.

    And yes, once you've have had 'quality' front facing stereo speakers, 'it just seems illogical to do it any other way'.
    Reply
  • lucam - Sunday, March 22, 2015 - link

    Dear Anand,

    Why you haven't used the new GFXBench 3.1 as well as the new Basemark ES 3.1?
    Reply
  • Andrei Frumusanu - Sunday, March 22, 2015 - link

    GFXBench 3.1 was recently released only 2 weeks ago and is currently only available for Lolipop devices. We will adopt it in future reviews, but for now we can present more useful comparison data for 3.0. Reply
  • arayoflight - Monday, March 23, 2015 - link

    Do you have a Galaxy S6 for review?

    Also, I think the Manhattan 3.0 and T-rex are more representative of real world performance then the ultra-high load of 3.1 in which the one with more compute performance wins.
    Reply
  • lucam - Monday, March 23, 2015 - link

    True, but the same was told last year for Manhattan 3.0 as it was very compute for that time.
    I guess in about 6 months- 1 years all mobile devices will run the new GFX 3.1 smoothly.
    Reply

Log in

Don't have an account? Sign up now