Using RCS with Google Messages on GrapheneOS

namecheckobnoxiously

Thanks for the reply! Google Play has the phone permission granted, Google messages is default with network permission enabled and Play Services Special Permissions is enabled. I've cleared the storage for Google Messages and rebooted. Still getting "Device not supported"

upi_policy_id = upi-zr-mt-with-fallback

inthewaves

Twlight-Princess In my experience, I've tried around 4 different carriers (3 Canadian, 1 US being Tello since they allow non-US to sign up and use Wi-Fi calling), and they've never needed more than what's listed in https://grapheneos.org/usage#rcs. This was on a fresh sandboxed Play services install, so all of the exploit protection settings are also at their defaults (dynamic code loading via memory and storage are both allowed), and internet/sensors are enabled as well. The verification process also involves Play services making API calls to a Google service, so that's another source where verification blocks can happen (e.g. rate limiting, blocking due to some unknown criteria, etc.).

Just now, I disabled RCS on Bell, cleared data for Google Messages, and then opened Google Messages. Now seeing this log line for Play services which indicates that I'm getting rate limited: [verification_manager] Verification API failed with error: syncVerif failed: generic::resource_exhausted: verification resource is exhausted due to too many recent verifications or attempts.

namecheckobnoxiously We do have the same policy then. Can you share some logs from Google Play services with the following steps?

Do this first to have the log viewer prepared in the recent apps: Open log viewer for Google Play services. You can do this from Settings -> Apps -> Sandboxed Google Play -> Play services app info -> View logs.
Now, open Google Messages and go to the RCS settings screen
Toggle the "Turn on RCS chats" off, wait a bit, then turn it then on again
Go back to the log viewer for Google Play services
Tap the search icon and set the filter to verification

userofgos

inthewaves In my experience, I've tried around 4 different carriers (3 Canadian

Did you test Rogers? Does it need the special permission to do ICC authentication with device identifiers?

namecheckobnoxiously

inthewaves :

type: logcat
osVersion: google/mustang/mustang:16/BP4A.260205.001/2026021201:user/release-keys
package: com.google.android.gms:255034035, targetSdk 36
buffers: main,system,crash,events,kernel
level: verbose
filterRegex: verification

--------- beginning of main
03-01 04:45:36.317 14680 26458 I constellation: [verification_manager] No cached state for flow: EXTERNAL_CONSENT_ACTIVITY_STATE
03-01 04:45:36.319 14680 26458 I constellation: [verification_manager] No cached state for flow: ON_DEMAND_CONSENT_STATE
03-01 04:45:36.323 14680 26458 I constellation: [verification_manager] No cached state for flow: ON_DEMAND_CONSENT_V2_STATE
03-01 04:45:39.336 14680 26458 I constellation: [verification_manager] No challenge issued due to state: NONE
03-01 04:45:39.359 14680 26458 I constellation: [event_manager] Successfully synced verification
03-01 04:45:39.366 14680 26241 W constellation: [api_verify_phone_operation] Invalid verification method:

Twlight-Princess

inthewaves Thank you I will tinker around with that. The less things I can give it a permission to the better.

inthewaves

userofgos I haven't tested Rogers yet, but if you are using Rogers, then you can check the RCS configuration using the debug menu steps from https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/2228. If is_ts43_supported and the UPI policy at the bottom contains ts43, then it will likely need the ICC auth permission.

namecheckobnoxiously So after deregistering Bell from RCS and waiting a day, I tried to reactivate, and now my logs are showing the same result, i.e .[verification_manager] No challenge issued due to state: NONE and [api_verify_phone_operation] Invalid verification method:.

I was able to still activate RCS on Tello, so this might be a Bell-specific issue: https://github.com/user-attachments/assets/54ff3375-a809-4c5f-8414-f4597bdbc97f

