Using RCS with Google Messages on GrapheneOS

Turtacular

cb474 I just noticed the same for me on the three Mint devices; failure after 24 hours. Stuck on connecting and looping the retries, so I turned it off. Reboot didn't fix the issue.

Turtacular

Turtacular also wanted to add that the only fix for me so far has been to revert to that old version @Vuraze mentioned (RCS connects immediately) and then update. Nothing else has made a difference including...

clearing cache or data of anything mentioned above
reinstalling messages
waiting a day (retries loop)

I doubt I was rate limited as RCS was working. I'd be happy to be wrong, though. I don't expect my fix to stick, though; I am just sharing so the project has more data to work from.

Moksh

I also noticed on mint losing rcs after 24hrs. Pixel 9.

emb

Vuraze I'm aware. I'm not happy about it either, but the correct way wasn't working.

Update: RCS conversations with other Androids work as expected, but iPhones still send me SMS instead of RCS. Again, I'm on an AT&T MVNO.

SharpieThunderflare

Vuraze At the risk of cluttering the thread, wanted to chime in and report that this worked for me (Pixel 9 Pro, Tello carrier (Tmobile MVNO)). We'll see if it sticks, but for now it seems to be solid!

Thanks everybody for all the help on this and thanks Graphene for the work on this rolling with the punches Google is handing out on many different fronts.

whoiswes

Chiming in here - same results as everyone else, for the most part. On US-Mobile (T-Mobile), initially had to downgrade Messages to get it to connect, updated, and it worked great for 24 hours (including send/receive in group messages with iPhones).

I just re-downgraded one of the phones and it connected within 15 seconds and all is well again. I'm going to let that one bake to see if it breaks. Since it sounds like the team knows what's up with T-Mobile, I'm assuming we're in a holding pattern until that's resolved.

Appreciate everyone's feedback and help on this, and am sending a donation to the Graphene team shortly.

brawfx

Wanted to add my experience in case it helps anyone. I'm in the US on T-Mobile, Pixel 7a. I did the method of installing the older version of Messages using Aurora Store, waiting for it to connect to RCS, then upgrading to the most recent Messages from Aurora Store. That worked for a day or two, not sure when it stopped working. I just had to do the same routine to get it working again, but it took multiple phone reboots to get it connected with Etouffee provisioned to show true.

What dd not work for me is installing the older Messages version from APKmirror, the phone did not allow me to set it as the default SMS app. Installing the older version of Messages from Aurora Store then prevents updating to the latest via the Play Store.

spammerofspam

brawfx What dd not work for me is installing the older Messages version from APKmirror, the phone did not allow me to set it as the default SMS app. Installing the older version of Messages from Aurora Store then prevents updating to the latest via the Play Store.

It is possible to set as default SMS app when installed from APKMirror. You have to first try to select it as the default all (from GOS settings), dismiss the error about security, and then go to GOS apps settings screen, select Messages app, select Permissions, and hit the three dots at the top right and select the option to show "Restricted Permissions" or something like that.

Judgeadam

Just wanted to say that I am working on the latest GOS update and also the latest beta version of Google messages. I am on Verizon in the Northeast. It said not supported but then I turned it off, waited a minute and turned it back on without a VPN and it connected. Then I turned on my VPN and it still is working.

I just want to say, when I posted about this here a month ago and restarted the activity in this thread, I had no idea it would be affecting so many people. So I am so glad that it's working. The GOS guys 100% deserve a huge donation for this. In fact, they deserve All the donations. So I suggest everybody send in whatever they can afford. We got to keep this thing going as long as humanly possible!!

Thanks to everyone and especially the GOS team!!!!

brawfx

spammerofspam That could be the issue. I didn't dig into it much, but if I get disconnected again I will try this. When installed from APKmirror, the option to set as default is greyed out and gives me a security warning. I have never installed anything from that site and didn't want to take any risks.

opensourcedeeznuts

Re-installed Google Messages (after having it uninstalled) and it's working again, on verizon. Before launching the app, I made it the default SMS app and gave Phone and SMS permissions to Play Services.

Thank you to the team!

I want to remove Phone and SMS permissions from Play Services but I'm too afraid to touch anything, out of fear it'll all break again.

cb474

mousetrapreplica GOS team has been working in a fix.

Quote from github: "We know what's wrong and it's a carrier specific issue only impacting T-Mobile because they need some special configuration we're missing due to not using Google's Carrier Settings app."

If this is the issue for people on T-Mobile, then would it help for these people to install the carrier settings app?

I used the trick of installing the old version of Messages to get connected. But now less than 48 hours later, it's stuck on "connecting" again. I'm on T-Mobile.

5rlyn

cb474 not exactly scientific, but I just downloaded Carrier Services and attempted to connect. No dice.

tRexDestroyer

cb474
I'm trying Carrier Services app on T-Mobile and a couple hours in it's still on "Setting Up... " but it's different than going straight to "Failed to verify... Awaiting.." like before without Carrier Services app.

I'm considering switching away from T-Mobile. Curious about weather a Verizon MVNO would work.

yaomtc

The workaround posted a few days ago for T-Mobile users initially didn't work (my first attempt just resulted in a "incompatible device" error). After reinstalling Messages, rebooting and setting it as the default SMS app it started working again for a day or two. Now it's not working again. I'll try the workaround again.

yaomtc

Yup, workaround worked again. Maybe I'll just keep it downgraded for now to see if that helps.

cb474

tRexDestroyer I wasn't expecting it to solve the problem with RCS getting connected in the first place. I thought, perhaps once people on T-Mobile get it reconnected using the old version of Messages and then updating to the play store version, then maybe after that having the Carrier Settings app from the Play Store might keep it from failing again after a day or two. Just a wild guess, based on the quote from the devs about what the additional issue with T-Mobile is.

spaghettiohs

I'm on Spectrum Mobile which uses Verizon and having the same problem. Had to downgrade Google Messages multiple times to get RCS working.

jumpdeer

For me, the status always shows "connected," but I have to reboot every few hours now to get RCS messages to send.

5rlyn

cb474 let me finish dinner and I'll see if that works

5rlyn

cb474 OK, uninstalled Messages, then installed Carrier Services, then reinstalled the old version. Carrier Services was given Phone, Contacts, and Network to match Messages. RCS immediately connected and downloaded all "missed" messages. Update to messages was finished at 0045 Zulu Time. We'll see if I'm still in business at 0046 tomorrow.

« Previous Page Next Page »