Battery Life

For many years the limited battery life of smartphones has been the most painful part of their experience. It's never fun to have your smartphone die during the middle of the day, and many users long for the days where their flip phone could last for days or even weeks on a single charge.

Although the battery life of smartphones is still a long way off from the simpler mobile phones of the past, it has improved significantly over devices like the original iPhone which were the first generation of what could be called modern smartphones. Improvements in software optimization and the power consumption of components has improved battery life, and the increasing size of devices has allowed for larger batteries to be used. However, that isn't to say that the battery life of a device can be determined solely by its battery capacity. The total power draw of all the components in a smartphone can vary dramatically from device to device. A great example is the Nexus 6 and the Galaxy Note 4, which have nearly identical specifications on paper but completely different battery life.

While many battery tests often standardize at some percentage on the Android brightness slider such as 50%, that percentage can correspond to various different luminance values. To ensure that the true brightness of each device is equal, all devices are calibrated to a brightness of 200 nits. As usual, we begin with our web browsing battery tests which are more display bound than our fixed CPU and GPU load tests. This test loads web pages on a fixed interval, which gives both the SoC and modem a period of idle time between each page load. This ensures that the test does not penalize certain SoCs for being faster by causing them to do more work.

Web Browsing Battery Life (WiFi)

Web Browsing Battery Life (4G LTE)

After rounding off a few seconds, the ZenFone 2 gets 7.37 hours in our WiFi web browsing test, and drops by an hour to 6.37 hours when using LTE on band 4. Both of these results are lower than one would expect from the ZenFone 2's fairly large 11.4Wh battery. However, I think there's a reasonable explanation for the results, and it also answers some questions that may have arisen after reading the previous page.

I had two big questions after testing the ZenFone 2's display. The first was "Why does ASUS employ the use of such heavy CABC and dynamic contrast?" The second was "Why does ASUS limit the maximum brightness to around 80% of what the display is capable of?" I think these battery results answer both of them, and ASUS provided some additional information that supports it as well. The display and LED backlight on the ZenFone 2 is likely not as efficient as those on some other smartphones. In our web browsing test the display is by far the largest consumer of power, and yet the OnePlus One with the same display size and resolution achieves a 77% longer run time with only 3% more battery capacity. Even with differences in SoC power usage, the only component such a large gap can be attributed to is the display.

In addition to the likely issues with display power usage, the ZenFone 2 also does not support Panel Self Refresh (PSR), which means that there's additional SoC and display bus power usage compared to smartphones that do support PSR. All of these factors lead to what is ultimately an underwhelming result for a 5.5" device with an 11.4Wh battery. The notable gap between the results on LTE and WiFi also would suggest that XMM7262 isn't quite at the level of Qualcomm's most recent parts when it comes to RF system power, but we would need to do a lot more investigation to draw any solid conclusions.

Our next battery test is PCMark's battery tests. PCMark's battery test is actually one of my favorite battery benchmarks because it mixes together various different tasks, stresses different parts of the hardware, and in general gives a very good idea of how battery life will be when the user is doing many things with their smartphone.

PCMark - Work Battery Life

In PCMark's battery life test we see that the ZenFone 2 actually lasts slightly longer than some of our recent flagship devices. This is a favorable result for ASUS, because it shows that in scenarios with mixed usage and varying display APLs the ZenFone 2 doesn't fall behind the competition in addition to sustaining high performance from run to run. However, it should be noted that in those lower APL scenarios the ZenFone 2 is dropping below 200nits of brightness for white in order to reduce display power, which means that the display is actually dimmer than the competition to achieve the same level of battery life in this test. PCMark's temperature monitoring in their graph doesn't seem to have worked on the ZenFone 2. While Canada can get pretty cold, it's not currently that cold.

