David Burke, director of Android engineering for Google Inc., speaks about the new Android operating system named 'Marshmallow' during an event in San Francisco, California, U.S., on Tuesday, Sept. 29, 2015. (Photo : Getty Images/David Paul Morris/Bloomberg )
The latest revised version of the Android Compatibility Definition Document requires that a full-disk encryption should be enabled by default before the device's setup procedure.
The new version was released after the first trial that Google made earlier this year when it had also put into consideration a full device encryption for phones and tablets that currently run on Android 5.0.
A few months after the announcement, the giant search engine once again made headlines when it withdrew its decision and in turn strongly advised Android device developers to activate encryption as opposed to adding the feature as an obligatory requirement, according to Android Police.
The rationale behind the change could be as a result of performance problems brought about by the full-disk encryption that appeared too much for some gadgets to handle. As a result, Google allowed manufacturers to enable encryption as a default feature in optional clause.
However, Google likely requires once again full-disk encryption specifically on devices that launch with the latest Android 6.0 Marshmallow. According to Static Google User Content, Google states in the Android Compatibility Definition Document that "the full-disk encryption MUST be enabled by default at the time the user has completed the out-of-box setup experience."
The encryption requirement only covers gadgets that launch with the latest Android 6.0, implying that those who get the new Operating System through an update would be exempted.
Google also does not require users to set a lock screen beforehand, which could work against the security feature accompanying the encryption. Furthermore, devices without lock screens and are shipped with Android 6.0 Marshmallow are also exempted from the encryption by default.
Since having a secure lock screen is not a common choice among users, the company may only have succeeded in offering a better user experience at this point. Those who will eventually want to add a PIN or passcode to their lock screen should not worry about re-encryption either, exempting them from the time-consuming process.
