yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] UTXPHANT0M:
So i went to test out the Nexus 6 at the T-Mobile store, The phone is indeed very snappy. Couple of things i have noticed:

1. Apps were not slow to open, given that they were all Google Apps. I couldn't download any games or third party apps so i couldn't mess with that.

2. I did test powering down the phone, waiting for about 10 - 15 seconds before powering on. It took for me 30 Seconds for the phone to power on. Now i heard other people testing this say it took well over that but that was not the case for me.

3. Also i did noticed the phone did have update available, a pretty big one at that! The downloaded i saw was over 192 MB in size! I wanted to downloaded it but it will not allow since i was on T-Mobile service; not WiFi.

4. Phone is pretty BIG but for me 6'8 with big hands, It felt natural to me it was also a bit slippery. I will be definitely putting a case on this phone for sure LOL :)

For the 20 minutes i had to test the phone i was not disappointed. I cannot wait for mine to come in so i can have more time with it!

P.S.

Sorry for the grammar errors if there are any :D
[Nexus 6  General] kusuriurikun:
That would match pretty much my own experience getting to play with a Nexus 6 live at a T-mo store--smooth operation, the phone is a Sasquatch-phone but that was expected and I use my phone with both hands (and primarily use it for the non-phone bits :D)

Of note, the person did pretty much explicitly note to me that sales had been delayed until the 19th due to a "firmware update" to be pushed, which hints to me that they do have a bugfix for the Starting Lag Issue.

(At any rate it's still gonna be an upgrade for me, considering I've been using a GS3! :D)
[Nexus 6  General] doitright:
If some people are too stupid to do something as simple as this, then they are too stupid to (a) notice the performance impact of encryption, (b) decide for themselves whether it should be encrypted.

Therefore my argument is perfectly valid.

---------- Post added at 05:03 PM ---------- Previous post was at 04:58 PM ----------

Having a 64 bit processor will have a MASSIVE impact on encryption.

---------- Post added at 05:13 PM ---------- Previous post was at 05:03 PM ----------

I can guarantee that in a *single threaded* process, THAT 64bit processor can perform crypto calculations 4 times as fast as SD805, which is interestingly similar to the speedup shown by the benchmark numbers. SD805 60 MB/s, Tegra4-64bit 280 MB/s. Little more than 4 times actually, but consistent when you factor in other differences between the devices.

---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------

I suspect that if the n9 was using hardware acceleration, its encrypted performance would be a lot closer to its unencrypted performance.

---------- Post added at 05:20 PM ---------- Previous post was at 05:15 PM ----------

Its actually amazing how many updates Google has already issued for 5.0.

The AOSP git tree is already tagged at 5.0.0_r6 --- that means the 6th revision of 5.0.0.

---------- Post added at 05:28 PM ---------- Previous post was at 05:20 PM ----------

Did that 60 MB/s review test the 32 or 64 GB version?

There are two ways to achieve double the storage space; double up the number of chips, or use twice the SIZE of the same number of chips.

Having double the chips can potentially double the read/write performance by effectively raid0'ing across the two.

Having a chip that is twice the capacity can even do the same thing internally.

Either way, the two versions probably do NOT have the same storage performance characteristics.
[Nexus 6  General] Unconn:
You shuld have thethered it to your phone's WIFI and downloaded the update for them. Then you could have tested the before and after for us. ;)

Intersting point, but I have never heard of this sort of performance difference in previous phones that have two storage sizes. I am not saying NAND performance improvements did not happen via some sort of memory striping, like in RAM, I am just saying I never heard of it.
[Nexus 6  General] Prod1702:
Just got the demo at the T-Mobile store I work in. The nexus 6 boots faster then my M8 running 5.0 GPE by about 5 to 10 secs. My M8 is not running Encryption. I also have done the 198mb update to the phone.
[Nexus 6  General] Ph0enix.:
SSD NAND

Solid State Drive (SSD) has the same behavior, when you do stacking/combination the controller can combine (not perfectly) the two individual speed of the NAND to achieve better read and write. Example if one MLC 128Gb (16GB) NAND chip is rated 533Mbps (66MBps), we need two NAND chips for 32GB set-up. Running the chips parallel to saturate the bandwidth is how we see better read and write performance due to two is better than one working by-itself with an 66MB cap. More NAND memory would be used for the 64GB set-up, would be nice if Fixit has one.
[Nexus 6  General] blair287:
This slow app opening is the only thing putting me off buying this as an upgrade to my note 3.
[Nexus 6  General] Xileforce:
I just tested my note 3. On latest stock with stock kernel. Sequential read is 100.44 and sequential write is 24.06...is something wrong with my phone? I guess I will be pleseantly surprised by the nexus then...
[Nexus 6  General] jkc120:
There's a boot image that has force encryption off. Hoping someone takes the time to test with and without!

