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.

  • sugar_in_your_tea@sh.itjust.worksEnglish
    13·
    16 days ago

    Yeah, I’d totally buy a phone running one of those provided it does all the phone things properly: SMS/MMS, reliable calls, all day battery, etc. I don’t need fancy apps, I just need a working phone.

    If I can get that, I could probably donate some time porting apps.

    • timbuck2themoon@sh.itjust.worksEnglish
      4·
      15 days ago

      I really want to give furios phone a shot. It’s apparently close to supporting my carrier.

      That and a sailfish phone. The community one though didn’t support my carrier (think it’s mainly EU specced only.)

      What I find missing most of the time though is any esim support. Makes me wonder if the hardware one that you can program an esim on works.