Battery Life

It goes without saying that battery life is one of the most important aspects of a mobile device. After all, a mobile device isn’t really mobile if it can only be used for an hour before running out of battery. In order to test this, we turn to our standard suite of battery life tests, which include our web browser battery life test, along with some compute-bound benchmarks to characterize battery life across various use cases.

However, as the Nexus 9 introduces such a unique CPU architecture, I felt that it was necessary to try and adequately capture the full extent of battery life. To this end, I’ve introduced a new test that is really quite simple but important, as we can start to separate display power from everything else since it can often be the single largest consumer of power in a test. In order to do this, everything that could run during a test is disabled, and the device is placed in airplane mode with the display at 200 nits. A white image is displayed on the screen from a full charge until the device shuts down.

White Screen Battery Life

Interestingly enough, the display runtime on the Nexus 9 is about as good as it gets when compared to other devices for which we have data. I suspect we’re looking at the direct result of the large battery combined with an efficient display, as the Nexus 9 can last as long as 15 hours in this test compared to the iPad Air 2’s 10 hours.

Web Browsing Battery Life (WiFi)

Unfortunately, the massive lead that we saw with the pure display test is significantly eroded in our web browser test. Our web test is primarily focused upon CPU, connectivity, and display efficiency. Seeing as how the Nexus 9’s display is far ahead of the iPad Air 2 and connectivity should be broadly similar in power efficiency, it seems that all of the efficiency gains from the display have gone into powering the Denver CPUs. It’s likely that process has a significant effect on this, so the more valid comparison is between SHIELD Tablet and the Nexus 9. At any rate, the Nexus 9 does manage to deliver solid battery life performance in this test which is definitely a good thing.

Video Playback Battery Life (720p, 4Mbps HP H.264)

When we move to our pure video test, the Nexus 9 does have a minor regression when compared to the Nexus 7 (2013) and SHIELD Tablet. In this case, the AMOLED displays on the Galaxy Tab S line make for an easy victory due to the relatively high amount of black displayed in the content. The gap is closed between the two devices though, due to a reduced focus on SoC power.

While our web browsing test can give some idea of efficiency, there are often cases where more compute is directly used to support a better experience. To try and test for these compute-bound cases, we use Basemark OS II’s CPU battery life test and GFXBench’s T-Rex rundown for a GPU battery life test. As with the web browsing tests, these are run at 200 nits to keep things relatively equal.

BaseMark OS II Battery Life

BaseMark OS II Battery Score

In Basemark OS II, the Nexus 9 does a surprisingly good job as the CPU manages to keep incredibly high sustained performance. The large battery and efficient display seem to help to a significant extent.

GFXBench 3.0 Battery Life

GFXBench 3.0 Performance Degradation

In GFXBench, it seems that not much changes overall. The GPU is definitely more power hungry than the PowerVR Series 6XT line-up and sustained performance is noticeably worse, but it’s in line with the SHIELD Tablet. End of run performance ends up a bit lower, but higher than one might expect. This is likely due to differing ambient temperatures. In practice, skin temperatures are about 45C in this test and localized to the top half of the device, and it’s likely that internal temperatures are around 80C as well. Seeing as how Tegra K1 can theoretically draw 33W in platforms such as the Jetson TK1 dev board with active cooling, it's incredibly impressive to see NVIDIA effectively keep such a powerful SoC within the constraints of a passively-cooled tablet.

Charge Time

While battery life is one part of the equation, charge time is an equally important aspect of overall battery life. To measure this, we measure the time from when charging begins to when the device reaches 100% charge. This is confirmed by taking measurements at the power outlet to make sure that power draw is below a certain level.

Charge Time

In this regard, the Nexus 9 is merely average for a tablet, although it does fall behind the competition as it uses a 5V, 1.5A charger for 7.5W instead of the 12-15W chargers that we’ve seen recently. It shouldn’t be a big issue, but in general this does mean that devices like the Galaxy Note 4 are actually better at battery life overall when compared to most tablets.

Display Software: Android 5.0 Lollipop
Comments Locked

169 Comments

View All Comments

  • cjs150 - Wednesday, February 4, 2015 - link

    No microSD - no chance of me buying it.

    Tablets are designed to be portable so why do designers never consider the needs of people on the move who may not have access to the cloud (either at all or at prohibitive cost). With 128 mb MicroSD card I can store tons of music, movies, tv shows and watch when I like on holiday
  • Impulses - Wednesday, February 4, 2015 - link

    USB OTG ftw
  • R. Hunt - Thursday, February 5, 2015 - link

    Hardly the same thing though.
  • UtilityMax - Sunday, February 8, 2015 - link

    They want you to pay royalties to store your stuff in the cloud. I agree that 16GB is somewhat limiting. Half of that space will be used by the OS and applications, with barely anything left for user's data. I'd go with the 32GB model at the very least.
  • NotLupus - Wednesday, February 4, 2015 - link

    What's the date today?
  • smayonak - Wednesday, February 4, 2015 - link

    Ryan, I noticed that the Nexus 9 offers always-on (screen-off) Google Now activation. I checked in CPUSpy (and other apps) and noticed that even when all cores are parked, this feature works, suggesting that NVidia may have included a custom DSP or third core for audio processing. The +1 core in NVidia's Tegra platform was apparently transparent to the operating system, because it never showed up in CPU activity monitor apps.

    If it is a custom DSP used for natural language processing, this would probably run afoul of Qualcomm's lock on the IP. Which might explain why NVidia never announced a third core (or DSP) in the Denver platform.

    I'm not sure if it's just my imagination at work -- can you confirm or disprove (or speculate) on the existence of a third core? Supposedly Android 5.0 includes support for idle-state audio processing, but only if supported by the hardware. But it would seem hardware support would require some kind of low-energy state processing core. And nothing of the sort appears in NVidia's press releases.

    By the way, thank you for the amazingly detailed and insightful review. You guys are amazing.
  • Andrei Frumusanu - Wednesday, February 4, 2015 - link

    Always-on voice activation is done by the audio SoC and has no connection to the main SoC or any DSP. Qualcomm's voice activation is done via the audio chip.
  • smayonak - Wednesday, February 4, 2015 - link

    Thanks. I have no doubt that's true, but I can't track down a reference. Anandtech's own article on the subject refers to Motorola's implementation of idle-state audio processing as relying on the X8's low-power cores, dedicated to handling audio processing.

    Motorola's press release claimed that their X8 included proprietary "natural language" and "contextual" processing cores (which I thought were some kind of analog-to-digital audio-processing DSP, but may be wrong), which allowed for always-on activation of Google Now.

    I can count the number of devices that support screen-off Google Now on one hand. The relatively small number of devices with this feature is perplexing. Or maybe no one advertises it?
  • toyotabedzrock - Wednesday, February 4, 2015 - link

    While turning a GPU into a CPU is a great accomplishment then essentially built a CPU that seems designed to benchmark well but will stall endlessly on real world code.
  • Anonymous Blowhard - Wednesday, February 4, 2015 - link

    This article is soooo late, clearly you should have just thrown up a half-page blurb with a clickbait title and was shallow enough that it could have just been written hands-off from the tech specs.

    /s

    Great read as always. Good things are worth waiting for.

Log in

Don't have an account? Sign up now