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.

  • @Vanilla_PuddinFudge@infosec.pubEnglish
    9•6 days ago

    I use a Oneplus 7 pro and my rom maintainer still updates and I still get a new version once every two months or so. If you want to omit gapps, you are more than free to do so. (Crdroid)

    • tisktiskEnglish
      3•6 days ago

      You are selling me mr. Fudge. I still need to do a lotta research but you are def sellin me here

      • @Vanilla_PuddinFudge@infosec.pubEnglish
        6•6 days ago

        The trap: He could stop builds for the OP7… tomorrow with zero warning.

        That leads to my main takeaway for custom roms. Pick the phone with the most topics and replies on XDA. The more popular and liked, the more supported you’ll be.

        and never get attached to anything. Your phone miraculously has support, none are guaranteed it.

        • tisktiskEnglish
          10•6 days ago

          You have now anti-sold me and hyper-enlightened me with some very worthwhile wisdom. I can not say thank you enough–I truly need more like you in my life