Using RCS with Google Messages on GrapheneOS

GrapheneOS

cb474 RCS currently only provides end-to-end encryption between Google Messages and itself. That's a Google Messages feature.

cb474

GrapheneOS RCS currently only provides end-to-end encryption between Google Messages and itself. That's a Google Messages feature.

Okay, it's still better than not having encryption. Also RCS is more secure (less easily hacked) in other ways that don't have to do with end-to-end encryption. Whereas SMS is wildly insecure and easily hacked. So my point remains that Google's verification protocols that are breaking RCS on some platforms are undermining security (by sending people back to SMS) in the same of "verification"/security.

EndoPlant

I recognize what was said above in terms of the 2025090800 update not changing anything related to the modem/that would break RCS. I am not blaming the update, but my experience was that I got RCS working a day or two before I received 2025090800 while I was on 2025090600 and it worked fine. I then installed 2025090800, and then it stopped working right after that. As soon as I opened google messages after the update, I was able to receive but not send RCS messages. I disabled RCS chats and reenabled them, and it's been stuck on "Setting up..." ever since. I have tried clearing cache+storage, deleting and reinstalling the app, removing my phone number from google's phone verification site and reenabling it, etc. Nothing has helped so far.

5rlyn

EndoPlant my experience as well. I don't doubt what GOS says, but my troubles started after the reboot for 2025090800. Refreshing constantly trying to get 2025091000

RazTheCat

I can confirm. This is happening to me as well. Unless Google is doing f-ery on their end, which I wouldn't doubt, this seems to be new behavior since 2025090800.

Judgeadam

Quick further update not sure if it is connected. Since all this happened over the last day or so people who call me were getting "disconnected or changed number" Verizon msg. I called and they had to manually push a "security update" of my carrier settings to get me back up. I still can't send RCS but it says connected still. Fwiw

catp96

Can confirm this has started happening to me recently. It was a bitch to setup anyways and this is no fault to the GrapheneOS maintainers/contributors, and the extended FOSS Android community. Google Messages and how their RCS protocol works with their client is a black box. It's a miracle any of us got it working in the first place to be honest.

Reep236

Similar to others, RCS was broken on 2025090800. Updating to 2025091000 has since fixed the issue, unsure as to why.

cb474

Reep236 As I've said above, RCS broke for me two days ago and I'm on 20250813_00_RC02. That's the version Google Play is giving me. Are the people with 2025090800 and 2025091000 using the beta program?

Viewable8616

cb474 I did also upgrade to ver 2025091000 from 2025090800 by activating the beta channel. I was able to get my device to say connected but it is doing the same thing as before where i can only send in sms even tho rcs says connected.

RazTheCat

Okay, so I did an experiment and reverted to stock, with stock firmware and re-locked bootloader. Now I'm getting "RCS unavailable on this device". People are reporting it for other ROMs on XDA. This looks to be an issue on Google's end.

Carter

RazTheCat That's pretty relieving. I was a little worried that google was targeting custom ROMS

Syberkonda

RazTheCat So you're getting RCS unavailable for this device even on the stock ROM? How bizarre.

Were you getting "Your device does not meet security requirements" on GrapheneOS (if you were using the messages beta)?

lcalamar

Just following along - but after spending some effort trying to enable RCS in google messages (stuck verifying phone number) - I came here and see this is likely a GOS issue... :(

Any updates or eta would be great!

cb474

Viewable8616 I'm confused now. When people are referring to 2025091000 are they talking about a Messages version or their GrapheneOS version?

RazTheCat

Syberkonda It was verified and has been working in GOS for the past month. It just started saying "Sending as MMS" yesterday afternoon, while still having the green check mark. That's what prompted me to try stock.

ElliesSurviving

cb474 they are likely talking about the latest GrapheneOS release, i dont see why any of that would change anything on the RCS side however, the changes are completely unrelated, the project account on discord seems to be looking into this regardless so there is something else that would have to be done

MiniSota

I just reflashed stock Android and initially Google Messages said your device does not meet the minimum requirements for RCS chats, but after I cleared Messages cache and storage and rebooted it reconnected and I can send and receive RCS again.

reflex4440

MiniSota

Just to add another data point: I reflashed stock Android on a Pixel 6 Pro (AT&T, physical SIM) and RCS immediately activated.
Over the past few days I have tried every trick mentioned on the GrapheneOS forums, Reddit, and elsewhere on an exhaustive Google search. That includes many versions of Messages, every set of permissions granted to Messages / Google Play Services, and complete reinstalls of GrapheneOS (and stock).
I have been using RCS for over a year so far on GrapheneOS before these issues started.

I agree that there are probably compatibility issues going on with many carriers, but my data point still suggests there is something unique going on with GrapheneOS.

Jandals

Was on GOS 2025090800 and RCS broke. Upgrading to GOS 2025091000 immediately fixed it. I've found that I get disconnected and unable to send single-recipient RCS (can still receive and send/receive in group chats) when I lose service then reconnect. I take an elevator every day that kills my service. After toggling airplane mode while in the elevator, I haven't lost my full RCS abilities for 3 weeks.

Pixel 7
US Mobile, Warp Network (Verizon)
GOS v2025091000

cvsickle

Jandals You didn't have to do anything to get it to reconnect? I updated this morning, and I'm still stuck at "Trying to verify your phone number...", but I also did a bunch of stuff to try to get it connected while on 2025090800, so I may have broken something.

Jandals

Jandals jk it's back to saying I'm connected to RCS but not sending messages. Reduced functionality even, as I can't participate in my group chats.

« Previous Page Next Page »