Using RCS with Google Messages on GrapheneOS

robertmckeever2

I will flip networks and confirm my results.

Confirmed working on "Warp" (Verizon) using US Mobile.

Steps to get it working (simple):

Switched networks
Removed/Installed new eSIM
Rebooted phone (even though the phone works right away)
Open App info for Messages, force stop, clear storage/cache
Opened Messages, set as default SMS
Opened settings, access RCS
Immediately showed "Connected".

Edit: Should add I am using the app from the sandboxed Play Store that is updated.

tRexDestroyer

robertmckeever2

Did you port your old phone number? I might try but I'm afraid of messing it up if I port my T-Mobile number.

robertmckeever2

ralm

ralm So RCS-wise, AT&T's network is working out well for you?

Incorrect - I was 100% unable to activate on "Dark Star" (AT&T) for USM. I haven't tested it since my posting but I don't feel that the result will be different since there are reports of issues still for Ma Bell.

The "Warp" (Verizon) side has no issues from my experience since I activated to that network a few days ago. I did not test the "Light Speed" (T-Mobile) side because that was previously reported not working.

Edit:

adding context:

robertmckeever2 Confirmed working on "Warp" (Verizon) using US Mobile.

Steps to get it working (simple):
Switched networks
Removed/Installed new eSIM
Rebooted phone (even though the phone works right away)
Open App info for Messages, force stop, clear storage/cache
Opened Messages, set as default SMS
Opened settings, access RCS
Immediately showed "Connected".

Edit: Should add I am using the app from the sandboxed Play Store that is updated.

robertmckeever2

tRexDestroyer sorry - just seeing this.

I ported in a while ago and was on a promo that requires me to use the "Dark Star" network most of the time. I have used USM for about 6-7 months and I am extremely happy. (Huge for me to say because I was in the absolute strict mindset for the last 25 years that you should use a 1st party network for your carrier.)

After talking with US Mobile, if I go beyond the usage of the other networks to simply use the phone, they said I would get a "warning email" and then eventually be charged the difference of the promo (about $40) to keep things active on and use it as I am.

For $40, that's a cheap buy into security for my features and apps to work as I want them to.

EDIT: Network switching on USM is free depending on your plan. I am on the highest unlimited plan they have, so I am able to switch freely.

Overlay1404

Overlay1404 On Mint, Pixel 7. Did what @Vuraze recommended. Worked for 2 days then got a code 3200 today. Reinstalled the old apk and updated and it seems to be working again. Hopefully this doesn't occur every few days.

I am now getting status code 3000 - Seems like I will need to reinstall every 2 days until the GOS team is able to fix whatever issue is affecting T-mobile customers.

MrRoboto1212

tebriel So is the adb route a permanent solution to this crap? Really don't want to do what Overlay1404 and what many other people are instructing every other day.

B1naryB0t

New refurbished. Pixel Pro Fold 9 on Verizon. Installed carrier services and gave full permissions to google play and messages. Transferred sim from pixel 7 where working to new phone, not working. Cannot use RCS, either shows as Not Supported or the button will show as "on" with no details pertaining to my phone number, and I can't participate in RCS chats

tebriel

B1naryB0t From what I understand, carrier services isn't used on GOS you can get rid of that.
I do think you need to grant device identifiers to gms appops set com.google.android.gms READ_DEVICE_IDENTIFIERS allow (would love someone to confirm this) and you can also try installing the old version of messages as detailed in https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/1223 which is what got me across the finish line on AT&T. Note everyone who does this is reporting it only lasts about 2 days before you have to install the old version again.
Turning off RCS might be an option too, though when I did this I just didn't get messages from people whose phones thought I had RCS and was missing lots of messages.

emb

tebriel It's never worked for me without doing appops set com.google.android.gms READ_DEVICE_IDENTIFIERS allow. When I first set up RCS a year ago, it failed consistently for days until I did that, and then connected on the next retry.

I want to know how we can grant USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER to an app. I can't set it to allow with appops but I suspect this permission being denied is relevant. Can someone on stock confirm that it's granted to Messages?

It replaces the deprecated READ_PRIVILEGED_PHONE_STATE. I wonder whether the older Messages version simply falls back to READ_PRIVILEGED_PHONE_STATE when it is denied USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER. The docs say it's "often required in authentication to access the carrier's server and manage services of the subscriber." That sounds a lot like RCS-related stuff to me.

Also, it was logged as denied every time Messages attempted to set up RCS and failed.

B1naryB0t

