Still Image Performance

After discussing the general architecture and the software experience of the camera on the ZenFone 2, we're ready to take a look at how it actually performs when taking photos in the real world. Since the world is very diverse, a camera needs to be able to adapt to various conditions. Lighting may not always be optimal, and if a scene has a significant amount of movement then driving long shutter speeds with the help of OIS in order to keep ISO down no longer becomes a viable option.

The first test I'm doing is an outdoor test during the day. There's ample lighting from the sun, and the scene has a variety of objects and surfaces that can be examined to see how well detail is resolved by the ZenFone 2 in optimal shooting conditions.

Looking at the overall image, it's clear to me that this sensor is capable of taking good photos. Unfortunately, there are a lot of issues related to the processing that ASUS is doing that really bring down the image quality. Not limited to this scene is the camera's tendency to oversaturate colors, as well as some very heavy sharpening that causes white and black borders on the edges of objects. Despite being taken at the base ISO of 50 and a shutter speed of 1/1135 seconds, there's still noise in the blue parts of the sky, which doesn't happen on any of the other devices in the comparison.

ZenFone 2 on the left, Nexus 6 on the right

Above is a 100% crop of the bicycle in the distance from the ZenFone 2 and Nexus 6 photos. I chose the Nexus 6 to compare to because it has the same resolution and pixel size. As you can see, in the ZenFone 2 photo there's a black border around the frame of the bike as well as the rings of the bike rack. There's also more noise on the concrete road in the background, and just an overall lower level of detail in areas like the grass and the second bike rack further in the background.

Some of the issues that I've mentioned are the result of the "Optimization" setting in the camera menu. This setting is set to auto by default, and it changes the amount of sharpening and noise reduction done during processing, as well as other aspects like contrast and color saturation. Turning this setting off makes some noticeable changes to the appearance of images, but not all of them are positive.


Above you can change between a 100% crop of an image taken with ASUS's optimization set to auto, and one where it is set to off. It's clear that when optimization is turned off the issues with heavy noise and dark edges caused by sharpening are eliminated. However, the image is also considerably softer, and no matter how hard I tried I could not get the leaves and flowers to appear as sharp and in focus when optimization was off as when it was set to auto. ASUS also gives you the option to manually set these values. While I'm sure you could spend your time tweaking them to get an optimal balance, that completely defeats the point having a camera mode where everything is automatic. Ultimately ASUS has to improve their algorithms and processing for shooting in auto mode.

The next test uses the same seen as the first test, but it is done at night where lighting is scarce and only provided by a handful of lamps on the road and on the sides of some of the buildings. Most smartphones now produce usable images with good lighting, and so low light performance has really become the area where a device needs to excel in order to be considered among the best smartphone cameras.

Relative to the other smartphones I'm comparing it to, the ZenFone 2's photo quality at night actually ends up being pretty good. Both it and the two Nexus devices didn't expose for the sky very well, but the ZenFone 2 is much brighter in the rest of the scene. It also has more detail on the pavement than the Nexus 6, but it also has more noise throughout the image. I think it actually outperformed the iPhone 5s overall as well, with a much more accurate white balance, and more detail on fine objects such as the bicycle and bike racks in the distance.

The black borders caused by ASUS's sharpening during processing are definitely still visible in areas where objects are in the light, but it's much less distracting when the scene is already very dark in general. Overall, I would actually rank the ZenFone 2 somewhere between the Nexus 6 and Galaxy S6 Edge in this scene, with the S6 Edge being the overall best of the photos despite being somewhat overexposed.

Special Camera Modes

In addition to the standard auto and manual modes, ASUS offers a variety of camera modes for special circumstances. There are ones like beautification mode and HDR, which I don't really care for that much. I'm actually shocked that there's no auto HDR in the automatic mode to begin with. However, there are two camera modes that I'd like to talk about because of how prominent they are in ASUS's marketing for the ZenFone 2 and its "PixelMaster" camera.

The first mode that I'd like to examine is the Super Resolution mode. This camera mode merges together the details of four slightly shifted images to produce a much higher resolution image. ASUS claims the images are up to 52MP in resolution, which is four times the native resolution of the sensor. In practice, my image was slightly over 50MP which is pretty close to what ASUS claimed.

Because of the immense size of the 50MP photo I was unable to include it in a gallery. You can view the super resolution photo here, and the normal resolution photo here. I recommend taking a look at them scaled to a reasonable size and seeing if you can notice any notable differences in sharpness.

Upscaled Normal Resolution on the left, Super Resolution on the right

