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.

  • roofuskit@lemmy.worldEnglish
    62·
    2 days ago

    Does this mean Graphene is dead? Probably the real reason they would do this is to kill Graphene.

    • Quik@infosec.pubEnglish
      2·
      22 hours ago

      This fits into Google tying Android closer to them, same with the recent move of only making release source publicly available.

      They’re regretting having started Android as an “open” platform and want to gain control fast, maybe preparing for the current anti-trust trials they are facing in the US.

    • tisktisk@piefed.socialEnglish
      8·
      2 days ago

      It certainly feels like it is judging by the general moodshifts occuring. But I’m a moron, what alternative exists for a secure phone of comparable functionality? It feels like ditching phones is the only option to some extent(for me). If stupid, isn’t the phone the most vulnerable weakpoint open to attack?