RCS (Google Messages) provisioning fails since September – Carrier Services no background activity

[Appstaaate]

Summary:
RCS / Google Messages chat features no longer provision on GrapheneOS as of early September. Chat features remain stuck on “Verifying…” indefinitely.

Environment:
• Devices: Pixel [model] running GrapheneOS (latest stable release as of [date])
• Carrier: T-Mobile US
• Apps: Google Messages (latest Play version), Carrier Services (latest Play version)
• SIM: tested with both old SIM and replacement SIM

What happens:
• Google Messages → Settings → Chat features → Enable → Status: “Verifying…”
• Carrier Services shows 0 background data usage (no traffic)
• No verification SMS received from Google Jibe

What I expected:
• RCS should provision and connect within a few minutes as it does on stock Android

Steps to reproduce:
1. Fresh install GrapheneOS on Pixel
2. Insert T-Mobile SIM (new or old, both tested)
3. Install Carrier Services + Google Messages from Play Store
4. Enable Chat features
5. Observe “Verifying…” loop and no Carrier Services traffic

Control test:
• Same SIM works fine on stock Galaxy phone → RCS connects immediately
• Confirms not a carrier or Jibe account issue

Notes:
• RCS worked on GrapheneOS before early September.
• Issue began after T-Mobile/Google messaging updates.
• Looks like Carrier Services background calls are blocked by Graphene (provisioning never fires).

Request:
Please investigate whether GrapheneOS restrictions are preventing Carrier Services from completing the new Jibe provisioning handshake.

[brothersw]

I am having the same issue with Spectrum as my carrier, may be related to issue #6056

[runna5k]

I have Fi as my carrier and I ran the same tests.

[electr0sheep]

I also ran into this with Fi as my carrier.

[jeremy-sylvis]

This also occurs with Mint Mobile (which uses T-Mobile as the backing ACS URL).

I've done significant diagnostics and info-gathering for this. To start, swapping my e-sim to my OnePlus 13 resulted in flawless activation of RCS. Swapping my e-sim back to my Pixel 8 Pro running GrapheneOS resulted in the exact same difficulty, stuck at verifying phone number. I tried swapping my e-sim back to a stock Pixel 7 Pro and similarly, flawless activation of RCS. Back to the Pixel 8 Pro running GrapheneOS and, once again, failure to activate.

My Pixel 8 Pro running GrapheneOS had a US Mobile sim (Verizon network) which was eventually able to activate via RCS but that allows you to specify your phone # etc as part of its activation path - I think this is self registration. Mint/T-Mobile do not allow this.

I ended up disabling my US Mobile sim so only the Mint sim was enabled, then enabling the messages debug menu and forcing RCS deregistration and registration to gather some log output.

Steps taken

I installed the Carrier Services app.

I manually gave com.google.android.apps.messaging, com.google.android.gms, and com.google.android.ims the READ_PHONE_NUMBERS and READ_DEVICE_IDENTIFIERS appopps permissions.

Observations & Speculation

In digging into the logs for the Google Messages app, there are frequent entries for RCS-related activity highlighting inability to gather information. Common trends are inability to sim-related or phone-related info, especially interesting given my attempts to manually allow those permissions.

There are errors that seem to imply dependency on a callback from GMS that fails to execute and a potentially-related binder failure.

System Logs

Link: Proton Drive

This is an 8MB text file.

Snippets:

Unable to get telephony subscription info.