The above photos compare a crop from the normal resolution photo taken using the auto mode and the photo from the Super Resolution mode. I've enlarged the normal resolution photo to 2x in order to make the crops the same size. While this has an impact on the quality of the normal photo, the point I'm trying to make is preserved because there's really no visible improvement in sharpness from using the Super Resolution mode that I can see even after blowing up the original image. There's definitely a visible reduction in noise throughout the frame, but it's not noise that you'll be able to see during normal viewing anyway, and a denoising filter in a photo editing application could achieve a similar effect. In the end I don't really think that the Super Resolution mode is very useful.

The second camera mode that I wanted to talk about is the low light mode. Some users may be familiar with this type of mode from other smartphones and from digital cameras. Essentially what the camera is doing in the low light mode is merging adjacent pixels together in order to combine their luminances. This is known as pixel binning, and at the sensor level this is done by combining charges on the CCD/CMOS sensor. For our purposes, it's easier to just discuss the end product which is a significantly improved signal to noise ratio (SNR) at the expense of spatial resolution. A commonly used form of pixel binning in cameras is 2x2 binning, where the light of four pixels is essentially combined into one pixel. This would confirm ASUS's claimed 400% increase in sensitivity when using the low light mode.

The downside is, of course, the lower spatial resolution. The use of 2x2 pixel binning and EIS during low light mode means that the resolution of the images is limited to 3MP. This means that it's only worth using this mode in circumstances where it's dark enough that you won't be able to see the subject of the photo properly in the normal camera mode. I've taken a couple of comparison images to see how well this feature works.


I chose this first scene because it doesn't have any lighting within the frame. I'll explain why that is in a moment, but for now lets discuss what improvements the low light mode makes in this scene. The most obvious improvement is that the scene is much brighter. The original photo is so dark that you can't even tell there are trees and power lines in the background. The bins are also very hard to make out, and only show up because of their white labels. You would also never know that on the right side of the frame there is part of another car being shown. In the image taken using the low light mode, all of these parts of the image are clearly visible and recognizable.

The obvious downside to the low light image is a loss in resolution. While the auto mode image is very dark, there's clearly more detail on the ground, as well as on the features of the cars that are bright enough to be seen such as the tires of the silver car on the left side, and the license plate of the car on the right. In the low light mode there's a lot of smearing and blur in those areas, and the noise throughout the image is not as fine grained.


In this second scene I've deliberately chosen an area where there's a light source visible in the scene. This puts less of a strain on the auto mode so we can see how low light mode improves over auto mode photos that actually aren't that bad. It also highlights some of the limitations of pixel binning.

In this case, the low light mode is again much brighter than the auto mode photo. However, while the low light mode pulls parts of the scene like the trees and the sky out of the shadows, the difference in quality between it and the auto mode photo is very noticeable and makes it difficult to choose which of the shots has more redeeming qualities. The blurring throughout the low light image scrubs away essentially all of the details. The cars are not as sharp, and the details of the bricks on the house are completely lost. The inclusion of a light source in the scene presents another problem. Since the camera is basically exposing for the darkest part of the scene, the light is completely over exposed and distracts from the other parts of the photo.

In this case, it's hard to say that the low light mode photo is certainly the better one, as it's not as hard to see the objects in the photo as it was in the first test case. You trade much of the detail to obtain a better exposure, and while that may still give the low light mode the edge here, in any case where there's even a bit more lighting I would probably opt for the normal auto mode or manual mode. In general, my recommendation would be to only use the low light mode when it's so dark that you won't be able to see what the subject of the photo even is with the normal camera modes.

My overall verdict on the ZenFone 2's camera quality is somewhat mixed. It actually did fairly well in the night time test, but during the day the image quality was negatively impacted by ASUS's processing. The sharpening causes white and black halos around objects, the images had a much higher level of blurriness than I would expect from a shot with a sub 1ms shutter speed, and at base ISO there was visible noise in the sky that I can't even begin to explain. I would love if some of these problems could be fixed in a potential software update, because I think that they are going to show up in the majority of circumstances where users will be taking photos. At present, these processing issues really cripple an aspect of the ZenFone 2 that I believe could be optimized to perform much better than it currently does.

Camera Architecture and UX Video Performance
Comments Locked

147 Comments

