Using RCS with Google Messages on GrapheneOS

lefthandrev

de0u I! DECLARE! DEFEAT!

Jokes aside, I saw octo was on it after I posted.

lefthandrev

After wiping application data and restarting, here are some of the messages I'm getting with logcat. Mine says "Setting up..." and "Trying to verify your phone number..." below that.

I am on a call with Verizon support as I'm working on this. I think I'm overwhelming the technician.

09-23 11:50:44.462 W/BugleRcsProvisioning(28145): Failed to get RCS configuration from the cached provider, configuration is empty. [CONTEXT x_message_id=-1861371666685764574 work_id="021e1e76-e226-4f9e-a2d9-8bb4ecbde76e" pipeline_type="SmsReceivePipeline" ]

09-23 11:50:43.727 E/BugleWelcome(28145): Asterism setConsented operation for message-id: 3600441726569733873 failed with request-code: 1 and audit-token: EhcKFQiNnsXriKeXhnoQ1szn8f2EurWOAQ== 09-23 11:50:43.728 E/BugleWelcome(28145): ProfilesConsentWorker: Failed to set consent. Retrying

09-23 11:52:55.742 I/BugleRcsProvisioning(28145): RcsAvailability: Subscription Id: 1, simId: redacted-pii:sim_id[chars:20,last3:692], sipConnectionType: DUAL_REG, isRcsAvailable: false

09-23 12:28:16.001 I/BugleRcs( 4747): phone number null, checking subscription exists in same subscription group. 09-23 12:28:16.003 W/BugleRcs( 4747): No RCS phone number found for subscription id. [CONTEXT ratelimit_period="30 SECONDS" group_by="1" sub_id=1 skipped=3 ] 09-23 12:28:16.003 W/BugleRcs( 4747): etfi: FULL

ButtholeBlackhole

Hmm... So if implementing RCS into the OS without Google Messages is impossible why not add encrypted XMPP (or Matrix) support to the default messages app? You could even add SMS fallback when the message fails to send if the contact has a phone number added. Just merge all the messages from the different sources by contact. Maybe color coat the SMS and encrypted messages from each other. Or add a little lock icon.

5rlyn

ButtholeBlackhole I think the main issue (at least for me) is that for better or worse, iMessage and Google Messages RCS is where people are, and we have to meet them where they're at. The fact is "I can't use RCS Chats because Google won't acknowledge my custom ROM as legitimate" isn't going to be a good answer for a lot of people who ask why messaging you is so strange.

jeffcodes

5rlyn ButtholeBlackhole
Spot on here. Asking developers to incorporate yet another protocol into an app is not going to go over well. The use case and user base for such a "want" is just so small. Most people are non-technical users, unlike most of us here who are more likely to be tech geeks and nerds.
Additionally, trying to get those non-technical users to use {INSERT ANY OTHER ENCRYPTED CHAT HERE} as an alternative just isn't going to go well either. Not for those of us that want more privacy by default, and not for those who just want "easy." The solution that serves all of us, technical and non-technical alike, is to use what exists already; iMessage-to-iMessage, iMessage-to-RCS, RCS-to-iMessage and RCS-to-RCS, and all integrated into the default messaging apps.
Frustrating, for sure.

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.

ButtholeBlackhole

5rlyn My solution to this is to literally take their phone and install whatever messenger you use and set it up for them. And then just start messaging them without explaining anything. Half the people I've done this with don't even realize they're using signal. They just see a message from me in their notifications and click on it.

5rlyn

I don't know if this is helpful to The Cause, but I was just able to get phone verification successfully turned on for my Pixel 9 Pro (no longer shows "Verification In Progress" on the website). RCS Chats still lists RCS as "Setting Up" on Mint Mobile, however.

Hiddenprior

5rlyn How did you manage that? Mine still says verification in progress.

Pixel 9a
Mint Mobile

5rlyn

