cross-posted from: https://lemmy.world/post/31229844

As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it’s more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.

  • henfredemars@infosec.pubEnglish
    191·
    1 month ago

    Does this mean Graphene is kill? This is why they only supported Pixel in the first place.

    If so, Pixel is just another Samsung in terms of software support.

    Google’s decision to now discontinue the Pixel as an AOSP reference device is unfortunate, as it has pulled the rug from under developers like the teams at LineageOS and GrapheneOS who build Android for Pixel devices. These developers will still be able to build AOSP for Pixel devices, but it will now be more difficult and painful to do so than before, as they will need to build their own device trees from scratch. This also brings Pixels down to the same level as other Android devices[.]

    Yep, looks like Pixel is just another Android to ROM developers. A sorry shame indeed. There goes another reason to both with the Pixel.