- Modem Partition Mismatch: The June 2026 Android 17 update has introduced a bug where Pixel 10 and 11 modems fail to authenticate RCS chats when transitioning from Wi-Fi to cellular data.
- Smart Switch Corruption: Users migrating data from legacy devices via Samsung Smart Switch or Google’s Restore Tool are seeing “corrupted cache tables” in the eUICC chip manager, preventing mobile handovers.
- Satellite Handover Failure: A primary cause for the “Connecting…” hang is a failed handshake between terrestrial 5G/6G towers and the new Android 17 Non-Terrestrial Network (NTN) satellite features.
You step out of your front door, your Pixel 11 Pro seamlessly drops the Wi-Fi 7 connection, and your 5G/6G signal bars hit the ceiling. But then, the silence hits. Your outgoing messages hang in limbo, and your “RCS chats” status in Google Messages flips to a permanent, agonizing “Connecting…” loop. For a segment of Google Fi customers running the newly minted Android 17, the dream of ubiquitous rich communication has hit a massive technical roadblock.
This isn’t just a minor lag—it’s a specific protocol failure. While your data works for browsing and streaming, the specific handshake required for RCS on mobile networks is failing to complete. If you’ve recently used the new tools to switch from iPhone to Android, you might be particularly vulnerable to this metadata mismatch.
The Android 17 “Modem-Partition” Ghost
As of late 2026, technical forensics suggest the issue lies within a modem-partition mismatch introduced in the August 12, 2026, OTA update. Pixel 11 owners are reporting that the phone’s internal “Rescue Party” protocol occasionally triggers when trying to re-verify RCS over cellular, fearing a network-level spoofing attack. This is compounded by the new Satellite-Messaging Handover feature; the device often gets stuck “searching” for an overhead satellite instead of locking onto the available Google Fi (T-Mobile/UScellular) ground towers.
⚠️ Warning: The “Rescue Party” Loop
Attempting too many rapid force-closes of the Messages app while on mobile data can trigger a “Rescue Party” boot loop on Android 17. Always perform fixes while on a stable Wi-Fi connection first.
Why “Smart Switch” is Part of the Problem
The “Smart Switch” cache corruption is a trending culprit. When users migrate their data, the eUICC (electronic Universal Integrated Circuit Card) manager sometimes carries over legacy provisioning tokens. These tokens are incompatible with the Android 17 security architecture, leading to a “Connecting” hang that Wi-Fi ignores but mobile data enforces due to stricter carrier-grade NAT (Network Address Translation) rules.
Troubleshooting the RCS Connection Loop
If you are among the Google Fi users affected, the community-standard fix has evolved. Since Google chose to discontinue the Pixel Pass subscription, many users are handling their own tech support—and the following “patch” sequence is the most effective current workaround:
- Engage Airplane Mode: This kills the radio state and prevents the modem from attempting a satellite handshake during the reset.
- Clear “Carrier Services” Cache & Storage: Navigate to Settings > Apps > All Apps > Carrier Services > Storage & Cache. Clear both.
- Clear “Messages” Cache: Do NOT clear storage for Messages unless you have a cloud backup, as this may delete local threads. Only clear the cache.
- The eUICC Reset (Optional): If the issue persists, go to Settings > Network & Internet > SIMs and select “Reset External SIM” (ensure you are on Wi-Fi to re-download your Google Fi profile).
- Disengage Airplane Mode: Restart the device and allow the “RCS chats” to re-verify over Wi-Fi before testing mobile data.
“The issue appears to be a provisioning error where the mobile data ‘handshake’ isn’t recognized by the Jibe servers under the new Android 17 identity headers.”
— From the official Google Fi Wireless Help archives.
While Google has not yet pushed a server-side “hotfix” for this specific 2026 bug, the company is aware of the reports surfacing on the Android Issue Tracker. For now, Pixel owners on Google Fi should keep a close eye on their “Carrier Services” app version in the Play Store—a silent update there is the most likely long-term resolution for this communication breakdown.