09-19 00:14:02.372 10189 19970 23617 I TelephonySubscriptionIn: getActiveSubscriptionInfo(): empty sub info for 1.
09-19 00:14:02.372 10189 19970 24043 D WM-GreedyScheduler: Ignoring {WorkSpec: c6d083bb-d008-4620-94a2-c65cb3be1920}. Requires ContentUri triggers.
09-19 00:14:02.372 10189 19970 24043 D WM-GreedyScheduler: Starting tracking for 0ae77268-fad4-4638-a09a-1cdc59457d13
09-19 00:14:02.374 10189 19970 23617 W RcsProvisioningManager: getSimIdFromSubId for subId: 1 returned no mapping.
09-19 00:14:02.375 10189 19970 20023 I BugleSelfIdentity: Rcs is NOT_AVAILABLE for SelfIdentity. [CONTEXT sub_id=1 rcs_availability="13" ]
09-19 00:14:02.377 10189 19970 20023 I RcsProvisioningManager: Skipping backfill of identity mapping.
09-19 00:14:02.379 10189 19970 23617 W SharedPreferencesSimSta: SharedPreferencesSimStateStore: No sim subscription info found for subscription id: 2
09-19 00:14:02.380 10189 19970 23617 I TelephonySubscriptionIn: getActiveSubscriptionInfo(): empty sub info for 2.
09-19 00:14:02.383 10189 19970 23617 W RcsProvisioningManager: getSimIdFromSubId for subId: 2 returned no mapping.
09-19 00:14:02.383 10189 19970 20023 I BugleSelfIdentity: Rcs is NOT_AVAILABLE for SelfIdentity. [CONTEXT sub_id=2 rcs_availability="13" ]
09-19 00:14:02.384 10189 19970 20023 I RcsProvisioningManager: Skipping backfill of identity mapping.
--------- switch to events
09-19 00:14:02.385  1000  1346  1930 I input_focus: [window=Focus leaving 9a14db4 com.google.android.apps.messaging/com.google.android.apps.messaging.ui.appsettings.ApplicationSettingsActivity,reason=reason=NO_WINDOW]
--------- switch to main
09-19 00:14:02.384 10189 19970 20023 I BugleSelfIdentity: Rcs is NOT_AVAILABLE for SelfIdentity. [CONTEXT sub_id=3 rcs_availability="10" ]
09-19 00:14:02.385 10189 19970 20023 I RcsProvisioningManager: Skipping backfill of identity mapping.
09-19 00:14:02.388 10189 19970 20023 I BugleSelfIdentity: Rcs is NOT_AVAILABLE for SelfIdentity. [CONTEXT sub_id=3 rcs_availability="10" ]

Unable to get phone # for RCS provisioning info; unable to get a phone number via android.telephony.SubscriptionManager.getPhoneNumber specifically due to missing android.permission.READ_PHONE_NUMBERS, android.permission.READ_PRIVILEGED_PHONE_STATE, or "carrier privileges".

09-19 00:13:58.060 10189 19970 23759 I BugleRcs: No phone number found for a given provisioning id.
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: eosz: FULL
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at djlb.f(PG:100)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at chjt.b(PG:12)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at chjt.a(PG:1)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at cnup.D(PG:572)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at cntk.b(PG:388)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at cntk.a(PG:13)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at fipv.b(PG:14)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at fipv.a(PG:2)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at fhxx.a(PG:52)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at cnup.E(PG:86)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at cntg.b(PG:16)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at cntg.a(PG:13)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at awux.b(PG:20)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at fhod.w(PG:12)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at fhzx.run(PG:107)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at ekxt.run(PG:3)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at emkx.run(PG:13)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at dttp.run(PG:7)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at dtst.run(PG:6)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at java.lang.Thread.run(Thread.java:1119)
09-19 00:13:58.060 10189 19970 23759 I BugleRcs: 	at dtun.run(PG:61)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : TelephonySubscriptionInfoAsOfT: getRawSelfNumber failed [CONTEXT ratelimit_period="1 MINUTES" sub_id=3 ]
09-19 00:13:58.066 10189 19970 23759 W Bugle   : java.lang.SecurityException: getPhoneNumberFromFirstAvailableSource: Neither user 10189 nor current process has android.permission.READ_PHONE_NUMBERS or android.permission.READ_PRIVILEGED_PHONE_STATE or carrier privileges. subId=3, allowCarrierPrivilegeOnAnySub=false
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at android.os.Parcel.createExceptionOrNull(Parcel.java:3349)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at android.os.Parcel.createException(Parcel.java:3333)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at android.os.Parcel.readException(Parcel.java:3309)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at android.os.Parcel.readException(Parcel.java:3251)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at com.android.internal.telephony.ISub$Stub$Proxy.getPhoneNumberFromFirstAvailableSource(ISub.java:2554)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at android.telephony.SubscriptionManager.getPhoneNumber(SubscriptionManager.java:4585)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at ir$$ExternalSyntheticApiModelOutline0.m(D8$$SyntheticClass:34)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cvgq.h(PG:13)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cvgu.h(PG:3)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cvfw.k(PG:94)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cvfw.i(PG:1)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at chjt.a(PG:87)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cnup.D(PG:572)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cntk.b(PG:388)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cntk.a(PG:13)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at fipv.b(PG:14)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at fipv.a(PG:2)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at fhxx.a(PG:52)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cnup.E(PG:86)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cntg.b(PG:16)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at cntg.a(PG:13)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at awux.b(PG:20)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at fhod.w(PG:12)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at fhzx.run(PG:107)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at ekxt.run(PG:3)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at emkx.run(PG:13)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at dttp.run(PG:7)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at dtst.run(PG:6)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at java.lang.Thread.run(Thread.java:1119)
09-19 00:13:58.066 10189 19970 23759 W Bugle   : 	at dtun.run(PG:61)
09-19 00:13:58.066 10189 19970 23759 I Bugle   : TelephonySubscriptionInfoAsOfT: getRawSelfNumber fallback to super
09-19 00:13:58.067 10189 19970 23759 I Bugle   : SubscriptionUtils.getCanonicalForSelf: self=redacted-pii[12-chars], country=US [CONTEXT sub_id=3 ]
09-19 00:13:58.071 10189 19970 23759 I Bugle   : CountryCodeDetector: updateSmsNetworkCountry from default subscription network country. detected country: us