---------- Post added at 08:03 PM ---------- Previous post was at 07:42 PM ----------

Well someone did it! Nearly 3x faster for reads from the looks of it. http://imgur.com/DquRHEo This means the SD805 HW encryption is either not working at all or is very poor.
[Nexus 6  General] Xileforce:
This is great news!
[Nexus 6  General] digitheatre:
with encryption

without encryption

read 188 MB/s

write 77 MB/s

this is very good .. much faster than others.. but damn can't beat the MotoX READ

while the WRITE ...Nexus6 is superior without encryption.. even already surpass others with encryption on.
[Nexus 6  General] italia0101:
Some more results without encryption

http://imgur.com/kce0rHO

http://i.imgur.com/0R9KxoK.png
[Nexus 6  General] gogol:
If that's Nexus 6 ... I meant, WTF! I don't want that f*cking encryption!

I have never encrypted my phone, and I don't live in the United States ffs ...

People probably afraid of NSA crap, but I don't care!

Google should give us option to NOT encrypt the Nexus 6 ...
[Nexus 6  General] dazed1:
WTH, WTH, 330 MB/s?????? is this real?
[Nexus 6  General] gtalum:
Seems to be, and it absolutely destroys Note 4 and iPhone 6. :highfive:
[Nexus 6  General] dazed1:
LOL!
[Nexus 6  General] robikonobi:
Androbench results are not reliable (yet) in lollipop. See anandtech's latest analysis which shows that nexus 6 sequential read without encryption is 131mb/sec.

http://anandtech.com/show/8725/encryption-and-storage-performance-in-android-50-lollipop
[Nexus 6  General] biggiestuff:
Hopefully there will be an elegant way to disable encryption w/o having to flash anything. Not that flashing something is that difficult but something where you can just flip a toggle would be nice.
[Nexus 6  General] StrizzMatik:
Anyone got a link for the unencrypted boot.img?
[Nexus 6  General] jeffreii:
http://xdaforums.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
[Nexus 6  General] Ballastatuz:
How is it no reliable when they got an official rom from moto?
[Nexus 6  General] gtg465x:
He said AndroBench (a benchmarking app) is not reliable, not Anandtech is not reliable.
[Nexus 6  General] xPXGx:
I decrypted mine last night. Very easy to do.
[Nexus 6  General] ryude:
Here's my nexus 6 benchmark from androbench. Not sure if it is correct or not, but i do notice stutters and slow app loading.
[Nexus 6  General] TheSopranos16:
Ok so I've read through this thread as well as the one describing the steps to remove encryption. Clearly, encryption is causing the bad read/write performance. The only explanation for this is that its being done in software instead of using the 805's hardware.

So, is this something Google can fix via software? By fix, I mean enable the encryption to be done using the phone's hardware. In one hand, I would think they would be aware of this issue by now and would be working to resolve it. On the other hand, I would have expected something like this to have been known long before the phones release. If they would release it with software encryption, maybe there is some reason they can't fix it?
[Nexus 6  General] italia0101:
Probably due to licencing issues with qualcom
[Nexus 6  General] MarkGbe:
I think the more important question is, is this really causing problems? I've read numerous posts of people saying that their Nexus 6 flys.. I realize this topic is on xda-devs, and benchmarks and geek stuff is the pretty much the basis of this site, but i'm thinking this whole thing is overblown.
[Nexus 6  General] TheSopranos16:
My N6 is the fastest phone I've ever used. My wife has a Note 4 and I did a few browser comparisons. My N6 loads the same websites significantly faster on every site I tested. I'm very happy with the performance so far.

