TLDR: He does not recommend CalyxOS and gave it a score of 3/10

47 points

This person does not understand open source or Android whatsoever. They talk a decent bit about “default installed apps”, without properly understanding what most of them even are. They complain about some apps “being out of date” when installing CalyxOS, calling it “concerning” that they’re not on the latest version out of the box, as if they couldn’t update the apps themselves. The whole “review” feels more like an iPhone user trying to switch to Android for the first time, being confused because it’s different, and complaining about it because they don’t understand it.

The main benefits of CalyxOS lie under the hood. It’s built to be more secure out of the box, and doesn’t connect everywhere without consent like most other Android ROMs. If you’re fine with the privacy and security of using something like LineageOS, CalyxOS doesn’t have much extra to offer.

permalink
report
reply
19 points

Thanks for the TL;DR, I figured it would be a uneducated take, you saved me the time of watching it 🫡

permalink
report
parent
reply
3 points

It’s worth watching, yes. To understand the purpose of CalyxOS, you must understand the purpose of the project, of course. We can’t simply say that it’s a terrible Custom ROM for privacy, as he did. It was quite wrong and in bad faith to say that a project that, yes, is much better than using a Stock ROM, however, the fact that he compared it to other Custom ROMs that also claim to focus on privacy and showed that CalyxOS doesn’t differ much from them is completely valid and truly a fact. DivestOS, with only one developer at the helm, was much more hardened than it. Which makes one wonder why CalyxOS, with an entire team behind it, doesn’t follow the same example. It really is disappointing. Want to prove it? Check out the website (https://eylenburg.github.io/android_comparison.htm) he shows in the video and see for yourself.

permalink
report
parent
reply
8 points

Not only is comparing these not the point (CalyxOS has a different purpose than GrapheneOS), the chart is heavily biased towards Graphene. Take for example the whole section on privacy. They list Graphene specific features, note that Graphene has them, and make other roms look bad for “not having them”, or even provide incorrect information. “Storage Scopes” and “Contact Scopes” for example, two Graphene features, intended to make closed source apps “happy” with giving them fake permissions. Although there’s definitely a use for this feature, being much more FOSS focused, Calyx provides the option to isolate non-foss apps into a work profile. This is effectively doing something very similar, although more limited to the user. Or the “Tracking through Android Advertising ID?” column, which lists only Graphene as “Not part of the system”, and everything else as “Randomized ID”. Graphene runs the official Google play services “in a sandbox”, without modifying or patching anything significant. This also means Google’s implementation of Advertising ID is being used. This is not randomized, and worse for privacy than anything using MicroG. Calyx MicroG and Graphene Google Play Services are both opt in, yet the chart favors Graphene by claiming it doesn’t have the anti-feature.

permalink
report
parent
reply
7 points
*

You end your comment by saying…

“Which makes one wonder why CalyxOS, with an entire team behind it, doesn’t follow the same example”

When you already answered your question in the beginning…

“To understand the purpose of CalyxOS, you must understand the purpose of the project, of course”

If you compare CalyxOS to DivestOS or GrapheneOS, then you’ve missed the point of CalyxOS, “the purpose of the project”. They are intended for different people, though there is some overlap. CalyxOS respects FOSS much more than does GrapheneOS, and to me that’s a very valuable thing. They tighten privacy, but are not as focused on security alterations beyond stock android, beyond making it less leaky when it comes to personal data, which in its own way is a reinforcement of security.

Also, DivestOS has “divested” itself of participation in the privacy/security game and stopped all development. It’s sad, but I’m happy that the developer is getting to live his life to a fuller degree now. He contributed a lot of value to the open source world in the past.

permalink
report
parent
reply
9 points

Ah yes, the faux techies. This happens for alot to the technical niches. Wouldn’t pay it any mind. Downvote and move on.

permalink
report
parent
reply
6 points

Seeing the perspective of somebody who’s not particularly well versed in Android forks is interesting, though.

I found the part around 2:45 to be interesting, where the YouTuber says the thought of the OS getting compromised was scary. This is a sort of privacy paradox where Calyx looks worse than other, less honest, alternatives.

Could a rouge employee compromise Calyx? I guess, but Calyx has the best possible setup to avoid it. And Android itself is basically compromised by default, which should be far more concerning. The biggest reason people aren’t concerned is because Google understands PR, and they know how to spin things in the most positive light possible.

permalink
report
parent
reply

Privacy Guides

!privacyguides@lemmy.one

Create post

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more…


Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don’t ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don’t repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

Community stats

  • 1.4K

    Monthly active users

  • 669

    Posts

  • 10K

    Comments