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

  • Shadowmaster625 - Monday, March 23, 2015 - link

    With 1080p snapdragon 801 phones regularly pricing in at $300, this phone clearly offers nothing to justify twice as much money. Why would anyone want this over an M8 for half the price? The battery dont even last as long. Wow.
  • tipoo - Monday, March 23, 2015 - link

    I wonder if it sticking far from its max clock speed has to do with the "fix" for its initial overheating issue, imaged below. I wish Android SoC makers would stop pursuing stupidly high clocks that they throttle back from in seconds. This whole thing might be confirmation that Samsung moved away from Snapdragon for the throttling/overheating.

    http://www.droid-life.com/wp-content/uploads/2015/...
  • testbug00 - Monday, March 23, 2015 - link

    Yes, not running the SoC at a level where the heat dissipation was to high for the case to handle fixed problems.

    Anyhow, the 810 has no thermal problems. Phone manufacturers cramming a 10W+ SoC into a phone and than people expecting it to be able to draw 10W+ over an extended period of time without causing heat issues are the problem.
  • Tigran - Monday, March 23, 2015 - link

    Dear AnandTech, two questions:

    >>> For those that are unfamiliar with how HTC's CPU cheats work, HTC continues to rely on some level of benchmark detection, and it seems that when a benchmark is detected it enables a "High Performance" mode in the developer settings with no option to disable this mode. It's possible to work around this mode by using benchmarks that evade such detection mechanisms (and we do), but it's also possible manually toggle this mode on and off if a benchmark isn't detected. <<<

    1) Was High Performance mode disabled in all CPU/GPU tests performed in Part I?

    >>> We'd normally go into depth about the PCMark, GFXBench, and Basemark OS II battery life results at this point but the new software update precludes this from happening at all as all three could be significantly impacted by changes to thermal throttling. In GFXBench, I saw a change from 1.73 hours to around 3 hours of battery life on our infinite T-Rex rundown test, and in PCMark I noticed that the M9 reached about 40C, which brings it close enough to the new update's maximum skin temperatures that all three tests must be re-done. <<<

    2) So are we to see infinite GFXBench test with actual fps in Part II? And why must you re-done tests because of the thermal throttling - isn't it going to be constant part of M9's software? Are you going to disable this thermal throttling in your following tests?
  • JoshHo - Monday, March 23, 2015 - link

    We do not enable HTC's high performance mode for performance benchmarks but we try to avoid throttling the SoC.
  • Tigran - Monday, March 23, 2015 - link

    It seems quite reasonable with high performance mode off, but if you disable throttling (enabled by M9's software) will it represent M9's real performance?
  • JoshHo - Monday, March 23, 2015 - link

    We can't disable the throttling mechanisms without root. For performance benchmarks (not thermally limited) we will often use cooling pads to try and avoid throttling.
  • Tigran - Monday, March 23, 2015 - link

    So you don't root and disable throttling, do you? But I don't understand what's the purpose of using cooling pads, if it doesn't represent real situation of the users. Do you allways use cooling pads in tests "not thermally limited"? I'm afraid I don't know which test are thermally limited and which are not.

    Sorry for asking many questions, I'm a tech blogger from Russia and often quote your reviews (I believe they are the most professional and unbiassed).
  • JoshHo - Tuesday, March 24, 2015 - link

    In general it isn't necessary to use additional cooling for most phones, but we do this in order to try and standardize the test conditions because we can't standardize room temperature and what surface the phone is on well enough. The tests where we don't do this are part of the battery life tests, which is why throttling is often seen in those tests.
  • Tigran - Tuesday, March 24, 2015 - link

    Thanks a lot for your answers, Joshua. Looking forward to see Part II, with infinite tests and SD810's long-term real performance.

Log in

Don't have an account? Sign up now