If Your Nexus 6 has Performance Issues, Blame the Encryption That You Can’t Turn Off!

[Preach2k]

I do not know if you guys read this Article about Some Nexus 6's having performance issues.

During our Nexus 6 review, we noted that at times the device seemed to suffer from weird performance issues or hiccups that were unexpected, especially knowing that the device runs one of the newest and most powerful mobile chipsets on the planet, has 3GB RAM, and was optimized specifically by Google for Android 5.0 “Lollipop.” Some of our readers, along with others at reddit and XDA, tossed around the idea that maybe the performance hit was due to the fact that devices shipping with Android 5.0 do so with encryption enabled. That encryption could potentially put a damper on read/write disks speeds, which would cause performance hiccups.

The folks over at AnandTech had similar thoughts, so they reached out to Motorola in hopes of testing a Nexus 6 that didn’t have encryption enabled. With an unencrypted Nexus 6 in hand they found results that seem to confirm our fears – the default encryption in the Nexus 6 does indeed slow down read/write disks speeds, which is unfortunate, because you can’t turn it off.

During their tests with a Nexus 6 running without encryption enabled and another with it enabled (as it comes out of the box), they saw as much as a 63% decline in read performance and a 50% drop in write performance in the device with encryption enabled. In case those numbers didn’t register yet, I’ll help explain it. THAT’S A HUGE DROP.

So, why not just turn encryption off and see the awesome performance we are seeing on devices like the Moto X (Pure Edition) and Nexus 5? Well, because you can’t on the Nexus 6 or Nexus 9 – at least not at this time. You see, Google is encrypting new devices that ship with Android 5.0 at first boot. They are actually warning developers about this through their encryption documentation:

Caution: Devices upgraded to Android 5.0 and then encrypted may be returned to an unencrypted state by factory data reset. New Android 5.0 devices encrypted at first boot cannot be returned to an unencrypted state.

So, what is the solution? Well, there really isn’t one at this time, unless you are willing to do some tinkering with a boot.img over at XDA that disables the forced encryption. If you buy a Nexus 6 or Nexus 9, Google has it set to encrypt the device at first boot. AnandTech opines that this is an overreaction to the idea that Android isn’t secure, so Google is taking security to an extreme without thinking about users. Encryption on an Android device really only works if a user has enabled security at the lock screen. If you happen to not use security on your lock screen, then the encryption is pointless and causes you a performance hit that you didn’t ask for.

One would hope that Google will change their minds on the forced encryption, but you just never know. If anything, we would love to see them give users the option to unencrypt after the fact. At least give us an option.

Will this Be a Big problem for you?
Has this Changed Your Mind about the Nexus 6?

Source

 

[FoxKat]

I've seen so many problems with encryption, not performance-wise but to do with lost data (priceless pictures and video), that I say use encryption with extreme caution. In this case, you have no choice but to use encryption and that to me, spells great potential trouble for people and their data.

But to know that it also impacts performance by such a great margin makes me happy I got the Turbo with KitKat and that if Encryption should come with the update at least I can reverse it.

 

[Ollie]

I don't have this issue with my Note.

 

[Preach2k]

I don't have this issue with my Note.

You wouldn't. It looks like it is a Nexus 6 and 9 issue.


Sent from my GNote4 using Tapatalk!

 

[bkdodger]

All I can say that phone was flying when I played with it yesterday... We shall see when I get hands on.. XDA has a thread on turning it off.. Still early stages...

M8 tap'd

 

[Ollie]

You wouldn't. It looks like it is a Nexus 6 and 9 issue.


Sent from my GNote4 using Tapatalk!

So it's a lollipop issue? I have been encrypted in KitKat and previously Jellybean as well with no side effects.

 

[Preach2k]

So it's a lollipop issue? I have been encrypted in KitKat and previously Jellybean as well with no side effects.

It is affecting only the Nexus 6 and 9 Lollipop. Nexus 4 and 5 are not affected. So far the preview of Lollipop on the GNOTE 3 has not shown any issues.

Sent from my GNote4 using Tapatalk!

 

[pc747]

Bk, think once we truly get it in hand and use it daily we will see. But playing with it at a store is not going to give you the full picture.

Foxkat, remember android on the software side have not been known for its encrypted security which is why when you turn it on you notice issues. Google is trying to fix the issue on their side and they are at a point where they have to. With more businesses turning to galaxies and even droids the device needs to be able to eventually provide the same security known with blackberries. Google is working with the issue and I do not think we will see it perform buttery smooth until probably 5.1 lollipop. There is obviously more coding that needs to be worked out.

 

[Ollie]

It surprises me that Google devices, of all devices, would have this issue. Their encryption has been working great for years on Sammy devices.

I wonder what it is that they changed?

 

[Preach2k]

It surprises me that Google devices, of all devices, would have this issue. Their encryption has been working great for years on Sammy devices.

I wonder what it is that they changed?

Could it be something that Motorola added?

 

[Jonny Kansas]

The price we pay for security...

It'll be interesting to see if an update fixes this, or if xda can crack the code for people to shut it off.

When they advertised the phone and lollipop, I thought they said that encryption was "on by default," which led me to believe it could be turned off if the user wanted to. Strange that they would take that option out of the user's hands. Seems like a simple popup warning you that it's less secure/multiple "Are you sure?" pages would've done the trick to cover google's rear...

 

[Ollie]

The only reason Google defaulted it was so that they could equal Apple.

 

[Jonny Kansas]

The only reason Google defaulted it was so that they could equal Apple.

Still..."Be together, not the same". Allow the user to turn it off if they prefer. It's voluntary right now on my Note 4 to turn it on, so it must be possible.

 

[Ollie]

Sure it's possible. Probably not after you update to Lollipop though.

I'm curious as to whether the encryption retains a mandatory pin entry at the lockscreen or if they made that optional now?

Will everyone be pinning their lock screens now?

 

[Jonny Kansas]

Sure it's possible. Probably not after you update to Lollipop though.

I'm curious as to whether the encryption retains a mandatory pin entry at the lockscreen or if they made that optional now?

Will everyone be pinning their lock screens now?

That's a good question. Encryption is kinda useless if it's not secured with some form of authentication...