Using RCS with Google Messages on GrapheneOS

[deleted]

dregrinfuces I can confirm enabling the toggle made RCS work with most recent app.

eatinggrumble84

I updated to the latest version with the toggle. I then uninstalled the old version of Messages, changed the READ_DEVICE_IDENTIFIERS back to "deny" and enabled the new toggle. I then rebooted and installed the latest Play Store version 20260126_00_RC0 and RCS worked immediately with T-Mobile in the US.

[deleted]

I am sure I am just being dumb but where is this new toggle?

[deleted]

Overlay1404

Settings -> Apps -> Sandboxed Google Play -> Play services special permissions

Follow this
https://discuss.grapheneos.org/d/31873-grapheneos-version-2026021200-released/11

chenxiaolong

^^ The website was just updated to mention this as well: https://grapheneos.org/usage#rcs

cb474

eatinggrumble84 Thanks. I'm on the stable channel, so I haven't gotten the new release yet. Can I switch to beta just for one update and then switch back to stable?

[deleted]

cb474 Yes, but it seems that the deployment of this version (2026021200) has been halted.

jcom

RCS working on Spectrum for now at least. Might be a good sign for other MVNOs given Spectrum is a Verizon mvno

Switched to beta channel to get 2026021200, flipped the new toggle then installed Google Messages from the play store, RCS was already Connected. Took a reboot to get it to switch conversations to RCS from SMS, but this seems promising given how simple it was. We'll see if it sticks.

[deleted]

cb474

Yes, you can. After it installs go back to stable. GOS won't install the older, stable version so it'll be fine.

[deleted]

chenxiaolong can confirm RCS is working for me on Mint mobile, Pixel 7, using these instructions.

aaravchen

I don't have the update with the ICC toggle, and I'm going on 4 days without issue, running the latest from the Store (on TMobile).

I haven't tried installing the latest version of the app directly to see if it will do the initial connection or not, but going 4 days without loss of provisioning or authentication means it has been successfully reauthorizing.

Has anyone tried confirming they still can't get initial authorization using the latest Messages app version with the ICC toggle off/not present?

[deleted]

I just installed 2026021200 and reinstalled Google Messages from the Play Store. Like @jcom, I had to reboot before actual messages started getting sent as RCS, but it looks like our long national nightmare is over.

Very grateful to those who worked on the fix!

[deleted]

RCS is working for me, US Mobile using AT&T initialized on latest version of Google Messages. Thanks @GrapheneOS!

aaravchen

Hat
Where did you hear about that (so I can follow along too)? Do we know why it was halted?

[deleted]

Because I gave up previously, I started with RCS disabled. I downloaded and installed 2026021200 (beta). I enabled ICC. Force stopped the Messages app, cleared the cache, and rebooted. Wait for the phone to warm up and connect. I opened the Messages app and enabled RCS waited some time.

Within the hour, on US Mobile Warp (Verizon) it went from connecting to ending with status code 4006 "Not supported: your device does not meet security requirements." I am on Pixel 7a. Messages app is latest at 20260203_00_RC00 and has all permissions. Google Play Services has phone permissions. Messages is default app. I am the Owner user profile.

[deleted]

aaravchen I couldn't download it when I posted the message. Perhaps the servers were just busy. I've been able to download the latest version a few hours ago, though. At the time of writing this message, the version had not yet been released on the stable channel.

cb474

Hat 2026021200 appears to be in stable now. I've noticed I usually get the updates a couple days after whatever date they are labeled with. So I guess the date names are based on when they go into beta or alpha even.

Coincidentally I just got the notification that the update was installed, while I am typing this message. :-) I'll see how it goes.

MrRoboto1212

Johnnyloans Followed this myself.

Tried it 3 times, double checked things... and still stuck on Connecting.
I honestly don't know. Using the latest ver of Messages via Aurora Store. (299663100). Waited ten minutes after each reboot whilst on the RCS screen within Messages.
My phone has not had the READ_DEVICE_IDENTIFIERS adb command enabled. That shouldn't matter.

One of the attempts had RCS disabled, completed the substeps in step 3, re-enabled RCS after rebooting/disabling airplane mode, still nothing.

I don't know why me specifically. Directly with T-Mo

[deleted]

MrRoboto1212 One difference I noticed is that Google Messages was installed via Aurora Store. A lot of the other successful posts (including the post with the steps you followed) seem to say installed from Play Store

[deleted]

Heureka GrapenOS team! It's the first time RCS works on my GOS and with German T-mobile!

What I did to enable it is (see also https://grapheneos.org/usage#rcs):

INFO: RCS currently only working in the Owner user profile of the phone AND with "Google Messages".
Some carriers (e.g. T-mobile!) use RCA verification method (GSMA TS.43) that requires Google Play services to have permission for ICC authentication with device identifiers enabled. This can be granted since GOS build 20260212 in: Settings -> Apps -> Sandboxed Google Play (+) -> Play services special permissions. (+)Note: it is a new dedicated entry below all apps and not within Google Play Services App itself!
-> Toggle it on "Allowing ICC authentication" (default is off).
Ensure that for Google Play services "Phone" permissions are allowed in Settings -> Apps -> Google Play services -> Permissions. (I have currently "Allowed": Network + Notifications + Phone + SMS)
To start clean (especially after many different attempts I decided to):
- tun on Airplane mode
- Uninstall all "Google Messages"
- Restart phone
- Disable Airplane mode
- Install current stable "Google Messages" via Play store (if it works via Aurora is TBC but currently seems not to be the case!)
  during install: --> confirm allow network permission
- Once installed open "Google Messages"
- Confirm to connect G-Messages with your google account
- Confirm "OK" for Spam protection (can be reverted later)
- Confirm "Set default SMS app"!
- In the app open RCA settings via: Avatar Icon top right -> Messages settings -> RCA chats and enable RCA (if it is disabled else just leave it on)
- wait and see for some minutes (for me it was <1 min) an then "Status: connected" was shown.
If you select a different approach, you need to make sure Google Messages is set to be the default SMS app and (TBC) likely that it is connected with your google account.
Once the RCA status is in "connected": Test to send a message to one of your contacts that has RCA enabled -> this is indicated with "RCA" next to the entry in contacts in Messages.

Confirmed on 15.02.2026 to work with Pixel 9 Pro XL on build 2026021200 with no betta or downgrade workaround at all and default settings except the new "Allowing ICC authentication" enabled.

ONLY remaining improvement would be, to introduce a notification when google messages is installed asking to enable "Allowing ICC authentication vor RCA messaging" on phones where the service provider is known to use an RCA verification method (GSMA TS.43). Else this will be frustrating for many (new) users! Same is true when it is installed but the sim/carrier is replaced with a new one.

Thanks a lot folks!

« Previous Page Next Page »