RCS on GOS in Canada

ohhqo50139

I am unable to get RCS to activate over in Canada with Bell

I have enabled "Allow ICC authentication with device identifiers", enabled phone for google play services, reinstalled Google Messages, rebooted my phone, and disabled my VPN but I'm still stuck on "Connecting..."

After waiting for a while I'm now getting "Your device does not meet security requirements" and status code 4006

Has anyone else been able to get RCS to activate with a Canadian carrier?

Johnnyloans

ohhqo50139

Hello! Many people are having rcs issues with Bell even on stock phones, unfortunately.

Review these 2 comments for help:

ohhqo50139

Johnnyloans thank you for the links, I will try to do what the first one said works

Johnnyloans

ohhqo50139 youre welcome.

This too
https://grapheneos.org/usage#rcs

namecheckobnoxiously

Also in Canada and with Bell. RCS won't activate for me at all and I've tried all the suggestions.

ohhqo50139

namecheckobnoxiously I got a public mobile sim and it activated right away no issues

inthewaves

I've tested RCS with Freedom Mobile, Fizz Mobile, and Bell. Freedom requires the ICC toggle, as it uses TS.43 verification. Fizz doesn't need the toggle as it uses incoming SMS verification.

Bell seems to be broken in general, and it's likely not GrapheneOS-specific. Recently, I've been trying to activate RCS on Bell on a stock Pixel 9. It's not activating there either and stuck on "Connecting" (status code 3000) even after following suggestions from Reddit and the Bell forums . Bell appears to use incoming SMS verification the one time it verified for me on GrapheneOS, so theoretically the ICC toggle isn't needed for Bell. However, Google's servers decide the verification method in the end, so we can never really tell.

I will try to test RCS on Telus and Rogers soon.

namecheckobnoxiously

I removed GOS and went back to stock last night. RCS activated immediately.... I reinstalled GOS today and I'm back to "Connecting"..

inthewaves

namecheckobnoxiously Not sure what's happening then. I have been on stock for a couple of days, and it still hasn't activated on Bell to the point where it's telling me I'm hitting verification limits: https://github.com/user-attachments/assets/9fad64cf-1c33-4b17-96ae-040516e062e6

Maybe you could try https://messages.google.com/disable-chat too if you just moved from stock to GrapheneOS

namecheckobnoxiously

@"inthewaves"

I have tried that, thank you! When I have the time (hopefully tonight), I'm going to remove my phone # from my google account, create a new account, add the # and see if that does anything.

I'm either stuck on "connecting" or "your device does not meet security requirements". Frustrating!!

inthewaves

namecheckobnoxiously So I found out that Google Play services turns back on Phone number verification after a reboot, and I needed to ensure it was off again before setting up Google Messages.

What I did on the stock OS that finally made RCS activate after it was unable to verify:

Disable RCS in Google Messages settings
Open Google Settings (on GrapheneOS, this is Settings -> Apps -> Sandboxed Google Play -> Google Settings) -> All services -> Phone number verification and toggle it off
Turn on airplane mode to disable cell service
Clear storage in Google Messages (long press on Google Messages app icon -> App info -> Storage and cache)
Restart the phone
Turn on Wi-Fi, but keep airplane mode on to keep cell service disabled
Open Google Settings -> All services -> Phone number verification and toggle it off again
Turn off airplane mode
Open Google Messages, press okay to the dialog
Wait

namecheckobnoxiously

inthewaves

Thank you very much! Will try tonight and report back!
Do you have carrier services installed?

Novalissoide

inthewaves found out that Google Play services turns back on Phone number verification after a reboot, and I needed to ensure it was off again before setting up Google Messages

Thank you for reporting this. Precisely the kind of counter-intuitive solution so hard to discover. 🫡

ejns

inthewaves Wow - I literally just did this and it solved my RCS connection problem! In my case, that toggle doesn't just turn on after a reboot - if I toggle it off and back out of the menu, then go back in and check, it was on again! But that was the only thing I changed after trying everything else.

inthewaves

namecheckobnoxiously No, I did not have Carrier Services

Also, from the debug RCS configuration screen, Bell has switched to a TS43 policy (upi-carrier-tos-ts43), so it seems the ICC toggle becomes necessary for Bell now. Hopefully the new policy will also make it more reliable to activate RCS on Bell for other users (not just on GrapheneOS), since other carriers using upi-carrier-tos-ts43 like Freedom had no issues in activating RCS.

namecheckobnoxiously

I turned off RCS for 24 hours. When I turned it back on it took about 12 hours, but it is now connected.

stampeder

RCS is now broken on Telus too.