View All Comments

  • loimlo - Saturday, May 30, 2015 - link

    My mom has been using 1st gen, Zenfone 5 for 10 months. ASUS SW update literally broke app compatibility several times during this period. At some time, my mom couldn't disconnect a phone call due to a nasty SW bug! I'd to lock the screen and unlock it again to disconnect. It's not the end of world, but still an alarming for potential 2nd gen, Zenfone 2 buyers. Fantastic HW value, but subpar SW update quality.
  • ketacdx - Thursday, May 28, 2015 - link

    I've been using the TW model since long before the NA launch and there have been a lot of software Updates and ZenUI updates but its not like a beta testing thing. They are fixing issues most manufacturers don't bother with. Little things that they are truly optimizing that a normal person would never notice. Aside from my worry about the quality of the gorilla glass when dropped (think nexus 4 outcomes), the QC elsewhere on this things feels prime. I have no concerns.
  • Dawgmatix - Wednesday, May 27, 2015 - link

    Are there any phones with arm processors that use the same display? What does their battery life look like? How can we be sure its not the cpu or gpu that is eating up the battery?
  • Brandon Chester - Wednesday, May 27, 2015 - link

    Because the SoC power usage is small relative to display power usage on any device during the browser test, and the ZenFone 2 performs worst of all in that test. In tests where the SoC has a greater impact and the display has a lesser one it actually achieves a battery life closer to that of other devices.
  • YOUCANNOTDENY - Wednesday, May 27, 2015 - link

    Hello,

    I had a few observations/questions. I currently own the $199 version of the Zenfone 2, and have not noticed any dynamic contrast or CABC during my time with the device. This may be because I cannot recognize it, but I'm pretty sure something similar is used in my Dell XPS 13 Ultrabook with Intel's HD Graphics drivers (I promptly disabled the dynamic contrast shifts in Graphics Settings). I have, however, turned off "Smart Saving" in Power Management on the Zenfone 2, so that may be what is causing the difference. I am also on the latest 2.17.40.12 software version, which may have introduced changes.

    One other thing, I noticed that in the "Splendid" app, owners can change the color temperature of the screen. I immediately noticed the overly cold white point of the screen when I first powered on the device, so I looked to the Splendid app to change the color temperature. I am currently on "Reading Mode" with default settings on the slider, which makes the screen more bearable to my eyes, but I am still unsure of the absolute color accuracy. If at all convenient, would it be possible to rerun screen accuracy measurements in the various color temperature modes offered in the included "Splendid" application? Perhaps, we may be able to find a setting that makes the most of the included panel and does it justice.

    Thank you!
  • Brandon Chester - Wednesday, May 27, 2015 - link

    The CABC is there on both models. I made sure that ASUS's power saving features were disabled before I did my testing.

    While I could try and adjust vaguely labelled sliders in the Splendid app to fix the display's white point, the gamma and greyscale are not possible to fix because of the CABC. Because of this, there's no point in trying to fix the display.
  • Quad5Ny - Wednesday, May 27, 2015 - link

    @Brandon Chester ASUS stock theme looks like a copy of Solstice by John Bussell (@myeverydayghost) who based his theme on Apple's iOS 7. -- http://modmyi.com/info/solstice.php, http://cydia.saurik.com/package/com.modmyi.solstic...
  • UtilityMax - Wednesday, May 27, 2015 - link

    The device is not without flaws, but the $200 model seems like a good value. However, the $200 model is a bit dubious proposition considering how close it is to the OnePlus One.
  • Sammaul - Thursday, May 28, 2015 - link

    Have the $300 model, and have used a OnePlus...frankly in real world usage it's kind of a wash. OnePlus has better battery life, camera, and speakers. The Zenfone is absolutely quicker and smoother, even with none of the bloat uninstalled. That 2 channel ram in it does wonders compared to other phones I have used.
  • MoJo JoJo - Wednesday, May 27, 2015 - link

    I have been using ZenFone 5 for almost 7-8 months. There's only one thing that I don't like about ASUS is that software and software updates.

    Software:
    ASUS ZenUI is buggy as hell. They provide some update to improve one area and ruins the other. They just cannot provide a single, practically stable, update/ROM. It irritates me a lot. Even now most of the ZenFone 2 users are facing so many issues of Shitty Battery" "Force Stop" "Worse Camera" "Heating under normal use (45 deg.C)

    Software Update:
    Like I said I have been using ZenFone 5 for 7 months, it seems like ASUS is very slow in updating their devices. First, ASUS launched the 1st gen. ZenFone series in July 2014 (in my country) with Jelly Bean 4.3 instead of KitKat 4.4
    After almost 2 months of waiting (Aug-September) they released the KitKat update. That update messed up everything, literally everything. It took another 1-2 updates for ASUS to remove the bugs.
    In November 2014 they announced that whole ZenFone series will get the Lollipop update in April 2014. It's almost the starting of June but no ZenFone (intel Version) has got lollipop yet! They are just delaying the update to sort out the bugs. But no use. In May Google has rejected their update during verification. So, still waiting for update, which will be 5.0 not even 5.0.2 (Though they have promissed to give 5.1 update, but it will take ages to come).

    Moral of the Story:
    No doubt, ASUS is great in providing high end specifications. But it ends there itself. The whole experience gets ruined by the software.

Log in

Don't have an account? Sign up now