Using RCS with Google Messages on GrapheneOS

RockHyrax

Jimmy2times i am also on verizon and RCS connected instantly after updating.

this is what i did:

gave play services SMS permission
uninstalled google messages
updated to 2025100900
installed google messages from playstore
set it as default SMS app
RCS successfully connected

i did have to reboot after successful connection in order for RCS to actually send/receive.

Jimmy2times

RockHyrax
Did you try it with Aurora version of Messages too? I will try again using the Play Store even though it didnt work in the past. I would prefer not signing into a Google account. Adding SMS permissions to Play Services now shows "Setting Up", so maybe it is required for some carriers? I'll kept you posted. Hopefully soon we will have knowledge of really what the issue is and clear guidelines to remediate. I know its probably difficult reverse engineering whatever Google did to break it for GOS.

Edit: tried using Play Store with signed in account version of Messages. Instantly gives Not Supported 4001 code. Both "Last Attempt" and "Next Attempt" show the same date and time, so I dont think its a rate limiting issue as ive had RCS chats off most of the time for the past month.
Wonder why it works for others on Verizon. Bummer. Thanks anyway.

chas1776

It's working for me. I have a 9a on a vzw mvno. I am not using a google account nor do I have carrier services installed. Play services has network and phone permissions and messages has everything save for location. What I did to get connected:
1) I used adb to give messages permission to read device identifiers.
2) deselect messages as default sms app
3) clear data for messages
4) grant necessary privileges to messages
5) grant play services phone and network
6) select messages as default sms app

Mine connected immediately doing this.

ButtholeBlackhole

Turtacular Nope. That did not work for me. I tried that exact version he mentioned and that one straight up says RCS isn't available on my device. It didn't even try. I'm on Mint now. (Last update when I tried I was on AT&T then.)

Turtacular

ButtholeBlackhole that's peculiar. I'm also on Mint, as are the other two devices I tried. One of the three devices, a Pixel 7, gave that same "not supported" message for about 15 seconds before I backed out of that screen and reentered to find it connected. Sorry I wasn't more help; I hope someone else has more info to help you get it working.

RockHyrax

Jimmy2times no i do not use Aurora store. Only playstore & Obtainium. SMS permission is explicitly listed that it is required for play services for RCS enablement. We do have the knowledge of what broke RCS on GOS as GOS themselves has posted about it in numerous conversations.

I would suggest you try the exact steps that GOS lists to enable RCS

edit: sorry my mistake. playservices needs Phone permission, not SMS.

Twlight-Princess

Been trying all morning since the latest update. Mint mobile user
no matter clear cache or app data, uninstalled messages, suggested permission set, or many reboots.
I still keep getting stuck at connected, trouble connecting, awaiting retry. at one point I was stuck at setting up.

I did try the older version, couldn't even set as default sms got a secure privacy error ?
on my account phone number page show both my cell number and GV number verified show my pixel 7a verification in progress.

HIghQualityH2o

Twlight-Princess I gave up. I've been at this for days No combination worked for me. Mint eSIM on P9P.

ralm

I tried it with build 2025100901 and the latest Google Messages from Play Store but no dice. Started over with the older Messages described above and RCS was already connected by the time I got to its settings. Messages app updated through Play, a reboot for extra measure, got the RCS prompt and RCS messages seem to be sending and receiving. Pixel 7 Pro on Mint Mobile.

Twlight-Princess I did try the older version, couldn't even set as default sms got a secure privacy error ?

That's a restrictive permission that can be un-done in Settings/Apps/Messages/Permissions then upper-right 3-dot menu. Once it says 'All permissions' Messages won't be greyed out for making it the default SMS app. Using adb to install the apk instead of tapping it will probably get around this.

ProfessorMonks

For all the trail blazing, and positive work GOS are doing, this is a gentle reminder to consider donating a couple bucks a month. It really adds up for them if many donate a little.

https://grapheneos.org/donate

Twlight-Princess

HIghQualityH2o Yeah I think at this point I'm throwing in the towel myself.

jumpdeer

HIghQualityH2o

Have you tried the downgrade app method?

Twlight-Princess
Were you able to get the old version of google messages to be the default sms app? You need to go into google messages app info, click the three dots on the top right, and allow it restricted settings.

Twlight-Princess

jumpdeer Alright so that actually worked and it got connected. But still sending SMS even after a reboot of the phone.

I wonder why that it is working with an older version. Can I Update the app now via google play store?

Twlight-Princess

ralm & jumpdeer So I got the older version installed and was able to set it as the default SMS app. I got connected as it seems even got a pop up about RCS. I have updated from google play and done a couple of reboots. But still sending SMS although it now shows I'm connected.

Twlight-Princess

jumpdeer & ralm after like 3 reboots maybe more lol it seems to be working now.

nulifyer

The 2025100900 update fixed RCS for me! Thank you to those that worked to make this happen.
Definitely deserves another donation to keep this dev team going!

Installed via Aurora Store.
Is up to date.
Play Services: Network & Notifications
Google Messages: Default Permissions except camera and mic
Shows: connected.

spammerofspam

Is it normal that Messages simply crashes when I select the "Report RCS Connection State" option in the debug menu?

Trying to troubleshoot RCS on T-Mobile on my P9P. I might just try the old version and then upgrade approach that others have suggested with T-Mobile, since it's hard to troubleshoot this way.

CrashTootall

spammerofspam I think an older post in this thread said Messages will crash with that debug option if Etouffee is not provisioned.

ralm

Twlight-Princess Nice, definitely leave it be and give it time. I'm not confident in my setup until I've used it more. I think once connected we're going to see mixed results depending on message participants with or without RCS, different devices and carriers... But at least we're seeing progress.

Twlight-Princess

ralm agreed, I will tell you it seems to have been working with my friend and nephew whom both have iphones and my father and mother who have samsungs.
Hopefully it stays that way and gets better.

oh and I noticed on myaccount.google.com the phone section it no longer saying verification in process. and I did log into that page via web browser on my phone as well.

nowcircumscribeyahoo

Vuraze
I'm on a P9 with T-Mobile, and this was the only solution I have found so far. Used APKmirror and updated from play store. Had to clear play services and messages cache + reboot to finalize the connection.
Not all features work between iphones; Only I get the typing bubble, and reactions/replies don't fully work or behave like SMS.
Videos/pics and normal texts work fine, read receipts work.
No testing for Android-Android.
I'm wondering if there needs to be a new line inserted or another string deleted specifically for T-Mobile. The only way I got RCS to work prior was using an older APK and updating. Same story here.

emb

Is it a good thing that doing:
adb shell appops get com.google.android.gms
gives me this line,
USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER: default; rejectTime=+14m47s543ms ago
(among others)?

From the Android docs, this is "often required in authentication to access the carrier's server and manage services of the subscriber."

I tried granting it, but it won't change the mode from "default" to "allow."

« Previous Page Next Page »