I believe the appeal for CalyxOS is attempting to bring more convenience with privacy, where apps you've mentioned are already installed. A major difference is the inclusion of microG, which means you have more freedom to use apps you have no alternative to (e.g. government apps, banking apps, etc).

I'm aware of the LineageOS for microG project, however apart from the aforementioned preinstalled set of apps, CalyxOS includes many system patches shared by other projects such as GrapheneOS, which include privacy enhancements on default AOSP DNS fallbacks, connectivity checks, NTP, and more.

I would also like to mention that Signal does not require microG or Google Play Services for auto backup (or notifications). The backup files are stored locally on the device and can be easily synced with Syncthing, Nextcloud, etc.

Beware of Signal: it depends on the proprietary Google Play Services library, so even if you don't have the Play Services on your phone, the app is built with the "client-side" code which speaks with it (or with microG) and checks for its presence.

FreeSignal was a project that aimed to remove this dependency completely but was stopped by the main developer of Signal. It is possible to clone Signal's repo and do this work yourself quite easily if you know Java a bit, but it takes time and it is not convenient.

> Beware of Signal: it depends on the proprietary Google Play Services library, so even if you don't have the Play Services on your phone, the app is built with the "client-side" code which speaks with it (or with microG) and checks for its presence.

That exposes client information to Google but not content. Besides, if my understanding is right, The Signal Protocol is non-repudiable, which means there's no way for an external party to conclusively prove if the communication did indeed take place.

It probably exposes nothing at all to anyone if the Play Services are not on the phone or the relevant feature is not enabled on microG. But it is still a chunk of code that is partly run and that you don't control. It probably just does what it says (check if the service is present), but it is a black box.

What's the problem there? If the code is there but not executed, and no data is sent to Google, is there any risk as a user?

It is executed to test the presence of the Google Play Services on the phone when the app is launched.

Then, it's probably not risky, but it is still proprietary code that you can't inspect and verify. You can't easily know if the library will not silently do something. If you are seeking to avoid running any proprietary code, then it's something you want to avoid.

Right, but you were talking about "even if you don't have the Play Services on your phone", which is what I'm worried about - but OK, if it's just because there's a chance it might be running, then I'm not too afraid of that.

At the risk of laboring the point, I'm talking about the piece of code embedded in the Signal application, that tries to talk to the Play Services. Not the Play Services themselves. This piece of code is definitely running whenever Signal is launched, "even if you don't have the Play Services on your phone". It probably does nothing significant when the Play Services are not present but still, it's there and (a small) part of it runs.

Now you have several options:

- you trust Google and trust this code not to do anything when the Play Services are not running

- you don't trust Google on this, but you don't care neither

- you don't trust Google and care, but you are willing to take the risk

- you don't trust Google and care, and are worried, or are not willing to run any proprietary code out of principle: you need to adapt Signal's code or dish the app entirely

> It probably does nothing significant when the Play Services are not present

Right, that's the part I care about. I think there are two possible situations:

- Signal's own open source code can detect the absence of Play Services and not call out to Google's proprietary code in the first place. Great, no problem there.

- Google's proprietary code attempts to use Play Services and doesn't do anything when it's not present. In that case I do indeed trust Google enough that I wouldn't expect it to actually do anything else, i.e. the first option you mention.

CalyxOS doesn't change the default connectivity checks and NTP. GrapheneOS does (NTP isn't used though [1]).

[1] https://grapheneos.org/faq#default-connections

Ah, okay, makes sense.

The network connectivity, NTP issues and others are the reason why I have Termux installed (to be able to modify the /system/etc/hosts file, as the network core library ignores VPN settings).

Granted, streamlining these apps makes more sense to the end user. I wish Android would have a package manager that would allow creating a meta package for this kind of stuff.

> because Signal still requires microG or other Google Services for their auto backup, which I don't agree with.

I never used Signal with GServices, so I don't know what you mean with auto backup, nevertheless I simply use the backup function and sync the backup folder with my cloud and it works fine for several years now. For me it seems like a hard constrain to use Telegram which is obviously less secure over Signal only because of an auto backup function. Using Android without GServices always has a compromise part.

Signal auto-backup works fine without Google services. Just point it to some local folder.

I too was wondering why LineageOS's forks were being discussed but not LineageOS itself, I assumed the author had made some remarks on it but after reading the article it seems the author made no attempts to explain why forks of LineageOS were chosen over itself.

I'm all in for android forks, I strongly believe improvements in such forks can be up-streamed for the benefit of the entire ecosystem but I'm yet to see a valid justification for recommending something other than LineageOS for someone new to aftermarket android scene.

By far the most important difference is that with CalyxOS, you can relock the bootloader. This means that probably one of the most important security features, verified boot, works on CalyxOS, but not on Lineage.