AOSP project is coming to an end
old.reddit.com
AOSP project is coming to an end
1–10 of 135 posts
Re: AOSP project is coming to an end
#2No it's not, they're just not releasing sources until a new version is actually released, and there's nothing inherently wrong with that.
Re: AOSP project is coming to an end
#3From https://calyxos.org/news/2025/06/11/android-16-plans/ -
> Google did not publish any device-specific source code for supported, modern Pixel devices.
> In previous years, Google released full device trees alongside new Android versions. This allowed developers to build and boot AOSP on Pixel hardware relatively easily.
> With Android 16, only the platform/framework code has been released. The device trees are missing, at least for now.
> 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.
Re: AOSP project is coming to an end
#4No 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.
Re: AOSP project is coming to an end
#5No it's not, they're just not releasing sources until a new version is actually released, and there's nothing inherently wrong with that.
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.
Re: AOSP project is coming to an end
#6No it's not, they're just not releasing sources until a new version is actually released, and there's nothing inherently wrong with that.
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."
Re: AOSP project is coming to an end
#7sad, was thinking to switch from iPhone to pixel 10 in few months once released exactly for the reason that is clean android and gives and escape hatch to use grapheneOS or lineageOS or calysOS. Any other android phone manufacturer that is supported by any of those projects? Most devices supported except pixel devices are few years old.
Re: AOSP project is coming to an end
#8No it's not, they're just not releasing sources until a new version is actually released, and there's nothing inherently wrong with that.
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
Re: AOSP project is coming to an end
#9As far as I understand this only concerns Google Pixel devices, and AOSP "coming to an end" is mostly speculation. Is this going to affect other manufacturers too, e.g. the Fairphone[1]?
Re: AOSP project is coming to an end
#10sad, was thinking to switch from iPhone to pixel 10 in few months once released exactly for the reason that is clean android and gives and escape hatch to use grapheneOS or lineageOS or calysOS. Any other android phone manufacturer that is supported by any of those projects? Most devices supported except pixel devices are few years old.
Fairphone