GrapheneOS: the private and secure mobile OS
grapheneos.org
GrapheneOS is a security and privacy focused mobile OS with Android app compatibility.

I run this on my Pixel 4, goodbye Google rubbish :D

  • CrypticCoffee@lemm.eeM
    31·
    1 year ago

    I’ve been happy with it on Pixel 6a. It feels good to know my phone isn’t spying on every little thing I do.

  • MigratingtoLemmy@lemmy.world
    1·
    1 year ago

    Unless there are reports of backdoors in Graphene OS I don’t see a reason to not use it (well, YMMV if the developer’s dialogue affects you - this is the internet bro). I get that Graphene is not the Degoogle expert in Android OS markets (\e\OS for you lot if you don’t want to do manual work), but it can be degoogled the same way that Lineage can be degoogled - change the API calls to google servers. That’s all of the Google influence these ROMs have.

    This OS is fantastic and if I were to purchase a pixel I would use it. Absolutely

  • Mek101@lemmy.ml
    1·
    4 years ago

    The main obstacle I see in all those private OS is that they usually support only a small number of highly-priced devices. So you either have money to spend and migrate to a private OS or you’re stuck with google.

  • slurp@programming.dev
    1·
    1 year ago

    Is there a safe way to try it and revert completely? Banking apps can be very sensitive and those not working is a deal breaker for me. The potential of trying it and them no longer working, even if I change back, worries me…

    • aussiematt@lemm.eeEnglish
      2·
      1 year ago

      The guy at the centre of much of this drama has stepped back, and is letting the GrapheneOS foundation take the lead. While Daniel clearly has some challenges in the people skills department, I think Louis may have over-reacted a little in his video when he claimed that Daniel might at some point act in bad faith.

  • onlooker@lemmy.ml
    1·
    4 years ago

    I like the project. I used it when it was called CopperheadOS. However, looking at the supported phones I can’t help but feel a little angry. Out of the 8 supported, only two have 3.5mm headphone jacks and none have SD card slots and my personal favourite, none have a freaking replacable battery. You know, the thing that’s most likely to crap out first?

    I get why Pixel phones were chosen, it’s very well explained actually, but I am never ever buying a phone that is so blatantly designed with planned obsolescence in mind.

    • jjspano@lemmy.ml
      2·
      4 years ago

      @onlooker@lemmy.ml Agreed. It makes zero sense to me. I’d rather get an old samsung with lineage 16.1, replaceable battery, microSD capability and a headphone jack. Plus i can buy it for around $100 USD.

      I’ll take the old hardware + software trade off for some freedom and peace of mind. It’s better to me than using shitty Nokia I have now on Android 10.

    • racoon@lemmy.ml
      0·
      4 years ago

      If I’ve understood the docs correctly, you can install it in many other phones

      • onlooker@lemmy.ml
        1·
        4 years ago

        You can build it for generic targets, yes. However, as the build page states:

        These generic targets can be used with the emulator along with many smartphones, tablets and other devices. These targets don’t receive full monthly security updates, don’t offer all of the baseline security features and are intended for development usage.

  • Echedenyan@lemmy.ml
    11·
    4 years ago

    I run this on my Pixel 4, goodbye Google rubbish :D

    But using a Google Pixel and depending on security features developed and promoted mainly by Google…