Using RCS with Google Messages on GrapheneOS

GrapheneOS

You should use a current version of Google Messages and keep it updated, not an old version. Carrier Services is definitely not needed and should be removed if you installed it.

SavyNanner

Is there a way to confirm if you are being rate limited? I was definitely playing around trying other's strategies including an older aurora version after it not working. Had an 1002 error at one point saying sim wasn't supported (us mobile) and tried going back to play store version and connecting...I guess I'll just let it go for a little and then disable for 3 days to try again after.

5rlyn

SavyNanner in the RCS Chats section of the app, where you get the "Trouble Connecting, Awaiting Retry" notification, click on details and you'll see a "Last Attempt" and "Next Attempt." The more you try to connect RCS unsuccessfully, the longer that window will increase (it'll start at an hour and eventually push to 8, 12, 24, etc)

SillySaurus

SavyNanner Is there a way to confirm if you are being rate limited?

No, and nothing appears in logcat either regarding that because it happens server side.

SavyNanner I'll just let it go for a little and then disable for 3 days to try again after.

I would just disable RCS with the toggle, and for good measure do https://messages.google.com/disable-chat the reason is because on one of my phones when i disabled RCS with the toggle, another phone still thought it had RCS enabled. The google page is meant for if you like lost your phone and could no longer disable it, but it works great in this case too.

Leave it 2 or 3 days, then clear Google Messages data (this won't wipe your messages or anything) and use above permissions that would be my suggestion to anyone who can't get this working right now.

canondrum

I confirm RCS is working again with this Alpha/Beta !
Before upgrading, I turned off RCS in Google Messages like a week ago, to be sure to not be rate limited by Google.
I also cleared cache and storage for the Google Message app.
I upgraded, turned on RCS : it worked instantly. Awesome.

Great job by the GrapheneOS team. Bravo ! 👏

ButtholeBlackhole

Hmm... I'll have to try this out when it hits stable. I'm not too keen on installing alpha/beta builds on my phone.

ElliesSurviving

ButtholeBlackhole alpha/beta builds are the same builds that eventually reach stable, if there any real bad issues it wouldnt have gotten past the alpha stage, its currently in beta as of now

WestQuester

Mint Mobile here, having issues still. Contacted Mint they said it wasn't on their end. I've tried rebooting, uninstalling, clearing cache and storage, the Google disable-RCS link. Always gets stuck on Status 3000, "Connecting" and after a while goes to code 3200.

ElliesSurviving alpha/beta builds are the same builds that eventually reach stable, if there any real bad issues it wouldnt have gotten past the alpha stage, its currently in beta as of now

By that logic, we shouldn't even need alpha and beta testing :)
Not every alpha and beta reaches stable. Thus the hesitation.

SillySaurus

WestQuester ontacted Mint they said it wasn't on their end

That would never yield a meaningful conversation. Support staff are not aware of security policies on the backend network like that, apart from the fact this is in relation to Google's provisioning and nothing to do with them anyway.

Disable RCS come back in a few days time, be patient.

WestQuester Not every alpha and beta reaches stable. Thus the hesitation.

Yes in this case, because testing.

mousetrapreplica

WestQuester I'm on Mint and build 2025100901 and got it working. I hadn't messed with RCS in a while before it connected, as SillySaurus suggested it might be good to turn RCS off for a couple days and then retry following SillySaurus' steps above: https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/1187

WestQuester

mousetrapreplica That's good to know, thanks. For reference, I had turned RCS off back in early September so this was the first time it had been attempted to be turned on in about a month.

But I've turned it off again and will try again in a few days. Out of curiosity, what permissions do you have for Google Play Services and Messages?

SillySaurus

WestQuester But I've turned it off again and will try again in a few days. Out of curiosity, what permissions do you have for Google Play Services and Messages?

Nothing special see the post above.

These things are obviously minimal, you may need other things like photos, or microphone in messages if you leave voice recordings or take photos in Google Messages, or use media scopes.

agenda5200 With the latest updated applied im seeing RCS "connected" but messages sent and received are still SMS. Do I just need to wait a bit?

That sounds like Etouffee is not provisioned and you may be rate limited. You can check in the Google Messages debug menu.

If you see:

Etouffee provisioned: false

You will not be able to start RCS chats. It needs to switch to true. and you need to be on 2025100900 or greater for that to happen. If you didn't mess with the phone since before September and Etouffee was still provisioned previously then applying the latest GrapheneOS update is all that is necessary. (I checked that on two handsets).

agenda5200

With the latest updated applied im seeing RCS "connected" but messages sent and received are still SMS. Do I just need to wait a bit?

billinmtl

agenda5200 Try restarting your phone. I had the same issue, and after a restart it still showed SMS but then switched to RCS.

WestQuester

SillySaurus Yes, I already read your post and followed it first thing this morning. I was asking mousetrapreplica specifically since he's on Mint like I am.

SillySaurus

WestQuester specifically since he's on Mint like I am

That won't change anything, as far as GrapheneOS/permissions are concerned as it is Google doing the rate limiting, not the carrier.

WestQuester

SillySaurus I've followed the RCS saga for a long while. T-Mobile and Mint (which is on the T-Mobile network) are the two with the most problems. Any potential datapoints I can get as to why a person with a similar setup to mine works but mine doesn't, may prove helpful. More information is better than less when troubleshooting.

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.

dylen

after a quick install of the Beta channel, a cache clear of Google Messages (it was already set to default SMS), and nothing but Phone + Network permissions for Play Services, & RCS is up and running smoothly! Freedom Mobile in Canada on a Pixel 7 Pro.

thank you team for a swift fix! just installed GrapheneOS last week and already better/fast security patches than Google. cheers!

SillySaurus

dylen Phone + Network permissions

Can confirm i checked that again and was able to provision with that didn't need Contacts or SMS. Contacts is used for syncing contacts to a Google account.

TheExtremelyDirtyDan

SillySaurus does the VPN need to remain off even after connection? It wouldn't be the worst thing if I have to split tunnel, but ofc I'd rather not if I don't have to.

SillySaurus

TheExtremelyDirtyDan nah after it's provisioned that's fine.

« Previous Page Next Page »