TL;DR

  • Efforts like Graphene OS face increasing pressure from apps that refuse to run on non-standard Android.
  • The custom ROM project characterizes Google’s approach to device attestation as incomplete and flawed.
  • Graphene OS is prepared to take legal action if Google won’t let it pass Play Integrity checks.
  • SpiceDealer@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    I really hope the GrapheneOS team succeed. Custom ROMs are reason I’m really into tech today. Coding, FOSS, Linux, etc. all that came from rooting my dad’s HTC phone back in the day. Google shouldn’t cannibalize its children.

  • flop_leash_973@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 months ago

    The world of mobile phones is a real world example of what we avoided on the PC back in the day when the IBM BIOS got reverse engineered, allowing for someone to put out an IBM compatible PC without having to pay the tithe to big blue first. Not that IBM didn’t do their level best to put those efforts in the ground with their lawyers and the courts as soon as they found out about it. Thankfully the legal system of the time didn’t allow that to happen.

    It has been pretty depressing to me that the tech literate have been so easily lulled into accepting such things in the name of “cool toys” and “security” virtually everywhere in modern life besides the PC/laptop/server spaces.

    Phones, TV set top boxes, smart TVs, IoT gear. They are all a cesspit of locked down propitiatory and gate kept gardens where nothing happens without the gardens keeper getting a cut and having final say over everything.

    This sort of control and gatekeeping from the likes of Google, Apple, and Qualcomm was not something that was hard to see coming a mile away, yet we all collectively let it happen anyway.

      • NicolaHaskell@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        Heracles could shoot the eagle and break the chains, but then Prometheus might inform Zeus of the path to Troy. Titanomachy is one way of exchanging fire, but I’m human and content to hand it back and forth between each other. The pain of letting go is nuclear enough after Gaia and Uranus’s Family Vacation tore valleys through the mountains.

  • towerful@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    The only reason I stopped using grapheneOS was because Google contactless payment didn’t work.
    Loved everything else about graphene tho

    • tabular@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      I’ve never used contactless on my phone, I already had a contactless debit card. Why are you, and others, using their phones to pay?

      • nevemsenki@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 months ago

        I can create a virtual card before every trip, use it via my phone and then cancel it after the trip, never worrying if my card got skimmed anywhere for one.

        • steel_nomad@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          2 months ago

          For some fucking reason there is zero option for this type of secure virtual card in my country. And I hate it. A friend got skimmed for over $1200 a couple months ago.

  • Blackmist@feddit.uk
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    Even without the custom ROMs, the whole Android ecosystem is a colossal fucking mess.

    I’ve got old apps that won’t work any more. It’s not even compatible with itself.

    People give Windows a load of shit, and deservedly so for some of it, but it’s a million times more usable than Android when you want shit to “just work”.

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    I hope some OEM (especially those opposed to google) picks up and develops mainline linux like Pine Phone. There are already several mobile UXs and distros with prebuilt images available as well, and it has been shown multiple times that Android apps can run fairly easily on linux. It would be a big risk, but I think it’d at least find a market success like the Steam Deck.

    Android in its current state is the same as Chromebooks. A glorified walled garden of google’s crappy choices & DRM which just so happens to run on the Linux kernel because it’s free. People downvote me for this, but I maintain that even Dalvik and the android runtime itself is an inefficient relic of 10+ years ago when mobile devices had at most 2gb of ram and a tiny low power ARM processor.

    It runs like complete crap sometimes on modern devices despite huge advancements in the underlying tech. It feels like a knockoff JVM which is already a known memory hog.

    On top of that, it sticks with single kernel releases with proprietary OEM binaries so you have devices out here running on kernels as old as 3.x because no custom ROM will be able to recompile the device modules for a newer kernel.

    It is almost hilarious to me that Moonshell, a multimedia homebrew software for the Nintendo DS (4mb of RAM), has more complete features, file compatibility, and better UI design than at least 95% of the music apps on Google Play. And it was written by literally one guy. I was honestly surprised at just how many music players lacked functionality as basic as supporting m3u playlists.

    • emergencyfood@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      2 months ago

      I hope some OEM (especially those opposed to google) picks up and develops mainline linux like Pine Phone.

      Huawei is being forced to do it. But like Android, their HarmonyOS is not 100% open-source. There’s also KaiOS, which some Nokia and Alcatel, and all Jio, devices use.

      even Dalvik and the android runtime itself is an inefficient relic of 10+ years ago when mobile devices had at most 2gb of ram and a tiny low power ARM processor.

      Both the ones I mentioned are designed to be more memory efficient. KaiOS in particular is aimed primarily at feature phones and entry-level smartphones.