• Sunshine@piefed.ca
    link
    fedilink
    English
    arrow-up
    33
    ·
    7 months ago

    Thank god people have a decent alternative to stock android. Graphene works amazingly!

    • AmbitiousProcess (they/them)@piefed.social
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      3
      ·
      7 months ago

      Received? GrapheneOS are the authors of their software, they don’t receive.

      That’s how this language is commonly used. “Received” is just in place of what you’d more commonly hear as “gets.”

      So for example, “Gmail gets new feature that allows users to X” Gmail didn’t receive it from somewhere else, but Gmail got a new feature.

      GrapheneOS “receiving” an experimental build is linguistically identical to saying “GrapheneOS gets new update that does X”

      I agree the article is pretty badly done, but that part I think is fairly normal. Heard that used by all sorts of outlets.

    • lemmysmash@beehaw.org
      link
      fedilink
      English
      arrow-up
      6
      ·
      7 months ago

      GrapheneOS pretty much solved the closed device trees issue you’re referring to. They don’t need them anymore and use their own toolchain to workaround the issues.

      The problem with Pixel 10 was different: it was released with Android 16 QPR1 out-of-the-box, but this very QPR1 hasn’t been pushed to AOSP until a couple of weeks ago. This is why the GrapheneOS build for Pixel 10 was not possible: they could not/didn’t want to port the older Android 16 OS to Pixel 10’s hardware, and they didn’t have the source code of the QPR1 to build GrapheneOS on top of it.

      Now the QPR1 (and currently even the QPR2) has been pushed to AOSP, so GrapheneOS has released Android 16 QPR1-based GrapheneOS both for older phones and for Pixel 10.