Probably one of the biggest changes with the HTC One series is emphasis on camera quality. It’s quickly becoming one of the most important axes of both improvement and comparison for handset vendors, and HTC has taken a rather unique approach with the One. So what is that unique approach exactly? It’s the inclusion of discrete ISP which HTC calls ImageChip.

Moving to a discrete ISP to tackle some of the image pipeline makes sense for a number of reasons. First, it makes optimizing for image quality less of a moving target if you’re a handset vendor. Each SoC has different ISP, and each combination of both ISP and camera sensor/module needs to be tweaked for optimal image quality. The result is a lot of optimization work that takes time if you’re deploying multiple platforms with silicon from different vendors. Moving to one single controlled platform in conjunction with one single module and sensor makes it possible to really squeeze everything out of that combination, and in addition spend more time characterizing the system. The other axis ties into the One branding - each One series smartphone should actually perform the same, thanks to this unified combination of ISP and rear facing camera. So far, this applies to all of the One S and One X(L) variants.

HTC’s ImageChip is responsible for most of the things that would traditionally be done on the SoC ISP. 3A (Autofocus, Auto white balance, and Autoexposure), lens correction (geometric and chromatic correction), noise reduction, best shot selection, continuous auto focus, controlling gains on the CMOS sensor, LED flash level decision, region of interest identification (augmented with face detection) and so on. This is all stuff you can verify yourself by taking apart some of the ISP related files - curiously enough internally ImageChip is actually referred to as “rawchip.” This is also the hardware responsible for enabling HTC’s extremely fast image continuous capture and frame grabbing during video capture (HTC Video Pic). It’s somewhat analogous to what Google and TI did with the OMAP4460 on the Galaxy Nexus, except discrete and with a much more ambitious focus.

The rest of HTC’s efforts involve both optics and sensor. The optical system consists of an F/2.0 3.6mm system (28mm effective). HTC has at present the fastest aperture on a smartphone camera that I’m aware of, surpassing some of its own F/2.2 systems and the F/2.4 systems on other vendors camera modules. Getting a larger aperture is no small feat, as aberrations quickly blow up with F/#. I’m impressed with how well HTC has kept these at bay with the One system. The HTC One X on AT&T (and the One X international) use the same front and rear facing cameras, and we’ve actually seen these modules before. The rear facing CMOS is a Samsung S5K3H2YX which Vivek spotted in the MyTouch 4G Slide. This is an 8 MP 1/3.2“ format BSI sensor with 1.4µm square pixels. The front facing camera is a 1.3 MP S5K6A1GX 1/6” format FSI sensor with 1.75µm pixels. You can check for yourself by catting “/sys/android_camera/sensor” on the device.

The next component of HTC’s camera emphasis is its new camera UI, which is excellent. There’s properly implemented tap to focus/expose, and in addition the camera preview appears to be close to native resolution. There are settings and configuration options if you want them, including ISO, white balance, and manual exposure. My only gripe is that HTC continues to ship with the camera set to 16:9 aspect ratio instead of 4:3 and taking full advantage of the sensor.

There are two other tabs - some camera scenes settings, and filters. Tapping on the scenes option lets you switch into HDR mode, panorama shooting, and a few other useful presets. HTC’s HDR mode is the first I’ve seen which works just like the HDR mode on the iPhone by combining 3 (or more?) exposures from a bracket capture, quickly. There are a bunch of applications which do this through the camera API on Android, but the result is too much time between frames and more chance of shift. I captured a few HDRs using the in-camera option which looks great. The other is the blue filter button which pops you into some vaguely Instagram-like options, including vignette, a depth of field filter, and others.

There’s no dedicated video or still mode, instead to start taking video or images you just tap the appropriate button. Still image capture is basically instantaneous, and just like the Galaxy Nexus there’s continuous auto focus running, alternatively you can tap to focus on a specific region before capture. The other feature is what I mentioned briefly before - continuous capture (by holding down the button) and the ability to select from what the ISP determines is the best of those captures, or save the whole series.


An AT&T eNodeB - Captured with the HTC One X (AT&T) - How meta...

To get to the bottom of still image quality, we turned to our regular set of evaluation tools, consisting of both photos taken in a fixed smartphone lightbox test scene with the lights on and off, with test charts (GMB color checker card, ISO12233, and distortion), and at our smartphone bench locations.

I’m very impressed with HTC’s One X/S series camera, to say that HTC has made massive improvements is an understatement. The One X has some of the best (if not the best) low light performance I have seen from a smartphone, no doubt in thanks to that fast F/2.0 aperture and noise reduction they’re doing on their ISP. HTC’s optics are very controlled with minimal distortion and remain nice and sharp across the field, which is no small feat. The lights on lightbox sample has great color saturation, sharpness, and dynamic range. In the dark with the flash on, their ability to control LED brightness also helps avoid the washed out flash look that I see from other smartphones as well.

The other part is that HTC’s optical system now has a low enough F/# to overcome the small 1.4µm pixels and deliver shallow enough depth of field to actually show some nice, visible bokeh. It isn’t perfect, but it’s definitely there.