My Pixel 6 on GOS is completely up to date. RCS was working but became quite buggy over the past month's updates and now is being rejected by Telus. When the bugginess started, the Status value was stuck on "Connecting..." for weeks. I looked through lots of RCS posts here and implemented many test reconfigurations but they all resulted in that same "Connecting..." timeout mode.

Now the Status value has changed to "Not supported" in red letters. I've attached a screenshot:

https://imgbox.com/7QGiPogZ

I tried the steps recommended by inthewaves but when I try to turn off number verification the slider goes back to the on setting immediately, in real time, no matter what I try.

inthewaves

stampeder Attempt to turn off phone number verification, then get logs from Settings > Apps > See all apps > Google Play services > View logs

Also can you share the upi policy from the bottom of the debug RCS configuration menu? To go there

Activate debug menu: Google Messages > Search icon in top right > Search for *xyzzy* and you should see a toast saying Debug menu enabled
Go back to Google Messages home, tap on your avatar icon in top-right, find the Debug button in the menu, then RCS and Configure MobileConfiguration
Tap on your SIM between the "Force Sync Mobile Configuration" and "Refresh" buttons
Scroll down and find upi_policy_id

stampeder

inthewaves

Logs from Settings > Apps > See all apps > Google Play services > View logs taken as I tried to turn off number verification. Swiping the slider right opens the PIN interface, so when I enter the PIN the screen returns but the slider immediately swipes right on its own, preventing me from turning off number verification.

--------- switch to events 05-01 15:19:52.683 10011 10011 I wm_on_top_resumed_lost_called: [Token=72002346,Component Name=com.google.android.gms.constellation.ui.ConstellationConsentSettingActivity,Reason=topStateChangedWhenResumed] 05-01 15:19:52.821 10011 10011 I view_enqueue_input_event: [eventType=Motion - Cancel,action=com.google.android.gms/com.google.android.gms.constellation.ui.ConstellationConsentSettingActivity] 05-01 15:19:55.598 10011 10011 I wm_on_paused_called: [Token=72002346,Component Name=com.google.android.gms.constellation.ui.ConstellationConsentSettingActivity,Reason=performPause,time=0ms] --------- switch to main 05-01 15:19:55.630 10011 10011 D VRI[ConstellationConsentSettingActivity]: visibilityChanged oldVisibility=true newVisibility=false --------- switch to events 05-01 15:19:55.643 10011 10011 I viewroot_draw_event: [window=VRI[ConstellationConsentSettingActivity],event=Not drawing due to not visible. Reason=!mAppVisible && !mForceDecorViewVisibility] 05-01 15:19:55.648 10011 10011 I wm_on_stop_called: [Token=72002346,Component Name=com.google.android.gms.constellation.ui.ConstellationConsentSettingActivity,Reason=STOP_ACTIVITY_ITEM,time=2ms] --------- switch to main 05-01 15:20:00.664 2006 3830 E NlpRequestHelper: failed to send request to NLP 05-01 15:20:00.665 2006 3830 E NlpRequestHelper: failed to send request to NLP --------- switch to system 05-01 15:20:04.266 9840 9881 W Looper : Drained --------- switch to main 05-01 15:20:05.710 10011 10038 I SharingClientImpl: client com.google.android.gms disconnecting 05-01 15:20:05.713 2006 4015 I NearbySharing: Package com.google.android.gms has requested to unsuspend Quick Share 05-01 15:20:05.716 10011 10585 E SharingClientImpl: Unsuspend failed: null 05-01 15:20:10.735 9840 9840 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.inappreach.service.START dat=chimera-action:/... xflg=0x4 cmp=com.google.android.gms/.chimera.GmsApiService } 05-01 15:20:10.739 9840 9840 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.audit.service.START dat=chimera-action:/... xflg=0x4 cmp=com.google.android.gms/.chimera.GmsBoundBrokerService } 05-01 15:20:10.741 2006 2006 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.auth.aang.events.services.START dat=chimera-action:/... xflg=0x4 cmp=com.google.android.gms/.chimera.PersistentApiService } 05-01 15:20:10.746 9840 9840 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.feedback.internal.IFeedbackService dat=chimera-action:/... xflg=0x4 cmp=com.google.android.gms/.chimera.GmsBoundBrokerService } 05-01 15:20:10.746 9840 9840 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.checkin.START xflg=0x4 pkg=com.google.android.gms } 05-01 15:20:10.750 10011 10011 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.core.settings.service.START dat=chimera-action:/... xflg=0x4 cmp=com.google.android.gms/.chimera.UiApiServiceNoInstantApps } 05-01 15:20:10.751 2006 2006 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.trustagent.BridgeApi.START dat=chimera-action:/... xflg=0x4 cmp=com.google.android.gms/.chimera.PersistentInternalApiService } 05-01 15:20:10.756 9840 9840 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.onboardingconsent.api.ConsentManagerApiService.START dat=chimera-action:/... xflg=0x4 cmp=com.google.android.gms/.chimera.GmsApiService }