My battery life leaves a lot to be desired though. 3-4 hours screen on time is all I'm able to get so far. Many others are reporting closer to 6 hours screen on time. When I look at the "Android System" and "Android OS" items on the battery screen, they are showing 30 and 40 minutes of "CPU Total". If I recall correctly, CPU Total is normalized to represent how long apps are using the CPU at 100 percent capacity. My phone has only been off the charger for 8 hours (and already battery is at 50% with only 1.5 hours SOT). I feel that CPU usage figure is way too high and I'm wondering if its being caused by the CPU having to work harder to handle the encryption overhead. That's the main reason I'm interested in a fix for this.
[Nexus 6  General] ggreenwood334:
My nexus 6 is screaming. Have noticed 0 lag so far. Received yesterday though. Apps are loading very fast. Camera opens quick. I'm living this. But if I could save battery. Bye bye encryption.
[Nexus 6  General] Baldilocks:
Encryption doesn't affect AnTuTu, as my score was 50015. Haven't tried Geekbench yet though.

Then I should try them both again if I ever remove the encryption.
[Nexus 6  General] :
These results are from my N5 flashed with stock 5.0 with encryption turned on.

I would expect the N6 to turn out way better results, given the updated chipset. I'm holding off on the N6 until the issues get worked out.
[Nexus 6  General] gtg465x:
Androbench gives wrong results in Lollipop. Use AndEBench.
[Nexus 6  General] mavronn:
http://www.androidheadlines.com/201...rs.html?utm_source=dlvr.it&utm_medium=twitter
[Nexus 6  General] phekno:
1. I don't understand why these drivers wouldn't be open source. I mean, I know there are plenty of drivers that AREN'T open source, but a hardware crypto module? Really? That's pretty low-hanging fruit to call proprietary, unless they're trying to avoid export restrictions, and even then, the software crypto probably has export restrictions.

2. I don't necessarily buy that you can't put proprietary drivers in to Android. There are plenty of cases where they simply get a binary blob from the hardware vendor for drivers. Is the Adreno driver open source? What about just about any of the radios?

Anyway, I'd like to think this could (and should) be fixed in a future release.

EDIT: I am not a kernel developer, but I think this is the Qualcomm Crypto Engine driver. I could be wrong though. It's definitely possible that the driver is there, but it's not being loaded or built, maybe. Again, I'm not a kernel developer, so take this with a grain of salt.

EDIT2: I did more digging and it looks like the driver specific to the Snapdragon 805 (Krait 450/APQ8084) is the qce50.* stuff. According to the kernel config file here the kernel was built with HW QCE support built in to the kernel, so it should be working. That is worrisome.
[Nexus 6  General] TheSopranos16:
So you are saying that it might already be part of the kernel? Is it possible that Google isn't making use if it, even if its technical built into the kernel?

Or, is it possible that the Qualcomm Crypto Engine is terrible and is actually slowing things down this much? Do any other devices make use of the Qualcomm solution with any success?
[Nexus 6  General] phekno:
I *THINK* it's already in the kernel. I don't even have the device, yet (thanks, T-Mo). It could be that they're not using it, I suppose. It also could be that the driver implementation is bad and needs to be optimized or something. I don't know if there are other devices that use this hardware. Again, I'm not a kernel developer, and I'm not really sure where to even begin looking to see if they're using it or not.
[Nexus 6  General] italia0101:
This is " faux " the kernel developer : https://plus.google.com/109078966818501160423/posts/GUCEGZEKsfW
[Nexus 6  General] LLStarks:
It's definitely open source

https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/tree/drivers/crypto/msm?h=msm-3.10
[Nexus 6  General] mtucker:
Before I set her up, I unlocked the boot loader and removed encryption. Here is what I get with Andebench.

Comparing my results to what anandtech got on the N6 without encryption

http://www.anandtech.com/show/8725/encryption-and-storage-performance-in-android-50-lollipop

some of the speeds agree well. Others are way off.

anandtech 4KB random reads = 16.64MB/s with encryption off

Me 4K RR (read, random) = 14.48MB/s

This seems close enough

Now looking at 4KB random writes

anandtech = 2.85MB/s

Me WR (write, random) = 14.75MB/s

Those numbers don't agree.

anandtech 256KB sequential reads = 131.65MB/s

me 256K RS (read sequential) = 73.24MB/s

Not agreeing well again.

Am I reading these wrong?

Mine is from ATT, 32GB, Samsung listed for both eMMC and RAM

