The Google Nexus 6P Reviewby Andrei Frumusanu on December 16, 2015 8:00 AM EST
In terms of software the 6P is able to sport the latest Android 6.0 Marshmallow, courtesy of course of being a Nexus device. There’s not terribly much to say about the OS that hasn’t been said already by Brandon’s analysis in the review of the Nexus 5X. This is due to the fact that all Nexus devices come equipped with the same software experience, but also due to the fact that Android 6.0 offers very little front-facing changes.
I’ll openly admit that I’m not too much of a fan of the stock Android experience: Over the years Google’s stock Android has always been praised as the “pure” experience and how Android should be. I find this a bit unfortunate as I find there’s a lot of usability flaws in the stock. It’s the simple things that most other OEM skins add that I find the most lacking in stock Android, examples being the lack of an auto-brightness toggle in the quick settings or even having a brightness slider directly available in the notification shade itself which reduces the motions to get to the settings.
My biggest gripe however are the navigation buttons and Google’s lack of an option to reorder them. While I understand the design decision and logic behind having a back button on the left, it makes no sense in terms of usability for the majority of people that are right-handed. The back button is by far Android’s most used navigation button, so I found the Nexus 6P’s larger size to exacerbate the issue as I need to always change grip or stretch my thumb to able to reach it properly. Still having this huge ergonomics issue after this many years is basically inexcusable – the notion that it’s more intuitive to have it on the left is a poor rationale as “unintuitive” use-methods can be learned and taught, but my thumb stopped growing a long time ago and I imagine so did everybody else’s. Virtually all OEMs recognize this issue and either come by default with reversed navigation buttons or by at least offering the option to rearrange them. Here’s hoping that Google listens and adds this as a stock option for future Android releases, similarly how they did for many other past features that were pioneered by third-party vendors.
Ambient display is a great feature that takes advantage of the 6P's AMOLED screen. Every time you pick up the device it will show you a minimalistic greyed out view of your current notifications without having to press any buttons. The detection is a bit finicky and sometimes goes off too easily as I often saw ambient display trigger itself while the device was just laying steadily on my table, and also sometimes when you do want it to go off when you pick up the device it might decide not to. However when it does work it works well, and it also enables you to directly unlock the phone from there. I do wish the display period had been configurable as sometimes where you have a lot of notifications the screen will go back off before you can read all of them.
Other than some of the aforementioned annoyances, the stock Android experience is a good one. In terms of performance, there were some concerns that I’ll reiterate in the PCMark writing sub-test but otherwise the device is fluid as you’d expect it to be. I may be biased when saying this but I just don’t think stock Android is an “exciting” experience or a platform where we see lots of innovation. I’m aware that there are groups who vehemently adhere to Google’s design decisions, but for me personally it just doesn’t do it as it comes with too many daily usability regressions.
In terms of NAND storage, the Nexus 6P uses a Samsung eMMC module. In fact, this is the same “BGND3R” variant as found in this year’s HTC One M9. For testing I also ran the NAND benchmarks on an unencrypted data partition to be able to analyze Android’s full disk encryption overhead that is now obligatory for all new devices shipping with 6.0 Marshmallow.
As we can see the unencrypted numbers perform as expected and within range of the HTC One M9’s performance. The encrypted numbers which come as default with the device are the more concerning ones as we see a decrease in read performance of up to 84% and write performance decreases by 43%.
The Nexus 6P uses software decryption, accelerated by ARMv8 cryptography instructions. Google claims that this method is actually faster than using Qualcomm’s Snapdragon built-in SoC dedicated hardware crypto unit, which points out to a possible severe lack of performance and readiness on the part Qualcomm's SoC. We were curious to determine if this was solely an issue for Qualcomm and re-did some encrypted and unencrypted runs on the Note 5 and found that the overhead of encryption on that platform is very minimal, pointing out to that the degradation seems to be limited to Qualcomm's SoCs. It would be interesting to see if the Snapdragon 820 will be able to offer improvements in this regard.
In the end, the Nexus 6P’s out-of-the-box performance on the encrypted data partition seems very lackluster and it may affect application speed. One has to remember that it’s only the data partition that is encrypted, as we see no degradation on the internal or system partitions as they remain unencrypted.
The Nexus 6P comes naturally with 802.11ac WiFi in 2x2 MIMO configuration, all powered by Broadcomm's BCM4358 WiFi SoC. This is the same chipset found in other devices such as the Galaxy S6, so hopefully performance will be similar.
And indeed we see excellent WiFi performance from the 6P as we reach up to an average of 467Mbps, up there among one of the fastest WiFi implementations in today's smartphones.
Post Your CommentPlease log in or sign up to comment.
View All Comments
Olaf van der Spek - Wednesday, December 16, 2015 - linkWhat kind of system overhead? Do you know the details or are we just speculating?
hfm - Thursday, December 17, 2015 - linkIf like to see a deeper explanation as well. I think maybe just a larger percentage of the total is overhead, but I'm not sure.
Andrei Frumusanu - Sunday, December 20, 2015 - linkFilesystem overhead and crypto layer overhead. While not really related to the 6P, switching from ext4 to F2FS on the S6 will for example give massive boosts to random IO results.
zeeBomb - Wednesday, December 16, 2015 - linkAndrei, any word or news on a Meizu Pro 5 review? I know you kinda lost contact with them this year, but I mean...there has to be some type of workaround right?
twizzlebizzle22 - Wednesday, December 16, 2015 - linkUsing androbench 4.0.
256kb buffer with 4kb random.
I get 107MB/s seq read, 45MB/s seq write, 20MB/s rand read, 12MB/s rand write.
This is unencrypted, I ran this a few times. Any idea why there would be such a difference between your device and mind?
ChronoReverse - Wednesday, December 16, 2015 - linkWhat is your storage size and how full is it? I tried on my unencrypted 128GB 6P, running a custom ROM, with 30.6GB of data, using 64MB file size, 256kb seq buffer and 4kb rand buffer:
210 MB/s seq read, 47 MB/s seq write, 21MB/s rand read, 13 MB/s rand write
Looks similar to yours except my read is much faster.
twizzlebizzle22 - Wednesday, December 16, 2015 - linkI have 32GB model with about 40GB free.
I'm completely stock though and encrypted. I don't know why I wrote unencrypted in my other post. I meant encrypted.
twizzlebizzle22 - Wednesday, December 16, 2015 - linkDamn! 20GB free. Not my day.
So to clarify, the results I posted are completely stock, encrypted. If I leave it at default I get a MUCH higher read.
Lothsahn - Wednesday, December 16, 2015 - linkSame here... the numbers are puzzling. I have a 32 GB Nexus 6 (not 6P), and my numbers exceed that.
With AndroBench 4, I clicked start to run all tests after my phone had been fully charged and off for >1 hour. My speeds are:
17.5 MB/s Sequential Read
??.? MB/s Sequential Write (don't see a 256K WS)
6.7MB/s 4KB RR
6.8 MB/s 4KB RW
Completely stock, encrypted. 8.83 GB Free. Haven't wiped or reloaded the device since I purchased it when it was first released.
tuxRoller - Thursday, December 17, 2015 - linkNM:)