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

  • ABR - Thursday, February 5, 2015 - link

    I don't know if it would change this conclusion, but load-every-15-seconds is still only testing "screenager" behavior. For example while I'm reading this comments page it's a lot longer than 15 seconds. More like 30 seconds, scroll, 30 seconds, scroll, 5-10 minutes load another. Reading e-books is another low-intensity usage. Not saying that gaming and other continuous usage patterns aren't out there, but a lot of what people say they use tablets for is lower intensity.
  • lucam - Thursday, February 5, 2015 - link

    Upspin, send your resume to Anand and write next time your article. Looking fwd to reading your pearl of wisdom...
  • Affectionate-Bed-980 - Wednesday, February 4, 2015 - link

    You guys really need to stop using that gray/black surface for the background to show off your black devices. It really makes it hard to see the details.
  • gijames1225 - Wednesday, February 4, 2015 - link

    It's a shame that NVidia couldn't get Denver out on a smaller process at launch. They're giving the A8 a run for it's money, but the 28nm process is killer at this point.
  • WereCatf - Wednesday, February 4, 2015 - link

    "it seems to be clear that an all-metal unibody design would’ve greatly improved the design of the Nexus 9 and justified its positioning better."

    I don't quite agree. This article mentions several times the author's wish for full-body aluminum design, but as someone who already has a tablet with a nearly full aluminum body I do have to point out that it tends to be quite slippery in one's hands; you need a much tighter grip just to hold it without it slipping and this makes it tiring to hold in the long run. A tablet with a sort of rubbery, non-slip back won't look as pretty, but it will certainly be much more comfortable and I definitely would choose practicality over looks.
  • danbob999 - Wednesday, February 4, 2015 - link

    Also metal blocks wireless signal. Asus Transformer Prime has abysmal wifi and GPS reception because of that.
    There is no rational advantage to metal cases. Only looks, which is debatable.
  • WereCatf - Wednesday, February 4, 2015 - link

    Aye, my tablet had that issue. Luckily it's easy to open up and replace the antenna with a stronger one, something that helps, but not all tablets are that easy to open or have a replaceable antenna.
  • Impulses - Wednesday, February 4, 2015 - link

    Metal would also make it heavier... Plastic doesn't have to mean back flex, it's just a design/QC issue they didn't address. My OG TF had a textured plastic back that was pretty solid, several years ago. It still creaked a little but it was mostly because of the mating of the back to the metal frame, no flex tho.
  • olivaw - Wednesday, February 4, 2015 - link

    I wonder if nVidia is "crazy enough" to develop a runtime that would JIT from android bytecode directly to denver. As it is, there are two layers of compilation going on, if ART could by swapped by an nVidia runtime things could get really interesting!
  • joe0185 - Wednesday, February 4, 2015 - link

    The browser tests are pretty worthless as it is but they are made even more worthless by the omission of version information. If AnandTech is going to include Javascript benchmarks they should at least include the browser version. What version of Chrome are you running on each device? There have been pretty dramatic improvements in Chrome on Android over the past year.

Log in

Don't have an account? Sign up now