Return of the UltraPixel

As I mentioned earlier, the One’s primary camera sensor remains unchanged from last year’s model. The M8’s primary shooter is a 4MP “UltraPixel” camera with 2.0µm square pixels. As Brian (correctly) theorized last year, there were two sources for HTC’s UltraPixel camera: ST (VD68969) and OmniVision (OV4688), the latter being the limited second source. Due to quality control problems with the ST sensor the M8, like later models of the M7, uses the OmniVision sensor exclusively. The entire module is almost identical to what we saw last year in the M7, with one notable exception: it no longer has OIS (Optical Image Stabilization). Dropping OIS was likely due to a combination of cost and performance concerns. HTC’s OIS was never quite as good as Nokia for example, and there’s surely an impact on yield. I’m curious as to whether or not we’ll see it return in a future flagship, but for now the feature is gone.

The impact is obvious. I carried both versions of the One (M7 and M8) and recorded some video while walking around RDU. The lack of OIS has a tremendous impact on image stability while recording a video:

The impact on still photography is also significant, although it’s easier to mitigate through tuning of the camera software.

HTC is quick to point out that although the camera sensor and lens system haven’t changed since last year’s model, they are backed by an improved Qualcomm ISP (Snapdragon 801 vs. 600). HTC maintains the dual-ISP approach with both its own Imagechip and Qualcomm’s integrated ISP working to process sensor data. It’s unclear just how different the underlying ISP architecture is in Snapdragon 801, however it is considerably faster (930MP/s vs. 320MP/s).

The camera UI has been substantially improved (not that it was bad to begin with). With enough light, the preview appears to be full res, accurate and at a high frame rate. In lower light the preview will drop frames as it attempts to maintain visual accuracy.

A full pass of the autofocus routine should take around 300ms. There’s virtually no capture lag as images are dumped directly from a capture buffer to NAND. Burst capture is supported, just hold down the capture button and the One will grab a maximum of 99 frames at a rate of around 12 fps. HTC offers a best shot button that will analyze all 99 frames, determine the best one and delete the rest. You can also use HTC’s Gallery to quickly select and delete all photos.

HTC continues to do an excellent job with the software tuning of its camera. The One’s auto mode is really good. There do seem to be some tweaks compared to the M7’s camera software (above and beyond mitigation for the missing OIS), for example color accuracy is improved on the M8. There's also a new dual flash, similar to what's in the 5s.

The whole point of HTC’s UltraPixel sensor was to capitalize on the fact that most of the time we’re taking these ultra high resolution photos on our phones, only to have them reduced to less than 1MP and shared on the web, Facebook or Twitter. If that’s your primary use case, the One’s camera is really one of the best, most versatile shooters on the market. HTC’s 2.0µm square pixels enable great low light performance.

Performance in well lit scenes is also more than reasonable if you’re talking about sharing for the web at reduced resolutions:

The problem becomes when you start trying to share at full resolution:

The fact remains that there are more pixels on a 15-inch MacBook Pro’s Retina Display than you can get out of the One’s UltraPixel camera. On the M8 in particular, you actually get higher resolution shots from the front facing camera than you do out of the rear.

If you look back at last year’s coverage of the M7, you’ll find large pockets of people who were put off by the sensor’s lack of spatial resolution. Unfortunately HTC did nothing to address this weakness with the M8.

One complaint I definitely had about the previous One was its insistence on driving to higher than needed ISO values when in really low light scenarios. I remember being so incredibly pleased with this shot taken with the M7, but having to manually set the ISO to 200 in order to get it.

With the new One, HTC seems to do a slightly better job of choosing ISO levels in auto to begin with. If it goes too aggressive however, HTC now offers an easy way to cap max ISO with an Auto Max ISO setting. Previously the ISO toggle was in the settings menu and only forced a single value, now with Auto Max ISO you can set the absolute maximum ISO level you’d like the camera to use and it’ll choose any value up to but not exceeding that.

HTC continues to limit the minimum ISO level to a fairly high value of 100. I’m not entirely sure why this is, but there’s definitely a negative impact on performance in scenes with lots of light. Both Apple and Samsung by comparison can go down to much lower ISO values.

If you need more control over the M8’s camera, HTC now exposes full manual controls for ISO and shutter speed, in addition to white balance, exposure and focus point. The UI is reminiscent of Nokia’s Camera+ manual controls. Tap on any of the values you’d like to adjust and you’ll get a vertical slider. The UI isn’t entirely intuitive. Instead of dragging down from the red A (which won’t work), you slide up from the bottom or tap directly on the desired value. The manual controls won’t hide automatically either, so tap on a few of these things and your camera preview becomes crowded with adjustments.

The biggest problem is that HTC attempts to give you a live preview reflecting the settings you’ve chosen. Drop shutter speed down too low and you’ll get a camera preview that’s effectively unresponsive as it updates the display in line with your shutter speed. HTC’s head is in the right space though, exposing full manual controls is a great step forward - it just so happens that HTC’s auto mode is good enough to not have to rely on them.

The One’s HDR mode requires around 2.5 seconds from the moment you capture until it’s done processing. The multi-exposure HDR still produces blown out highlights in bright scenes, somewhat defeating the point of HDR photography to begin with.


Not all situations are terrible for HTC's HDR mode however. In this setup below, I actually get more detail in the shadows and highlights rather than just one:


Overall HTC’s more aggressive HDR definitely increases detail in the shadows, but often fails to preserve detail in highlights.

Switching between front and rear cameras is a simple downward swipe (and the same to switch again). Switching between other modes is similarly quick by using the new camera selector button in the lower right of the UI. Tapping it will bring up this screen exposing all six modes supported by the camera:

