Earlier this week Google announced two new flagship Nexus devices: the Nexus 4 smartphone and the Nexus 10 tablet. We received review samples of both earlier this week, and while we're hard at work at full reviews of the devices we couldn't help but share all of the test data we've been able to amass at this point.

For those who aren't familiar with it, the Nexus 4 features Qualcomm's Snapdragon S4 Pro SoC - a quad-core 28nm Krait CPU with Qualcomm's next-generation Adreno 320 GPU. The combination proved quite formidable in the MDP/T we tested, as well as LG's recently announced Optimus G. The SoC drives a 4.7-inch 1280 x 768 IPS display and is paired with 2GB of LPDDR2 memory. The Nexus 4 ships unlocked with 8GB of NAND for $299 without a contract ($349 for the 16GB version). Pair that with DC-HSPA+ support and you get an absolute killer smartphone for use on T-Mobile: no contracts, very low monthly fees, and compelling cellular performance:

Brian will talk more about the combination in his full review, but rest assured that the lack of LTE is workable depending on T-Mobile coverage where you live/travel to.

The Nexus 10 also boasts a brand new SoC: Samsung's Exynos 5 Dual. The Exynos 5 Dual features two ARM Cortex A15 cores running at 1.7GHz as well as ARM's own Mali-T604 GPU. This happens to be the exact same platform used in the new Chromebook, just running Android. The Nexus 10 features a 10.1-inch 2560 x 1600 display, giving it the same resolution as the 13-inch MacBook Pro with Retina Display - but in an even smaller form factor. Google is also aggressive on Nexus 10 pricing: the 16GB WiFi-only tablet sells for $399, with the 32GB version going for $499.

