11–20 of 135 posts
As 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]? [1] https://www.fairphone.com
sad, 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.
LineageOS is the only one of the three that supports older hardware, but I'd recommend getting a previous-gen Pixel for the seven-year (at least) support cycle.
[0] https://grapheneos.org/faq#supported-devices
With Apple's ongoing refusal to enable VM/JIT support on iOS and iPad, Google Pixel + GrapheneOS + Debian is a very competitive 2025 offering.
As 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]? [1] https://www.fairphone.com
Fairphone should still be able to get the source for Android from Qualcomm.
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.
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/0…
Earlier quoted context omitted.
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/0…
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.
Hopefully AOSP Pixel device support is merely delayed, not ended, since Pixel is the only way to get Debian Linux ("Terminal") VM + desktop mode support, https://news.ycombinator.com/item?id=43973395 . With Apple's ongoing refusal to enable VM/JIT support on iOS and iPad, Google Pixel + GrapheneOS + Debian is a very competitive 2025 offering.