Pretty much all of the modes here are self explanatory, though there are two I want to focus on in particular. HTC’s Zoe camera was a big focus of the original One, and it’s obviously back here with the M8. Instead of Zoe being an awkwardly placed button on the left side of the camera UI, it’s now a separate camera mode.

Just as before, you can use the Zoe camera to capture full resolution stills or 1080p30 video. Tap the capture button and you’ll dump a still just like in the standard camera. Hold the capture button down and you’ll record a short, vine-like video as well as capture 20 stills in tandem. Unlike Zoe on the M7, the short videos aren’t of a fixed length. The M8’s Zoe camera records video as long as you have the capture button depressed, and after a short while it’ll lock into recording letting you free up your finger. The Zoe experience is much better on the new One.

The M8’s Gallery app automatically grabs photos, videos and short videos recorded with the Zoe camera, adds some filters and background music and creates a short 30 second highlight of your event/day. There are a number of predefined themes, but you can also add your own music, select start/end photos and directly control what content appears in the highlight. The real beauty of the feature is that if you don't want to do any of that, you don't have to - the One will automatically put together a highlights reel without any user intervention.

The Pan 360 mode lets you stitch together awesome panoramas with an incredibly easy to use UI. The tool just presents a bunch of red boxes on the display, line up the focus target with each box and it'll automatically capture/move to the next one. You never have to hit the shutter button.

5MP Front Facing Camera

The front facing camera uses a 5MP Samsung S5K5E sensor with 1.12µm pixels. The rear sensor is still capable of better images, but it is sort of funny that the front facing camera has a higher resolution sensor than the primary shooter. It's interesting just how important the front facing camera has become in recent times. Moving to a 5MP sensor on the front of the M8 is something that would've been unheard of not too long ago.

Front Facing Camera
Rear Facing Camera

1440 x 2560 - 1.5MB

1520 x 2688 - 2.5MB (1.65MB without Duo Cam)

 

Camera Architecture & Duo Cam Video & Extreme Power Saving Mode
Comments Locked

222 Comments

View All Comments

  • althaz - Wednesday, March 26, 2014 - link

    Why are the OLED screens not listed in the brightness for black and contrast tables? Yes, they have zero black levels and infinite contrast, but that's the level LCDs should be aspiring to and it's worth comparing them, IMO.

    There's a reason most people go for OLED screens (despite almost every reviewer preferring LCDs), they have MUCH better contrast. IMO this is a serious flaw of all LCD phones and should be mentioned. Sure, the tradeoffs may well be worth the relatively poor contrast, but that's something each user has to decide for themselves.
  • Braumin - Wednesday, March 26, 2014 - link

    There's not enough horizontal pixels to graph infinity.
  • evonitzer - Saturday, March 29, 2014 - link

    True, but it still seems like there should be some mention of that, or just putting them at the top a bit above the leader. When I was looking at HDTV's some years ago, black levels were of very high priority, hence me getting a plasma. To think we would have perfect blacks on phones and people would shrug just a few short years later ...
  • hangfirew8 - Wednesday, March 26, 2014 - link

    Great review, not enough reason to trade-up from my M7, especially given the OIS video difference.

    I'll repeat my request to review the matching car dock and car mode/launcher with each review. With so many places passing hands-off laws for drivers, this mode is more and more important, and is obviously not given enough attention by either OEM's or reviewers.

    Besides car dock mode, I really think a BT test such be conducted against, say, a Pioneer, a Kenwood and some select factory auto receivers. Complaints about niggling sync or lag or other bugs are common, but if no one is reviewing these combinations systematically, the manufacturers of both the phones and the car audio systems are not going to do anything about it.

    Think of it this way- many phones spend most of their screen-on operating time docked in a car dock or holder of some kind, and BT synced with the receiver. It is the second most common operating usage after sitting beside us on our desk or armchair.
  • SorryItsAThrowAway - Wednesday, March 26, 2014 - link

    I disagree that Sense UI is the best experience "bar none." If you've only compared it to Samsung or LG - then, sure. That would be an obviously true statement. However other manufacturers have arguably far more usable designs. If we stay with the Western audience as this article so clearly does then the best examples would be Motorola recently and even more especially Sony.

    Even if these still somehow came up short to Sense (debatable) they are certainly not so far away from the strong wording this review claims.
  • dylan522p - Wednesday, March 26, 2014 - link

    Moto isn't classified as a skin and Sony adds VERY VERY little features and a lot of pointless changes.
  • SorryItsAThrowAway - Wednesday, March 26, 2014 - link

    I disagree. If it isn't stock then it's a skin. Moto is very minimal. Sony as well but they also have an entire theme system to change things like the appearance of the on-screen interface buttons. So, Sony can go either way with that in mind (good or bad).
  • rxzlmn - Wednesday, March 26, 2014 - link

    That's wrong. Sony keeps the main UI elements all the same, but does add many little helpful things. But they don't change how things behave and look in terms of usability compared to stock (different from HTC, LG or Samsung).
  • CoryWeston101 - Monday, March 31, 2014 - link

    No. Sense is the best user experience and best UI. No other Android OEM comes close. Motorola's UI is just stock with some added stuff. And Sony has a good UI but it isn't better than Sense.
  • icwhatudidthere - Wednesday, March 26, 2014 - link

    Actually that photo of you in the bar is how normal bokeh would look as well. Everything in your plane should be in focus, in this case, the second sensor is doing its job correctly and rendering a more realistic bokeh instead of a software-only solution.

    There is one artifact though on the wall paneling close to the table. I guess they're not actually assigning depth values to individual pixels but grids instead for faster processing.

Log in

Don't have an account? Sign up now