Description: Google listed a fix for Pixel eSIM profiles that refuse to stay enabled. Identify the Android 17 beta build, check the SIM toggle safely, and understand why erasing an eSIM or leaving beta can make matters worse.
If you enable an eSIM on a Pixel and the switch immediately slides back to Off, Google has documented that exact behavior. It appears in the Android 17 QPR3 Beta 1 fixes released October 2, 2026, under issue #541436675. This is a beta-branch fix, not a promise that every stable Pixel has already received it. Start by checking which software branch your phone actually runs.[1][3]
Is it the same as having no signal?
Not quite. The documented failure is the Use this SIM control reverting to off without an error. A carrier outage, a missing signal bar, failed eSIM activation, or a data-only problem can look similar but require different checks. Google's release notes do not identify a single affected Pixel model, carrier, or first broken build. Avoid treating one online report as a device-wide failure rate.[1]
| Software | What the evidence says |
|---|---|
| Android 17 QPR3 Beta 1, October 2 | Google's listed fix for the eSIM toggle problem |
DP11.260918.005 |
Reported QPR3 Beta 1 build for Pixel 11 family |
DP11.260918.006 |
Reported build for other supported Pixels |
| Stable Android / QPR2 beta | Different tracks; do not assume the QPR3 patch is offered on your track |
Four checks that preserve your eSIM
- Connect to Wi-Fi and arrange a backup way to receive important calls or authentication codes.
- In Settings → About phone, record the build number. Check your enrollment on the Android Beta Program page. A QPR2 beta and a QPR3 beta are not interchangeable update labels.[3]
- Open Settings → Network & internet → SIMs, choose your eSIM, and observe Use this SIM. If it flips back off, note the time and exact wording; menus differ slightly by region.[2]
- Try a normal restart once, then check Settings → System → Software updates for an update offered to your current track. Ask your carrier whether the plan is active and whether it has a local outage. A restart is a test, not proof of a permanent fix.
Should you install QPR3 just to get the fix?
If your device is already on the QPR3 beta track, review the official update offered to it. If you're on stable Android or QPR2 beta, weigh the beta risks before switching branches: Google lists an August 5, 2026 security patch level for QPR3 Beta 1. Google's beta program also warns that leaving for a public stable build generally wipes local device data, except for specific no-wipe windows.[1][3]
Do not tap Erase eSIM as a troubleshooting shortcut. Deleting a carrier profile may require a new activation from your provider. Factory resets and manual downgrades are bigger risks still. If the toggle remains broken, send your carrier or beta feedback channel the build, model, timestamp and symptom rather than repeatedly deleting profiles.[2][3]
Bottom line
Google listed the self-disabling eSIM toggle as fixed in Android 17 QPR3 Beta 1. Verify your installed build and carrier status first, and use the official update for your own branch. Keep the eSIM profile intact while you investigate: the thing you want to repair is the connection, not your phone's entire setup.
Sources checked: 2026-10-17 [1] Google, Android 17 QPR3 Beta 1 release notes (2026-10-02), issue #541436675: https://developer.android.com/about/versions/17/qpr3/release-notes [2] Google, Use dual SIMs on Pixel (SIM settings, eSIM deletion, carrier requirements): https://support.google.com/pixelphone/answer/9449293 [3] Google, Android Beta Program (build eligibility, program switching, data-wipe warning): https://www.google.com/android/beta [4] Google Issue Tracker, #541436675 (public issue reference; detailed reproduction may require sign-in): https://issuetracker.google.com/issues/541436675 [5] Droid-Life, Android 17 QPR3 Beta 1 released (2026-10-02; build-to-device mapping): https://www.droid-life.com/2026/10/02/android-17-qpr3-beta-1-released-for-pixel-phones/
