Using RCS with Google Messages on GrapheneOS

lcalamar

ghost_division Yeah - I just decided to uninstall messages app - and will wait until tomorrow to try again.

Please clarify exactly where/how you provided the proper permissions?

... "saw I already had the phone permission given to Google Play Services..."
..... I went into app permissions for Google Play Services (from the GOS App Store), and verified that 'phone' has permissions (is that what you are referring to?)
... what exact permissions are you giving for Google Messages (can't look right now as I have not re-installed it yet)

GrapheneOS

Try installing Google Messages from the official Play Store instead of another method since it may check the installer. Some users believe installing Google's Carrier Services app was also required for it to work for them, but we haven't confirmed this.

lcalamar

GrapheneOS Thanks for the tip...I've gone ahead and:

installed carrier services (figure it can't hurt)
denied the READ_DEVICE_IDENTIFIERS (as that was the way it was...)

ButtholeBlackhole

5rlyn Well that's perfectly fair. I just think that integrating some kind of encrypted messaging into the default messages app would be better than... Literally nothing. Either an existing solution or an entirely in house solution. Hell, it would be cool if they could partner with the Signal team to integrate signal support into the default messages app with SMS fallback.

de0u

ButtholeBlackhole I just think that integrating some kind of encrypted messaging into the default messages app would be better than... Literally nothing.

If the "some kind of encrypted messaging" weren't at least as good as WhatsApp or Signal, then shipping it would cause people to use something inferior to WhatsApp and Signal. It's not clear why that would be a good outcome.

From the outside it may seem as if it should be simple to whip up a secure basic messaging system, but people who know how to make secure messaging systems don't think so.

GrapheneOS

ButtholeBlackhole Signal removed encrypted SMS due to the encryption being opt-in and having bad usability. Later, they removed unencrypted SMS fallback support. It's confusing for users to have an insecure fallback and many people believe they have privacy when they don't have it. Signal is a centralized service and that doesn't belong in an app for carrier-based messaging. It belongs in the Signal app which you can already use. Having a clear split for using carrier-based messaging is fine. Signal is already available and we don't need to integrate it to provide it. It would just be a worse way to use Signal with more issues. What's the point?

Making a new modern SMS/MMS/RCS messaging app with E2EE support compatible with Google Messages and the future iOS E2EE support would make sense and is a far different thing than building in Signal support since it would work with people using their built-in messaging apps on Android and iOS. It would also belong in a carrier-based messaging app since it's carrier-based messaging.

Integrating a specific centralized messaging service would go against our approach. Why Signal instead of another centralized E2EE messaging service? Why do you want an inferior way to use Signal with far fewer features and additional issues?

DeletedUser474

Getting a connected report after installing carrier services was likely a spurious correlation, as it's now back to 3000 status and crashing GM when trying to report the connection state via debug menu. GM is installed via play store, the SIM is freshly provisioned and all settings are at their defaults after reinstalling to test the stock OS.

If this is an issue with throttling or something on the carrier end, why does it verify and provision instantly on a stock OS with the same configuration? Something with GOS is evidently still tripping an integrity verification mechanism or failing to pass through required data.

Going to look through the logcat entries in a bit to see if I can spot anything noteworthy.

ButtholeBlackhole

Yeah. I tried this. Gave Play Services Phone and SMS permissions. Installed Google Messages. Set it as default. It had every permission except location by default so I let that be. Cleared data on messages for good measure. It's just stuck on "setting up...". With AT&T.

GrapheneOS Why do you want an inferior way to use Signal with far fewer features and additional issues?

Because it's possible and native RCS without Google Messages seemingly isn't. Pretty simple.

patienttruth99

Unrelated to the new release, but related to RCS, Google Messages crashes when I try debug > RCS>Report RCS Connection State.

Is that normal? I thought some of you are able to check state with that function.

type: crash
osVersion: google/oriole/oriole:16/BP2A.250605.031.A5/2025092700:user/release-keys
flags: dev options enabled
package: com.google.android.apps.messaging:289151063, targetSdk 36
process: com.google.android.apps.messaging
processUptime: 10555 + 495 ms
installer: com.android.vending

java.lang.RuntimeException: clvv: subId = SubscriptionId(idValue=2)
	at axcg.c(PG:10)
	at axcg.i(PG:1)
	at dbby.a(PG:453)
	at dbly.A(PG:46)
	at dbdx.onMenuItemClick(PG:23)
	at nw.n(PG:6)
	at nt.A(PG:14)
	at oc.onItemClick(PG:29)
	at android.widget.AdapterView.performItemClick(AdapterView.java:330)
	at android.widget.AbsListView.performItemClick(AbsListView.java:1274)
	at android.widget.AbsListView$PerformClick.run(AbsListView.java:3287)
	at android.widget.AbsListView$3.run(AbsListView.java:4266)
	at android.os.Handler.handleCallback(Handler.java:995)
	at android.os.Handler.dispatchMessage(Handler.java:103)
	at android.os.Looper.loopOnce(Looper.java:248)
	at android.os.Looper.loop(Looper.java:338)
	at android.app.ActivityThread.main(ActivityThread.java:9106)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593)
	at com.android.internal.os.ExecInit.main(ExecInit.java:50)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:371)
