Google has confirmed it isn't discontinuing AOSP, but it's making a change that makes it harder for devs to build Android for Pixel phones.

TL;DR

  • Google has made it harder to build custom Android ROMs for Pixel phones by omitting their device trees and driver binaries from the latest AOSP release.

  • The company says this is because it’s shifting its AOSP reference target from Pixel hardware to a virtual device called “Cuttlefish” to be more neutral.

  • While Google insists AOSP isn’t going away, developers must now reverse-engineer changes, making the process for supporting Pixel devices more difficult.

  • mctoasterson@reddthat.comEnglish
    16·
    2 days ago

    I am running GOS on a Pixel 7, which means I’ve had this device for ~2.5 years at this point, and back when I transitioned to this setup I was aware they were talking about being beholden to Pixels due to the hardware security module not being available on other devices.

    It has been a known issue. I understand it is a very difficult and costly undertaking to develop new hardware and new entrants would be competing against the big guys for fab space, manufacturing and assembly etc.

    We need some kind of nonprofit or independently financed group to advance this cause. Could it be FUTO, Framework, or some other company/organization like this?

    There would be market incentive to solve these problems - There has got to be a lot of demand for a neutral hardware platform that meets the hardware security module and other requirements for bootloader security, custom ROMs, etc.