Final Words

The Nexus 9 is undoubtedly an aspirational device. For a long time now, Google and the Android tablet market in general have been in a position similar to Amazon’s Fire tablet. This has meant that the margin on the hardware itself has been quite low, and while quality was possible to achieve there were often sacrifices made in order to reach the targeted price point. This was seen in the form of lower CPU and GPU bins in the SoC, lower quality NAND, and generally poorer displays.

The Nexus 7 (2013) did manage to mostly avoid these issues, but Google had set the bar for price and performance to the point where OEMs would have issues with maintaining acceptable profit margins on a device. The Nexus 9 changes this strategy by reaching for a higher price point and attempting to deliver a no-compromise tablet in return. To figure out whether Google has succeeded, it’s worth going over each aspect of the device before coming to any sort of judgment.

The first and quite possibly most important aspect of the Nexus 9 is the SoC. To this end, the Nexus 9 is the very first Android device with AArch64 support enabled in Android. NVIDIA’s Tegra K1 with Denver is effectively the state of the art when it comes to SoCs in the Android OEM space, and no other device has launched with this SoC. While the fact that the SoC is built around the ARMv8 ISA is important, the architecture of the CPU itself is easily one of the most interesting designs we’ve seen in years. Unfortunately, while the design of the CPU is academically interesting it doesn’t seem that this produces real-world benefits. The Nexus 9 has one of the fastest SoCs we’ve seen to date, but this comes at the cost of worse power efficiency than the Cortex A15 version of the Tegra K1.

Another piece of the puzzle is the design, which is one of the key differentiators for a high-end mobile device. While one can debate the merits of various materials, it seems to be clear that an all-metal unibody chassis would’ve greatly improved the design of the Nexus 9 and justified its positioning better. While there is some level of give in the back cover, the buttons are quite thin and hard to find, and there’s a noticeable seam where the back cover and metal frame meet, the design isn’t actually all that bad in practice. Unfortunately, this seems to be a bit of a sore point as well for the Nexus 9 when compared against the iPad lineup.

While the SoC and design are often points of distinction for a premium tablet, the display is critical for any tablet. In this regard, the Nexus 9 does surprisingly well. With a 4:3 aspect ratio, high resolution, and high quality color calibration HTC and Google have outfitted the Nexus 9 with a great display. Unfortunately, there’s a great deal of variability present in these displays that presents itself in the form of backlight bleed along the edges of the display. While my unit only has a slight amount of bleed along the top edge of the device, other units can have more or less backlight bleed depending upon variance in production.

The one aspect that seems to be the product of a poor design choice is the high reflectivity of the display. Although I’m reasonably sure that the display is laminated due to the lack of an obvious gap between the display and glass, it seems that the optical material between the display and glass is poorly designed as I can see a distracting double reflection in the display. The Nexus 9 also compares unfavorably to the iPad Air 2 in this case as the anti-reflective coating on the iPad Air 2 is far superior to just about anything I’ve seen on the market.

Although I previously noted that the power efficiency of the SoC isn’t up to scratch, overall battery life is quite good on the Nexus 9. With a combination of a large battery and efficient display, Google and HTC have managed to compensate for the power consumption issues that come with Denver’s performance. Unfortunately, it seems that Kepler’s desktop-first design results in worse power efficiency than what we see on competing solutions such as the “GXA6850” found in competing SoCs. Even if this is compensated for by the ability to enable desktop-class gaming, the Nexus 9 doesn’t appear to support full OpenGL to begin with, unlike the SHIELD Tablet. This means that the extra capabilities enabled by the GPU are effectively wasted, which hurts the value proposition for the device overall. In light of the launch of the Tegra X1, I can't help but wonder how different the experience of the Nexus 9 would be with NVIDIA's latest SoC.

Outside of these primary elements of the tablet, there seems to be a reasonable level of attention to detail. The camera is acceptable, even if the focus and capture latency aren’t the greatest. The audio quality from the speakers is also quite good, and really helps to enable a great experience when watching any kind of video or listening to music without earbuds/headphones. The software experience is acceptable, although Google continues to fight issues with ecosystem support for tablets.

