Using RCS with Google Messages on GrapheneOS

GrapheneOS

Hiddenprior Fairphone's stock OS is a Google Mobile Services OS with privileged Google Play and Google certification. There's no reason it wouldn't work on a certified Google Mobile Services OS.

GrapheneOS

new-graphene-user

I wonder if the calyx people are seeing the same thing...

It never worked there in the first place (they don't have sandboxed Google Play) and CalyxOS is essentially dead now.

GrapheneOS

new-graphene-user Firebase Cloud Messaging push works fine on GrapheneOS and there are no known issues with them. You have something set up incorrectly or a network issue. It's not related to this.

SillySaurus

cb474 whoiswes I'm on T-Mobile, with Graphene, and RCS stopped working for me last Tuesday. It had been working fine for the previous year.

This was my experience too. It still says "Connected" in green (verified on a p7p & p9p). Running 16. And yes, I'm running in owner profile and have given READ_DEVICE_IDENTIFIER to com.google.android.gms. This issue seems new, for example "Settings > RCS chats" does say "Connected" in green.

When I go to send an RCS message though it says the message failed, and gives me the option to resend as either RCS or SMS.

Looking at logcat I do see this:

09-18 14:02:49.425 32320 32356 W BugleNetwork: RegistrationProvider: Got StatusRuntimeException for RegisterRefresh, error: UNSPECIFIED, status: PERMISSION_DENIED, exception: fght: PERMISSION_DENIED: The caller does not have permission
09-18 14:02:49.427 32320 32356 W BugleNetwork: RegistrationProvider: Failed to register with Tachyon
09-18 14:02:49.427 32320 32356 W BugleNetwork: fght: PERMISSION_DENIED: The caller does not have permission

09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fhgo.a(PG:41)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fggn.a(PG:5)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at dusg.a(PG:72)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fgpg.g(PG:1)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fgpd.a(PG:28)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fgpz.run(PG:7)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fgzv.run(PG:12)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at java.lang.Thread.run(Thread.java:1119)
09-18 14:02:49.427 32320 32356 W BugleNetwork: RegistrationProvider: Got error in StatusRuntimeException. Notifying tachyon registration error listeners, error: 1, status: PERMISSION_DENIED
09-18 14:02:49.427 32320 32356 W BugleNetwork: fght: PERMISSION_DENIED: The caller does not have permission
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fhgo.a(PG:41)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fggn.a(PG:5)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at dusg.a(PG:72)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fgpg.g(PG:1)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fgpd.a(PG:28)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fgpz.run(PG:7)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at fgzv.run(PG:12)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
09-18 14:02:49.427 32320 32356 W BugleNetwork: 	at java.lang.Thread.run(Thread.java:1119)
09-18 14:02:49.429 32320 32356 I BugleRcsProvisioning: PhoneNumberRegistrationInfo: redacted-pii:phone_number[chars:12,last2:65]
09-18 14:02:49.430 32320 11048 I BugleRcsProvisioning: onTachyonRegistrationError for simId: redacted-pii:sim_id[chars:20,last3:509]
09-18 14:02:49.431 32320 11048 W BugleRcsProvisioning: Unhandled TachyonError type 1.
09-18 14:02:49.438 32320 11048 W BugleTachygram: TachygramSendMessageOperation failed: call into chat api to maybe try the operation again.
09-18 14:02:49.438 32320 11048 W BugleTachygram: eukh: Registration to tachyon failed., TachygramErrorReason(tachygramError=PERMISSION_DENIED, recoveryType=ERROR_NO_RETRY)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at cqrh.a(PG:19)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at emkv.a(PG:13)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at estz.d(PG:3)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at esub.run(PG:130)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at dttp.run(PG:7)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at epir.run(PG:44)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at dtwe.run(PG:18)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at dtsy.run(PG:89)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at java.lang.Thread.run(Thread.java:1119)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at dtun.run(PG:61)
09-18 14:02:49.438 32320 11048 W BugleTachygram: Caused by: fght: PERMISSION_DENIED: The caller does not have permission
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at fhgo.a(PG:41)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at fggn.a(PG:5)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at dusg.a(PG:72)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at fgpg.g(PG:1)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at fgpd.a(PG:28)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at fgpz.run(PG:7)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at fgzv.run(PG:12)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
09-18 14:02:49.438 32320 11048 W BugleTachygram: 	at java.lang.Thread.run(Thread.java:1119)
09-18 14:02:49.438 32320 32408 W BugleRcsCapabilities: Capabilities failed with an exception from the downstream provider.
09-18 14:02:49.438 32320 32408 W BugleRcsCapabilities: aupg: RetryingFuture failed to fetch RCS capabilities.

I'm not exactly sure how these components work, perhaps @GrapheneOS can provide more insight.

Edit: seems it's related to this https://xcancel.com/TransGirlLinux/status/1968446098978021383#m

benwaffle

ButtholeBlackhole As someone who has no idea how RCS works on the carrier side.... Why isn't it possible for someone to write an open source RCS background service that connects to the carrier provided RCS like iOS does? As far as I know iOS doesn't need to activate with Google or connect directly to Jibe

iOS does connect directly to Jibe servers for US carriers, and uses GSMA spec-compliant RCS, but it requires App Attest (like play integrity for iOS)

ButtholeBlackhole

benwaffle Well yes and no. It does technically use Jibe in US because that's what the carriers use on the backend. But iOS won't go completely around the carrier and connect directly to Jibe like Google Messages will in some cases.

benwaffle

If anybody is doing reverse engineering of the Google Messages apk, check out https://github.com/benwaffle/rcs-dump and https://github.com/benwaffle/jadx-google-helpers - I've got a lot of the obfuscated classes/methods renamed

Octo

Hi, I'm working on the recent RCS issue. Please reproduce the issue and capture the logs per the provided instructions. After capturing the logs, please send them over to contact@grapheneos.org or my matrix account @octocorvus:grapheneos.org

Make sure that Google Messages is directly installed from the Play Store. If you've installed it from somewhere else or sideloaded the apk, please uninstall it and reinstall from Play Store.
Give Play Service these permissions: Phone, SMS
Set Google Messages as the default SMS app.
Clear data of Google Messages app before proceeding. NOTE: This may cause some data specific to Google Messages to be lost. The messages will be kept, but proceed with caution.
Open Google Messages and go to settings -> RCS chats. It should show status as "Connecting"/"Setting Up". If you did not clear app data, turn off RCS and turn it back on. If RCS settings are unavailable, try restarting your device.
Open Settings app and go to System -> View logs. Click "Save" and now it will ask where to save the log file.
Send the saved log file over the contact@grapheneos.org email with subject "Google Messages RCS Logs". You may also DM the logs to my matrix account @octocorvus:grapheneos.org

Thank you for your time.

cap9qd

Octo Beta helpful/ok or should I leave beta?

de0u

jeremy-sylvis Thanks! Please see above (Octo) for submission instructions.

Judgeadam

Octo thank you for working on this issue

de0u

lefthandrev Suffice it to say, it looks like grapheneOS is definitely not being allowed to use RCS anymore.

A GrapheneOS developer recently indicated (Octo) that the team is working on this. I think it might make sense not to declare defeat, or even to attribute a cause, until more information is available from the team.

Octo

To check where Google Messages was installed from, open settings app and go to Apps -> See all apps -> Find the app and click it. Scroll all the way down and near the bottom, under the "Store" section, it should say "App installed from Google Play Store"

ralm

Since losing RCS my house hasn't burned down and my car still starts. Enshitification is still a problem, though.

jumpdeer

ralm Maybe for you. My car burned down and my house doesn't start. Could just be due to a phone reboot tho

de0u

jumpdeer My car burned down and my house doesn't start.

Is your refrigerator running?

If so, you'd better catch it!!

jeremy-sylvis

I've gathered some logs and shared them on a related GitHub issue in case it helps anyone: https://github.com/GrapheneOS/os-issue-tracker/issues/6173#issuecomment-3312721190

Twlight-Princess

Please no preaching of Signal-Molly or something else to use instead of AOSP SMS. I get it and I agree but, realistically friends, family and colleagues are not techie and will use whats default on Samsung phones and iPhone.

I want to give google messages a shot again, as for the past years Ive been using the AOSP SMS app and its God awfulness. It does the job, but it would be nice if google messages + RCS can work and disable the AOSP SMS can be disabled.

I tried using googles messages in the past and well my result was messages would sometimes come in a few days later if at all at times.

I think the major flaw I had last time was because I don't have play services always running in the background. Also been looking at other post and some mention Carrier services?

Even with the recent issues it seems with RCS is it still worth using google messages even for SMS?

de0u

Twlight-Princess I want to give google messages a shot again, as for the past years Ive been using the AOSP SMS app and its God awfulness.

See this recent post in this thread: de0u.

DeletedUser495

Twlight-Princess Ive been using the AOSP SMS app and its God awfulness

You don't know what's good for you (and it's not always what you think)

Gira

As of update 2025091900 on the Pixel 7 pro, my RCS has started working again. Using Google Fi.

Gira

Gira no idea how to edit yet, RCS worked for around an hour and then turned itself off or at least got stuck on "setting up". Weird issue, sorry for the false hope :(

antidigerati

Just upgraded to 2025091900 on Pixel 9 Pro XL. Cleared Messages cache/storage etc.
My RCS did NOT start working again. Still "Setting up..." and "Trying to verify your phone number..."

Canada on Telus.

I saw that 2025091900 had "backport latest carrier and cellular radio configurations from Android 16 QPR1" in the release notes and got hopeful. Alas, it didn't fix it.

« Previous Page Next Page »