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.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    6 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.

    • Quik@infosec.pub
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 days ago

      It’s so crazy (technically understandable, but still crazy) to me that reliably receiving calls is still such a major issue

    • interdimensionalmeme@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      5 days ago

      I want a phone with only cellular data, no calling, no sms, just an open source browser capable of webasm and webrtc

      • Ibuthyr@lemmy.wtf
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 days ago

        We had those, they were called Pocket PCs. I too want them back. I loved the Dell Axim x51v. A tablet does the job, but it’s the same shitty OS.