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

  • melgross - Wednesday, February 4, 2015 - link

    So, people only buy devices during the first three months?
  • Impulses - Wednesday, February 4, 2015 - link

    Apparently... Although getting the review in before February would've shut all these people up, cheapest place to get the Nexus 9 all thru the holidays was Amazon ($350 for 16GB) and they gave you until January 31 to return it regardless of when you bought it.

    Only reason I'm so keenly aware is I bought one as a February birthday gift, opened it last weekend just to check it was fine before the return window closed... Not much backlight bleed at all even tho it was manufacturerd in October (bought in late December), some back flex but it's going in a case anyway.
  • blzd - Friday, February 6, 2015 - link

    What does the month of manufacture have to do with the back light bleed? You don't actually believe those "revision" rumors, do you?

    If you do, consider how practical it is for a hardware revision to come out 1 month after release. Then consider how one set of pictures on a Reddit post proves anything other than that their RMA worked as intended.
  • ToTTenTranz - Wednesday, February 4, 2015 - link

    I wish more smartphone/tablet makers put as much thought into their external speakers as HTC does.

    Once having a HTC One M7, I simply can't go back to mono speakers at the back of devices.
  • Dribble - Wednesday, February 4, 2015 - link

    Glad the review is here at last, next one a little bit quicker please :)
  • UpSpin - Wednesday, February 4, 2015 - link

    I have following issues with your review:
    1. You run webbrowser tests and derive CPU performance from it. That's nonsense! It's a web-browser test, and it won't be a CPU test whatever you do. If you want to test raw CPU performance you have to run native CPU test applications.

    2. Your battery life analysis is based on false assumptions and you derive doubtful claims from it.
    The error is quite evident on the iPad Air test. In your newly introduced white display test, with airplane on, CPU/GPU idling, etc. the iPad Air 2 has a battery life of 10:18 hours. Now in your web-browsing battery test with WiFi on and the CPU busy, the iPad Air 2 has a battery life of 9:76 hours. That's a difference of 4%. The Nexus 9 has a difference of 30%, the Note 4 15%, the Shield Tablet 25%.
    You conclude: The Tegra K1 is inefficient. But I could also conclude that the A8 is inefficient and the Tegra K1 very efficient. The Tegra K1 needs significantly less power while idling, compared to the A8, which consumes always the same, mostly independent on the load. So finally, the A8 lacks any kind of power saving mode.
    That's abstruse, but the consequence of your test. Or maybe your test is flawed from the beginning on.

    3. " 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."
    Sorry, but I don't get this either. The Nexus 9 has a 25.46 WHr battery, the iPad Air 2 a 27.3 WHr battery (+7%). The Nexus 9 has a 8.9" Display, the iPad Air 2 a 9.7". (+19% area). The resolution is the same, thus the DPI on the Nexus 9 higher. The display techonoly is the same, as you said in your analysis. So the difference must be related to something else, like a highly efficient idle SoC in the Nexus 9.
  • Andrei Frumusanu - Wednesday, February 4, 2015 - link

    The battery life tests analysis is based on true facts on the technical workings of the SoC and its idle power states and we are confident in the resulting conclusions.
  • JarredWalton - Wednesday, February 4, 2015 - link

    Going along with what Andrei said, an SoC isn't "efficient" if it's doing no work -- the A8 may not have idle power as low as the K1-64, but when you're actually doing anything more with the tablet in question is when efficiency matters. It's clear that the Air 2 wins out over the Nexus 9 in some of those tests (GFX in particular). Doing more (or equivalent) work while using less power is efficient.

    Imagine this as an example of why idle power only matters so far: if you were to start comparing cars on how long they could idle instead of actual gas mileage, would anyone care? "Car XYZ can run for 20 hours off a tank while idle while Car ZYX only lasts 15 hours!" Except, neither car is actually doing what a car is suppose to do, which is take you from point A to point B.

    The white screen test is merely a way to look at the idle power draw for a device, and by that we can get an idea of how much additional power is needed when the device is actually in use. Also note that it's possible due to the difference in OS that Android simply better disables certain services in the test scenario and iOS might be wasting power -- the fact that the battery life hardly changes in our Internet WiFi test even suggests that's the case.

    To that end, the battery life of the N9 is still quite good. Get rid of the smartphones in the charts and it's actually pretty much class leading. But it's still odd that the NVIDIA SHIELD Tablet and iPad Air 2 only show a small drop between idle and Internet, while N9 loses 33% of its battery life.
  • ABR - Thursday, February 5, 2015 - link

    Idle power is pretty important for real world use for tablets, for example where you are reading something and the system is just sitting there. Those "load web page then pause for xx time" test would probably be really good for measuring.
  • JarredWalton - Thursday, February 5, 2015 - link

    That's exactly what our Internet test does, which is why the 33% drop in battery life is so alarming. What exactly is going on that N9 loading a generally not too complex web page every 15 seconds or so kills battery life?

Log in

Don't have an account? Sign up now