> 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.
> 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.
> 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
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.
https://en.wikipedia.org/wiki/Board_support_package presumably. Never heard that TLA in my life and it's not like I've not gotten my hands dirty in Android
https://taoofmac.com/space/blog/2025/06/03/2155
> Apple has dropped the ball so badly that Sky is like a perfect storm of what they could have done, but didn’t. And now, not only is it a third-party app that is doing what Apple should have done, but it is also doing it in a better way that anything they ever shipped.
> For more than 90 percent of the billings and sales facilitated by the App Store ecosystem, developers did not pay any commission to Apple.
Would the remaining 10 percent of App Store sales have meaningful competition from a CLI (no GUI) terminal VM that enables development workflows on iPad?
https://9to5google.com/2025/06/12/android-open-source-projec...
However, I personally switched to CalyxOS. I was a bit unhappy with LineageOS pushing users towards the Gapps, by blocking microG from working properly (they blocked signature spoofing, a problem during the pandemic) and by forbidding discussions about microG on their subreddit, together with forbidding to even talk about issues with VoLTE or anything that touches rooting the system. They course corrected only a little bit with the signature spoofing, but still project user hostility otherwise via those rules. CalyxOS gave me a more usable system out of the box, while having a bigger focus on security (locking the boot loader) and presenting the project nicer. Vastly less devices supported though, and if pixels go closed now the Calyx project would have to implement big changes, those were their main devices.
From the Android VPN and GM: "We're seeing some speculation that AOSP is being discontinued. To be clear, AOSP is NOT going away. AOSP was built on the foundation of being an open platform for device implementations, SoC vendors, and instruction set architectures.
AOSP needs a reference target that is flexible, configurable, and affordable – independent of any particular hardware, including those from Google. For years, developers have been building Cuttlefish (available on GitHub as the reference device for AOSP) and GSI targets from source. We continue to make those available for testing and development purposes."
Sales commission is the percentage of the value of a sale that a sales associate or sales representative may earn.