I think with the HTC One series it’s time to add HTC to the short list (Nokia, Apple) of smartphone vendors doing more than just integrating a module into their smartphone platforms.

Video

Video is the other part of the camera puzzle, and here ultimately HTC has to touch the SoC for video encode, which isn’t done on ImageChip. At that point there’s going to be some differences between platforms, but at the high end (everything but the One V) 1080p30 video encode is in order.

In the case of the One X on AT&T, that means 1080p30 video encoded at 10 Mbps H.264 baseline with one reference frame. That’s unfortunate since I know that MSM8960’s encode blocks can do more, but I’ve seen similar for a while now from other vendors. Audio is 128kbps stereo AAC. The One X also can do 60 fps video capture at the rather odd 768x432 resolution, which plays back at around 24fps. I’m still waiting for a platform that can do 720p60 properly, unfortunately. Front facing video is 5 Mbps 720p30 also at H.264 baseline.

I have no complaints with video capture quality other than that I feel quality would get a bump from either higher bitrate or better encode. That said there isn’t much distracting macroblocking or other annoying artifacts. HTC also gives you control over whether you want to stabilize video or not in the menus.

Rear 1080p Sample
 
Front 720p Sample
 
Rear Slow Motion Sample

As usual I’ve uploaded the videos to YouTube, and to the AT servers for you to download in a zip without YouTube’s transcode.

Performance Display - Infinity Screen
POST A COMMENT

137 Comments

View All Comments

  • frostyfiredude - Tuesday, May 01, 2012 - link

    If there is one difference that really stood out between the International and ATT versions of the One X, it's the battery life. For all the talking nVidia did about Tegra3 allowing world beating battery life, it really got served by the S4 in that regard.

    In the fall I really hope HTC makes a One X like phone with WP8 on it, if I'm not feeling cheap I think I'll buy one.
    Reply
  • ImSpartacus - Tuesday, May 01, 2012 - link

    Yeah, that's really the most important thing for me. I'm glad Anandtech puts it earlier in the reviews. Reply
  • Chloiber - Wednesday, May 02, 2012 - link

    It's true. I'm currently owning a One X (international). I'm okay with the battery life (it's better than my previously HTC Desire). But as Brian has mentioned, software updates are on the way. The second update has been released yesterday. The updates are coming out nearly weekly! The improvements are huge in many aspects. The last update (released yesterday in Europe for unbranded devices) finally enabled 2D GPU Acceleration. That's right: 2D GPU Acceleration wasn't working properly before. It couldn't even be forced in the dev settings.

    I really hope they can improve the device even more, and I'm pretty confident they will. To be perfectly honest, I would have preferred the S4 version of the One X. Nvidia still seems to have some problems with the T3 - again, I'm confident that the device's performance and battery life will improve massively over the next couple of months, but S4 seems to be the safer bet.
    Reply
  • pikahatonjon - Tuesday, May 01, 2012 - link

    i know its offtopic, however, how come it seems like the Droid Razr performs like 40% better than the galaxy nexus 58.7 fps vs 33.1 when they both have the same SoC? was there some error in the test Reply
  • frostyfiredude - Tuesday, May 01, 2012 - link

    Higher resolution display on the Nexus would be the cause of most if not all of the difference. 960x540 for the RAZR v 1280x720 for the Nexus Reply
  • PyroHoltz - Wednesday, May 02, 2012 - link

    I really wish Anandtech would normalize the graphics benchmarks to FPS/megapixel of screen resolution.

    Or, implement something that will take the fluctuations in native resolution, out of the equation a bit.
    Reply
  • Goty - Wednesday, May 02, 2012 - link

    Just look at the "offscreen" numbers, those are all rendered at the same resolution regardless of handset. Reply
  • ChronoReverse - Wednesday, May 02, 2012 - link

    The Offscreen Test is a seriously flawed one. It's clear that the act of rendering to the screen has a different penalty for different GPU's.

    Since you have to render in actual 3D applications, this means that the Offscreen test is worse than useless since it's _misleading_.

    You can't even say it's a VSync issue because in this very article, you have the GLBenchmark test at 720P where the results for both the Global and ATT OneX phones are both significantly below 59-60FPS.
    Reply
  • Goty - Wednesday, May 02, 2012 - link

    Writing of the framebuffer to the screen is the least part of what each GPU has to do and certainly has less of an impact that differing resolutions between screens; I highly doubt that writing out the framebuffer is even that different between different architectures. Reply
  • metafor - Thursday, May 03, 2012 - link

    It's very much in line with the V-Sync results we've seen with the MDP and other devices that allow you to turn V-Sync off.

    The tests with the Qualcomm MDP show exactly this kind of difference with V-Sync turned on and off, even if the resulting average doesn't come close to 60fps.

    Why? Because framerate can vary by a lot within the running of the benchmark. Simple sequences can burst up to the 100's of frames per second. That will throw off the average by a lot.
    Reply

Log in

Don't have an account? Sign up now