Comment by ranger_danger
1 year ago
No it's not, they're just not releasing sources until a new version is actually released, and there's nothing inherently wrong with that.
1 year ago
No it's not, they're just not releasing sources until a new version is actually released, and there's nothing inherently wrong with that.
Which makes life more difficult for downstream projects. However the recent release didn't include the usual device-specific sources.
> This means AOSP 16 cannot currently be built or run on any recent Pixel device easily just using official source. It’s unclear whether this is a delay or a policy change. Either way, it seriously disrupts custom ROM development and our porting efforts.
https://calyxos.org/news/2025/06/11/android-16-plans/
Once they give you the device, they're legally required to give you the source code. Most manufacturers don't, but you can sue them and win.
Most of AOSP is Apache 2.0 licensed (permissive, not copyleft)
3 replies →
I think they're counting on that fight. Good luck, I look forward to seeing the gofundme...
1 reply →
seems not exactly true, they did release android 16 to AOSP but "Google did not publish any device-specific source code for supported, modern Pixel devices."
https://calyxos.org/news/2025/06/11/android-16-plans/
The alleged claim being made is different than the previous official announcement.
The claim here is that AOSP will stop releasing sources publicly altogether similar to other versions of Android like Wear OS.
FYI: https://source.android.com/docs/setup/about/faqs#android-lat...
> Google pushes the code for the next release to the latest public release branch and updates the android-latest-release manifest to point to that branch.
Along with https://source.android.com/docs/whatsnew/site-updates#aosp-c...
> The android-latest-release manifest is set to the latest AOSP release branch, android16-release