Google Decides Twice a Year Is Enough for Android Source Code!

Custom ROMs:Projects likeLineageOSandGrapheneOSmay struggle to integrate feature updates as quickly as before.
Transparency Concerns:Open-source advocates argue this move “moves Android behind closed doors” for longer periods.
OEM Advantage:Major partners like Samsung and OPPO often have private access, meaning the public AOSP delay primarily hurts smaller community-driven projects.

Monthly Security Remains Frequent

Crucially, security is not being throttled.

Monthly Patches:Google confirmed that monthly security bulletins will continue as normal.
Security Branches:Fixes will be pushed to a dedicated, security-only branch every month.
Separation:Feature code is now technically decoupled from the monthly vulnerability pipeline. This ensures that even if feature code is delayed, the devices remain protected against known exploits.

Conclusion of the Shift

While Google claims this helps simplify development, the move has stirred the developer community. By reducing public drops, the barrier to entry for independent forks of Android grows higher. 2026 will be the testing ground for this biannual model.