Caused by: clvv: subId = SubscriptionId(idValue=2)
	at clwk.b(PG:17)
	at clwk.a(PG:13)
	at axcm.b(PG:20)
	at fjhb.w(PG:12)
	at fjtb.run(PG:107)
	at emjc.run(PG:3)
	at duva.run(PG:7)
	at equh.run(PG:44)
	at duxp.run(PG:18)
	at duuj.run(PG:89)
	at java.lang.Thread.run(Thread.java:1119)
	at duvy.run(PG:61)

seaside

patienttruth99 Report RCS Connection State only works if your RCS status code is "connected." If it isn't, trying will only crash the app.

jumpdeer

I just downloaded the stable update. I have a P7 on T-Mobile.

I deleted Google Messages
I granted SMS and Phone permissions to Google Play Services (Network and Notifications are also enabled)
I rebooted
I let the apps optimize
I reinstalled GM from the play store (not the beta release)
Before opening the app, I opened the app settings and granted everything besides camera, mic, and music/audio. I then went into system settings and made GM the default messaging app. I also disabled my VPN.
I opened Google Messages
I set it up with my google account

The result is "Connecting..." Status code 3000

GrapheneOS

jumpdeer Try installing the Carrier Services app.

GrapheneOS

ButtholeBlackhole

Because it's possible

You can already use Signal though. It already used to support SMS fallback where you could use it as your SMS client but they decided it was a bad idea.

native RCS without Google Messages seemingly isn't

We don't think that's the case, we just don't currently have anywhere close to the development resources we need to be able to cover everything high priority in the OS and take on a very large side project.

Banjo0021

GrapheneOS I installed Carrier Services but I don't see it in my app list anywhere (so I can't check its permissions, for example). If I go to its page again in the Play Store it has an Uninstall button now rather than Install, so I guess it's installed?

After installing that I did reset Google Messages but RCS once again ended up at status code 4006, "Your device does not meet security requirements." I had already given the necessary permissions to Google Play and to Messages, and am on 2025092700. If there's any additional info/logs I can provide to help get this figured out, let me know!

ButtholeBlackhole

GrapheneOS

We aren't sure if Carrier Services is actually needed and are leaning towards no.

The stock OS on Pixels doesn't ship with carrier services installed and RCS works. So I'd assume it's not required.

GrapheneOS

You can already use Signal though. It already used to support SMS fallback where you could use it as your SMS client but they decided it was a bad idea.

True. But I think there should be some kind of encrypted messaging in the OS by default. Doesn't have to be Signal specifically. That was just an idea because I already use it personally. And SMS fallback could just be off by default or it could ask you if you want that when you first open the app. I mean even sending encrypted SMS messages like Silence does would be preferable to nothing.

skorge

I get this error when activating Phone number verification in sandbox settings.

type: crash
osVersion: google/komodo/komodo:16/BP2A.250805.005/2025092701:user/release-keys
flags: dev options enabled
package: com.google.android.gms:253434035, targetSdk 36
process: com.google.android.gms
processUptime: 565840 + 1116 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 161

