Expectedly, there are a handful of new features debuting with Android 12. This document allows OEMs to prepare themselves for future hardware launches. Failing to meet the requirements mentioned in the CDD could result in the manufacturer failing the Google Compatibility Test Suite, thus making them ineligible to use Google’s apps and services. A bulk of the changes outlined in the new CDD don’t have a major impact on the manufacturers. However, Google is officially introducing a “performance class” to define Android smartphones and tablets. This was originally showcased with Android 12 Beta 1, but the document goes a step further by offering a definition for Android 11 Performance Class as well. Android 11 and 12 are mentioned as Performances Classes R and S, respectively on the CDD.
Android 12 Performance Class devices need to have at least 6GB of RAM
Google said that each Android release will have its own performance class, allowing app developers to determine the capabilities of a phone or tablet. There are minimum hardware requirements for each Android performance class, including future releases. Here are some of the requirements for Performance Class 11: 100MB/s sequential write, 10MB/s random write, 200MB/s sequential read, and 25MB/s random read performance 6GB of RAM 400 dpi and 1080p display resolution 12MP rear camera with 4K 30 fps recording 4MP front camera capable of 1080p 30 fps recording Performance Class 12 requirements: 120MB/s sequential write, 10MB/s random write, 250MB/s sequential read, and 40MB/s random read performance 6GB of RAM 400 dpi and 1080p display resolution 12MP rear camera with 4K 30 fps recording 4MP front camera capable of 1080p 30 fps recording We’ve only listed out a handful of the key requirements above. It’s worth noting that the minimum requirements for both 11 and 12 performance classes remain mostly unchanged barring the storage read/write speeds. Although these performance classes are defined for upper-tier phones, they will also help app developers make their apps compatible with lower-end hardware. Additionally, Google is also including a recommendation to ensure the touchable area of the under-display fingerprint scanner doesn’t come in the way of the three on-screen navigation buttons. Device manufacturers will also have to ensure that the camera and microphone indicators are visible when apps are accessing them. You can check out the entire CDD here.
