> 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.
The claim here is that AOSP will stop releasing sources publicly altogether similar to other versions of Android like Wear OS.
> 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
That case was dismissed because they settled privately, so technically it does not prove anything about LGPLv2, and Germany is not as big on blindly following precedent in law as other countries anyway.