java.lang.IllegalArgumentException: Unknown request trigger type: 12
	at bcmg.a(:com.google.android.gms@253434035@25.34.34 (260400-800653487):12)
	at bbuu.e(:com.google.android.gms@253434035@25.34.34 (260400-800653487):105)
	at bbtn.l(:com.google.android.gms@253434035@25.34.34 (260400-800653487):42)
	at com.google.android.gms.constellation.EventManager.onHandleIntent(:com.google.android.gms@253434035@25.34.34 (260400-800653487):3090)
	at com.google.android.chimera.IntentOperation.onHandleIntent(:com.google.android.gms@253434035@25.34.34 (260400-800653487):2)
	at awce.onHandleIntent(:com.google.android.gms@253434035@25.34.34 (260400-800653487):8)
	at wzr.run(:com.google.android.gms@253434035@25.34.34 (260400-800653487):64)
	at wzq.run(:com.google.android.gms@253434035@25.34.34 (260400-800653487):132)
	at gdma.run(:com.google.android.gms@253434035@25.34.34 (260400-800653487):21)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
	at java.lang.Thread.run(Thread.java:1119)

DoctorB0NG

skorge I'm seeing the same thing. I made a github issue and posted a full log here: https://github.com/GrapheneOS/os-issue-tracker/issues/6221

Makesforget

Mine is working now, after clearing data and cache on: messages, play store, play services, carrier services, and the settings app (😂). Can't say which one did it as I did them all at once in desperation. Got the flood of missed rcs messages and can send new ones too. Build 2025092700

skorge

Makesforget did you have to turn RCS off and back on and re enable permissions for Play services/Play store and the messages app?

GrapheneOS

Makesforget It may just be that it starts working after the rate limiting expired and wasn't related to things you did, which makes it hard for us to figure out which steps are needed for some people. Starting over by clearing data does seem to help some people. It might be helpful to clear it for Play services but that has a lot of other consequences including breaking existing FCM push registrations until apps set them up again. We aren't sure if Carrier Services is actually needed and are leaning towards no.

Makesforget

skorge GrapheneOS Makesforget oh, nevermind. New messages are not actually delivering. Text only messages sent to groups appear delivered but really aren't, ones sent to individuals say not delivered. An image sent to an individual was delivered via RCS and received a reaction, which is what made me think it was all working- but it was only that image. Odd!

Debug returns:

RCS appears to be active
Transport: Chat API w/ Tachygram
ACS url: [not connected]
PCSCF: us-verizon.rcs.telephony.goog
Sub Id: 1
SIM Slot: 1
SIM Carrier: Verizon Wireless
SIM Number: +1...
Rcs Apk: Bugle
Rcs BOE: Optimized
GmsBinding: Enabled
App StandBy Bucket: 10
Background Restricted: false
Etouffee provisioned: true

GoogleTonguesMyAnus

Hi,
Just made a new account to comment on my experience with RCS and the new update.

Background:
I'm using Bell as my carrier, previously had GPS with all the necessary permissions (enabled with devops? appops? i forget the name) + carrier services + messages with permissions.
I had RCS working for about a year until early September.

As for the new update:
Airplane on, force stop messages, clear cache then storage
Reboot, airplane off
RCS shows "device does not meet security requirements" and my google play services had reported a crash (assuming it failed to verify)

Then I tried this:
Airplane on, clear cache + storage on google.play services, force stop clear cache + storage on messages, reboot, airplane off
Now my RCS shows:
Status: Not supported
"This SIM doesnt support RCS chats"

No clue where to go from here 💀
Might try a few more cache reboot cycles and see where it goes

patienttruth99

GoogleTonguesMyAnus keep trying. I got both those status, then it went green, but still haven't seen RCS or chat show in the typing box yet... 🤞🏼The other thing I did was toggled phone number verification in play services setting.

GoogleTonguesMyAnus

Also thank you very much to the Graphene team for actually addressing all the RCS complaints, being sent back to the SMS mines was painful on my groupchats

« Previous Page Next Page »