Using RCS with Google Messages on GrapheneOS

seaside

Verizon through US Mobile MVNO works perfectly on the latest update.

AT&T through US Mobile is stuck in connecting status 3200. No settings changes between the two carriers, aside from switching the AT&T sim to be primary. When I try clearing cache/storage on Messages and cache on Play Services, status changes to "Setting up..." and hangs there.

Switching Verizon sim back to primary, it connects and is able to send RCS almost immediately. So it seems the latest update did not fix whatever is wrong for AT&T.

HIghQualityH2o

WestQuester Mint here also using P9P. Followed the permissions and cache clearing tips. RCS went to setting up verifying phone number for about 2 hours then connecting for about 3 hours then connection failed. Still watching the thread.

WestQuester

SillySaurus Google Messages does not need Contacts permission.

SillySaurus

WestQuester I think it does, i just revoked it and reopened the app and it came up with the "You've almost finished" wizard and won't let you proceed unless you grant that, unless you mean using a scope.

SillySaurus

HIghQualityH2o You're probably rate limited, disable RCS and wait out the time.

WestQuester

SillySaurus Pretty sure it uses it to correlate what messages you received from which number to what to label it (e.g., this phone number belongs to this person named John). I could certainly be mistaken.

AxiomPraxis

I just fixed an issue with RCS on GrapheneOS where it wasn't verifying my account, and managed to fix it.

At https://myaccount.google.com I had to disable an old device that somehow was stuck in progress verifying, which is weird because this GrapheneOS install is months old now.

To check this:

From the https://myaccount.google.com

Go to Personal Info on the left
Go to Contact Info in the middle
Click your phone number

My number showed as "Verified" at the top. It should show all of your devices you've used with this phone number.
I have my current Pixel 9 on GrapheneOS which showed as verified, but somehow an old Pixel 7 was stuck "Verifying" on this page, even though that install had since been factory reset. I toggled the Pixel 7 to disable it from this page, and RCS on the GrapheneOS Pixel 9 came up within seconds.

I had also previously cleared the app storage for the Messages app on the 9 but in retrospect not sure if that needed to be done.

Maybe this will help someone else experiencing the issue.

WestQuester

AxiomPraxis Didn't work for me, unfortunately, but good find. Thanks for posting.

DeletedUser638

On T-Mobile RCS still does not work.

I opted into the beta to install it
I deleted google messages
I rebooted
I reinstalled Google messages and waited for apps to optimize
I confirmed google play services had the relevant permission
I disabled phone verification (it was marked as in progress) at https://myaccount.google.com/phone
I disabled my VPN
I opened google messages and enabled it as the default messenger.
Result: Connecting... Status code 3000
I rebooted. Same result.
I refreshed phone verification page. It was turned on by itself and says verification in progress
10 minutes later. Status 3200. Trouble connecting. Awaiting retry. Please wait, activation is ongoing

Vuraze

I'll post it here as well.

It seems that people who are on the T-Mobile network need to use an older version of Google Messages for RCS to initially connect.

Here are the steps I did exactly:

Give Play services the Phone and SMS permission (you most likely don't need the SMS permission, I did it just to be on the safe side).
Download and install an older version of Google Messages. I used Apkmirror, but you can use Aurora Store's "manual download" feature. The version I used was messages.android_20241120_00_RC07.phone_dynamic (262371063). Make sure you have the genuine version installed. Confirm using AppVerifier from Accrescent.
Set the Google Messages app as the default SMS app before opening it. If you accidentally open the app before doing that, simply just clear all app data and you should be fine.
Open the app and wait until it says RCS is connected in the RCS Settings menu. It should only take a few seconds to a minute.
Once RCS is connected, update Google Messages from the Google Play Store.
If you can't send or receive RCS messages, reboot the phone. All missed RCS messages should come flooding.

Here is the correct hash for Google Messages:
com.google.android.apps.messaging
CC:75:52:6D:6C:0F:80:AC:3B:3A:84:EB:44:83:84:40:DB:BE:6B:12:44:43:A7:C7:D7:BD:19:18:2A:C0:22:C9
F7:E7:3D:4E:DC:2B:7F:55:EE:CD:3F:89:8D:3C:CA:7D:A9:CB:BF:51:69:4E:BA:14:F8:16:E2:EC:CF:01:50:35

If someone who uses the T-Mobile or its MVNO's like Mint and Tello has a different way of getting it to work, please post your steps.

Overlay1404

On Mint, Pixel 7, still stuck with status code 3000

EDIT: tried @Vuraze suggestion and that worked.

WestQuester

Vuraze Excellent, that got me (Mint Mobile) back online. I tried the Aurora store first and while that worked I couldn't update from the Play Store (wrong signature I think) so had to go with APKMirror instead. Thanks for sharing this!

Vuraze

WestQuester People are having that issue with Aurora Store so I take it back and would remove it as a recommendation if I could edit the post. It's best to get it from Apkmirror because it doesn't have that issue.

t1c

I got RCS working on my Pixel 9 with Google Fi as of the latest update!! What helped me was doing:

1) Turn on Airplane mode
2) Clear cache of Play Services (NOT storage)
3) Clear stotage of Google Messages, CarrierConfig2, and RcsService
4) Settings > System > Reset options > Reset Mobile Network Settings
5) Reboot immediately (so it doesn't have time to connect after resetting)
6) Open Google Messages, and viola!

DeletedUser474

Installed the 2025100900 update and redid everything, RCS now connects immediately but Etouffee still does not provision, and messages are neither sent nor received. Cleared data and attempted again to make sure I didn't miss a step and same result.

I guess this problem is still more complicated than it appears, and I'm probably going to return to the stock OS for my primary phone. Already a month of my communications flow being heavily disrupted and I can't wait any longer for a full fix.

DeletedUser552

Vuraze Amazing, this worked for me.I went the apk mirror route, and provisioned permissions sms and phone to play services. I use mint mobile.

DeletedUser474

t1c Cleared storage for CarrierConfig2 and RcsService along with Google Messages (resetting mobile network entirely seemed a touch drastic for a first attempt) and now Etouffee is provisioned with RCS sending and receiving for now. Thanks for reminding me of those other related system apps I didn't think to check for!

Fingers crossed it keeps working. Maybe I'll get to keep my primary phone on GOS after all.

carcosa

Vuraze I am on another T-Mobile MVNO (Ting), and have not needed to do any of this. Up-to-date Messages from Play Store, had only worked briefly on the previous release with the official instructions. Turned off RCS for a few days, saw 2025100900 was supposed to fix the issue, installed it, turned RCS on, and it just worked. I've cleared Messages data a few times lately, but not this time.

DeletedUser638

Big thank you to the GrapheneOS team for getting it working (hopefully permanently!). I just set up a recurring donation. I encourage everyone who wanted the team to prioritize RCS support to do the same!

I hope the T-Mobile solution will turn into a more sustainable solution.

mills559

I'm on Google Fi, pixel 9 pro, and I no longer meet the security requirements for RCS?

« Previous Page Next Page »