[Nexus 9 General] doitright:
Ehm... OpenGL vs OpenGL ES.

The version numbers on them **DO NOT MATCH**.

ES is the "mobile" OpenGL.

OpenGL ES 3.1 matches against OpenGL 4.5.

---------- Post added at 02:55 PM ---------- Previous post was at 02:30 PM ----------

You aren't understanding.

Lock and crypto are two separate things. Being locked does not have any impact on whether or not the encrypted data remains encrypted.

The ONLY attack vector on the crypto that *may* make things easier on an unlocked bootloader, is compromising the NON-ENCRYPTED system partition, to, for example, install something (to the system partition) that provides remote access *once the device is back in the owner's hands and therefore has the crypto pass in memory*.

You don't *need* a root or privilege escalation attack against Android to unlock or relock the bootloader without wiping the userdata partition. There are tricks available at the bootloader level to do that. I'll give you a hint, which is not even half the story: the WIPE part of the unlock process involves rebooting to recovery with a wipe command. Oddly, it doesn't do this directly by a bootloader format. That means that the WIPE can be prevented by simply powering it off at the right moment, which is pretty easy to time, if you have the back cover off and your thumbnail under the power cable plug.

A very basic concept for computer security is *physical* security. If a device is used for sensitive information (the definition of which varies...), ANY time the device leaves your PHYSICAL control, you MUST ASSUME that it has been compromised in some manner, which could be as elegant as installation of something to the unencryped system partition, or something as crude as having a data logger chip installed somewhere under the back cover.

No matter what kind of bootloader barriers the device has, a sophisticated and well equipped hacker can make quick work of getting around it.

As a direct example, if you had a laptop that was encrypted in the same way as Android devices are, i.e., the "operating system" is not encrypted, but the userdata is... i.e., encrypt the /home and /var partitions, leave everything else unencrypted... and you happen to have a bios password set... how difficult do you think it would be for a hacker to alter a configuration file in /etc? The answer is TRIVIAL, since all he would have to do is pop out the hard disk and connect it to another system, mount the partition containing /etc, change the file, sync, umount, and reinstall the disk back to your laptop.

YOU CANNOT TRUST ANY DEVICE THAT HAS BEEN OUTSIDE OF YOUR PHYSICAL CONTROL.

In case anyone here with a Nexus device happens into a situation where their tablet DOES leave their physical control, especially if it has been in the hands of untrusted entity, the procedure to follow to reassert YOUR control is this;

1) Turn it off by press and hold power button.

2) Pop off the back cover and inspect for any "extras" that have been added. Remove any if found.

3) Boot straight to fastboot.

4) (optional, since the bootloader is signed) fastboot flash the factory bootloader.

5) (optional, if you did (4)) fastboot reboot-bootloader.

6) fastboot flash system, boot, recovery, vendor.

7) fastboot format cache

7a) (optional, if your userdata partition is NOT encrypted) fastboot format userdata

8) reboot normal

---------- Post added at 03:12 PM ---------- Previous post was at 02:55 PM ----------

Well, considering that oneplusone has a QUAD-core Snapdragon 801 that runs up to 2.5 GHz..... vs this DUAL-core nvidia 2.3 GHz..... the SD801 is going to obliterate the N9 in responsiveness and multitasking.

ButbutbutbutSIXTYFOURBITZ??!?!!!

Nope, sorry. 64bit is going to show its strengths primarily on very large number mathematics, the kind that you really don't do much of on mobile devices. General throughput on the Cortex-A57 (class) of CPUs will be better than on the A15 class (aka Krait) due to deeper pipelining and various other improvements in the general CPU design, not so much from being 64bit. Some of the benchmarks give an unfair advantage to the 64bit chips because they weight heavily on uncommon very-large-number math, which is basically the biggest reason why they seem to hang with the likes of SD805. For general mobile computing, the 32bit chips are still king. This will, of course, change... once we start to see large core count, high frequency, power efficient 64bit chips, like SD820.