The Nexus 4 is based around a 1.5 GHz Qualcomm Snapdragon S4 Pro SoC, the quad core Krait APQ8064 with Adreno 320 GPU, which is still built on a 28nm process. The combination of APQ8064 for AP and MDM9x15 for baseband is Qualcomm's Fusion 3 platform, and the Nexus 4 and Optimus G are the first phones to market based on that platform. This is a relatively unique opportunity for Nexus, which until recently wasn't really first to market with the latest and greatest silicon. 

A while ago we posted our Nexus 4 and Nexus 10 performance preview. At that point we still had a lot of testing to perform, and many people noted that the Nexus 4 performance was far behind the LG Optimus G despite it being based on the same platform. Later, some people noticed that I had uploaded another set of results from GLBenchmark 2.5 to the online result browser with much better performance. The difference wasn't some over the air software update but rather that I was running some of the tests with the Nexus 4 in a ziplock bag inside the freezer to mitigate any condensation problems, and simultaneously nail down any possible thermal throttling. 

I've re-run everything and can confirm obviously that there was thermal throttling going on affecting some of the results, and have included the new results wherever there was a deviation from previous. For those wondering why the LG Optimus G wasn't affected in spite of it having the same platform, the reason is because the results from the Optimus G were run in parts due to some instability affecting its ability to run a complete set of tests without crashing. The Nexus 4 has newer drivers that don't crash during a full GLBenchmark 2.5 run but as a result run the device long enough for thermal throttling to kick in. 

GLBenchmark 2.5 - Fill Test

GLBenchmark 2.5 - Fill Test (Offscreen 1080p)

GLBenchmark 2.5 - Triangle Texture Test

GLBenchmark 2.5 - Triangle Texture Test (Offscreen 1080p)

GLBenchmark 2.5 - Triangle Texture Test - Fragment Lit

GLBenchmark 2.5 - Triangle Texture Test - Fragment Lit (Offscreen 1080p)

GLBenchmark 2.5 - Triangle Texture Test - Vertex Lit

GLBenchmark 2.5 - Triangle Texture Test - Vertex Lit (Offscreen 1080p)

GLBenchmark 2.5 - Egypt HD

GLBenchmark 2.5 - Egypt HD (Offscreen 1080p)

GLBenchmark 2.5 - Egypt Classic

GLBenchmark 2.5 - Egypt Classic (Offscreen 1080p)

The result of the tests in the freezer results that are much closer to what we'd expect based on the APQ8064 MDP/T runs and the Optimus G numbers I saw in Korea. 

When it comes to the CPU side of things there were results also affected by thermal throttling. I spaced some of those runs out (unintentionally) enough that performance didn't change, but for other things it did affect performance. I can't tell what GPU clocks end up being when the SoC decides to throttle, but it is possible to nail down what CPU performance state APQ8064 settles down into when there's throttling going on by looking at the state tables. 

 
Left - 1.134 GHz during throttling (running tests), Right - All the performance states

I can see the Nexus 4 not use any of the performance states above 1134 MHz when it's getting hot, as shown in the images above. I've tweeted a link to the pastebin for thermald.conf which I believe configures the thermal cutoffs and will be interesting to kernel hackers trying to play with these values. 

SunSpider Javascript Benchmark 0.9.1 - Stock Browser

BrowserMark

Google Octane Benchmark v1

Mozilla Kraken Benchmark

Vellamo Benchmark - 2.0

Vellamo Benchmark - 2.0

Sequential Read (256KB) Performance

Sequential Write (256KB) Performance

Random Read (4KB) Performance

Random Write (4KB) Performance

Our CPU performance side is unfortunately still dominated by JavaScript performance tests. The story there is that the Nexus 4 ships with Chrome (and originally shipped with a newer build of Chrome than what was on the market - we were running that updated version all along) and thus the mainline version of the V8 JavaScript engine. OEMs perform their own optimizations to the V8 library, and try to upstream whatever they can into the main project, but in the case of Chrome for Android that means V8 sans secret OEM sauce. 

Battery Life and Charging Android 4.2 - New Flavor of Jellybean
POST A COMMENT

188 Comments

View All Comments

  • Fx1 - Tuesday, November 13, 2012 - link

    My God why is the battery life so crap? How does the HTC X manage to beat it? Reply
  • IKeelU - Tuesday, November 13, 2012 - link

    I also would love to know the answer to this. Reply
  • amdwilliam1985 - Tuesday, November 13, 2012 - link

    I say you need to take battery life test with a grain of salt. My SGS3 didn't have the best battery life tests on paper, but in real time it's a champ. My gf shoots me with her envy look while holding her iphone 4s. She can't go through a day with a charge while I can easily do 2 days ;) Reply
  • uhuznaa - Tuesday, November 13, 2012 - link

    Yeah, but this is about the Nexus 4 and the battery life DOES suck. Reply
  • yipwssg - Tuesday, November 13, 2012 - link

    Your gf must be checking her faceBook account constantly :)
    If not, the bettery must be aged . Ask her to get a new replacement from Apple if her set is still under warranty.
    Reply
  • kmmatney - Wednesday, November 14, 2012 - link

    it must be about the settings. I can easily go 2 days, and sometimes 3 with my 4S... Reply
  • phillyry - Thursday, November 15, 2012 - link

    Are you sure that's not cause she does more with it / uses it more? Reply
  • Mbonus - Tuesday, November 13, 2012 - link

    "My God why is the battery life so crap? How does the HTC X manage to beat it? "

    I wonder if it has to do with HTC One-X overly aggressively killing background apps . As I recall there were a lot of complaints about no multitasking on the One X. I bet that would improve battery life.
    Reply
  • Impulses - Tuesday, November 13, 2012 - link

    That wouldn't diminish power usage by memory a whole lot, and HTC actually went back and addressed it with a patch so it behaves much much closer to other phones. I think the biggest issue is they 're cramming a tablet-bound SoC into a phone (see the thermal throttling issues) without even giving it a larger battery. Reply
  • Strk - Tuesday, November 13, 2012 - link

    Why do the speaker volume test at just 3" away? How about normal browsing distance? (k, that's subjective, I guess, but for a typical person browsing the internet/watching a video) Cupping the speaker vs not cupping the speaker etc. Watching a clip on youtube, netflix or whatever on my Galaxy Nexus is such a pain if there is even the slightest ambient noise. Reply

Log in

Don't have an account? Sign up now