Google Messages debug log:
https://imgbox.com/ifJcGur0

It shows upi-carrier-tos-ts43

inthewaves

stampeder Do you have access to adb via USB Debugging in the Developer options in Settings?

There are some logs in Google Play services that require this adb command for extra logging:

adb shell setprop log.tag.constellation VERBOSE

Then run adb shell am force-stop com.google.android.gms and then try to go for the toggle again and re-capture logs.

Note that this will result in sensitive info being logged, so after you should either reboot to remove it or set it to adb shell setprop log.tag.constellation ""

For example, when I toggle the automatically verify phone numbers switch off withlog.tag.constellation set to VERBOSE, I see these logs and the switch stays off when I remain on the screen:

25477-30015 cn_CronetU...estContext com.google.android.gms.persistent    I  destroyNativeStreamLocked org.chromium.net.impl.CronetBidirectionalStream@44f435f
 9955-9955  WindowOnBackDispatcher  com.google.android.gms.ui            D  setTopOnBackInvokedCallback (unwrapped): qkv@576b724
 9955-9955  constellation           com.google.android.gms.ui            I  [biometrics] Authentication succeed
 9955-9955  WindowOnBackDispatcher  com.google.android.gms.ui            D  setTopOnBackInvokedCallback (unwrapped): android.app.Activity$$ExternalSyntheticLambda0@5ce16ca
 9955-9981  constellation           com.google.android.gms.ui            D  [consent_manager] setConsent, consented = false
 9955-9981  constellation           com.google.android.gms.ui            D  [consent_manager] Deleting consent and verification from the key value store
25584-32569 cn_CronetU...estContext com.google.android.gms               I  destroyNativeStreamLocked org.chromium.net.impl.CronetBidirectionalStream@80154a1
 9955-9981  constellation           com.google.android.gms.ui            V  [storage_manager] Delete all and insert new verifications
 9955-9981  constellation           com.google.android.gms.ui            V  [database_helper] Getting a writable database.
 9955-9981  constellation           com.google.android.gms.ui            D  [consent_manager] After deleting: consent = false, automaticCostSetting = false
 9955-9955  InsetsController        com.google.android.gms.ui            D  hide(ime())
 9955-9955  ImeTracker              com.google.android.gms.ui            I  com.google.android.gms:8ef7ccf3: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN
 9955-9981  constellation           com.google.android.gms.ui            D  [rpc_manager] Setting up set consent request
 9955-9981  constellation           com.google.android.gms.ui            D  [rpc_manager] Create client info
 9955-9981  constellation           com.google.android.gms.ui            D  [device_id_util] Building DeviceID with Iidtoken, DeviceAndroidId: <>, DeviceUserId: 0, UserAndroidId: <>
 9955-9981  constellation           com.google.android.gms.ui            D  [rpc_manager] Adding deviceID in request header, deviceAndroidID:<>, deviceUserId: 0, userAndroidID: <>
 9955-9981  constellation           com.google.android.gms.ui            D  [rpc_manager] Setting droidguard token for device signals
 9955-9981  constellation           com.google.android.gms.ui            D  [rpc_manager] SetConsentRequest: <>
25584-10050 Conscrypt               com.google.android.gms               W  Could not set socket write timeout: java.net.SocketException: Socket closed
25584-10050 Conscrypt               com.google.android.gms               W  	at com.google.android.gms.org.conscrypt.Platform.setSocketWriteTimeout(:com.google.android.gms@260931035@26.09.31 (260400-877989800):204)
25584-10050 Conscrypt               com.google.android.gms               W  	at com.google.android.gms.org.conscrypt.ConscryptFileDescriptorSocket.setSoWriteTimeout(:com.google.android.gms@260931035@26.09.31 (260400-877989800):4)
25584-10050 Conscrypt               com.google.android.gms               W  Could not set socket write timeout: java.net.SocketException: Socket closed
25584-10050 Conscrypt               com.google.android.gms               W  	at com.google.android.gms.org.conscrypt.Platform.setSocketWriteTimeout(:com.google.android.gms@260931035@26.09.31 (260400-877989800):204)
25584-10050 Conscrypt               com.google.android.gms               W  	at com.google.android.gms.org.conscrypt.ConscryptFileDescriptorSocket.setSoWriteTimeout(:com.google.android.gms@260931035@26.09.31 (260400-877989800):4)
 9955-9981  constellation           com.google.android.gms.ui            D  [rpc_manager] SetConsentResponse: <>