I Installed a Graphene-Based OS on Non-Pixel Phones… Here’s the Catch

https://www.youtube.com/watch?v=-RjGjqBAAgQ


"I was watching youtube(Invidious) and notied RestlessOS . Have you heard of this and are there people actually tried this on non-pixel phone?

“RestlessOS is an unofficial, unaffiliated fork of GrapheneOS packaged as a Generic System Image (GSI) for Project Treble devices. It is not endorsed by, sponsored by, or in any way connected to the GrapheneOS project or its developers.”

https://github.com/cawilliamson/treble_restlessos

I’m very hesitant to give money to Google pixel so I’m going to experiment on this one."

  • tapdattl@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 day ago

    Looks like they put in a ton of effort to make this compatible with generic devices, but I have to ask, with all the features removed, why choose this over any other ROM?

    Features removed

    hardened_malloc — causes boot loops on devices with 39-bit virtual address space. replaced with AOSP Scudo.

    Auditor — requires hardware attestation which > doesn’t work on GSI

    mtectrl / misctrl — Pixel-specific memory tagging control; breaks vendor TEE drivers

    USB protection — the low-level USB port controls rely on Pixel-specific hardware and are non-functional on other devices

    native debugging protection — not ported; breaks compatibility with root solutions and vendor debugging tools

    Features disabled by default

    These can be re-enabled in TrebleApp → Hardening or Settings → Exploit protection.

    MTE/TBI for vendor processes — memory tagging breaks some vendor drivers

    hardened thread stacks — non-standard memory layout breaks some vendor drivers

    secure (exec-based) app spawning — breaks root solutions (Magisk / KernelSU)

    • slacktoid@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      Still better than nothing? And more privacy centric options out there are better as it gives people a way to figure out how it can fit into their life vs the all private where nothing works and you need to know tech to get around or nothing private but at least things work, world people are in.

      • schipelblorp@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        24 hours ago

        Why are a multitude of poor options better than a few good options?

        There’s this weird mix of free market capitalism and FOSS philosophy that says more and shallower forks = better ecosystem.

        Not commenting on this OS specifically, but just questioning your blase assertions that more options is better. Maybe it would be have been better to invest more time into an existing project.

        • WhyJiffie@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          5 hours ago

          Why are a multitude of poor options better than a few good options?

          because you see it wrong. it is not poor just because it is not shiny polished perfect. it is still an improvement over the factory rom, and if the maintainer is trustworthy then it’s an improvement over lineage os too.

        • 0_o7@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          0
          ·
          15 hours ago

          Why are a multitude of poor options better than a few good options?

          People make do with what they have.

          It would be ideal if everyone had access to the “best” options, so a single approach makes sense, but we don’t live in an ideal world.

    • monovergent@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      1 day ago

      Minimalism. Compared to AOSP, Google components and pings removed. Compared to other privacy GSI ROMs, no weird, quirky, or flashy functions or themes the author decided to bake in.