Matt
[Nexus 6  General] mjs2011:
So I have to ask, and I mean this with all respect, does this issue affect someone like me who has no interest in benchmarks rooting or roms but just wants the pure android experience? Basically, is this more of a geek issue or is the phone that slow with encryption?
[Nexus 6  General] knitler:
Nope. All you would maybe notice would be it taking a little bit longer to save a photo when it writes it after taking it vs a non-encrypted phone.
[Nexus 6  General] cobyman7035:
Where do I get the 5.01decrypted boot img file thx., tutorial link

Decrypt for longer battery times
[Nexus 6  General] TheSopranos16:
Has anyone ran any storage benchmarks with 5.0.1? Does the performance while encrypted get any better?
[Nexus 6  General] swapnme:
Encryption takes toll

I received my Nexus 6 64GB on Dec 16 '14, and well I booted in, ran benchmarks, checked the phone before I unlocked, installed custom recovery, rooted and then disabled encryption.

The ones with Antutu 5.3 are WITH encryption, running pure stock, factory condition with very minimal apps installed from play store. Android v5.0

The ones with Antutu 5.5 are WITHOUT encryption, disabled encryption but with same stock kernel with the switch off, running custom recovery, is rooted and has all my about 200 apps installed, and this was also taken after few days of use, so the benchmark is with more crude caches and data lying here and there. Android v5.0.1

The difference is quite substantial!!

Do thank if this was informative!!
[Nexus 6  General] biggiestuff:
Is there any way to flash decrypt without losing user data
[Nexus 6  General] xciton:
So, by using those numbers

18% speed penalty by using Encryption

22% speed gain by turning off Encryption

Not sure how that plays in real world usage, I would expect much less noticeable difference in practice.

I would have expected more than 18% penalty for soft encryption however. That may be acceptable for a bit more security should you loose your phone and don't want your personal data exposed (or a Cop/TSA dude sifting through it in the back room).

Would be nice if Qualcomm could play nice and release an API or library for the hardware encryption assist (assuming that's where the problem is and not Moto/Google).
[Nexus 6  General] merouleau:
From this line of the leanKernel feature listing, I infer that Qualcomm has already played nice and that Google elected not to use the API:

"sw crypto drivers updated (to use arm NEON instructions) for better encryption/decryption performance. Sequential 180MB/s reads, 60MB/s writes (using dd)"

I haven't taken the time to reencrypt and test performance since I started running leanKernel, but it certainly seems promising. Here's the thread link: http://xdaforums.com/nexus-6/orig-development/kernel-leankernel-minimalistic-kernel-t2954316.
[Nexus 6  General] xciton:
Thanks for the hint.

I read that to mean he/she optimized the software crypto stuff to take advantage of some of ARM's specialized multimedia instructions (I beleive this is similar to Intel's MMX stuff back in the day). It's still not touching the 805's hardware crypto module unfortunately.

Judging by Qualcomm's co-operation with the open-source community in the past, they love their patents.
[Nexus 6  General] merouleau:
When I googled "arm neon crypto" I saw lots of references. I don't interpret the leanKernel developer's comment as having anything to do with multimedia - I think he used ARM Neon vector instructions to implement fast encryption and decryption just like everyone else does.
[Nexus 6  General] xciton:
Yea, nothing to do with multimedia, but you can use some of the additional NEON specific instructions for parts of the Crypto library (and thus speeding things up with hardware as he mentions).

In the end, we're still not taking advantage of Qualcomm's crypto hardware.

ARM NEON for reference: (mentioning multimedia "and stuff" as the prime usage)

http://www.arm.com/products/processors/technologies/neon.php
[Nexus 6  General] TheCryptoFairy:
Hey guys, kernel dev who got a shiny new Nexus 6 yesterday here.

(really technical post ahead, aimed at devs)

I took a stab at porting in the Vold instrumentation for the qualcomm crypto hardware into AOSP:

system/vold: github dot com/jamesr66a/nexus6vold/tree/hw_crypto

device/qcom/common/cryptfs_hw: github dot com/jamesr66a/device_qcom_common_cryptfs_hw

To my surprise, things didn't go as horribly wrong as I thought they would. I'm going to copy my latest commit message for the first repo since it explains most of what's going on:

Conceptually, vold is calling into the /vendor/lib/libQSEEComAPI.so library to set the encryption keys in the hardware keystore. This calls into the QSEECom Linux device driver (drivers/misc/qseecom.c) which prepares the data and makes a TrustZone secure monitor call to communicate with the qualcomm Secure Execution Environment. I was hoping QSEE would do its job just fine, but the response code from the call above suggests it isn't. Reading online, someone mentioned that Qualcomm didn't release "binary blobs" to enable the crypto hardware and I suppose that meant the TrustZone image that handles key management. I sincerely hope that's not the case and we can get around it on the outside :) If any devs want to hack around on this and see if maybe there's something externally wrong that's causing this issue, feel free.

