eSIM Was Sold as Freedom. In Practice, It's a Leash.

eSIM was supposed to make switching carriers feel like changing a password. No tiny plastic card, no paperclip, no trip to a store. Just a QR code, a few taps, and you are on a new network. In the US, carriers have spent the last few years selling that story hard. eSIM-only phones are now normal. The pitch is freedom.

The reality for anyone running an open-source phone is messier. The eSIM is not the lock. The workflow around it is.

The Promise vs. the Paperwork

An eSIM is a profile that lives on a chip soldered to your phone. In theory, that profile can be downloaded, moved, and deleted without plastic. In practice, the carrier decides how activation works. Sometimes you scan a QR code. Sometimes you need the carrier app. Sometimes you need a support agent to push a profile to your device ID.

That device ID is called an EID. It is unique to the phone. The carrier uses it to tie your line to the hardware. When you want to move the line to another phone, the carrier has to release it and reprovision it. That should be a self-service button. Often it is a chat session.

Where Ownership Slips Away

The first problem is the app. Many US carriers route eSIM activation through their own app. That app may require Google Play Services, SafetyNet, or a platform-specific API. On a QtMoko-style phone, the app may not install. Even if it does, it may refuse to run because the device is not certified.

The second problem is the platform vendor. Apple and Google sit in the middle of eSIM installation on their devices. They provide the APIs that let carriers deliver profiles. That is convenient if you use their phones. It is a gate if you do not. The carrier may say the eSIM works, but only through the vendor's activation service.

The third problem is eSIM-only hardware. Once the physical SIM slot disappears, there is no fallback. If the carrier's app breaks, if the activation server is down, or if the profile will not transfer, you do not have a phone. You have a screen that can call emergency services and not much else.

Testing the Workflow

I tried to move a prepaid line from a flagship to an open-source handset with eSIM support. The carrier's website offered a QR code. The QR code led to a page that asked me to install the carrier app. The app was not available for my phone. A support agent told me to use the app. I explained the app did not exist for my device. The agent offered to send a physical SIM, which my phone does not have a slot for.

A second carrier was better. It allowed a QR code activation through the phone's built-in eSIM manager. That worked because the open-source build included a standard eSIM management tool and the carrier supported generic activation. It took three tries and one expired code, but it worked.

That is the difference between a feature and a lock. The second carrier treated the eSIM as a standard. The first treated it as an app-controlled service.

What a Portable SIM Stack Needs

A privacy-respecting eSIM stack does not need to be complicated. It needs to be boring and standardized.

• App-free activation. A QR code or a carrier-neutral web flow should be enough. No Play Store dependency. No vendor certification check.
• User-controlled transfer. I should be able to move a profile between my own devices with a confirmation, not a support ticket.
• Open management tools. The phone should expose eSIM management to open-source software. The user should be able to see profiles, delete them, and back them up locally.
• Clear ownership. The carrier owns the line. The user owns the device and the profile on it. The platform vendor should not be a required middleman.
• Regulatory pressure. The FCC and state regulators should treat eSIM portability like phone number portability. Switching networks should not require a specific app store.

The Lock Is Not the Chip

eSIM is not evil. A soldered chip can be more reliable than a plastic tray, and it makes dual-SIM setups easier. The problem is the layer of apps, certifications, and vendor APIs that turn a standard into a permission slip.

Open-source phones pry that open by demanding plain activation, visible profile management, and no app-store gate. If a carrier cannot support that, it is not selling freedom. It is selling a leash with a QR code.