Your GrapheneOS device supports both physical SIM cards and eSIM profiles. Setting up cellular connectivity correctly ensures you can make calls, send messages, and use mobile data — while understanding exactly what information your SIM exposes and to whom. This guide covers both physical SIM and eSIM configuration, dual SIM operation, and the privacy considerations that come with carrier connectivity.
A SIM card — physical or embedded — is your device's identity on the cellular network. It tells your carrier who you are, where you are, and when you are active. Unlike app-level tracking, SIM-based identification operates at the network infrastructure level. You cannot block it with a setting or an app. Understanding this is essential to making informed decisions about how you connect.
GrapheneOS does not change how cellular networks work. It cannot make your SIM invisible to your carrier. What it does offer is control over everything else: how apps access your network state, how your device identifies itself on Wi-Fi, and how you compartmentalise connectivity across profiles. Getting your SIM setup right is the first step in that chain.
Setting up a physical SIM on GrapheneOS is straightforward:
For most major carriers, no further configuration is needed. The device reads the SIM's carrier profile and configures itself. If you experience issues, see the APN configuration section below.
eSIM on GrapheneOS requires an additional step that stock Android does not: you must enable eSIM support before you can add an eSIM profile.
Important: eSIM management on GrapheneOS does NOT depend on Google Play Services. The eSIM stack is handled by the operating system directly. Adding, removing, or managing eSIM profiles does not share data with Google Play, even if sandboxed Google Play is installed in the same profile.
After adding the eSIM, check that your carrier name appears in the status bar. If data is not working, tap on the eSIM entry in SIM settings and confirm mobile data is enabled. Some carriers may require a reboot after initial eSIM activation.
The most common issue is the "Checking network info..." screen that appears to hang during eSIM download. If this happens:
Note on eSIM PIN: If your eSIM carrier supports or requires an eSIM PIN, keep the eSIM support toggle enabled at all times. Disabling eSIM support while an eSIM PIN is active can create complications when re-enabling.
Pixel devices running GrapheneOS support dual SIM operation — one physical SIM and one eSIM active simultaneously. This is useful for separating personal and work numbers, using a local data SIM while travelling, or maintaining a data-only SIM alongside a voice SIM.
To configure dual SIM defaults:
Both SIMs remain registered on the network simultaneously. This means both are visible to their respective carriers at all times, regardless of which one is set as the default for data.
Most carriers configure APN (Access Point Name) settings automatically when a SIM is detected. If your mobile data is not working after SIM insertion, you may need to configure APN settings manually.
This is most commonly needed with smaller carriers, MVNOs (mobile virtual network operators), or data-only SIM providers.
A SIM card — physical or eSIM — inherently identifies you to the carrier network. This is worth understanding clearly:
For users seeking higher network-level privacy, consider a data-only eSIM combined with a VoIP service for calls and messaging. A data-only SIM from a privacy-respecting provider, paid for with minimal personal information, reduces — but does not eliminate — carrier-level identification. Voice calls and SMS over the cellular network are not end-to-end encrypted and are logged by carriers.
This is not a limitation of GrapheneOS. It is how cellular networks function globally. GrapheneOS protects everything above the network layer — app behaviour, data access, permissions, and local storage. The network layer requires separate, informed decisions about which SIM you use and how.
No SIM configuration — physical, eSIM, or dual — makes you invisible to the carrier network. Cellular connectivity is inherently identifying. GrapheneOS mitigates app-level and device-level tracking with strong defaults, but the carrier sees what the carrier sees. If network-level anonymity is a requirement, that demands decisions beyond SIM setup: dedicated devices, prepaid SIMs acquired without personal identification where legally available, and acceptance of significant usability tradeoffs.
For most users, the practical goal is control and awareness — knowing what your SIM reveals, to whom, and making deliberate choices about connectivity.
SIM and eSIM setup on GrapheneOS is functionally simple — insert a physical SIM or enable eSIM support and scan a QR code. The complexity lies in understanding what that connection exposes. Configure your SIMs deliberately, use dual SIM to separate contexts where useful, and recognise that carrier-level privacy is a separate problem from device-level privacy. GrapheneOS handles the latter. Your SIM choices handle the former.
Need a device ready for secure connectivity?