Google released the latest Android compatibility definition file (CDD) today, It specifies two hard requirements for mobile phone and tablet manufacturers to adapt Android 6.0 system to old devices and new Android 6.0 devices: the Doze power saving mode of Android 6.0 and the default full disk encryption must be retained in the system, and they are not allowed to be excluded from the Android open source project (AOSP).

The first is the Doze power saving mode, commonly known as the snooze mode. In Android 6.0, the system can let the application enter the sleep state after being unused for a period of time, and only keep push messages and synchronize at a specific time (aligned wake-up). This can make the equipment occupy less system resources when not in use, so as to achieve the effect of power saving.

However, this is only for non Google applications. Google services and Android device manager will not be affected by the Doze mode. However, Google's service has always been a major power consumer. I wonder if users have any comments on this. In addition, device manufacturers are likely to add their built-in applications and services to the white list of Doze mode when adapting Android 6.0 to their devices.

The other is that Google restricts device manufacturers from modifying their functions, which is the full disk encryption function. In fact, this function was applied to Nexus 6 when Android 5.0 was just released last year. All Nexus 6 phones with Android 5.0 system pre installed in the factory have the full disk encryption function enabled by default, and other Android 5.0 devices are required to enable this function by default. As a result, the device's read/write speed drops significantly. Google had to make a concession and change the default to "strongly recommend" to enable the encryption function. But Google said at the time that it would make it a requirement to enable full disk encryption by default in future Android versions, which came unexpectedly fast.

In addition, Android 6.0 adds native fingerprint authentication function. Android 6.0 will include native fingerprint authentication. The new feature allows users to log in to all supported applications on Android devices without entering a password. The new generation Nexus mobile phone is also equipped with fingerprint identification function, but the device manufacturer must comply with Google's requirements to ensure that the fingerprint sensor is compatible with Android 6.0 and the application calling its application program interface. That is to say, at present, no matter Samsung, Sony, HTC or domestic Android mobile phone manufacturers must comply with Google's requirements to ensure that fingerprint sensors are compatible with Android 6.0 and applications that call its application program interface.

Since the birth of Android system, Google has been trying to strengthen its control over Android, including that Google has replaced the original Android open source project (AOSP) with a large number of its own applications on Android system before For applications, manufacturers are also required to carry the latest Android system on newly launched devices, and this time it is required to retain the two functions of Doze power saving mode and default full disk encryption in Android 6.0. It is all a manifestation of Google's tightening of Android system permissions. On the one hand, Google will help reduce the fragmentation of Android system and further unify the experience of Android system.

If you want to know more about Android 6.0 Marshmallow, you can follow the article we shared earlier“ ”。