Using RCS with Google Messages on GrapheneOS

eatinggrumble84

I'm on T-Mobile and it was working with the latest version about a week ago but then stopped again a few days ago and had issues with connecting. I uninstalled and used the steps from @Turtacular. And now it's been connected and provisioned and working again. However I'm curious if anyone else staying on the 20250311_04_RC01 bundle has noticed features missing, specifically photomojis and the ability to reply to specific messages. These features were there with the latest version but the RCS stopped working after a couple days with that version so I have updates turned off.

BuckWylde

eatinggrumble84 Those same issues happened to me too. Things stopped working yesterday after over a week, and I also can't use photomojis after doing the usual fix.

BuckWylde

eatinggrumble84 The photomojis capability just kicked back in all of the sudden fyi

Robbartham

jumpdeer dang, truly my only issue with the OS. Unfortunately RCS is something I need daily living in NA. Hopefully the team can push a fix soon.

SouthernPolish99

I wanted to share an update and a new trick that worked for me, on at&t.

After last weeks sudden RCS disconnected that many experienced, mine came back on it's own a few days later, then disconnected again after about a day. I had previously been able to follow the recent instructions of uninstalling, reinstalling the old version and setting permissions and get my number to verify easily. That is no longer the case. I went through this many times over the last two days without any success at rcs connection.

What I did today that finally helped me: I left my old version of messages alone, I cleared storage and cache from google play services, which then made me have to turn permissions back on and resign into Google. As soon as I did this, messages reverified my number and loaded all missed RCS messages in an instant. Sharing in case it helps someone else.

bolzam

SouthernPolish99 This worked for me!! Thank you for the strategy

snaz

I am using US Mobile with the warp network (Verizon towers). I have the default Messages installed, RCS Connected, says I am chatting in RCS, but it doesn't seem to want to send the messages via RCS. It only wants to either fail to send, or reroute to SMS. Anyone have a clue what could be causing the issue?

HVW

I took our phones back to stock and am doing the best I can with privacy while I wait for fixes.
Hope the Team can get everything sorted with the RCS changes that are no fault of their own.
Our Pixels are great phones and I cannot justify crippling ours.
I feel for my ATT and Tmobile bros. Hang in there !
Will check back in this thread every few weeks.

SnappingWaffle

HVW Just want to echo this, I want to use GOS but I can't work without RCS.

Been checking this thread every so often for a while and it saddens me to see that a fix hasn't been found yet.

BuckWylde

Are there any Visible Mobile users here that can confirm or deny RCS working? I'm thinking of switching from Mint.

cb474

jumpdeer Unfortunately that post on Reddit doesn't really say anything new that hasn't been known for a couple months now. It gives no sense of when a solution might be coming.

It's also a little bit random they way Graphene project representatives communicate with people. Sometimes here, then long silences, sometimes on Twitter, then on Reddit (which supposedly is no longer offcially supported, because people are supposed to come here), sometimes a comment on the github issue for this. I know there are a lot of platforms to keep up with. But it would be nice if there was one centralized place for official announcements and communication.

In goodish news, I've remained on 20250311_04_RC01 for a couple weeks now and RCS continues to work. (I had to get connected with 20241120_00_RC07 and then switch to the former version to get Etouffee to true. This is following @Turtacular's method.) T-Mobile, Pixel 8.

mrmoxey

@Turtacular method worked today for me.

Phone: Pixel 9a
Carrier: US Mobile (AT&T network)

I had to reboot after upgrading. Fingers crossed....

jumpdeer

The most interesting about @Turtacular's method is that RCS connectivity is sporadic for me. Sometimes it'll work for many hours without problems, and then stop working for a few hours, requiring me to send an SMS. Sometimes it will stop working for just a few minutes and then start working without even rebooting.

I'm on T-mobile.

cb474

jumpdeer That's odd. I'm not experiencing that. I'm also on T-Mobile. It's weird to me that people have been having inconsistent experiences, even on the same carrier.

user5678

cb474
P10Pro (GOS 2025121001) T-mobile

@Turtacular 's method has worked for me in general without needing to re-install.

However, some changes to (presumably) Google Play Services permissions (?) broke RCS requiring me to reset.

2 examples: When Nearby Share did not work to Airdrop with a family member's iphone, I disabled Nearby Share and removed Nearby Device permission from Google Play Services--> broke RCS

When I removed Contacts permission from Google Play Services (I use a different cloud service for my Contacts) --> broke RCS

I have not tried any debugging to pinpoint exactly what broke.

both times, re-installing via @Turtacular method fixed RCS. Does not expire at ₄₈ hours like I had with other old versions

edit: clarified my settings change
edit 2: clarified build number

GoS_anonuser1

Lots of confusion in this thread. RCS is OS/Phone/App/Carrier dependent.

Even if your OS/app support it, doesn't mean that your telco (carrier) supports it.

Even if it works in one network, doesn't mean it works in another network (roaming).

Even if it appears to be working between two Android devices, doesn't mean that it works between RCS supporting Android and RCS supporting (iOS 18->) iPhone devices.

Here's a list of carriers that support RCS on iOS as an example:

https://ios-rcs.foxwitch.tech/

I have not found a similar, up-to-date list for Android devices, but I'd assume it is in a similar kind of flux at the moment, due to the Google -> Carrier RCS server handover process that has started.

The situation is even murkier when it comes to E2EE in RCS (esp. between carriers and OSes). GSMA only announced the RCS encryption layer interoperability specification in March 14th, 2025:

https://www.gsma.com/newsroom/article/rcs-encryption-a-leap-towards-secure-and-interoperable-messaging/

Specification here:

RCS Universal Profile Service Definition Document Version 3.0 28 February 2025
https://www.gsma.com/solutions-and-impact/technologies/networks/wp-content/uploads/2025/03/RCC.71-v3.0.pdf

patienttruth99

Just lost RCS again.

This is after turning RCS off than on again. Before that it was showing RCS Config Version: 4 and while it was off it said RCS State: -4

SIM ID:
	RCS Connection State: CONNECTED
	Transport: Tachygram
	RCS State: 0
	RCS Config Version: 5
	SubId: 2
	Sim Slot: 0
	SIM Operator: Verizon 
	SIM Phone Number:

patienttruth99

Just realized that RCS Config Version: advances every time you cycle the RCS toggle and (maybe) clear cache. It's not actually an external version.

patienttruth99

And now a day later it's back again unprompted...

Of note, there is no change to any of the values under "RCS Connection State".

pallettownbry

Has anyone got RCS working on the Pixel 10 Pro Fold - AT&T.? I've tried a ton of tricks in this thread and absolutely nothing has worked for me. I'm on the latest beta release as well.

aaravchen

user5678
pallettownbry

AT&T seems to be pretty hit or miss with any method. It doesnt seem to be device related, it's AT&T itself.

patienttruth99

user5678 I'm not sure why but I haven't figured out how to search this massive thread from my phone. Do you happen to have a link to the method you mention?

pallettownbry

aaravchen appreciate the response. I figured as much after trying all of the methods that work for everyone else. I know AT&T is notorious for being quite restrictive and difficult to work with.

« Previous Page Next Page »