605
GrapheneOS is finally ready to break free from Pixels, and it may never look back (www.androidauthority.com)
submitted 10 months ago by to c/privacy@lemmy.dbzer0.com
111 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 10 months ago (1 child)

Can they please make it work for Samsungs? I made the mistake of getting an S23 and I didn't realize it was incompatible with all non-standard OSes.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 18 points 10 months ago (3 children)

    Samsung phones blow e-fuses when you unlock their bootloaders, so there's no going back. I think this would prevent a proper GrapheneOS installation.

    Perhaps Samsung could start shipping phones with GrapheneOS natively installed, but since the phone's owner would not have control of the OS, that would arguably not be GrapheneOS as we know it today. Or maybe Samsung could change their chain of trust implementation to be more like Google's, allowing the bootloader to be re-locked.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 5 points 10 months ago (1 child)

    Samsung would never. Their customized OS is this nested egg of vendor lock-in, with your data at the center. They would rather harvest data from 99.5% of their customer base than see the 0.5% of us that actually like their equipment buy it and do anything other than sink into their ecosystem.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 10 months ago

    I got a z flip 4 the other week for 90 quid off ebay. Was in perfect condition, and it felt nice in the hand. Liked the big screen, all that stuff. They I started running into the Samsung customised OS. It took less than a day to piss me off so much I gave it away.

    Samsung make really nice phones, but then ruin them with their custom OS and bloat.

  • permalink
  • fedilink
  • source
  • parent