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

  • jabber - Monday, April 6, 2015 - link

    Yeah I rarely make calls on my phone. Why bother to spend 5 minutes chatting needlessly when maybe two short and quick text messages will do the same.

    Just have no use for small talk in day to day stuff. People only really call if they have to.
  • DanNeely - Monday, April 6, 2015 - link

    The name smartphone is increasing a mis-nomer. The phone capability is a gateway feature; but the more the average person uses one, the more it ceases to be a phone, and instead becomes a hand computer that includes voice calls in the me-too feature checklist section. If almost all you're doing are voice calls and texting; any entry level phone will work as well as anything else on the market. It's the hand computer uses that differentiate the higher end models from each other.
  • Dorek - Wednesday, April 8, 2015 - link

    "But the camera is a gimmick."

    The camera is one of the most important features of a smartphone. Every smartphone can competently make and receive phone calls. Every $20 flip phone can do that!
  • maroon1 - Monday, April 6, 2015 - link

    S6 has faster CPU and GPU, and far better display.

    ALso, does all android games run on 1440p on S6 ?! I mean just because the display is 1440p that does not means that the game will run on native resolution.
  • aenews - Tuesday, April 7, 2015 - link

    Most games will not have a problem with 1440P and most higher-end games have options to adjust the resolution. I don't know if any games would by default output in 1080P (although it may not make a difference in some games).
  • ToTTenTranz - Monday, April 6, 2015 - link

    «There is also the issue of the “logo bar” bezel, but it’s physically impossible to get rid of this bezel due to engineering constraints.»

    I'm sorry Joshua but these are just HTC's claims and I call bollocks on that.
    Check the M9's teardown at ifixit and you'll see the PCBs have lots of free space everywhere and is oddly shaped for no apparent reason at all. The difference for the iphones and Galaxy Ses is astounding, where everything is a lot more compact and neatly organized.
    Nor is there any valid reason not to at least even out the black bar between top and bottom, making a symmetrical phone.

    At this point, the "HTC black bar" is just a result of lazy industrial design choice and/or incompetent PCB design, IMO.
  • JoshHo - Monday, April 6, 2015 - link

    I've discussed the issue with people outside of HTC, and independently verified HTC's claim by checking multiple device teardowns.

    Fundamentally, the display driver is a large chip that must be coplanar with the display. It's possible to hide the appearance of this display driver, but there is a minimum level of bezel necessary to enable an active matrix display.
  • Raniz - Monday, April 6, 2015 - link

    Yet, somehow, Sony's bezel is significantly smaller.

    http://i-cdn.phonearena.com/images/articles/138100...
  • Connoisseur - Tuesday, April 7, 2015 - link

    Looking at that pic, the Z3 totally has a bezel that's about the same size as HTC's. It just doesn't have a front firing speaker... Speaker height + Bezel Height = Complaints about HTC bezel size?
  • TrojMacReady - Tuesday, April 7, 2015 - link

    The Z3 has 2 front firing speakers, just like the HTC. They are even visible in the picture posted...

Log in

Don't have an account? Sign up now