Software

With the Nexus 9, Google has released the biggest upgrade to Android since 4.0. In some ways, Android 5.0 represents one of the biggest shifts in the design of the OS ever. While we’ve had JIT compiling on Dalvik since Android 2.2, this has remained largely static for the past few years during Android’s monumental growth. With Android 5.0, we see the introduction of Android Runtime, or ART. Instead of trying to compile the application right before execution, ART does most of the compilation well before the application is launched. This incurs higher storage requirements, longer app-install times, and longer first-boot times, but with great benefits to performance. Google has done a great deal of work in general to try and resolve performance issues, as we first detailed in our coverage on ART.

While performance is one major aspect of Android 5.0, Google has also fundamentally redesigned the interface. To replace Holo, Google has introduced Material Design, which emphasizes depth, physics, animation, and a new palette of colors. While it would be great to go over all of these aspects of the Nexus 9, it’s best to refer to Brandon's review of Android 5.0 Lollipop for these issues. Instead, for this review I will mostly focus on the Lollipop experience specific to the Nexus 9. This means that the focus will be on performance of the device in general usage, along with the app ecosystem for Android tablets.

Unfortunately, these seem to be sore points of the Nexus 9 and the broader Android tablet ecosystem. Without question, if we’re talking about tablet applications they definitely do exist for the Nexus 9. The problem is that there is a pervasive lack of applications that are truly designed for a 9 inch, 4:3 aspect ratio display. Applications like Twitter, Facebook, and other first-party apps are simply blown up versions of the phone application. There is some level of extra content presented, but a lot of applications just don’t scale correctly which wastes a lot of real estate on the display. While we found issue with the Nexus 6’s lack of phablet-specific layouts, this is an even bigger issue on the Nexus 9.

While it’s possible to point fingers at app developers for not supporting Android properly, Google seems to have these problems as well. The settings interface is a single large pane of options, instead of a dual-pane interface that allows for simultaneous navigation of the overall settings and individual settings. The Play Store application is mostly similar in this respect, and the YouTube app is possibly the worst example of these kinds of issues. For example, while there is a tablet-specific video view in landscape, most navigation, search, and video selection is identical to what we see on a smartphone.

Nothing really takes advantage of the screen size other than simply being bigger than before. There aren’t any multi-window modes that exploit the larger screen size, and in general the Nexus 9 doesn’t introduce any new functionality that clearly justifies the need for a bag/backpack to carry it. There are applications that take advantage of the larger display, but these are rare. For the most part though, this is effectively true for most tablets other than the Surface Pro 3 which is effectively in a different category altogether.

On the performance side, the story is better but it isn’t perfect either. Similar to Brandon’s experience with the Nexus 6, I often saw random stutters on animations such as the app drawer or while opening an application. It’s hard to say what the cause is at this point, as the Nexus 6 seems to have similar issues with lag even though the Nexus 5 has none of these issues. One might point to FDE causing worse performance, but even that isn’t quite accurate as a build of Lollipop with FDE disabled didn’t do all that much in the way of solving these problems. Overall though, the experience is somehow less performant than the SHIELD Tablet on Android 5.0, even if these issues mostly present themselves in the form of minor frame drops from time to time. I also noticed that there was a distinct lack of available memory over time, which suggests a memory leak as on reboot launcher redraws effectively disappeared.

While these are significant issues that need to be resolved, the experience isn’t actually as bad as it seems. For what it’s worth, Material Design is a great new design scheme to replace the somewhat dated Holo UI that has been in use since Honeycomb/Android 3.0. While there are issues with the tablet experience, if one is willing to look past these issues they will find that the Nexus 9 is a respectable software experience. There’s also the potential for the Nexus 9 to spur improved tablet experiences, although this would be a slow change that could take years to be meaningful.

Battery Life and Charge Time Camera
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