Hiddenprior I'm not sure what exactly did it, I went to https://myaccount.google.com/phone and unticked the slider for "Verification in Progress," which was stuck on Attempting to Verify. Then going through the Sandboxed Google Play menu I was able to reenable it. This caused two crashes of GMS Compact, but while that was happening I got a message from Google indicating the number was being verified. It now shows "On," for my phone.

ghost_division

5rlyn I tried that on my Pixel 9a with T Mobile
I actually got an SMS verification message from it this time, however Google Messages still is reporting "Trying to verify your phone number" in RCS Chats, and pressing "Report RCS Connection State" still crashes the app.

I don't see any "Verification in Progress" on the website anymore and it appears as if it verified, but I still don't see anything like that in the app.
GMS Compact didn't do any crashes when I tried this

SillySaurus

ghost_division I actually got an SMS verification message from it this time, however Google Messages still is reporting "Trying to verify your phone number" in RCS Chats, and pressing "Report RCS Connection State" still crashes the app.

You need to clear your google messages app data to fix that. It won't clear your messages. It should connect and say "Connected", as mine does on two devices, the issue is further along with

XMPP/Matrix = not substitutes for receiving RCS/SMS, these are still used and have zero conversion effort. The latest version of Google Messages does in fact do MLS as well, so in theory that will be compatible with iMessage at some point.

We have come closer to it, and think it's an SELinux policy that needs tweaking. Some of the Google Messages services need access in the android.gms domain. This has nothing to do with Google "preventing" GrapheneOS or anything like that, it's just they've split up some of the modules in Google Messages and they don't have correct access. GmsCompat may also need some tweaks but not certain yet on that.

5rlyn

SillySaurus I've tried that a few times, always with VPN and WiFi disabled, but haven't made it past "Setting Up" yet.

SillySaurus

5rlyn You can get more of an idea about the connection state under Debug > RCS > RCS Connection State

You do need to enable the debug menu above.

5rlyn

SillySaurus Found that, but still haven't progressed beyond Setting Up or Crashing when RCS Connection State is selected.

madjack

Just for another reference: I am on a Pixel 9 Pro on Verizon. RCS stopped working about 3 weeks ago. My debug output says that an RCS Connection was successful, but on the https://myaccount.google.com/u/1/phone page, it still says "Verification in progress". No RCS functionality seems to be working as of now still.

bake

Hi everyone, I am having the same issue with RCS messages. RCS worked just fine until about 3 weeks ago, then stopped. RCS chats were enabled and connected in the settings, but would not connect when sending or receiving a message. I got an error that said cannot connect, check your data connection, and everything reverted to SMS.

I am trying to read through all the posts here but it is a LOT. So someone please correct me if I am wrong, there is an issue with RCS settings that currently cannot be fixed without an update from the Graphene team, am I correct?

If not, please help me, I am on a 7a with RCS chats enabled on Spectrum (Verizon) and all was fine until the mentioned 3 weeks ago. I cleared the app cache and data, I am running through the verification process again, and now seem to be stuck on "setting up, trying to verify your phone number."

de0u

bake So someone please correct me if I am wrong, there is an issue with RCS settings that currently cannot be fixed without an update from the Graphene team, am I correct?

An issue with RCS, yes.

bouncy3915

I finally made it out of the verify stage. I'm currently seeing:

Status: Not supported
Your device does not meet security requirements

When I press "Details" the popup says

Status code: 4006
Status details: Your device does not meet security requirements

rambling_man

bouncy3915

New grapheneos user here, joined to forum to keep up to date with the fun here. I'm in exactly this situation - recently moved from "setting up" to "Status: Not supported" with the same status code 4006.

Edit: https://myaccount.google.com/phone still shows my phone/number "On" with "verification in progress"

5rlyn

I've moved to "Connecting," Status Code 3000.
I'm afraid to try anything to speed the process along lol

connor112case

5rlyn Me and you are in the same boat, keep us posted on progress. 😬

5rlyn

connor112case I'm at least at "Trouble Verifying, Awaiting Retry." Status Code 3202, verification limit exceeded.

« Previous Page Next Page »