Both Nexus devices run Android 4.2 and are guaranteed to be the first devices to be updated to upcoming Android revisions for the foreseeable future (it's the power of Nexus).

We haven't had a ton of time to test the devices and put this together so you're going to see combined performance charts throughout the rest of this article.

CPU Performance

The big story when it comes to CPU performance is a look at how the Cortex A15s perform under Android. Unfortunately we're still left with mostly browser based benchmarks to measure CPU performance, which actually highlights a major issue in our testing: Android V8 optimization doesn't seem to be anywhere near as good as it is under Chrome OS or Windows. As a result, all of the Nexus 10 performance scores end up slower than the new Chromebook - despite using the same SoC and running Chrome on both platforms. It's also possible that the Exynos 5 Dual in the Chromebook is allowed to burn a bit more power, translating to better performance, but either way the solution here in the Nexus 10 doesn't look as good across the board.

SunSpider Javascript Benchmark 0.9.1 - Stock Browser

SunSpider performance is good, but not significantly better than Qualcomm's Krait based Snapdragon S4. Both the iPhone 5 and RAZR i are able to outperform the Nexus 10. The S4 Pro based Nexus 4 tends to be in line with other S4 based devices - SunSpider doesn't really give much credit to the extra 2 cores.


BrowserMark puts the Nexus 10 behind many platforms that should be faster, I'm even wondering here if there's some hard partitioning of memory bandwidth between the CPU and GPU to drive the 2560 x 1600 display that's simply choking the CPU here.

The Nexus 4 does ok, but again there seem to be some V8 optimization issues at work here under Android 4.2. At 1.5GHz it should deliver at least the performance of the dual-core Snapdragon S4 solutions.

Google Octane Benchmark v1

Octane is the first test where the Cortex A15s are really able to flex their muscle - the Exynos 5 Dual based Nexus 10 manages to outperform the RAZR i by 34%, and compared to the A6/Swift based iPhone 5 the advantage grows to 64%.

The Nexus 4 performs about in line with other Snapdragon S4 based devices, although once again the extra 2 cores don't seem to be doing much for it here at all.

Mozilla Kraken Benchmark

Kraken also paints the Cortex A15 based Nexus 10 in a good light: there's a 30% advantage over the RAZR i and a 76% advantage over the iPhone 5. These numbers will shrink a bit compared to other tablets, but not by much. The Nexus 4, once again, ends up performing similarly to dual-core Snapdragon S4 based devices.

Overall, the Nexus 10 results show us some real promise for what we can expect from ARM Cortex A15 based SoCs. The potential upside to this new architecture is huge.


GPU Performance & Display
Comments Locked


View All Comments

  • MadMan007 - Friday, November 2, 2012 - link

    Using mobile benchmarks to judge devices as a potential customer is pretty frustrating. Same hardware in different devices gets different scores, sometimes by huge amounts, and we don't always know where the variation comes from. Not to mention that the most often used benchmarks may not correspond with actual use anyway.

    So, the important question is how well do these benchmarks correspond to real-world use? Does a device that scores 2x in a bunch of benchmarks really feel 2x faster? Does it depend on what you're doing, or is the network speed the limiting factor for web browsing anyway? These are the kinds of questions that are important to actual customers...after the 'new shiny' benchmark e-peen high wears off, we are left actually using the device. Anything you can do to help answer these questions would be awesome - we need an Anandtech Smartphone Bench!
  • doobydoo - Sunday, November 4, 2012 - link

    GL benchmarks don't vary by software.
  • ctenorman - Friday, November 2, 2012 - link

    For most of the every day benchmarks, like Google's Octane, my Galaxy Nexus actually performs better. For example, I get a 1300+ score for octane in browser (not chrome). I'm not overclocked, just running a recent build of AOKP.

    In what way is the nexus 4 a real upgrade over the Galaxy Nexus if not in speed? The Galaxy Nexus display is pretty impressive still (especially if you're using a ROM which punches the brightness up to an appropriate like AOKP does and makes it quite readable in sunlight), its performance is still as good or better than than the Nexus 4 for day-to-day tasks, and the Galaxy Nexus doesn't have a lot of weak points (other than a less-than-incredibly-impressive camera). Mind you, even the camera isn't as weak as it's often made out to be: http://www.zdnet.com/blog/cell-phones/galaxy-nexus... Granted, the Nexus 4 has more power in the graphics department, but ever since Jelly Bean I haven't wished for more graphical smoothness.

    I wouldn't mind 2gb of RAM, but other than that, I fail to see how this is a big advance unless you're a hard-core gamer, and even then I rarely wish for more gaming horsepower on my GN.
  • A5 - Friday, November 2, 2012 - link

    There must be some problem with the V8 optimizations in 4.2 right now. Engadget's review has the Optimus G getting 1283ms in SunSpider on ICS, so the hardware isn't the problem...
  • MrSpadge - Friday, November 2, 2012 - link

    I read this as "4 cores are (currently) useless in a phone, however smart it may want to be".
  • MadMan007 - Friday, November 2, 2012 - link

    Yeah, I'd rather have seen an Exynos5 dual core in the Nexus 4, or an S4 dual core with Adreno 320. Single threaded performance is still more important once you've got dual cores.
  • Jorange - Friday, November 2, 2012 - link

    Which version of Chrome ships with 4.2?

    On a Nexus 7 @ 1.6 GHz with the latest (1st November) update I get a sunspider of 1300ms ~, on stock AOSP 4.1.2 Browser I get 1100ms~. Chrome as a default browser is not great, on the Chromium logs there is mention of Chrome for Android next milestone as version 24, so I was hoping for a increase in performance using Chrome in 4.2.

    Just re-run Sunspider at stock on a Nexus 7, I still get 1500~ms. Anand are you running the latest version of Chrome from the play store, as it apparently has improvements relevant to the Nexus 4 & 10?

    I hope Google has not cobbled these Nexus gems with a browser than never should have left beta.
  • uhuznaa - Friday, November 2, 2012 - link

    Chrome is basically a very nice fit for a tablet (or even larger smartphones) but it feels beta very much indeed.
  • A5 - Friday, November 2, 2012 - link

    Other reviews are showing browser performance issues in 4.2, too. Might just be the software...wouldn't be shocked if we see 4.2.1 by the time this actually gets into anyone's hands.
  • staticx57 - Friday, November 2, 2012 - link

    Chrome is a very poorly coded app as much as I like the interface. On all of my devices it lags like no other unlike the stock android browser.

Log in

Don't have an account? Sign up now