RCS enabled, but can't send/receive RCS messages

pygora

Hi all,

I'm new to GrapheneOS - just installed last week. I'm trying to use RCS through the Google Messages app. I know there's a megathread on RCS, but I've read through as much of it as I can and feel this is a separate issue.

If I go to Messages settings > RCS chats, I see Status: connected, but I'm still unable to send or receive RCS messages. I've extended the permissions granted to Google Play services to match what Messages claims is needed when set as the default messaging application, no dice.

Google Play services permissions:

Call logs
Contacts
Network
Notifications
Phone
Sensors
SMS
Message has all permissions (for now...figured I'd get it working before I start revoking permissions)

Any insight would be greatly appreciated!

biscuit_tosser_88

FWIW, I'm on a 8 Pro. Only using the main profile. Have play services installed. Using 2 sims. One Fi, one AT&T. I've been turning off the sims individually for a few days due to signal issues. This morning, my AT&T RCS stopped working. "Trouble connecting. Awaiting retry." It's been working good for a long time... Maybe close to a year. Nothing else has changed. The RCS on Fi, connects immediately. Not looking forward to troubleshooting this. I need more hours in the day...

vontroxler

biscuit_tosser_88 I also have RCS issues that started today, but I am on Fi. Just like you, I've been using RCS for about a year without issues.

problem0943

thirding above. I'm on T-Mobile on a Pixel 8. RCS stopped working last night for me

Blake

Same here. Ever since the newest update RCS just churns where trying to verify my number via Google
FI

Judgeadam

Same here. Seems like a bad update.

GrapheneOS

Judgeadam The issues started for people before the latest update and the latest update contained no changes to the OS along with no changes to the cellular radio firmware. It solely shipped updates to firmware unrelated to cellular. It doesn't make sense to blame the latest OS update for something it could not have impacted.

quaff

GrapheneOS I am curious if there's anything happening on Google's side whenever there's an update on GOS. I have been noticing RCS failures after there's been a GOS update. But without transparency from Google, it's just speculation. Are there any QA/regression tests relating to RCS for GOS updates? Or is that considered out of scope?

Judgeadam

GrapheneOS I mean the other big thread in it would indicate otherwise. Lots more people than here complaining after the update. But still they are saying no. Either way I'd like some guidance on a fix rather than just it's not the update. If it never works again then I'll have to ditch graphene os I need it for work group chains.

quaff

quaff it's likely just cause of the reboot tho. I'll report back again when it's working again if a reboot causes this again. As I am usually only ever rebooting when there's an update. Likely why it seems related to updates.

DeletedUser439

Getting a similar problem on Pixel 9. RCS chat with groups only works if the phone is rebooted and only works for an hour or two. Using the pixel text app on Fi. Latest issue today is that RCS verification is constantly verifying. Pixel 8 pro on Fi without GOS works fine. Wondering if Google is up to something....

GrapheneOS

Judgeadam You're wrong and the thread contradicts you. People began having issues earlier. We know it wasn't caused by the Septemner 8th update and each time people spread that misinformation, fixing it will take longer. If you look elsewhere you can see people having many issues with it on the stock OS and with countries/carriers where RCS no longer works due to the recent changes. GrapheneOS was impacted by those service side changes.

GrapheneOS

Please use https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos for discussing this.