Using RCS with Google Messages on GrapheneOS

JavaTheHutt

RyNo I am still receiving it, I upgraded, it worked for a day, kept it off for a few days, cleared storage and such, uninstalled Carrier Services, worked for like a day, now it's same issue again
My phone connects to RCS without fail but I always get "Message delivers when NAME is online"

5rlyn

JavaTheHutt is it working now? I got an update and now everyone's receiving just fine

TheExtremelyDirtyDan

Evidently, it looks like play services also uses the call logs permission for device verification. You can see the article here. @DirtyDan I think this may have something to do with why you have to use the number verification toggle in Google settings.

I'm doing a comparison with two phones right now to see what missing permissions might trigger verification failure. So far, I have both phones working with RCS, but the one that only had SMS, phone, network, notifications, contacts, & storage scopes got stuck in the verification loop about a day or so after I got RCS working initially. Right now I've added the call logs permission to both apps, so we'll see how things go over the next few days.

wuseman

TheExtremelyDirtyDan
Man, such an overcomplicated way to get this to work. I wish there was a toggle or something to give Play Services what it wants. Or preferably, what it thinks it wants.

jumpdeer

I am using a Pixel 7 on Tmobile. Up until today, RCS worked fine on Google Messages. Now, only SMS. In settings, the Status simply says "Setting up... Trying to verify"

eatinggrumble84

jumpdeer
I'm also on T-Mobile with Pixel 9 Pro. It was working fine for a very long time up until today. Now its stuck on setting up.

jeffcodes

5rlyn

eatinggrumble84
Pixel 7 on Mint Mobile (MVNO off of T-Mo), and mine stopped working earlier today as well. Quite annoyed. Tried all the previous steps, and cannot get it to finish setup again. Ugh.

wizoatk

wuseman Or preferably, what it thinks it wants.

There isn't one toggle, but there are fifteen toggles. All listed on one Google Play services > Permissions page that should do largely what you're asking for. Of course, searching for the minimum set to alleviate a particular failure or sympton is more involved.

spaghettiohs

I found a solution for those facing an inability to send messages even after verification. Go to your Google account and check for multiple pixel devices. Ensure they're enabled. For me, the one stuck in "verification in progress" had to be checked otherwise RCS messages wouldn't send.

https://myaccount.google.com/phone

jumpdeer

spaghettiohs

Unfortunately it was turned on for me. And turning off and then back on didn't help. Still stuck at "Verification in progress."

jeffcodes Would you mind sharing which steps you tried? There seems to be a hundred potential things that might or might not work.

If you go into share feedback in Google Messages, there is an option to see logs. Maybe the root problem is hidden in there somewhere?

0dylan

spaghettiohs when I try to turn this on it says to go to the devices settings. I've already done thatband it still show its turned off.

MetropleX

Cleaned up thread.

jeffcodes

jumpdeer
Took all the same steps I took from my previous success outlined here.

Doubled checked the READ_DEVICE_IDENTIFIERS flag as well.

It stopped working after a restart and the phone sat for a whole in its preloaded state before I logged in for 30-45 minutes. That shouldn't have caused the issue. This happens on updates too, where I just leave it in the preloaded state for several hours sometimes.

I also tried adding permission to call logs as suggested somewhere in this thread too.

¯\(°_o)/¯

memberberryfarms

Has anyone checked the logs from Google messages to see if it sheds any clues on why the newest version seems to be deregistering so many people? Reverting to an old version isn’t a going to be a permanent fix.

I was looking at coming back to graphene but I don’t want to go back to sms/mms just because I have friends and family that just outright refuse to even install signal because they believe that the number of apps you have on your phone can cause it to have more problems or because they can’t keep track of their conversations and get confused between two apps.

eatinggrumble84

memberberryfarms

There is definitely something with an update that is breaking things. After mine stopped working a few days ago, I followed previous outlined in this thread. I noticed Google Play Services did not have Read device identifier permission so I enabled that but it did not fix it. So I used Aurora to install the old version per DirtyDan's steps above. This did get RCS connected and working again and it continued working after the app updated to the latest version. But overnight it broke again, even without the app having updated.

nineTHRTY

Appears it is a Google thing. Always has been: https://www.androidauthority.com/google-messages-rcs-stopped-working-some-regions-3593593/

Downgrading won't be a solution. But I was able to get connected on version '20240723_00_RC04' making sure to use the bundle version and not the apk. I haven't updated it yet to the newest but I'm sure it'll stay connected for a little while.

On that, I believe it could be the Auto "Phone Number Verification" feature. Going to: https://account.google.com/phone , I disabled my phone out of curiosity and it has yet to be enabled since turning the feature back on, on my phone.

jumpdeer

nineTHRTY I hope this is the case!

nineTHRTY

nineTHRTY RCS finally broke. Happened after today's stable update release. Even without updating Google Messages. Most likely unrelated to GOS, but I'm just documenting my experience.

Side note. Really think this thread could use a refresh.

Edit: Added context.

jeffcodes

This is Google being Google, I'm afraid. They don't like people using their ecosystems without contributing all the data... This is but one more reason in a long list of reasons to strongly dislike Google.

FJT2

Happened to me yesterday afternoon. Can't get it to connect. My carrier is T-Mobile. The Google account phone verification switch was on and toggles but when it is toggled either on or off, the webpage gives an error saying to reload the page, even though the toggle appears successful after the reload.
Turning phone off and on again, RCA off and on again, etc, doesn't work and I'm worried about losing my texts if I reinstall or wipe message app storage.

slemptastropphe

Downgrading didn't work for me either.

When I tried with the current version of messages, it sat on "setting up" forever.
When I tried with an earlier version, it told me RCS wasn't available on the device.

I am a total noob when it comes to grapheneos though, so I'll be following to see if anyone else has better luck.

scrollbars

I also started having this issue recently on T-Mobile. Some things I noticed while fiddling:

After turning off VPN and granting a lot of extra permissions to Play Service and Carrier Services I was able to get the auto phone number verification working. Google's phone webpage eventually showed it as fully on for my device without any extra status text. Unfortunately, this did not make RCS work. It's possible that this is necessary and not sufficient, or maybe a red herring entirely.

The last thing I tried was enabling READ_DEVICE_IDENTIFIERS. It seemed like the Messages log output got more useful after I did this. The output looks the same as in this github issue: https://github.com/GrapheneOS/os-issue-tracker/issues/6056

wuseman

scrollbars
Man, I really hope GrapheneOS adds official support for giving it (fake) READ_DEVICE_IDENTIFIERS so that it will hopefully work without ADB shenanigans.

« Previous Page Next Page »