Description: Google fixed an Android 17 beta fault that could stop both calls and mobile data. Find the trigger, QPR3 Beta 1 builds, safe checks and the risks of deleting an eSIM or downgrading.
If your Pixel suddenly shows No service and loses calls and mobile data together, a repeated phone-service crash is one possible cause. Google says Android 17 QPR3 Beta 1, released October 2, 2026, fixed issue #554049220: com.android.phone could enter a crash loop when the modem reported unexpected SIM-slot indices.[1] A carrier outage can look similar.
What the official fix covers
The documented trigger is an unexpected SIM-slot index reported by the modem. The phone service repeatedly crashes and all cellular service can disappear. This is not proof that a physical SIM is damaged. Google's release notes do not list every affected phone, carrier or reproduction rate.[1]
Check without wiping data
- Open Settings → About phone → Android version and note the build number.
- Open Settings → Network & internet → SIMs; check the carrier name and whether Use SIM is enabled.[3]
- Consult the carrier's outage page or another phone on the same network.
- Record whether calls, texts and mobile data all fail, or only one service.
Arrange another communication method, such as working Wi-Fi. Toggle airplane mode once and try a normal restart. These are temporary diagnostic steps, not a confirmed permanent repair for this crash.[3]
Builds with the fix
| QPR3 Beta 1 distribution | Build |
|---|---|
| Pixel 11 family | DP11.260918.005 |
| Other eligible Pixels | DP11.260918.006 |
Both are covered by the same Google fix list. This is a build distribution table, not evidence that every eligible model experienced the defect. Check Settings → System → Software updates for your device. Stable Android 17 and other manufacturers require separate confirmation.[1][4]
Preserve your SIM and files
Do not delete your eSIM profile merely because the phone has no service: your carrier may need to reactivate it. Avoid starting with a network reset, factory reset or manual firmware flash. Leaving Android Beta and installing a downgrade may wipe all local data, outside specific public-release transition windows.[5]
If service stays unavailable, give your carrier or Pixel support the model, build, time, SIM type and restart result. For urgent calls, use another functioning phone.
Bottom line
Google fixed a specific cause of complete cellular-service loss: repeated phone-service crashes triggered by unexpected modem SIM-slot indices. Check the build and carrier first, then seek an official update while protecting your eSIM and data.
References (1)
[1] Google, Android 17 QPR3 Beta 1 release notes, October 2, 2026: https://developer.android.com/about/versions/17/qpr3/release-notes [2] Google Issue Tracker #554049220 (some details may require sign-in): https://issuetracker.google.com/issues/554049220 [3] Google Pixel Help, Fix mobile connectivity issues: https://support.google.com/pixelphone/answer/14116080?hl=en [4] Google Pixel Help, Check and update your Android version: https://support.google.com/pixelphone/answer/7680439?hl=en [5] Google, Android Beta Program and data-wipe policy: https://www.google.com/android/beta [6] HelenTech, Android 17 QPR3 Beta 1 release, October 3, 2026: https://helentech.jp/news-pixel-android-17-qpr3-beta-1-92079/
