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.

  • Quik@infosec.pubEnglish
    16·
    6 days ago

    Now more than ever we need more work on PostmarketOS, Mobian, Gnome Mobile etc…

    Bummer that it’s still so hard to find a somewhat modern, affordable phone that is Linux compatible

    • sugar_in_your_tea@sh.itjust.worksEnglish
      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.pubEnglish
        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.mlEnglish
        01·
        6 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.wtfEnglish
          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.

    • corsicanguppy@lemmy.caEnglish
      2·
      6 days ago

      I know someone at a company that built and sold a Linux phone 19 years ago.

      You’re not upset you can’t find a Linux phone: you’re upset you can’t find one anymore.