|
|
Log in / Subscribe / Register

Google will now only release Android source code twice a year (Android Authority)

Android Authority reports that Google will be reducing the frequency of releases of code to the Android Open Source Project to only twice per year.

A spokesperson for Google offered some additional context on this decision, stating that it helps simplify development, eliminates the complexity of managing multiple code branches, and allows them to deliver more stable and secure code to Android platform developers. The spokesperson also reiterated that Google's commitment to AOSP is unchanged and that this new release schedule helps the company build a more robust and secure foundation for the Android ecosystem.

The release schedule for security patches is unchanged.


to post comments

The Spirit of Open Source?

Posted Jan 7, 2026 15:58 UTC (Wed) by NightMonkey (subscriber, #23051) [Link]

"Release late, release seldom"? Waterfall-as-a-Service?

GPL violation?

Posted Jan 8, 2026 10:58 UTC (Thu) by Vorpal (guest, #136011) [Link] (5 responses)

This seems like a potential GPL violation, unless they still release their patched Linux kernel (and any other GPL components) more often (to match when vendors get to push it to customers).

GPL violation?

Posted Jan 8, 2026 11:31 UTC (Thu) by khim (subscriber, #9252) [Link]

> This seems like a potential GPL violation

How is it a GPL violation?

> unless they still release their patched Linux kernel (and any other GPL components) more often (to match when vendors get to push it to customers).

Kernel is updated pretty regularly, you may see android-mainline is not frozen on AOSP web site, like most other branches.

It just no longer includes any interesting drivers, they were moved to userspace ages ago.

GPL violation?

Posted Jan 8, 2026 18:02 UTC (Thu) by jmalcolm (subscriber, #8876) [Link] (1 responses)

If vendors push to customers, they are the distributors and they need to provide the code to comply with the GPL.

Are vendors pushing Android versions to customers before they show up in AOSP? Even under this new policy, AOSP is updated twice per year.

GPL violation?

Posted Jan 8, 2026 21:49 UTC (Thu) by khim (subscriber, #9252) [Link]

Vendors (including Google) routinely push updates, usually once per month.

But as I have already said Android kernel is not updated on two-drops-per-year schedule.

You can see it here, it's not frozen git repo like the rest of Android.

GPL violation?

Posted Jan 10, 2026 9:31 UTC (Sat) by MaZe (subscriber, #53908) [Link] (1 responses)

The vast majority of Android code is AOSP (effectively Google) written/copyrighted/owned, so they can do whatever, regardless of any licenses they (as the copyright holder / author) may or may not choose to grant you as an end user.

Furthermore, the vast majority of Android isn't GPL licensed at all.
It's Apache 2 licensed, which has no source release requirements.

This is why other vendors don't release their modifications to Android, in spite of not using bare AOSP.

This non-requirement to release the source was a day one requirement of Android - it's a large part (along with it being free) of why Android is a commercial success. Vendors were scared of GPL.

For the small quantity of stuff which is GPL, you can request the GPL sources and get a tarball.
I've done it, there's just basically nothing interesting in there, besides the Linux kernel itself.
(in addition to the kernel, there's some external cli utilities for talking to the Linux kernel, they - cumulatively get a few dozen patches per release, often just updates to (better) work with the Android build system, and thus useless outside of an Android build)

The Android forks (GKI/ACK) of the Linux kernel are still developed in the open in AOSP.
So you can simply follow those along live on AOSP gerrit instance.

--

Wrt. the article itself. This is basically a nothingburger.

Not great, but also doesn't really matter - it affects mostly GrapheneOS/Calyx/LineageOS custom roms - they'll be releasing some updates 3 months later than previously...

Android for the majority of its lifetime has had *yearly* source releases to AOSP.
Android 9/P, 10/Q, 11/R, 13/T - were released, and then a year passed until the next version was released.
Occasionally there would be an extra point release in the middle of the release cycle (example 8/O 8.1/O MR1 and 12/S 12.1/Sv2 and 14/U).

btw. Honeycomb source release was delayed by a year.

The past <2 years (since Android 14 QPR2) have switched to a quarterly release cycle (though A16 QPR1 was delayed enough that it basically came out just before A16 QPR2 did - make it quarterly only in theory, and basically nearly half-yearly in practice).

Now they're switching to twice a year...

You'll note this is still better than the overall average frequency of Android source releases (since inception) which is I think at the moment averaging around 3 quarters.

GPL violation?

Posted Jan 10, 2026 23:10 UTC (Sat) by pardo_bsso (guest, #111452) [Link]

Thanks for the clarification.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds