Nexus 6 Performance With Android 5.1
Does the Android 5.1 update bring performance and battery life improvements to the Nexus 6?
GPU And Gaming Performance
The 5.1 update brings support for OpenGL ES 3.1 to the Nexus 6, which was missing from the initial 5.0 release. Beyond this, I could not find any other changes that should affect GPU performance.
GPU Benchmarks
Benchmark | Nexus 6Android 5.0 | Nexus 6Android 5.1 | Difference | |
---|---|---|---|---|
3DMark: Ice Storm Unlimited | Score | 23618 | 21253 | -10.01% |
Graphics | 25651 | 22294 | -13.09% | |
Physics | 18489 | 18267 | -1.20% | |
Basemark X: Medium Quality | Performance | 30315 | 26339 | -13.12% |
Dunes: Offscreen | 32.82 fps | 28.03 fps | -14.61% | |
Dunes: Onscreen | 23.65 fps | 23.03 fps | -2.64% | |
Hangar: Offscreen | 44.45 fps | 38.98 fps | -12.31% | |
Hangar: Onscreen | 34.24 fps | 31.01 fps | -9.43% | |
Basemark X: High Quality | Performance | 20825 | 19178 | -7.91% |
Dunes: Offscreen | 29.04 fps | 26.84 fps | -7.59% | |
Dunes: Onscreen | 20.56 fps | 20.26 fps | -1.46% | |
Hangar: Offscreen | 25.76 fps | 23.65 fps | -8.17% | |
Hangar: Onscreen | 17.38 fps | 16.93 fps | -2.59% | |
GFXBench 3.0 | Manhattan Offscreen | 17.0 fps | 18.4 fps | 8.89% |
Manhattan Onscreen | 12.0 fps | 12.1 fps | 0.75% | |
T-Rex Offscreen | 37.0 fps | 39.1 fps | 5.47% | |
T-Rex Onscreen | 26.5 fps | 27.5 fps | 3.88% | |
Alpha Blending Offscreen | 10694 MB/s | 11344 MB/s | 6.08% | |
Alpha Blending Onscreen | 9281 MB/s | 9755 MB/s | 5.10% | |
ALU Offscreen | 140.5 fps | 141.5 fps | 0.75% | |
ALU Onscreen | 59.5 fps | 59.0 fps | -0.06% | |
Driver Overhead Offscreen | 25.0 fps | 24 fps | -3.28% | |
Driver Overhead Onscreen | 22.0 fps | 19.5 fps | -11.01% | |
Fill Offscreen | 7334 MTexels/s | 7465 MTexels/s | 1.79% | |
Fill Onscreen | 8474 MTexels/s | 8490 MTexels/s | 0.19% | |
Render Quality: Standard | 2503 mB PSNR | 2503 mB PSNR | 0.00% | |
Render Quality: High Precision | 3633 mB PSNR | 3628 mB PSNR | -0.14% |
The 5.1 update on the Nexus 6 reduces 3DMark and Basemark X performance by up to 15%. Even though these tests primarily stress the GPU, the CPU still plays a supporting role. To understand this better, we logged CPU and GPU frequency while running Basemark X.
As expected, the GPU runs at its max frequency of 600MHz during each test segment regardless of OS version. With the initial Android 5.0 build, the Nexus 6 keeps two cores offline and the other two above the 1497MHz threshold most of the time and at least one core at max frequency fairly often. CPU behavior with the 5.1 update looks very different. No single core runs at max frequency for very long, with cores taking turns jumping from 300MHz to 2649MHz and back down again. There’s also several gaps where all four cores are sitting at 300MHz. Looking at the raw data also shows that only one or two CPU cores are above idle at any given time, so having all four cores online does not provide any performance advantage in this particular benchmark.
Things aren’t all bad, however, as we see small performance improvements in the GFXBench Manhattan, T-Rex, and Alpha Blending tests, indicating that some games will see an uptick in performance.
Stay On the Cutting Edge: Get the Tom's Hardware Newsletter
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
PlayStation 5 transformed into a laptop for $2,750 — Chinese modders made Sony's console more portable with a 17.3-inch 4K display weighing over 9 pounds
There's a budget GeForce GPU selling in China that not even Nvidia knew it made — RTX 4010 turns out to be a modified RTX A400 workstation GPU
How to enable XMP to improve RAM speeds
-
ZolaIII Just to point out how CPU clocking logic effect busses on Qualcomm SoCs. For instance if 1 core CPU frequency fell down under the minimum frequently than is tied to max bus frequency it will narrow & memory bandwidth & this will impact GPU performance badly under GPU intensive tasks. For me it looks like that on-demand scheduler is working more as it should under 5.1. Including patch sets from Linux kernel 3.12~3.21 (on demand to use more mid frequencies) should be just enough to address performance regressions still savings (even litle more) juice. They should really disable file encryption on any ARM V7 build. Switching to last stable GCC should increase user experience greatly, it's funny they still use 4.6. To address possible fluctuations & determine real impact of changes do the tests again with performance governor & disable MP decision (hot plug) for GPU tests.Reply -
theusual Be sure to upgrade 'Android System WebView' through Google Play as well as for me it didn't upgrade automatically and was causing app issues.Reply -
Plyro109 Sorry. Browser seems to be autofilling and submitting in every comment thread I visit.Reply -
Tracy Kohler Get that stupid bar off the top of my screen please! It takes up a whole INCH of screen space (and vertical space is LIMITED already on this wide CRAP they call monitors today).
I guess I'll have to come up with a way to kill it and still be able to navigate, other than scrolling. Go back to pages with a bar at top or bottom for index. While your at it FIRE the guy/gal who decided an inch of real estate on a monitor is OK to block all day. He/she will only piss off users over and over (hired from win8 team?...LOL). -
musical marv
Why do you say Loliipop sucks?15881932 said:TL, DR : Lollipop s*cks! next update please...
-
musical marv
Back Up what you post here and do not ignore it.15881932 said:TL, DR : Lollipop s*cks! next update please...
-
endeavour37a I thought Tom's was a place we could have opinions and points of view we could share and express freely, how does one back up what they like and don't like? I sort of like 5.0 but it's just fine if some else does not, I ignore a lot of stuff myself.Reply