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.

  • Noxy@pawb.socialEnglish
    71·
    3 days ago

    Nah, you have it backwards. GrapheneOS didn’t choose Pixels for any reason other than they’re the only acceptably secure devices out there. I can’t imagine they want this to be the case.

    • nintendiator@feddit.clEnglish
      1·
      1 day ago

      That still sounds like choosing to me. Like, if your project requirements are so strict that it only works on the mornings of a Tuesday that falls in a prime number day that has a blue moon and where there are no ATP tennis matches going on (all pre-existing things you have no vote on), maybe you should re-evaluate if you actually want your proyect to have a viable audience.