With all of this in mind, it’s hard to give a resounding recommendation of the Nexus 9. The Nexus 9 is a step towards a high-end Android tablet, but not the leap that Google was hoping for. If you want an Android tablet near the size of the Nexus 9, I can’t really recommend anything else. The Galaxy Tab S falls short on account of performance and battery life, and despite the somewhat unremarkable design of the Nexus 9 I believe that it is nicer than the Galaxy Tab S. However, if one were to assume that OEMs are currently readying devices to truly carry the torch of the high-end tablet, the Nexus 9 is a hard sell. I suspect that this wouldn’t be nearly as difficult if the Nexus 9 had a lower price point of $300 and $350 USD for the 16GB and 32 GB WiFi variants, and $450-$500 for the 32GB LTE variant. Google has managed to get close to the mark with the Nexus 9, but like the Nexus 6 it seems that it’s up to the OEMs to cover the remaining distance.

WiFi Performance, GNSS, Misc
Comments Locked

169 Comments

View All Comments

  • lucam - Thursday, February 5, 2015 - link

    Next time you will write the article for Anand.
  • tuxRoller - Thursday, February 5, 2015 - link

    Just tested on my N7 2013. Results were far higher than shown in the chart.
    SR:64.2->76.1
    SW:18.4->30.1
    RR:11.2->13.4
    RW:0.7->3.1
  • mpokwsths - Thursday, February 5, 2015 - link

    Well, your results are far far more improved than 10% Andrei says.
    3 devices by 2 different users, all showed vast improvements (10-500%).
    Only they refuse to acknowledge it.
    Who knows, it seems Anandtech guys are on Apple's payroll...
  • eiriklf - Thursday, February 5, 2015 - link

    Just wanted to note that on the NAND performance front, I believe the android devices which beat the nexus 9 in sequential speed use emmc 5.0 while the nexus uses a high quality emmc 4.5. I think this is because the tegra K1 SoC does not support emmc 5.0.
  • tviceman - Wednesday, February 4, 2015 - link

    Better late than never, although being this late is indeed a big letdown.

    Onto the hardware, looks like Denver is an interesting first custom SoC from Nvidia. Solid in some respects, lacking in others. I think it's a solid building block from which to work on and improve. I hope Nvidia continues the custom ARM core path and gets more design wins (if warranted) moving forward.
  • kepstin - Wednesday, February 4, 2015 - link

    The Denver chip design is pretty interesting, but it reminds me very strongly of another mobile-targeted chip that didn't do well in the marketplace; the Transmeta Crusoe.

    Both are VLIW designs with in-order execution, both rely on software code translation that runs on the CPU itself. Both even used a partitioned section of system ram as a translated ops cache.

    The most significant difference that I see between them is the addition of a native ARM decoder to the Denver CPU; the Crusoe didn't have a native X86 decoder and relied on the dynamic translation for all code that it executed.

    I had a Crusoe for a while in a Sony Vaio; it was used in some of the very small/lightweight ultraportable laptops by Japanese manufacturers for a while.
  • phoenix_rizzen - Wednesday, February 4, 2015 - link

    Didn't a large group of Transmeta devs get hired by Nvidia?
  • ABR - Thursday, February 5, 2015 - link

    Crusoe lost because Transmeta woke the sleeping giant Intel to the value of low-power, and then a group of 100 people couldn't keep up the resulting engineering race. The x86 world would be a pretty different place today if that hadn't occurred. But I'd say the jury is still out on the overall capability of the VLIW + morphing approach.
  • frenchy_2001 - Thursday, February 5, 2015 - link

    I would second that. A quick search returned a licensing agreement where nvidia licensed Transmeta's technology.
    This could be a good part of Denver.

    About in order execution, the biggest experiment was from intel: itanium.
  • kgh00007 - Wednesday, February 4, 2015 - link

    It's 3 months late, the nexus 9 was released on the 3rd of November!!

    No excuses, but it's just too late to help people make an informed decision!! Just like dog years, one year for a tablet is like 7 technology(dog) years!!

Log in

Don't have an account? Sign up now