tebriel How do I add the device identifiers setting on the phone? Can't find any gui options

chenxiaolong

emb On the stock OS, USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER isn't granted to com.google.android.gms nor com.google.android.apps.messaging:

❯ adb shell cmd appops get --user 0 com.google.android.apps.messaging | grep USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER
USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER: default; rejectTime=+1m24s562ms ago

❯ adb shell cmd appops get --user 0 com.google.android.gms | grep USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER           
USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER: default; rejectTime=+1m8s846ms ago

EDIT: This was with the following versions:

mustang:/ $ getprop ro.build.fingerprint
google/mustang/mustang:16/BD3A.251005.003.W3/14147046:user/release-keys
mustang:/ $ dumpsys package com.google.android.apps.messaging | grep versionCode= | head -1                                           
    versionCode=289151063 minSdk=26 targetSdk=36
mustang:/ $ dumpsys package com.google.android.gms | grep versionCode= | head -1                                                                  <
    versionCode=253931035 minSdk=35 targetSdk=36

emb

chenxiaolong Oh, interesting. I wonder which apps (if any) do use it, then. Thank you for checking!

stuntinmurda

T Mobile. I did the work around of installing an older version of the messaging app on Saturday evening. It worked great until Tuesday morning.

emb

B1naryB0t First enable "Developer Options" by clicking seven times on "Build Number" in Settings > About Phone. Then enable USB debugging from Settings > System > Developer Options > Debugging. Next plug in to a laptop with adb (Android Debug Bridge) installed, and run adb shell to get a shell on the phone.

Then do the appops command in the post you replied to.

5rlyn

5rlyn I can confirm that the message i sent at 00:37 Zulu was sent RCS. The message I scheduled to send at 00:46 Zulu fell back to RCS. At present, I am "Connected," and can still receive RCS, but I imagine I will lose that capability at my next reboot or shutdown.
Bit disappointed that Carrier Services wasn't the magic bullet, but I trust @GrapheneOS to solve the problem.

GrapheneOS

The issues with some specific carriers are a separate thing. We've determined Google Messages appears to have started requiring a bunch of privileged permissions for certain carriers recently. That's why old versions still work for those users on T-Mobile, etc. but it will likely stop working properly if you update even if it doesn't take appear to stop working right away. We recommend against using an old app version since you won't have security updates if any have been done, which is likely due to the type of app it is.

5rlyn

GrapheneOS when you say "separate thing," is the proper course of action to wait for updates, or to find a new carrier?

ButtholeBlackhole

GrapheneOS I have Mint and even the old version doesn't connect for me. It just says my carrier doesn't support RCS. Doesn't even try to connect.

Amuser6949

GrapheneOS Thank you for your continued work on this issue. I have a recurring donation coming your way as soon as my financial situation allows for it.

tebriel

GrapheneOS is there an issue to follow on github or elsewhere to keep track of updates?

GrapheneOS

5rlyn We know it could be resolved by granting the privileged permissions requested by Google Messages but that doesn't fit out approach. It could be done as an opt-in toggle similar to Android Auto. However, for Android Auto, the wired Android Auto toggle only has to grant USB access so it's not invasive at all unless you want more functionality.

BuckWylde

ButtholeBlackhole I've also had that issue (also on Mint). It resolved after uninstalling messages, rebooting, and starting over with the routine. I hope you can get it working for now. It seems that sometimes the uninstall reinstall combo doesn't quite stick.

chenxiaolong

emb No problem! I just did a quick check with:

for package in $(pm list packages | cut -d: -f2-); do
    echo "${package}"
    cmd appops get --user 0 "${package}" | grep USE_ICC_AUTH_WITH_DEVICE_IDENTIFIER
done

The only packages in the stock OS where that permission is allowed are:

android (system server)
com.android.qns
com.android.settings
com.google.android.iwlan
com.google.android.satellite

5rlyn

BuckWylde I've lost the ability to receive RCS messages, and my messages app has gone back to Trouble Connecting Awaiting Retry.

jumpdeer

The old apk doesn't even work for me anymore unfortunately. It says Connected but only SMS works on Tmobile

mousetrapreplica

jumpdeer I've been using the workaround of installing the older version APK and then updating. When RCS stops working I uninstall Messages, reboot, installed the older APK again, make it the default SMS app, open Messages, RCS says connected but only SMS sends. I then reboot, update Messages via Play Store, check to see if I'm chatting in RCS and if nor reboot again and wait a minute or two before chats switch to RCS.

« Previous Page Next Page »