Seems to be implying GmsCompat/Hooks is spoofing permissions (READ_PHONE_STATE) for getService(), I can't help but wonder if this is related to my attempt to manually grant permissions. It also seems to be spoofing a device identifier.

22577 is com.google.android.gms.unstable, 19970 is com.google.android.apps.messaging, 20123 is com.google.android.apps.messaging:rcs.

09-19 00:11:26.226 10189 20123 20158 I BugleRcsEngine: Connected state: [1], networkType: [MOBILE] [CONTEXT thread_id=24 ]
09-19 00:11:26.227 10189 20123 20166 I BugleRcsEngine: handleMessage processing message:[NOTIFY_UPTIME_IGNORE_STATE_CHANGED] with [non-null]:RcsEngineImpl reference [CONTEXT log_prefix="RcsEngineImpl[DUAL_REG]:[b04499b1-d1cc]>Handler" thread_id=32 ]
09-19 00:11:26.232 10120  2312  8960 D SHANNON_RCS: 0836 [1][PROX][TELE] onCapabilitiesChanged, Network: 108, NetworkCapabilities: [ Transports: CELLULAR Capabilities: MMS&SUPL&IA&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED&NOT_BANDWIDTH_CONSTRAINED LinkUpBandwidth>=12248Kbps LinkDnBandwidth>=12248Kbps Specifier: <TelephonyNetworkSpecifier [mSubId = 3]> SubscriptionIds: {3} UnderlyingNetworks: Null] (DefaultNetworkCallback%onCapabilitiesChanged:76)
--------- switch to system
09-19 00:11:26.233  1000  1346  4345 D ActivityManager: sync unfroze 22577 com.google.android.gms.unstable for 7
--------- switch to events
09-19 00:11:26.234  1000  1346  1919 I am_unfreeze: [Pid=22577,Process Name=com.google.android.gms.unstable,7]
--------- switch to main
09-19 00:11:26.237 10189 19970 20034 D WM-NetworkStateTracker: Network capabilities changed: [ Transports: CELLULAR Capabilities: MMS&SUPL&IA&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED&NOT_BANDWIDTH_CONSTRAINED LinkUpBandwidth>=12248Kbps LinkDnBandwidth>=12248Kbps Specifier: <TelephonyNetworkSpecifier [mSubId = 3]> SubscriptionIds: {3} UnderlyingNetworks: Null]
--------- switch to system
09-19 00:11:26.239  1000  1346  2066 D BackgroundInstallControlService: Package event received: 0
09-19 00:11:26.241  1000  1346  2066 D BackgroundInstallControlService: Package event received: 0
09-19 00:11:26.241  1000  1346  2066 D BackgroundInstallControlService: Package event received: 0
--------- switch to main
09-19 00:11:26.249 10189 20123 20166 I BugleRcsEngine: No RCS Configuration was found in Bugle for simID: redacted-pii:sim_id[chars:19,last3:029] [CONTEXT log_prefix="ProvisioningEngineDataRetriever" thread_id=32 ]
09-19 00:11:26.252 10152 22577 22615 D GmsCompat/Hooks: start spoofing self permission checks for getService() call for API 25, perms: [android.permission.READ_PHONE_STATE]
09-19 00:11:26.252 10152 22577 22615 D GmcPackageManager: notifyPermissionsChangeListeners
--------- switch to system
09-19 00:11:26.252  1000  1346  5708 W ProcessStats: Tracking association SourceState{25f4ece com.google.android.apps.messaging/10189 BFgs #21362} whose proc state 4 is better than process ProcessState{6953d58 com.google.android.gms.unstable/10152 pkg=com.google.android.gms} proc state 14 (0 skipped)
--------- switch to main
09-19 00:11:26.254 10152 22577 22615 D GmsCompat/Hooks: end self permission check spoofing
09-19 00:11:26.254 10152 22577 22615 D GmcPackageManager: notifyPermissionsChangeListeners
09-19 00:11:26.282 10189 19970 19970 I BugleDataModel: ActionExecutorImpl: ACTION_EXECUTE_QUEUED_GenericWorkerQueueAction
09-19 00:11:26.282 10189 19970 23763 I BugleDataModel: ExecuteActionRunnable: running action GenericWorkerQueueAction
09-19 00:11:26.285 10189 19970 23763 I BugleDataModel: ActionExecutorImpl: ACTION_BACKGROUND_QUEUED_GenericWorkerQueueAction
09-19 00:11:26.297 10189 19970 23759 I BugleJobs: GenericWorkerQueueAction: Work found

...

09-19 00:11:26.427 10152 22577 22614 D GmsCompat/Hooks: Generating serial number from SSAID: 14A6D11CEF73C205

Difficulty handling MCC/MNC:

09-19 00:10:55.268 10189 19970 23759 W Bugle   : BuglePhoneNumberUtils: canonicalizeMccMnc: invalid mccmnc. mcc: null, mnc: null [CONTEXT x_message_id=8305765674466146388 work_id="1253f206-ba5d-4abe-b3a7-231b8b1be012" pipeline_type="SmsReceivePipeline" ]

Permission rejected for auto classifying an SMS as spam though this should be working:

09-19 00:10:55.834 10189 19970 20026 I BugleSpam: SpamErrorHandler#handleClassificationError: failed to classify spam [CONTEXT x_message_id=8305765674466146388 work_id="1253f206-ba5d-4abe-b3a7-231b8b1be012" pipeline_type="SmsReceivePipeline" ]
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: fght: PERMISSION_DENIED: The caller does not have permission
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at fhgo.a(PG:41)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at fggn.a(PG:5)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at dusg.a(PG:72)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at fgpg.g(PG:1)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at fgpd.a(PG:28)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at fgpz.run(PG:7)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at fgzv.run(PG:12)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
09-19 00:10:55.834 10189 19970 20026 I BugleSpam: 	at java.lang.Thread.run(Thread.java:1119)

Lines 36188-36894 seem to capture part of a provisioning attempt.

Messages Logs

Unfortunately, I didn't save a text log here - I just grabbed screenshots as I went.

com.android.providers.telephony.SmsProvider SMS permission issue: link

Tie between messaging and GMS? link

RCS provisioning looks like it's dependent on a callback from GMS; I think this is the callback failing with a binder issue link

This is why I think RCS provisioning is dependent on a callback - looks like GMS is using GoogleApiManager somehow to try and call into messages and it's choking out link

Another example of the above but this time close-proximity to RCS provisioning flow log messages link

Some sort of issue calling a system process method as a response to telephony state change? link

Another example of needing READ_PHONE_NUMBERS or READ_PRIVILEGED_PHONE_STATE despite my having provided READ_PHONE_NUMBERS via ADB link

[hamzamemon]

I have the same issue on US Mobile (T-Mobile and Verizon) with Carrier Services installed. I have given com.google.android.gms and com.google.android.ims READ_DEVICE_IDENTIFIERS.

In my logs I've seen

• "No RCS phone number found for subscription id."
• "getPhoneNumberForSubscriptionIdOptional: accessing uninitialized provisioning identities"
• "No phone numbers available"
• "phone number null, checking subscription exists in same subscription group."
• "Rcs is NOT_AVAILABLE for SelfIdentity. [CONTEXT sub_id=4 rcs_availability="10" ]
• "No RCS provisioning id found for given phone number. Last four digits of input phone number: XXXX. Last four digits of phone numbers in mapping: []

[Sfven]

Same issues here.

Pixel 6, AT&T
GOS 2025091000
Google Messages 20250907_01_RC00 from Play Store
Extra permissions added through AppOps + Shizuku

Stopped working in early September. Can't get RCS to get past "Verifying" stage on current versions of Messages. But on older versions, specifically 20241120_00_RC07, it'll connect to RCS, and that used to work fine. You could then upgrade to modern Messages version and it'd retain connected status. However since early September, using this method, you can still get it connected, but it will not actually send RCS messages anymore.

[Arson31]

Same issue with or without carrier services installed. Status stuck on "Setting up..."

Pixel 9
messages.android_20250907_01_RC00.phone_dynamic - all permissions given besides location
GOS 2025091000

Log file:
Messages log 62c94369773a.txt

[Appstaaate]

Unfortunately I’ve learned RCS now requires frequent handshakes between the carrier and device and utilizing carrier services app. Graphene blocks carrier services from functioning.

…

Sent from my gmail app

On Fri, Sep 19, 2025 at 3:22 PM Arson31 ***@***.***> wrote: *Arson31* left a comment (GrapheneOS/os-issue-tracker#6173) <#6173 (comment)> Same issue with or without carrier services installed. Status stuck on "Setting up..." Pixel 9 messages.android_20250907_01_RC00.phone_dynamic - all permissions given besides location GOS 2025091000 Log file: Messages log 62c94369773a.txt <https://github.com/user-attachments/files/22433574/Messages.log.62c94369773a.txt> — Reply to this email directly, view it on GitHub <#6173 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BXRHBBMIRQ43RCKSTQ3XLZT3TRJY5AVCNFSM6AAAAACGZUPEYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJTGUZDOMRSHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[hamzamemon]

Unfortunately I’ve learned RCS now requires frequent handshakes between the
carrier and device and utilizing carrier services app. Graphene blocks
carrier services from functioning.
…

Does this mean we no longer should have the Carrier Services app installed for RCS to work?

[Appstaaate]

Mine doesn't even do anything.

…

On Mon, Sep 22, 2025, 5:39 PM Hamza Memon ***@***.***> wrote: *hamzamemon* left a comment (GrapheneOS/os-issue-tracker#6173) <#6173 (comment)> Unfortunately I’ve learned RCS now requires frequent handshakes between the carrier and device and utilizing carrier services app. Graphene blocks carrier services from functioning. … <#m_-6965270094367214288_> Does this mean we no longer should have the Carrier Services app installed for RCS to work? — Reply to this email directly, view it on GitHub <#6173 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BXRHBBLPKZMYDVTVJKYMWDL3UBUBVAVCNFSM6AAAAACGZUPEYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMRRGU3TOMJSG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Arson31]

Does this mean we no longer should have the Carrier Services app installed for RCS to work?

I never had it installed when it was working.

[hamzamemon]

I never had it installed when it was working.

Darn, if only it was that simple.

[Appstaaate]

Yeah, but apparently now that it’s been shifted over to carriers, something in graphene blocks permissions needed - supposedly carrier services is that bridge. I wish I could let carrier services work to actually try it out (can’t though…)

…

Sent from my gmail app

On Mon, Sep 22, 2025 at 6:11 PM Hamza Memon ***@***.***> wrote: *hamzamemon* left a comment (GrapheneOS/os-issue-tracker#6173) <#6173 (comment)> I never had it installed when it was working. Darn, if only it was that simple. — Reply to this email directly, view it on GitHub <#6173 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BXRHBBKPLBWHS7I7BAZ3H433UBX2RAVCNFSM6AAAAACGZUPEYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMRRGY2TIMBRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[hamzamemon]

Could it be Network settings? Like Private DNS, internet connectivity checks, or attestation key provisioning?

[Appstaaate]

I tried all of those. Sigh! Also tried old messaging apk’s and carrier settings apk’s nothing worked Something is hardened by graphene because stock pixel works great. Wish I knew what it was but my guess is carrier settings app now being more crucial after Google no longer keys old jibe rcs tokens stick.

…

Sent from my gmail app

On Mon, Sep 22, 2025 at 6:28 PM Hamza Memon ***@***.***> wrote: *hamzamemon* left a comment (GrapheneOS/os-issue-tracker#6173) <#6173 (comment)> Could it be Network settings? Like Private DNS, internet connectivity checks, or attestation key provisioning? — Reply to this email directly, view it on GitHub <#6173 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BXRHBBLKH5TFZOOY4IETIDL3UBZZ3AVCNFSM6AAAAACGZUPEYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMRRGY4TSMJVGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>