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

  • mkygod - Saturday, February 7, 2015 - link

    I think so to. The 3:2 ratio is one of the things that Microsoft has gotten right with their Surface Pro devices. It's the perfect compromise IMO
  • UtilityMax - Sunday, February 8, 2015 - link

    I am a little perplexed by this comment. A typical user will be on the web 90% of time. Not only the web browser does not need to be natively designed or optimized for any screen ratio, but it also will be more usable on a 4:3 screen. So will the productivity apps. The only disappointment for me on the 4:3 screen would be with watching the widescreen videos or TV shows. Moreover, there is quite a bit of evidence than a lot of the next generation tablets will be 4:3. Samsung's next flagship tablet supposedly will be 4:3.
  • gtrenchev - Wednesday, February 4, 2015 - link

    Anandtech is becoming more and more boring last year. Sparse on reviews, short on tech comments, lacking on depth and enthusiasm. I can see Anandtech has become a just job for you guys, not the passion it was for Anand :-) And yes, his absence is definitely noticeable.

    George
  • Ian Cutress - Wednesday, February 4, 2015 - link

    Was the Denver deep-dive not sufficient enough? Always welcome for comments.
    As for timing, see Ryan's comment above.
    We've actually had a very good quarter content wise, with a full review on the front page at least four out of every five weekdays if not every weekday.
  • milkod2001 - Wednesday, February 4, 2015 - link

    Why not to post on your forum some sort of suggestion box/poll where all could say what should get reviewed first so some folks won't cry where is the review of their favorite toy :) ?
  • Impulses - Wednesday, February 4, 2015 - link

    Because they'll still cry regardless, and they can't possibly work entirely based on readers' whim, doesn't make sense logistically or nor editorially... Readers might vote on five things ahead of the rest which all fall on the same writer's lap, they won't all get reviewed before the rest, or readers might not be privy to new hardware because of NDAs or cases where Anandtech can't source something for review.
  • tuxRoller - Thursday, February 5, 2015 - link

    While I enjoyed the review, I would've loved to have seen the kind of code driven analysis that was done with Swift.
    In particular, how long does it take for dco to kick in. What is the IPC for code that NEVER gets optimized, and conversely, what is the IPC for embarrassingly instruction-wise parallel code? Since it's relying on ram to store the uops, how long does the code need to run before it breaks even with the arm decoder? Etc.
  • victorson - Wednesday, February 4, 2015 - link

    Are you guys kidding? Better late than never, but heck.. this is freaking late.
  • abufrejoval - Wednesday, February 4, 2015 - link

    Thanks for making it worth the wait!

    The in-depth analysis of Denver is uniquely Anandtech, because you can't get that anywhere else.

    And while Charly D. is very entertaining, the paywall is a bit of an impediment and I quite like again the Anand touch of trying to be as fair as possible.

    I was and remain a bit worried that there seems to be no other platform for Denver, which typically signals a deeper flaw with an SoC in the tablet and phone space.

    While I'm somewhat less worried now, that Denver might be acceptable as a SoC, the current Nexus generation is no longer attractive at these prices, even less with the way the €/$ is evolving.
  • Taneli - Wednesday, February 4, 2015 - link

    eDRAM cache à la Crystalwell would be interesting in a future Denver chip.

Log in

Don't have an account? Sign up now