Initial Conclusions

Overall, the One M9 is a pretty significant device for HTC and really sets the tone for the entire year, so it’s well worth going over everything again before we draw any conclusions about the One M9. However, any of these initial thoughts will be limited in their scope because it isn’t really possible to characterize HTC’s camera performance, nor the performance of Snapdragon 810 under load at this time due to HTC's last-minute software update. We can only really look at some key areas like the display, battery life, and SoC performance, along with design and software.

To start, HTC has done a decent job of refreshing the One design for the M9 with their new brushed finish and dual anodization process. HTC has also finally moved the power button to the right side of the phone, and improved the fit and finish of the plastic front bezel. However, there are a lot of missing details that one might have expected from a refinement of a previous design. The power button on the side ends up a bit too low for most people as far as I can tell, and ends up being rather easy to accidentally press and is also being difficult to press intentionally. The volume buttons are also easily confused for the power button, even with the textured pattern on the power button to avoid confusion. The back cover does have a nice feel, but the hard edge between the back and sides of the phone is just too sharp for everyday use and the front bezel is too far separated from the back cover to really make sense. It’s obvious that the bezel on the front of the phone can’t be eliminated, but the arrangement of the bezel combined with on screen buttons really affects the ergonomics of the device. The M7’s keyboard feels comfortably placed in comparison to the M8 and M9, which seem too tall for comfortable typing.

SoC performance is a mild improvement over Snapdragon 805, and a significant improvement in GPU over Snapdragon 801. However, it’s definitely alarming at how small the differences are when Snapdragon 810 is placed in a phone, and it seems that the thermal output of the Snapdragon 810 is high enough that sustained tests end up placing it somewhere around the range of the Snapdragon 805 in CPU-bound tests. In GPU performance, the improvements over the Snapdragon 805’s Adreno 420 are generally somewhat minimal, which really justifies HTC’s decision to go with a 1080p display for the M9.

Unfortunately, in battery life HTC manages to fall somewhat flat as the combination of the Snapdragon 810 and the loss of panel self-refresh causes a significant regression in battery life despite the increase in battery size. I’m not sure how much HTC could’ve done to prevent this, but the removal of PSR is definitely something HTC could’ve kept to try and keep battery life similar to the One M8. This is really the first generation to my memory that actually regressed on battery life in our benchmarks, which is concerning for any device with a Snapdragon 810 SoC. It may be that this is just HTC’s problem, but given that HTC has generally managed to do well at extracting maximum battery efficiency from previous platforms I’m not sure if other OEMs will be able to improve the situation here.

The display is one of the more disappointing aspects of the One M9 thus far. Although the 1080p resolution isn’t really a problem in actual use, the lack of improvement or regression in every other metric suggests that HTC has gone backwards in display quality. Combined with the removal of PSR, it’s concerning to see that cost optimization has affected such a crucial aspect of the smartphone experience. Overall, even when comparing against 2014 smartphones the One M9 ends up closer to the bottom for display quality.

The software experience seems to be one area where HTC continues to do relatively well compared to most Android OEMs, and Sense 7 remains a relatively enjoyable experience. However, the new additions to Sense 7 aren’t really all that helpful. There’s a lot of effort spent on introducing new features like additional personalization and some new widgets and applications, but none of this really feels well-differentiated, and there isn’t much change to the rest of the UI to make it mesh with Lollipop’s UI. It also seems that Snapdragon 810 causes some minor performance issues, but the effects of this are incredibly minor and it’s hard to tell whether this is due to random variance to some extent.

Although we’re still missing some of the pieces, based upon what data we have the One M9 is in an alarming place for a new smartphone. It’s pretty rare that a new phone ends up regressing in almost every major way compared to an old phone, but the One M9 ends up doing this in display and battery life. The SoC is better, but I can’t help but feel that Snapdragon 805 ends up being a better choice than Snapdragon 810 for a flagship smartphone at this time. The Snapdragon 808 may be better suited as an upgrade to the Snapdragon 805, but given the performance of the 810 I’m not really holding my breath. Given all of these issues, I’m almost tempted to point to the One M8 as the better phone, but until we get the full picture we won’t be coming to any final conclusions about the One M9.

Software: Sense 7
Comments Locked

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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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'.
  • 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?
  • 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.
  • 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.
  • 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.

Log in

Don't have an account? Sign up now