3 ms·

In which ways is CalyxOS "better"? This comparison is pretty damning: https://eylenburg.github.io/android_comparison.htm https://eylenburg.github.io/android_co

In which ways is CalyxOS "better"? This comparison is pretty damning: https://eylenburg.github.io/android_comparison.htm 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, ...).

userbinator 1y ago
The insecurity is freedom.
onli 1y ago
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 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.
- UnreachableCode 1y ago
  Thanks for the vid. I've been down the rabbit hole now. Looks like he departed the project though?
  - bramhaag 1y ago
    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-slowing-down/7 https://discuss.grapheneos.org/d/12565-is-gos-development-sl... [2] https://discuss.grapheneos.org/d/21819-impact-of-ongoing-war-on-grapheneos-development https://discuss.grapheneos.org/d/21819-impact-of-ongoing-war...
  - onli 1y ago
    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.
    - UnreachableCode 1y ago
      It's a shame. He's clearly very talented. Mental health is no joke, you're right.
- aniviacat 1y ago
  The requirements are detailed on the GrapheneOS website [0]. I think the main issue with FairPhones was lacking a secure element and not receiving (anywhere near) timely firmware updates. [0] https://grapheneos.org/faq#future-devices https://grapheneos.org/faq#future-devices

userbinator 1y ago

The insecurity is freedom.

onli 1y ago

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 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.

UnreachableCode 1y ago
Thanks for the vid. I've been down the rabbit hole now. Looks like he departed the project though?
- bramhaag 1y ago
  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-slowing-down/7 https://discuss.grapheneos.org/d/12565-is-gos-development-sl... [2] https://discuss.grapheneos.org/d/21819-impact-of-ongoing-war-on-grapheneos-development https://discuss.grapheneos.org/d/21819-impact-of-ongoing-war...
- onli 1y ago
  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.
  - UnreachableCode 1y ago
    It's a shame. He's clearly very talented. Mental health is no joke, you're right.
aniviacat 1y ago
The requirements are detailed on the GrapheneOS website [0]. I think the main issue with FairPhones was lacking a secure element and not receiving (anywhere near) timely firmware updates. [0] https://grapheneos.org/faq#future-devices https://grapheneos.org/faq#future-devices