Android 15 Raises Minimum Storage Requirement to 32GB
Google is increasing the minimum storage requirement for Android devices starting with Android 15. To pass Google’s certification, all devices must now ship with at least 32GB of internal storage—up from the previous 16GB minimum set with Android 13 in 2022. Additionally, 75% of that storage must be allocated to the data partition, which houses preinstalled system apps, their data, user apps, and personal files.
While most flagship Android phones already offer 128GB or more, many low-cost models still ship with much less. In some cases, devices with just 16GB of storage struggle to offer a usable experience, as the Android OS and essential apps take up a large portion of that space. Google has made efforts to optimize Android for low-end hardware, but storage limitations remain a major barrier.
The new 32GB minimum applies not only to new devices launching with Android 15 but also to existing devices looking to upgrade. Without meeting this requirement, they won’t be eligible for the update.
Android 15 also introduces additional certification requirements, including mandatory support for Vulkan 1.3 in chipsets and a feature that allows telephony-enabled devices to share emergency contact information with emergency services.
Why Google’s 32GB Requirement Only Applies to GMS-Certified Devices
While Google is raising the minimum storage requirement for Android 15, it cannot legally stop manufacturers from building phones with less than 32GB of internal storage—provided those devices run the open-source version of Android (AOSP). That’s because AOSP is governed by open licensing terms, which do not permit such restrictions.
However, the story is different for devices that ship with Google Mobile Services (GMS). Since GMS is proprietary, Google can enforce stricter requirements, including the new 32GB minimum. These rules are detailed in the confidential GMS Requirements document, which outlines what devices must meet to obtain a GMS license. Most manufacturers follow these standards, as having a GMS license is essential—without it, devices can’t include key apps like the Play Store or Google Play Services, which are critical for user adoption.
Google’s goal in raising the minimum storage requirement is to improve the user experience on entry-level Android devices, which make up a significant portion of Android sales globally. More storage means more room for apps and system data, both for users and OEMs.
That said, more storage doesn’t necessarily mean faster performance. Many low-end devices still use eMMC storage chips, which are slower than the more modern UFS alternatives. But given the higher cost of UFS chips, eMMC remains the more viable choice for budget hardware.
What other new Android 15 requirements are there?
Android 15 Adds Emergency Contact Sharing Requirement for GMS-Certified Devices
Beyond the increased minimum storage requirement, Android 15 introduces several new conditions for devices seeking Google Mobile Services (GMS) certification. While most of these updates are backend changes or apply specifically to chipset vendors, one new feature directly affects user safety.
Google now requires that cellular devices launching with Android 15 or later include the option to share emergency contact information with the system’s Emergency Location Service during emergency calls. If users choose to opt in, this feature allows their emergency contacts to be shared along with their location data when contacting emergency services. This can help responders reach out to a user’s designated contacts for updates or assistance during critical situations.
To safeguard privacy, Google mandates a clear explanation of what data may be shared, and ensures that no contact information is shared unless the user explicitly opts in.
Android 15 Tightens Graphics Requirements with Vulkan and ANGLE Support
Another major addition to the Android 15 GMS certification requirements focuses on graphics performance. Starting with Android 15, all new chipsets must support Vulkan 1.3 or higher and comply with both the Android Baseline 2022 profile and the Vulkan Profile for Android 15.
In addition, all Android 15 devices—excluding Android Go Edition models—must include ANGLE libraries and provide developers with a way to use them as alternatives to the native OpenGL ES driver. ANGLE (Almost Native Graphics Layer Engine) translates OpenGL ES API calls to Vulkan, ensuring compatibility with older apps and games on devices that no longer ship with native OpenGL ES support.
Google clarifies that ANGLE support doesn’t have to be enabled by default in Android 15, but it will be required to be enabled by default starting with Android 16.
These new graphics-related requirements align with Google’s broader strategy. The company recently declared Vulkan as the official graphics API for Android, part of its push to strengthen Android as a gaming platform. By gradually raising the bar through GMS certification, Google is ensuring that future Android devices deliver better and more consistent graphics performance.
Android 15 Expands Low Memory Optimization Requirement to 3GB RAM Devices
The final notable change in Android 15’s GMS certification requirements involves a subtle shift in minimum RAM expectations. Under Android 14, devices with 2GB of RAM were required to enable Android’s low memory optimizations—typically associated with Android Go Edition—to receive certification.
With Android 15, this requirement has now been extended to devices with 3GB of RAM. While devices with 2GB and 3GB must use these optimizations, OEMs currently still have flexibility with 4GB RAM devices. However, Google may enforce low memory optimization for 4GB devices in future Android versions.
This move reflects Google’s effort to raise the baseline for Android performance. Since memory directly affects how smoothly devices run, increasing the minimum RAM expectations is a welcome shift that could lead to more consistent and user-friendly experiences, even on entry-level hardware.
Other Android 15 Requirements: Technical Notes for Chipset Vendors
While most Android 15 requirements won’t impact everyday users, Google has included several lower-level updates that apply primarily to chipset vendors. For completeness, here’s a summary of the additional changes:
-
Context Hub Feature Flag: Chipsets that set
ro.board.first_api_levelorro.board.api_levelto 202404 and support CHRE (Context Hub Runtime Environment) functionality must declare theandroid.hardware.context_hubfeature. -
ID Attestation: Chipsets with the same API level identifiers (202404) must support ID attestation.
-
Security & Provisioning Requirements: Devices launching with Android 15 must also meet several security-related requirements if supported by hardware:
-
StrongBox implementation
-
Remote Provisioning v3 HAL interface on the application processor (AP) that supports the primary KeyMint instance
-
KeyMint 3.0+ HAL interface in secure hardware with performance on par with the AP
-
Android Profile for DICE support for the Remote Provisioning HAL
-
-
Vendor APEX Packaging: Chipsets launching with Android 15 support are strongly recommended to package each HAL (Hardware Abstraction Layer) in a vendor APEX. This will become mandatory in Android 16.
-
Bluetooth Hearing Aid Support: Devices supporting Bluetooth 5.0 or higher are strongly encouraged to support hearing aids over Bluetooth LE using the ASHA protocol. This, too, will be mandatory in Android 16.
-
Widevine L1 & Secure Decoding: Devices are strongly recommended to support Widevine L1 and provide a secure decoder for each hardware-supported codec (AVC, HEVC, VP9, AV1). These requirements will also become mandatory in Android 16.
-
Remote Key Provisioning: The Remote Key Provisioning Mainline module is now strongly recommended to be preloaded on Android 15 devices. This will be a requirement in Android 16.
Leave a Reply