Google halves Android open-source cadence

Google’s Android ecosystem changes are drawing a broader backlash than a single social post. The immediate complaint on May 22 centered on claims that Google is effectively slowing how often Android’s open-source code is exposed in easy-to-track public release branches, while tightening rules around who can distribute apps outside Google Play. Official Google pages do not use the phrase “halves Android open-source cadence,” but they do show a model built around release branches, a recommended `android-latest-release` manifest, and a developer-verification system that starts affecting user installs in September 2026. ### What exactly changed in Android’s open-source workflow? Google’s AOSP documentation now tells platform developers to use `android-latest-release` instead of `aosp-main` to build and contribute to Android. The AOSP site says that manifest currently points to `android16-qpr2-release`, which is a release branch rather than the always-moving main development trunk. Google’s public release pattern has long included big platform drops and quarterly platform releases, but the current documentation emphasizes the release branch lifecycle rather than promising a continuous, consumer-friendly public mirror of everything under active development. (source.android.com) The AOSP release lifecycle page says upstream code is published in the next release branch, and Google’s Android 15 and Android 14 launch posts each framed AOSP publication around a named platform release date. (android.googlesource.com) ### Does this mean Android is no longer open source? Google still publishes Android source code through AOSP. The AOSP homepage remains live, the public Git repositories remain accessible, and monthly Android security bulletins continue to say source-code patches are released to AOSP, in some cases within 48 hours of bulletin publication. The dispute is about timing and visibility, not whether AOSP exists. Developers criticizing the change are arguing that a release-branch model gives outsiders less day-to-day visibility into platform development than a more continuously updated public branch would. (source.android.com) That criticism is an inference from Google’s documentation and the public developer reaction, not language Google uses in its own materials. ### Why are sideloading rules getting pulled into the same argument? (source.android.com) Google’s developer-verification program widened the fight because it directly affects apps distributed outside Google Play. Google says apps on certified Android devices in Brazil, Indonesia, Singapore and Thailand must be registered by verified developers starting September 30, 2026, and it says the policy expands globally in 2027. (android.googlesource.com) Google says sideloading is “not going anywhere” and that developers and power users can still use Android Debug Bridge, or ADB, to install modified or unverified apps on their own devices. But the company also says unregistered apps will require either ADB or an “advanced flow,” adding friction that did not previously apply in the same way. ### How do Samsung and Xiaomi fit into this story? Samsung has not published an official U.S. support notice saying Odin is being shut down across its lineup. (android-developers.googleblog.com) The evidence circulating publicly is largely community discussion and third-party reporting, not a formal Samsung product bulletin. Xiaomi, by contrast, publicly states that unlocking the bootloader increases security risk, can invalidate warranty coverage, and is limited in some cases by account-based controls. (support.google.com) Xiaomi’s support pages say an account is limited to unlocking one device per month and warn users to avoid unlocking the bootloader unless necessary. ### What can developers actually verify right now? As of May 23, 2026, developers can verify three concrete points on official pages. (samsung.com) Google recommends `android-latest-release` for AOSP work, Google is rolling out developer verification now, and the first user-facing install restrictions begin on September 30, 2026 in four countries. Google’s next public milestones are already posted. The Android Developers blog says limited distribution accounts and the advanced flow arrive in August 2026, followed by the September 30 enforcement date in Brazil, Indonesia, Singapore and Thailand. (mi.com) (android-developers.googleblog.com) (android.googlesource.com)