Google today released an updated version of its Compatability Definition document for guiding phone manufacturers to run Android Marshmallow on their handsets. There are three major highlights of the 74 page document related to full disk enrcryption , requirement of fingerprint sensors and Doze mode settings.
Google has now made default enabling of full disk encryption mandatory. As stated in the document –
For device implementations supporting full-disk encryption and with Advanced Encryption Standard (AES) crypto performance above 50MiB/sec, the full-disk encryption MUST be enabled by default at the time the user has completed the out-of-box setup experience.
Secondly, Google has released some guidelines for manufacturers for implementing finger print sensors in Marshmallow. These guidelines have to be followed to ensure that sensors work with Marshmallow and any apps that use its API. These fingerprint sensors are already working in Nexus devices and it is upto OEMs to include them in their android devices. They can be used for unlocking a device, to authorize transactions in the Google Play store, sign into third-party apps, and for checking out with Android Pay.
Third and perhaps the most important one is related to the power management of an Android device through Doze mode which allows a device to use fewer resources when left unattended so it automatically goes into a deep sleep state to conserve power. There are app exceptions which can bring the device out of Doze mode automatically for example an alarm app can wake up the phone provided it has sufficient battery power.
Google has now made it mandatory for manufacturers to show the list of such exempted apps to users for having a better control over their device battery power.
All apps exempted from App Standby and/or Doze mode MUST be made visible to the end user. Further, the triggering, maintenance, wakeup algorithms and the use of Global system settings of these power-saving modes MUST not deviate from the Android Open Source Project.
The new compatibility changes point towards the fact that Google is now trying to limit the intervention of manufacturers to customize the stock Android however they want.
To go through the complete document of updated Compatibility Definition, follow this link.