Camera Performance

Now that we've finished going over the camera architecture and user experience of the One M9 we can talk about the end result, namely the quality of the still images and video that the One M9 can produce. Our first test is a basic test of spatial resolution, which uses high-contrast line pairs that make it possible to get a good idea for what the effective maximum resolution of the camera is.

In this test, we can see the benefits of the 20MP camera sensor of the One M9, spatial resolution in this test is a massive improvement over what we saw from the One M8. At the center, the resolution of the camera is sufficient to resolve up to the 20 mark. Resolution at the edges of the frame remains sufficiently high, with no obvious field curvature in this test. To get a more nuanced look of low ISO camera performance, we can look at some standard daytime shots to get a better idea of real-world camera performance.

Here we can start to see some of the real issues with the One M9's camera. It's immediately obvious that the sky here is just the wrong color. Although Los Angeles can be a smoggy place, the sky in this photo should be a stronger shade of blue, not gray with a tinge of blue. Looking at the texture of the roof, the grass throughout the photo, and the bleachers off in the distance, it's pretty obvious that HTC needs to strongly reduce the noise reduction that they're using here, as there's almost no detail in these photos. The detail is basically comparable to the iPhone 6's 8MP camera, which shouldn't be the case in these daytime conditions. The lack of shadow detail also degrades perceived quality. In general, the photo appears to be a bit underexposed as well.

With the HDR mode, all of the issues seen in auto mode are still present. However, to HTC's credit HDR mode is now usable instead of being almost useless as it was with the One M8. HTC still needs to focus on reducing halos as there seem to be issues with this on some high contrast edges/moving objects and make HDR a live preview similar to the Galaxy S5 and S6 camera, but in general this is a dramatic improvement when compared to previous devices.

In low light, the One M9 performs horribly. There's really not much else to be said because there's next to no detail in these photos. Noise reduction has smeared away what detail there was. Despite the fact that the photos have evidence of incredibly strong noise reduction, there's still a lot of noise visible in the image. Thankfully, the color noise of the image is low which makes things better, but for 1600 ISO and 1/9 second exposure time, the output is nothing to talk about.

Moving on the video quality, we can first look at 1080p30 quality. HTC uses a 20Mbps encode rate, using H.264 Baseline for video, and 192Kbps AAC for audio encoding. While the iPhone 6 can serve as a reasonable reference, there are a lot of apparent issues even if one doesn't look to the iPhone 6 for a point of comparison. In general, 1080p video doesn't seem to carry a great deal of detail with it, and it looks like there isn't any kind of video stabilization going on here. The result is that footage is extremely shaky and really kind of disappointing here.

For 1080p60 we can basically see the same story, as the One M9 still has a noticeable lack of detail and there are a lot of problems with camera shake that aren't dampened out. It almost looks like HTC doesn't have any kind of stabilization for video here, which is rather disappointing. The bitrate of 1080p60 footage is also unchanged from the 1080p30 settings, which is a bit curious.

For 720p120 slow motion, HTC does manage to capture real 720p footage instead of upsampled 480p video, and it compares favorably to the iPhone 6 but detail continues to be a problem here. The encoder settings are similar to 1080p30 with its H.264 Baseline setting, but bit rate is reduced to 12.1 Mbps.

Overall, the performance of the One M9's camera is disappointing. Overall, it's still probably better than the One M8's camera, but the execution is lacking. HTC needs to focus on improving detail by avoiding aggressive noise reduction, reduce aggressive sharpening, improve shadow detail, implement effective EIS and OIS, and work on improving auto-focus and capture latency. It's concerning that HTC still cannot come close to the competition in this area, and given that camera is a crucial aspect of any smartphone experience HTC needs to resolve all of these issues if they want to remain relevant in the smartphone market.

 

Camera Architecture and UX WiFi Performance and GNSS
Comments Locked

127 Comments

View All Comments

  • TrojMacReady - Tuesday, April 7, 2015 - link

    Colors were more accurate, resolution a hair higher, contrast and blacklevels were seriously lagging compared to the S2, speed of the phone was quite a bit slower, camera was much worse too.
  • CrazyElf - Monday, April 6, 2015 - link

    Thanks for the review.

    It's a disappointing phone. I wonder what they were thinking about when they made this? Hmm, probably not much on how it would be received.
  • zodiacfml - Monday, April 6, 2015 - link

    Heartbreaking even without the S6. The S6 is just too good right now.
  • mhaager2 - Monday, April 6, 2015 - link

    Joshua, your concerns regarding the snapdragon 810, do you think they are device specific or can we expect this to hold true across different flagship phones? I'm waiting for the Xperia Z4 but wondering if it's worth it compared to the 801 in the Z3
  • kspirit - Tuesday, April 7, 2015 - link

    I hope the Z4 and G4 both use the S808 or even 805 instead of this (literally) hot mess.
  • lilmoe - Monday, April 6, 2015 - link

    Ouch. That horrible SoC might have been OK to swallow, but the camera is definitely a deal breaker for many...

    They could have stuck with the exact same design and internals of the M8 while dramatically improving the camera, and it would have been much more of an upgrade than ^this...

    On a side note, HTC SERIOUSLY needs to reconsider the internal design and layout of components. Repairing the One, _any One_, is a nightmare.
  • Gunbuster - Monday, April 6, 2015 - link

    Repair has been a nightmare since always for HTC, Touch Pro's and Radar come to mind.
  • Dorek - Wednesday, April 8, 2015 - link

    I was going to replace my Radar's battery before I decided to just buy a new phone, and it didn't look too awful...
  • Gunbuster - Thursday, April 9, 2015 - link

    Battery is okay, anything involving the screen stack that is glued to the digitizer...

    Also super easy to wreck the microphone mylar flex cable.
  • tom5 - Monday, April 6, 2015 - link

    So to wrap-up: HTC had quite a nice device to start with - the HTC One M8, but decided to ruin it all, starting with the camera subsystem which is a joke, followed by a I'm_A_Mistake_SoC - the 810. Samsung knew what they were doing when they chose their own Exynos to power the S6.

    It's a pity because I really like HTC devices. Having put so much emphasis on the camera features I just can't believe what they did in this area with the M9. They wanted to "buy" us with the megapixel count or what?

Log in

Don't have an account? Sign up now