← Back to context

Comment by saligne

8 hours ago

You should search for the many times where GrapheneOS has stated they won't work with Fairphone

It's because Fairphone doesn't fulfil GOS's hardware requirements. If Fairphone addresses that, there's no reason for GOS to not support a Fairphone device.

  • I don't understand the issue. If Fairphone wants GOS can't they just compile it themselves with whatever unsupported hardware based security features disabled? Ditto for any given end user. It's not as though we're talking about a device with hardware specs locked behind an NDA and drivers that only support outdated kernel versions.

    • Simple. Fairphone doesn't want GOS.

      Forking GOS and porting it to a new device is a huge and unreasonable ask for an individual user. Even less so when you include the fact that you'll need to keep it up to date.

      3 replies →

    • Yes, they can, but they have promoted /e/OS, and they have no ability to develop Android.

Yep. Gos isn't the only mfg in town if you have or want a fairphone.

https://wiki.postmarketos.org/wiki/Fairphone_(Gen._6)_(fairp...

Given the state of Fairphone hardware, software and business, it is not surprising.

  • For those of us out of the loop, could someone summarize the situation?

    •   > Fairphone has said they don't plan to add a secure element. It can be seen from their current devices that they don't fully keep up with privacy/security backports and lag a year behind on shipping yearly OS releases. They skip over the monthly and quarterly releases entirely. They replaced their own non-GMS Fairphone OS with a dramatically less secure /e/OS option in partnership with Murena. They clearly demonstrate that security and even privacy are not the priorities.
      

      https://grapheneos.social/@GrapheneOS/114733211017800480

      4 replies →