eSIM on CalyxOS

The Calyx Institute published a letter to its community on 1 August 2025 announcing that CalyxOS development had stopped, following the departure of the institute's founder and the CalyxOS tech lead. An update days later went further and recommended that existing users uninstall, because no further security patches would arrive while the rebuild was underway. That is an unusually honest thing for a project to say about itself, and it should be recorded rather than quietly skipped over.

The rebuild finished. The project redesigned its signing process around a hardware security module, shipped an Android 16 test build in May 2026, and declared itself back in July 2026 with release 7.2.2.0 and normal maintenance. The August 2026 security update is out for all supported devices. The practical consequence for eSIM is simply that you should be running a current build before you try to download anything, because a device stranded on a 2025 image is missing a year of telephony and platform fixes.

On CalyxOS you add a profile the ordinary way, through Settings > Network & internet > SIMs, and the setup wizard also offers an eSIM route when no physical card is detected. There is no hidden developer flag and no separate app to sideload. From the user's chair it is indistinguishable from stock, which is precisely because the component doing the work is the same one stock uses.

That component is Google's eUICC implementation. CalyxOS carries it, and there is an open request in the project's own issue tracker asking to replace it with OpenEUICC, the fully open-source alternative that other de-Googled builds have adopted. Until that request is acted on, the accurate description of CalyxOS eSIM support is that it works reliably and that the download step is not Google-free. Everything after the download, registering on the network and receiving calls and messages, is plain AOSP telephony with nothing proprietary in the path.

This is the most common misunderstanding we get asked about. microG reimplements Google Play services APIs so that apps expecting them will run. It handles push messaging, location backends and the API surface that ordinary applications call. It does not implement the eUICC service interface, and it has no role in fetching a profile from an operator server.

So if you are choosing CalyxOS specifically to avoid proprietary code in the telephony stack, microG does not get you there, and no combination of settings inside CalyxOS currently does. The honest framing is that CalyxOS gives you a de-Googled userland with a proprietary eSIM downloader sitting inside it, used once per profile and idle thereafter. Whether that trade is acceptable is your call, and it is a smaller exposure than most people assume, but it should be a decision made with the facts rather than by default.

We issue a standard GSMA activation code, identical in form to what any operator would send you. Whether your handset accepts it is decided by your build and your hardware. We sell the eSIM profile. We do not control whether a given ROM can install it, and we will not pretend otherwise to close a sale. Test the device before you pay, and write to us first if anything in that test looks off.

Two specifics matter for CalyxOS buyers. The UK number QR is single use and is never reissued, and that purchase is not refundable if your build cannot download it. And on app verification: the line takes standard SMS and voice calls, which is what verification flows generally use, but no provider anywhere can guarantee a given service will accept a given number.