In a significant move to enhance performance, Android is transitioning to a 16 KB page size, a shift that will soon be mandatory for applications in the Google Play Store. This change marks a departure from the long-standing 4 KB page size that has been the foundation of Android’s architecture.
Performance Enhancements
The rationale behind this transition lies in the efficiency gains it offers. Memory management units (MMUs) in CPUs play a crucial role in translating program addresses to physical memory locations, operating on a page-size basis. With a larger page size, the system can reduce the overhead associated with memory bookkeeping, allowing for a smoother user experience. This means that applications can deliver better visuals, enhanced gaming experiences, and overall improved functionality.
With the introduction of Android 15, the operating system has been refactored to accommodate this larger page size, ensuring that applications can leverage the performance benefits on newer devices. The Pixel 8 and Pixel 9 series are currently available for testing these enhancements, which promise notable improvements such as:
- Faster app launches: Users can expect improvements ranging from 3% to 30% across various applications.
- Improved battery usage: An average gain of 4.5% in battery efficiency is anticipated.
- Quicker camera starts: The camera can launch 4.5% to 6.6% faster.
- Speedier system boot-ups: Android devices will boot approximately 8% faster.
As of November 1, 2025, Google Play will enforce a requirement that all new apps and updates targeting Android 15 and above must support the 16 KB page size. This mandate is designed to ensure compatibility with future Android releases.
Without recompiling to support 16 KB pages, your app might not function correctly on these devices when they become more widely available in future Android releases.
Google has indicated that a substantial number of apps are already compatible with this requirement, suggesting that many developers may find minimal adjustments necessary. The compatibility landscape is as follows:
- Apps without native code should remain compatible without any changes.
- Apps utilizing libraries or SDKs with native code may need updates to compatible versions.
- Apps containing native code might require recompilation with a more recent toolchain and a review for any incompatible low-level memory management code.
Developers can verify memory page size support through the Play Console, ensuring their applications are prepared for this upcoming transition.
