AOSP project is coming to an end

Re:AOSP project is coming to an end by ranger_danger on Thursday June 12, 2025 @01:51AM (#44254628)

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.

[ Parent | on HN ]

Re:AOSP project is coming to an end by fc417fc802 on Thursday June 12, 2025 @02:05AM (#44254689)

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/

[ Parent | on HN ]

Re:AOSP project is coming to an end by immibis on Thursday June 12, 2025 @02:58AM (#44254892)

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.

[ Parent | on HN ]

Re:AOSP project is coming to an end by flotzam on Thursday June 12, 2025 @03:55AM (#44255136)

Most of AOSP is Apache 2.0 licensed (permissive, not copyleft)

[ Parent | on HN ]

Re:AOSP project is coming to an end by fc417fc802 on Thursday June 12, 2025 @04:20AM (#44255259)

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

[ Parent | on HN ]

Re:AOSP project is coming to an end by immibis on Thursday June 12, 2025 @06:47AM (#44256099)

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.

[ Parent | on HN ]

Re:AOSP project is coming to an end by ranger_danger on Thursday June 12, 2025 @09:40AM (#44257700)

> 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.

[ Parent | on HN ]

Re:AOSP project is coming to an end by rob_c on Thursday June 12, 2025 @03:02AM (#44254899)

I think they're counting on that fight. Good luck, I look forward to seeing the gofundme...

[ Parent | on HN ]

Re:AOSP project is coming to an end by lipowitz on Thursday June 12, 2025 @03:17AM (#44254958)

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

[ Parent | on HN ]

Re:AOSP project is coming to an end by pzo on Thursday June 12, 2025 @02:16AM (#44254726)

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/

[ Parent | on HN ]

Re:AOSP project is coming to an end by charcircuit on Thursday June 12, 2025 @02:08AM (#44254695)

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.

[ Parent | on HN ]

Re:AOSP project is coming to an end by flakiness on Thursday June 12, 2025 @02:21AM (#44254736)

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

[ Parent | on HN ]