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