A search on Reddit reveals users having the same RCS activation issues (https://www.reddit.com/r/bell/search/?q=RCS&restrict_sr=on), so it seems like it's likely broken everywhere.

This post is from 4 days ago: https://reddit.com/r/bell/comments/1rfv4jc/s25_rcs_chats_stuck_on_connecting/. Doing what the commenter said appeared to work for me (I didn't do a reboot or clear data). Could you try these steps?

Go to Google Messages and make sure the RCS toggle is off
Go to Settings -> Apps -> Sandboxed Google Play -> Google Settings
Go to the All services tab and find Phone number verification under Privacy & security
Turn off "Automatically verify phone number(s)"
Go back to Google Messages and turn on RCS and wait

I'm back to being connected to RCS on Bell after following these steps, with the logs showing [verification factory] Doing MT verification (incoming SMS verification) and [verification_manager] Verification attempt finished, new state: VERIFIED

inthewaves

There are other people reporting issues and discussing possible solutions on the official Bell forums as well, if the above steps don't work: https://forum.bell.ca/t5/mobility/rcs-verification/td-p/89565. This seems like a general issue and not GrapheneOS-specific.

loop0

bebop10

I'm curious, are you using a physical SIM? I've done this exact process and still get the dreaded "connecting..." or "not supported".

bebop10

loop0 Sorry for the late reply, but I am using an eSIM. I had to go to ATT to get it transferred from my previous phone to my graphene phone.

namecheckobnoxiously

@"inthewaves"

Thanks for the help!! I'm going through the reddit and bell forum suggestions now. Seems to be stuck on "connecting" for now.

AnonTNR

Hi all, just a quick success story! Brand new user to GOS here. I followed the official instructions on a clean install of GOS and it worked quickly. RCS was marked "connected" immediately in the Google Messages settings. I did have to take one further step, though: in order to establish full functionality, I had to clear Google Messages storage and then reboot.* Worked well from there.

*(The reboot may have been enough on its own? Can't say.)

I'm using a Pixel 8 Pro. My carrier is Mint (T-Mobile). I'm signed into Messages with my real Google account (already connected to my number).

Very grateful for all the work put in to make this go smoothly!

oldschkool

AnonTNR Hi all, just a quick success story! Brand new user to GOS here. I followed the official instructions on a clean install of GOS and it worked quickly. RCS was marked "connected" immediately in the Google Messages settings.

Same here. I've had GOS installed for a week, followed instructions according to the usage guide and RCS is working just fine. I'm quite pleased with my minimalist Pixel 9a setup. :)

Lantash

samsepi0l I have it working on my Pixel 8 What I think did it was turning on the setting Apps > Sandboxed Google Play > Play Services Special Permissions > Allow ICC authentication with device
identifiers.

ejns

I recently switched to US Mobile from Google FI. RCS was working well on Fi, and worked well on US Mobile for several days but today it stopped and now says my device does not meet security requirements. (Status code 4006).

I'm using their Verizon network if that matters. How can I get this going again? Sorry if this has been covered - I can't figure out how to search within this monster thread (any tips there would be appreciated too!)

ejns

Sorry to bump but I'm still stuck. Is there a list of steps to take to get this going?

1-11

oldschkool

Perfect. Was stuck all day after installing and performed the settings recommended in the instructions and immediately regained RCS.

EndoPlant

Just want to mention in case this helps anyone else:

I am a Telus user in Canada and my RCS stopped working yesterday. I tried reactivating it a few times and it wouldn't connect. I looked at the link mentioned above and enabled the ICC authentication permission and it started working again.

Novalissoide

EndoPlant Thanks for reporting.👍

yonecessito

I'm having a strange issue where RCS works but only when the app is open. If someone send me a message through RCS I won't receive it until I open the messaging app. Not sure how to address it. I'm on a pixel 6a.

de0u

yonecessito I'm having a strange issue where RCS works but only when the app is open. If someone send me a message through RCS I won't receive it until I open the messaging app.

This may indicate that Google Messages or some part of Play needs to have unrestricted battery access and/or the ability to run in the background.

Kubiac

Google seems to actively blocking registration on custom Roms. I got the same error "device does not meet security requirements. Status code 4006"

« Previous Page Next Page »