While our web browsing test is mostly display-bound, and PCMark is a more balanced workload, the next two battery tests tend to be SoC-bound. These tests tend to reveal which OEMs handle thermal throttling more gracefully than others. The first test is GFXBench 3.0's battery test, which puts a strong stress on a device's GPU, similar to playing a visually intensive 3D game.

GFXBench 3.0 Battery Life

GFXBench 3.0 Performance Degradation

There are two sides of the story with the GFXBench battery test. While it's good to achieve a long battery life, it's not very useful if your frame rate during the test would have made for an unplayable game in the situation where the user is actually playing a game instead of running a benchmark. Devices like the iPhone 6 don't last as long as other devices, but show essentially no GPU throttling and retain a high frame rate even by the last run of the test.

In the case of the ZenFone 2, we see that it lasts exactly as long as the HTC One (M9). Last run GPU performance is noticeably slower though. Overall I would say the ZenFone 2's performance in this test is fairly good. Its battery life is in range of devices like the LG G3 and the Nexus 6, but it has higher sustained performance than either of them. ASUS and Intel also handle thermal throttling very well, with the frame rate dropping down from around 30 to 22 over the course of the first 20 minutes, and remaining there for the remaining two hours of the test.

BaseMark OS II Battery Life

BaseMark OS II Battery Score

Our final test is BaseMark OS II's battery life test. This test puts a sustained load on the CPU, and the battery score is calculated based on the average amount of battery percentage consumed for each minute the test runs, as well as the level of CPU usage during the duration of the test. In both results we see that the ZenFone 2 does well for a device with its speed. Both the battery life result and battery score result are very close to those of the LG G3.

Overall the battery situation on the ZenFone 2 is somewhat mixed. Web browsing is definitely the heaviest scenario for power usage due to the display, but the ZenFone 2 is able to last fairly long in more mixed workloads. The downside that isn't reflected in these results is that the ZenFone 2 is lowering its brightness during tests that have lower display APLs, which means that while it may last as long as a competing device, if you were actually doing those tasks yourself you would be dealing with a dimmer display than the competition. Ultimately I think ASUS's solution of display dimming is the best option they could have chosen, as the alternative is basically to just have short battery life in every circumstance.

Charge Time

Something that is becoming a common feature for modern smartphones is the ability to charge at a rate faster than the standard 5V 1A spec that devices and charging blocks used in the past. The most well known standards for achieving this are Qualcomm's Quick Charge and Quick Charge 2.0.specifications. Fast charging is essentially a trade off between battery longevity and charge times, and it really relies on the assumption that smartphones are replaced every two years which is less time than any user would notice possible adverse effects. This rapid replacement of devices is somewhat worrisome, but that's a topic for another time.

The $199 model of the ZenFone 2 ships with a standard charging block, while the $299 model ships with ASUS's 18W BoostMaster charger. While ASUS is marketing their charger using their own branding, I have confirmed myself that the ZenFone 2 also supports fast charging using Qualcomm QC 2.0 certified charging blocks, such as the one that shipped with the Nexus 6. This is good news for anyone who buys the $199 model and can't get ASUS's charging block separately.

Charge Time

ASUS's 18W charger supplies power at 9 volts and 2 amps. This is the fastest charging block I have in my possession, and it charges the ZenFone 2 extremely quickly. While it's still beaten by the S6 Edge, the gap is very small, and the ZenFone 2's battery is around 27% larger. While battery life on the ZenFone 2 may not always be the best, buyers may find some comfort in knowing that when it does die they'll be able to get it up and running in a very short period of time.

Display System Performance


