zlacker

>>kaladi+(OP)
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.

>>ranger+q1
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/

>>fc417f+p2
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.

>>immibi+G5
Most of AOSP is Apache 2.0 licensed (permissive, not copyleft)