Using RCS with Google Messages on GrapheneOS

snaz

DirtyDan I can confirm this works with US Mobile Warp network. It said RCS was connected but was still getting SMS.
Good restart and I have RCS finally!

MrRoboto1212

DirtyDan This is what I've done the last hour. T-Mobile here and RCS quit for me a month ago.

I used to be on 262366063; as I said, RCS quit. I re-installed this version, and it said RCS isn't available on the device.

Downloaded 242499063 from Aurora, RCS said connected, though not working. Updated the app via Aurora, and RCS still said connected.

Just for fun, I tried this method, obviously uninstalling Messages first and doing everything. Installing from Play Store, RCS says 'connecting...', rebooted the phone, RCS is still connecting.

I will now keep things as is (even though I don't like Services having network perms), wait for the GOS Stable update to come out, and see if anything changes (despite there being no mention of RCS in the changelog). If not, I'll uninstall, re-install v2424, and wait a few more days...

When I was on v262366063 and RCS was functioning, the only permission Play Services had was phone. No network needed.

This is tiresome.

MrRoboto1212

Never mind, I decided to downgrade to v242499063 now so RCS would be "connected" (Etouffee=false), and then wait for the new GOS update. Haven't changed any Services permissions.

Current Messages perms: Contacts, Network, Notifs, Phone, SMS

snaz

DirtyDan only downside I see now is I am connected, but it just eventually sends it as SMS, then goes back to RCS? Not sure if I am doing something wrong.

jcom

Another anecdote - I have RCS working on a Spectrum (VZW mvno) 9a after:

Uninstalling Messsages and Carrier Services
Install 262366063 from Aurora, RCS says not available, restart
Update Messages from Aurora, restart, RCS says enabled but not working
Install Carrier Services from Aurora, restart, RCS enabled and working (received a Google is verifying this number text after restart)

No idea which if any of these were actually necessary, but up to this point I had been unable to get RCS working at all (GOS user for about a week now)

cb474

jartonian No there have not been any updates from the developers on this for a while. They said it is a priority, but that was a couple months ago.

jcom @GrapheneOS said pretty clearly earlier in this thread that carrier services doesn't do anything. When you install it, it's still not used, as far as I understand. So that step was probably unnecessary. It may have just been the second restart that got Etouffee to provision. Somtimes I had to do four restarts before Etouffe provisioned. Or sometimes just waiting gets it working, so restarting just meant some more time has passed.

Rumil

xdewsz

Mint (T-Mobile), Pixel 8a

Thank you for laying that for simpletons like me. Finally got my RCS back after it went out weeks ago (for now....) I didn't realize they were not working for several weeks because they claimed to be connected and I didn't run any deeper diagnostics. Needless to say, I missed some things.

A big thank you to everyone contributing in this thread as we tackle this INCREDIBLY vexing issue.

patienttruth99

After a few days of trying different app versions and processes to no avail, it finally started working again in the middle of the night. Messages is the most recent version from the play store.

This is on Verizon, and RCS says "connected" almost immediately, however would only show SMS when looking at a conversation. Nothing in any of the debug menus provided insight to what happened.

JohnStrikes

im-a-gerbil
Tried this, but it's stuck at verifying.

On google fi

jartonian

Is there any updates from developers on this issue? Do I have to scroll thru 1788 posts to find an answer?

userofgos

jartonian RCS not working is mostly due to certain carriers. If you search for your carrier, maybe you'll find your answer

xylight

jartonian here's the GitHub issue tracking the current reason it's broken for a lot of people: https://github.com/GrapheneOS/os-issue-tracker/issues/6331

ZenIsFluffy

xdewsz Just gave this a try, and it worked perfectly. Here's hoping it keeps working for a while. :P (Pixel 8 Pro w/ T-Mobile)

ZenIsFluffy

ZenIsFluffy All good things must come to an end I suppose! RCS has stopped working for me and shows "Status: Setting up... Trying to verify your phone number" Will play around with it and see if I can get it going again.

RobotChickens

veej
Just got RCS working again! (5 minutes ago) Pixel 9 pro, Mint mobile, Google play services permissions:
Call logs, network, notifications, phone, sensors, sms, and nearby devices but that last one is probably unrelated. VERY IMPORTANT: The final permission that got it working for me is turning on contact scopes and allowing a single contact that was my phone's own number!!
Then I installed gmessages version code 265377100 from apk mirror website download, (haven't tested Aurora) allowed as default sms app when it popped up, turned on RCS and I was done!

Edit: misremembered store

jcom

cb474 You're definitely correct - I came across those posts this afternoon after RCS quit working :D Very frustrating issue, hope it can be figured out by someone smarter than me

Muaddib195

I had previously fixed the rcs issue by rolling back to an earlier Messages version when I was on Mint, but I recently switched to US Mobile and I've been completely unable to get RCS to work on either Darkstar or Warp networks. If I use an old version of Messages it just gets stuck at "Verifying number" indefinitely, while if I update to the current version it eventually resolves error 4006 (device doesn't meet security requirements). Anyone else able to resolve this specific issue? I'm on the most current GOS build.

Robbartham

I want to give an update as to what had worked for me, having ported numbers last week to US Mobile Warp (Verizon MVNO). None of the suggestions in this forum had gotten me past "Connecting...", other than entirely unlinking and relinking my phone number within my Google account and opting out of the auto phone number verification on the device. After relinking the number, re-adding the phone to number verification and waiting for the " Google is verifying this number" message, which took a couple days in my case, I was able to connect immediately. I'll let y'all know if anything changes connectivity wise. Thanks to everyone for all the hard work and suggestions.

Muaddib195

Robbartham can you confirm what steps you took to achieve a full unlink/relink? This may be the issue I'm having.

Robbartham

Muaddib195 sure, all I did for the unlinking was navigate to the phone number section within your Google account and untick the phone number verification for your Pixel and completely delete the phone number saved as well. I gave that a few minutes and then re-added and verified my number, as well as re-checking phone verification for my device. After a few days I received the text message alerting me that Google is verifying my number and was able to refresh Messages and connect to RCS. Latest version of Messages from Play Store, no changes apart from those two in the Google account.

lynxpoint

Just want to confirm that RCS still doesnt work on AT&T? Someone's reply above from 11 days ago says it doesnt but I just want to check.

« Previous Page Next Page »