zlacker

[parent] [thread] 1 comments
1. zeech+(OP)[view] [source] 2025-06-12 06:00:41
From 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.

replies(1): >>nabogh+hj
2. nabogh+hj[view] [source] 2025-06-12 10:09:32
>>zeech+(OP)
That's awful. I bought a pixel because the ecosystem around alternative android roms was healthy. This seems to change that.

Why can't I just get a general purpose computer in my pocket? Why is everything so hostile? I am willing to pay!

[go to top]