BTW, trying to encrypt the device with those patches applied just reboots my device; It doesn't seem to do any damage but of course I'm not responsible if it does :)
[Nexus 6  General] flyinj54:
Xllllszfo
[Nexus 6  General] TheCryptoFairy:
Here are some benchmarks I did this morning using dd and preventing caching

Sequential read

i dot imgur dot com/YwKTsB1.png

Sequential write

i dot imgur dot com/6Ej4iNU.png

Also, the crypto engine reports its stats in /d/qcrypto. A simple cat on the file within that directory shows me zeroes across the board after encrypting and running benchmarks, so we can say for sure now that the hardware isn't being used.
[Nexus 6  General] Magnet42:
I do think the memory storage sucks in the Nexus 6. That's the reason why it's slow.
[Nexus 6  General] Xileforce:
You must have dug for a long time to find this thread....the necro post is real...
[Nexus 6  General] SMARTPHONEPC:
Yeah that was some deja vu time travel there..:highfive:

I ultimately passed on the Nexus 6 when I had compared it side by side with the much brighter Note 4 with its removable battery buying it during a Best Buy online sale, then later I was impressed enough by the Moto X Pure's screen+speakers+form factor+price in Best Buy that I did get a 32GB on Amazon sale for $349 (1/2 the price of the Note 4) even if it didn't offer the removable battery I'd have preferred but could still pop in a 128GB card & last December got a Nexus 6P 64GB which offers a solid fingerprint reader with reasonable encryption speed.

I like them all & while the Nexus 6P may not be perfect it's the first Nexus that was compelling enough for me to want. I like having different backup handsets & I highly customize all my devices because I'm not a fan of the out of the box stock experience which at least Android offers..:good: I prefer unlocked devices but I'll check out http://www.technobuffalo.com/2016/03/22/galaxy-note-6-said-to-launch-this-summer-with-android-n/:cool:
[Nexus 6  General] dahawthorne:
Well, now that it's been resurrected... :)

I've used an N5 & N6, in both encrypted and unencrypted forms, and I've never noticed any particular slowness or lagging.

On the other hand, after my wife lost her phone a couple of months ago to a thief (from a charity shop where she was volunteering, for god's sake...), it gives me the creeps to think that some filthy lowlife piece of dog excrement was able to see our photos and maybe other stuff (it was at least PIN-protected).

So... my vote goes to encryption. Bite the bullet, people, and I'll bet you'll notice nothing except the peace of mind that comes with data security.
[Nexus 6  General] simms22:
encryption on the n6 with android 5.0, it was a little slow. that said, with android 6.0+, encryptuon finally performs as it should.
[Nexus 6  General] najoor:
You will also notice about 3GB (12%) of internal storage lost to encryption on a device with limited storage that does not have external SDcard capability.
[Nexus 6  General] SMARTPHONEPC:
Good to know as I have some devices not on 6.0+ yet..

Did her smartphone have a microsdcard that was being utilized (unencrypted)? Do you think they'd break the PIN lockscreen?

Just curious what thieves do with smartphone's that are unencrypted with PIN-password lockscreen enabled vs totally encrypted? (I'm always surprised when people hand me their smartphones without any lockscreen enabled)

While I've always had PIN-password lockscreens I used to have smartphones with microsdcards in without encryption because I'd want to easily pop it out & in my PC but obviously a thief could do the same so I eventually encrypted it at an inconvenience to me.. Also curious what encryption people use on their PCs & external hard drives as well as if there is any encryption that can be utilized on their microsdcard smartphones that can be easily used on their PCs?

-Thnx:cool:
[Nexus 6  General] najoor:
If the phone is just password protected but unencrypted there are many possibilities to get into it. For example with an open bootloader you can just boot with a different image and mount the internal storage. Or if there is custom recovery such as TWRP installed on the phone, regardless of the bootloader status, you can boo tinto recoery and access the internal sotrage via USB. These are just two ways that my simple mind came up with on the fly. I am sure there is a lot more that a shrewd hacker can do with an unencrypoted phone.