zlacker

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+(OP)
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+h3
I think they're counting on that fight. Good luck, I look forward to seeing the gofundme...

>>rob_c+o3
This is more an opportunity for the EU to suddenly play harder ball than expected.

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

>>flotza+d7
I believe the device tree stuff is GPL due to the kernel. Might be mistaken though.

>>fc417f+c9
A device tree is probably counted as data, so not copyrightable. I am not a lawyer and this is not legal advice. But there's plenty else that is GPL, and in AVM vs Sebastian Steck, it seems that even LGPLv2 requires the manufacturer to give you all the stuff you need to install a modified version of the software, i.e. it seems that all GPL licenses imply anti-tivoization.

>>immibi+Km
> AVM vs Sebastian Steck

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.