[Nexus 6 Q&A, Help & Troubleshooting] doitright:
Focus is a PHYSICAL MOVEMENT of the lens. No update will change the amount of time it takes to move the lens.

I congratulate you on finding a thread about an imaginary problem, and a "fix" for an imaginary problem.

There is a certain subset of people who will do anything, IMAGINE anything, to find a problem. Don't ask me why they are like that. Sucks to be them.

You can't do anything to increase the fuzzyness of an image, unless you actually stretch it larger. I.e., if it takes the same physical space on the screen, then increasing the DPI on the screen won't cause it to become more fuzzy -- it just won't increase in SHARPNESS with the display. Google has specifications regarding the dimensions of the icons, and these specifications have always included a "much larger" image than what will actually display on the screen. The icons actually get scaled down to fit. So really, don't worry about it. If you find an application with a ugly/fuzzy icon, complain to the application vendor, because they're the ones who made an ugly icon, not the platform.

I just can't stress enough, that this is a silly point to use to avoid a device.

---------- Post added at 06:03 PM ---------- Previous post was at 05:49 PM ----------

I *absolutely promise you* that they WILL NOT eliminate the encryption requirement. Those "android one" devices are... really really cheap. It is likely that they don't force encryption simply because they are not up to the task.

I CAN confirm that it does. There is no question at all. It is part of all snapdragon SoC's since about S4.

There are two sides to the use of encryption hardware with qualcomm SoC's; the first is the "blobs", and the second is the integration with Android and the Linux kernel. Specifically, qualcomm's hardware crypto requires changes both to the kernel (which is under GPL), as well as VOLD (which is under APL).

Obviously, to include the kernel part, that kernel part MUST be provided as source. There is absolutely no option here.

VOLD is the part of Android responsible for mounting and managing disks. It is under the Apache license, which means that technically speaking, it can be distributed without including source, HOWEVER, this is a Nexus from Google, which means that they really can't ship a blob in place of VOLD. It has to be possible to build VOLD from AOSP.

So here is what was going on; at the time that Nexus 6 first shipped, Qualcomm HAD NOT made the source for Kernel or Vold available on CAF. That made it *impossible* for Google to include, since they would have to provide kernel code on request, and require that AOSP VOLD actually build and work.

QUALCOMM HAS SINCE MADE THE SOURCE AVAILABLE!!!!

And, in fact, there are a number of devices for which CM actually builds and includes hwcrypto *right now*.

This isn't even a half solution, because even though it may seem to improve storage performance to an acceptable level, it has to nail the CPU while doing so.

Technically possible, but I *promise* you, it won't happen.

Most definitely CAN be used. No question about it.

You could disable crypto now, and let it encrypt when the update rolls around. Disabling forced-crypto does not prevent you from using crypto now or later.

Keep in mind that the test unit in the store gets abused.