RCS compatibility on Cape
Quick-reference guide to what works, what you need to set up.
iPhone (iOS)
Supported
Android
Supported
GrapheneOS
Supported
iPhone (iOS) Supported
Requirements
- iOS 18 or later (iPhone XS and newer)
- Cape eSIM downloaded on or after May 11, 2026
- E2E encryption (Beta) must be OFF
RCS
activates automatically for non-iMessage contacts. After
porting your number or downloading a new eSIM, allow up to
15 minutes. If it doesn't appear: toggle off → restart →
toggle back on.
How to enable
- 1Settings → Apps → Messages
- 2Toggle RCS Messaging on
- 3If the toggle isn't there, update iOS and restart
If E2E encryption is blocking RCS
- 1Settings → Apps → Messages → RCS
- 2Turn off End-to-End Encryption (Beta)
- 3Reset network settings → restart → re-enable RCS
Android Supported
Requirements
- Google Messages set as default SMS app
-
Cape
IMSI starting with
314560 - Cape Roaming app set to United States
- IMSI rotation must be OFF
- Device will use LTE, not 5G, while RCS is active
Verify
your IMSI: Cape app → Support → Advanced → Phone Info
Cape doesn't currently support RCS over 5G on Android — enabling RCS
means your device will operate on LTE instead. If staying on 5G matters
more to you than RCS, leave RCS off and continue using SMS/MMS.
GrapheneOS Supported
Setup requirements
- Google Play Services + Play Store (via GrapheneOS Apps, sandboxed)
- Google Messages from Play Store (not the default AOSP app)
- Google Messages set as default SMS app
- Network permission granted to Google Play Services
- Full permissions granted to Google Messages
-
IMSI
starts with
314560(not USCC)
Stuck on "connecting" or "not supported"?
Status code 4006 = Google Play Integrity failure. Clean re-registration:
- 1Toggle RCS OFF in Messages
- 2Settings → Apps → Messages → Storage → Clear Data
- 3Uninstall Google Messages
- 4Reinstall from Play Store
- 5Re-grant permissions, set as default
- 6Toggle RCS ON
Unsupported configurations Not supported
| Configuration | Why |
|---|---|
| IMSI rotation enabled | Incompatible with RCS — must be disabled |
| E2E encryption (Beta) on | Conflicts with RCS — must be disabled |
| RCS + last-mile encryption | These features conflict — use one or the other |
| /e/OS or other custom Android | Only stock Android and GrapheneOS are tested and supported |
Please note:
RCS on Samsung is not currently supported at current.
It will be in the later half of the year when we have official Samsung support.
Although we're no longer in beta, Cape's network will continue to evolve and improve. We keep track of our progress on this page: https://www.cape.co/network-progress
Related: How to Enable RCS on GrapheneOS | Enabling RCS on iPhone