View All Comments

  • der - Tuesday, May 26, 2015 - link

    Sweet review mates. Y'all the best! Reply
  • Daniel Egger - Tuesday, May 26, 2015 - link

    Two things:
    1) The x86 problems are very real; about any serious Android application contains native code for performance reasons, the rest are very non-demanding gimmicks or simple games. There're still plenty of application which do not even attempt to run on x86 which can be easily seen by e.g. checking the F-Droid repository with the app. And of those which do run quite a few simply don't work correctly; I've found quite a few of those in the Humble Bundles. My suspicion is that the developers do compile them for x86 but do not really test them on that platform...
    2) Those Silvermont cores do have decent performance but I've yet to see a single implementation where battery life doesn't suck. One discovery I've made is that those devices are very reluctant to go into deep sleep, even with some tweaking they'll usually stay on the lowest possible frequency most of the time. Could be that the software is not quite ready to properly handle those Intel cores or they simply suck...
  • MikhailT - Tuesday, May 26, 2015 - link

    Both are software issues. Google doesn't have any incentives to stick with ARM only, they'd want to work with Intel to fix these issues.

    At my work, we had an issue where our app would crash on Intel devices, it took us a few weeks to figure out that it was a low-level bug in Android. We filed a bug report but no news if Google or Intel will fix it. We managed to work around it but it was difficult and took a lot of time.

    The latest rumors is that Android M is supposed to work on the battery issues. Hopefully, that includes optimization for Intel SoCs.
  • kpb321 - Tuesday, May 26, 2015 - link

    I was surprised that the review seemed to skip this entirely. It is certainly an issue when dealing with x86 android phones. Theoretically any app that doesn't include NDK "should" work fine on x86. My experience with Android phones/tablets was that I don't ever recall installing a single app that had NDK in the permissions list so it didn't seem like it was very common to me. On the other hand I've never actually had an intel tablet to actually see how good or bad it was. Reply
  • Brandon Chester - Tuesday, May 26, 2015 - link

    I also reviewed the Venue 8, and like I said in both this review and that review, I have never found a single app that doesn't work because the SoC is x86. A lot of people like to say that there are lots of apps that have issues, but they never seem to name any so there's no way for me to actually confirm that. If people do know of some problematic apps please let me know via email or Twitter so I can take a look. Reply
  • Muyoso - Tuesday, May 26, 2015 - link

    An app called Photo direct that I use for work crashes instantly when launched. Reply
  • rocketbuddha - Wednesday, May 27, 2015 - link

    I bought a Dell Venue 8 with KitKat
    and found that it was the POS.
    Dunno if it was 1GB RAM that came with it, but it was hanging even while opening tabs in chrome/stock browser.

    With Lollipop, Google officially has both a ARM as well as x86 version it tests and releases. Pre-lollipop it was Intel who customized Android to work with its Atom processors.
  • Maleficum - Saturday, May 30, 2015 - link

    Brandon, you'd be really surprised to know that most apps in the top charts are using NDK.

    Google claims that 85% apps are written in Java. I'm not saying it's a lie, but it is far from realistic since most apps in the top charts - apps most people use most of their time - are NDK based.

    Even more surprising would be the fact that roughly half of these apps contain ARM binaries only, thus forced to run via binary translation that results in a performance reduction of roughly 70% while the power consupmtion doubles.

    In that sense, your article is misleading IMHO, simply repeating Google's claims.

    I think it's clear why so many apps are NDK based: Java isn't simply the right language for computationally intensive apps, and primitive apps written in Java cannot make it into the top charts.

    And app developers aren't interested much in supporting x86 natively considering the tiny market share. No one can blame them for neglecting x86.

    That's the reason why I'd never buy nor recommend x86 Android phones, and Intel having difficulties getting foothold in mobile segment.

    I think it would be worth an investigation and probably a separate article.
  • Thunderc8 - Saturday, May 30, 2015 - link

    I have installed all known apps and then some and all working perfect and super fast. If what you say is true then Intel CPU is a beast since it looses so much performance and at the same time is so Damn fast. Reply
  • coolied - Wednesday, May 27, 2015 - link

    NDK wouldn't be in the permissions list, it simply means the app was coded in C++ and not JAVA. Unfortunately, most apps you would WANT to run and run WELL are written in C++ aka most 3D games. Reply

Log in

Don't have an account? Sign up now