Android 17 Beta 4 Is Here, and the Stable Release Is Almost in Sight
Google dropped Android 17 Beta 4 today, April 16, and the label that matters most is the one attached to it: this is the last scheduled beta of the cycle. That designation means the platform is essentially done cooking. The APIs are locked, the feature set is final, and what remains between here and the stable release is polish, testing, and the kind of quiet confidence that comes from knowing nothing critical is left to change. A mid-2026 stable release is looking very much on track, consistent with how Android 16 landed last June.
Beta 4 is available as an over-the-air update for everyone enrolled in the Android Beta Program, and it covers a wide device range stretching from the Pixel 6 all the way through the entire Pixel 10 lineup including the Pro Fold, the 9a, the Pixel Tablet, and the original Pixel Fold. The build number is CP21.260330.008. If you are already enrolled, the OTA should find its way to your device. If not, enrollment through Google's Beta Program is the quickest path in, with manual sideloading via factory images available for those who prefer the direct route.
Unlike Beta 2 and Beta 3, which delivered the heavier feature payload including the new desktop multitasking tools and large-screen orientation enforcement, Beta 4 is deliberately lighter on new user-facing additions. That is appropriate. Platform stability was declared at Beta 3, which means the development focus has shifted toward ensuring that the existing feature set is solid, consistent, and ready for the billion-plus devices that will eventually receive the final build. The biggest new introduction in Beta 4 is app memory limits, and it is worth understanding what that actually means. Android 17 will now enforce RAM caps on applications relative to the total memory available on each specific device, rather than applying a single threshold across all hardware. The intent is to prevent any single application from consuming a disproportionate share of system memory to the point where it causes UI stuttering, accelerated battery drain, or forces the OS to kill other background processes to compensate. Google has been careful to set these limits conservatively for now, targeting the genuine outliers rather than imposing aggressive constraints that would affect normal application behavior. Developers whose apps are killed by these limits will see the reason flagged in ApplicationExitInfo.getDescription as "MemoryLimiter," giving them a clear diagnostic signal to work from.
The other notable addition in Beta 4 is Post-Quantum Cryptography, a security hardening measure Google previewed weeks ago that arrives in this build as promised. PQC upgrades Android's cryptographic foundations against the class of attacks that sufficiently advanced quantum computing could theoretically enable in the future. It is a proactive security investment rather than a response to any immediate threat, and it is exactly the kind of infrastructure-level work that belongs in a late-cycle beta where it can be validated without the noise of feature development happening around it.
On the bug fix side, Google has addressed several issues that accumulated community attention across the Beta 3 period. A fix resolves a problem where webpage URLs were being automatically appended when sharing screenshots from the capture preview, resulting in unintended links being bundled with shared images. An accessibility regression that caused devices to become completely unresponsive has been corrected. The media control widget, which had been known to disappear or fail to navigate between multiple simultaneous active media sessions, has been stabilized. Dream services, which power screensaver and ambient display functionality, had been incorrectly processing key events and failing to execute certain lifecycle callbacks correctly, and that too has been addressed. On the user experience side, the Save button that had been removed in an earlier build makes its return in Beta 4, which will please anyone who noticed and complained about its absence.
A few small but pleasant user-facing touches arrived as well. The empty notification shade now displays "You're all caught up" with a trophy icon instead of the flat "No notifications" text that has been a fixture for years, a minor quality-of-life change that reflects the kind of attention to small moments that characterizes a mature release cycle. The Android 17 Easter egg, a tradition Google has maintained across every major version, also makes its appearance here for the first time.
With Beta 4 now in the hands of testers and the API surface fully locked, the runway to stable is short. Google I/O 2026 in May will likely serve as the broader consumer-facing announcement moment for Android 17, with the actual stable rollout following in the weeks after. For developers, the guidance is clear: final compatibility testing should be happening now, and any SDK or library updates needed to support Android 17 targets should be published promptly to avoid blocking downstream app developers from being able to ship against the new platform. The finish line is close.
