←back to thread

Fairphone 6 is switching to a new design that's even more sustainable

(www.androidcentral.com)
401 points Bluestein | 4 comments | 23 Jun 25 15:29 UTC | HN request time: 0.763s | source
Show context
exabrial ◴[23 Jun 25 16:37 UTC] No.44357521[source]▶
ahhh I wish GrapheneOS was supported on these!
replies(1): >>44357566 #
onli ◴[23 Jun 25 16:41 UTC] No.44357566[source]▶
CalyxOS support Fairphones. It is a better option anyway, also supports bootloader relocking etc.
replies(3): >>44359981 #>>44361786 #>>44363767 #
bramhaag ◴[24 Jun 25 00:50 UTC] No.44361786[source]▶
In which ways is CalyxOS "better"?

This comparison is pretty damning: https://eylenburg.github.io/android_comparison.htm

Calyx is _not_ a hardened OS, and runs on devices with insecure hardware and firmware (like a Fairphone). Additionally, app compatibility suffers because they use microG instead of proper sandboxed Gapps, and also lacks many QoL features that guard against hostile apps (storage scopes, contact scopes, ...).

replies(2): >>44362927 #>>44363073 #
onli ◴[24 Jun 25 05:25 UTC] No.44363073[source]▶
Why would you call the Fairphone an insecure device? It has long update support and can re-lock the bootloader, which is like the one criteria ROMs like that pick as the security feature. What is your attack scenario, what your security criteria here?

microG is not a drawback, it's a proper FOSS implementation, which I vastly prefer to running Gapps in a sandbox. App compatibility has been perfect for me.

The main criteria for it to be strictly better is that you do not give root to a dev that hallucinates enemies and then send their goons to attack them. See https://www.youtube.com/watch?v=4To-F6W1NT0. It's nice that Graphene has a hardened kernel, that helps nothing if you can't trust the developer - different attack scenarios.

replies(2): >>44363603 #>>44363683 #
1. UnreachableCode ◴[24 Jun 25 07:13 UTC] No.44363603[source]▶
Thanks for the vid. I've been down the rabbit hole now. Looks like he departed the project though?
replies(2): >>44363835 #>>44363853 #
2. bramhaag ◴[24 Jun 25 07:57 UTC] No.44363835[source]▶
Micay did not fully leave the project [1]. AFAIK he is the only senior developer left, after their other senior developer was forcibly conscripted earlier this year [2].

[1] https://discuss.grapheneos.org/d/12565-is-gos-development-sl...

[2] https://discuss.grapheneos.org/d/21819-impact-of-ongoing-war...

3. onli ◴[24 Jun 25 08:00 UTC] No.44363853[source]▶
Last I checked he announced his departure only to rescind that announcement later. For example in the discussion about the shutdown of the Mozilla location service he was active and spoke for the project, completely derailing the issue with versions of the accusations the video depicts as well, which was afterwards.

I am always a bit sorry when I have to bring this up, that is why I only mentioned it when prompted. Mental health is a sensitive topic and hammering the problem won't help him, but it is just so relevant when users rely on the security of their system, even pick Graphene because of heightened security needs.

replies(1): >>44363925 #
4. UnreachableCode ◴[24 Jun 25 08:15 UTC] No.44363925[source]▶
It's a shame. He's clearly very talented. Mental health is no joke, you're right.