Using RCS with Google Messages on GrapheneOS

Heisenburgh

Attempted version 262366063 and I am back to square one of "verifying phone number"

BuckWylde

As of today I'm having trouble doing the "every other day" fix with version 262371063. It's stalling at Trying to verify. I also tried version 262366063 with the same results. Such a bummer.

Heisenburgh

Back on current version installed from play store

Failed after a couple attempts to verify error code 4006: device does not meet security requirements

BuckWylde

I was just getting accustomed to doing the annoying fix every other day. Now we're back to zero ffs.

cb474

@headgear3896 @Buck Did you follow all the steps that @Vuraze outlines above?

When RCS stops working I uninstall Messages, reboot, installed the older APK again, make it the default SMS app, open Messages, RCS says connected but only SMS sends. I then reboot, update Messages via Play Store, check to see if I'm chatting in RCS and if not reboot again and wait a minute or two before chats switch to RCS.

I find after the last step of updating to the Play Store version that it usually takes more than one reboot, sometimes as many as four.

BuckWylde

cb474 Yep, that process was working for me until today. Once installing the old version no longer do I get to RCS being connected.

cb474

BuckWylde I had it fail the way you're describing once. I just started over from the beginning and got it working. Maybe try clearing storage on messages, then uninstalling it, then reboot, then install the old version and follow the procedure from there.

JavaTheHutt

cb474 I am using US Mobile with Verizon towers. I've barely heard of people having my issue, I've mostly heard of RCS just straight up not connecting

cb474

JavaTheHutt I don't know. If I were you I'd try to method @Vuraze describes and see if that gets RCS working.

cb474

MrRoboto1212 Funny you ping me, cause as of about 2 hrs ago, my RCS on v262366063 began working as of now (and it surprised me), so I will keep the thread updated on how long it functions.

I tried 262366063 today, when I had to do the whole reset process. But it never went to Etouffee true. I tried four reboots and waited around a while between them, but no dice. Then I updated to the Play Store version and after two reboots got it working. So this is the same as my experience with 262371063.

MrRoboto1212

cb474 This may sound dumb, but as long as RCS is working (for me currently), what exactly does Etouffee do? Is it to further secure your RCS messages?

MrRoboto1212

cb474 Oh, okay, I guess I could have checked mine before asking lol (it is set to true). My inputs fields have said 'RCS' instead of 'Text' for a bit now

cb474 But it never went to Etouffee true. I tried four reboots and waited around a while between them

My RCS never worked with 71063, but I waited it out while testing 66063 and it took 3 days to actually connect. I thought after that amount of time it would fail again like the others, but suddenly RCS began working after not checking the status for a full day. That's why I was surprised - I sent a message to someone and it was a dark color instead of grey

cb474

MrRoboto1212 If RCS is working then Etouffee is true. It's effectively just another way to check if RCS is working. In other words, when people get to that stage where RCS says "connected" in Messages' settings, but they are still unable to send and receive RCS messages, it's because Etouffee is not provisioned (not showing "true" in the debug menu). Both of those things have to be accomplished for RCS to work, "connected" and Etouffee "true."

I just find it more convenient to enable the debug menu and check if Etouffee is true, as a way to know that RCS is working, than looking around for a text thread that I know should be RCS and see if it says "RCS chat with...." Also, there is no way to tell in a group chat if it's working. Once RCS gets to connected, the text entry field in a group chat will say "RCS," but the only way to tell if it's working (other than checking Etouffee) is to send a message and see if it fails.

So checking Etouffee is just a more technical way to know that RCS is working.

ralm

MrRoboto1212 what exactly does Etouffee do?

It's the name of the RCS server. 'Etouffee provisioned: true' just means you're connected to it.

cb474

MrRoboto1212 My RCS never worked with 71063, but I waited it out while testing 66063 and it took 3 days to actually connect. I thought after that amount of time it would fail again like the others, but suddenly RCS began working after not checking the status for a full day. That's why I was surprised - I sent a message to someone and it was a dark color instead of grey

Once it started working on 66063, how long has it continued to work? Is it working beyond the 36 hour typical failure point?

MrRoboto1212

cb474 It is still functioning as of now

Judgeadam

Well it finally happened bois. My RCS stopped working and is falling back to SMS. I was more or less fine on Verizon for a few weeks and now it don't connect again. We are back to square one.

Am on latest GOS and messages. Any ideas what to try? Just wondering. This is starting to worry me. I can't believe RCS may tank using GOS. How are you guys doing with the latest update for those on Verizon? I did the whole install messages ver 2020804 etc then update. No dice.

Judgeadam

Judgeadam after latest GOS update now it says device not supported. Ugh. Back to this again. Oh well.

mousetrapreplica

Something has almost certainly changed with the way RCS is working, at least through my carrier, in the past 48 hours. On T-Mobile MVNO Mint Mobile.

I'd had 0 issues for weeks using the "workaround" of installing the old version sited often in this thread, rebooting a lot, upgrading the app after RCS connection. Yesterday I had intermittent RCS downgrades in different conversations. Today I cannot seem to get the "workaround" to work anymore despite many retries and lots of patience/waiting.

GrapheneOS

If you're on GmsCompatLib 101, try downgrading it to the version included in the OS via Settings > Apps using the menu at the top right for uninstalling updates in the app menu.

pfbangs

GrapheneOS

This worked. Rolled back, rebooted, cleared recently updated (official play build) GMess cache (not storage), relaunched, RCS sent successfully. Reply received. Confirmed working. (Thank you)

@GrapheneOS would/should this be the first TSing step should future builds see similar behavior?

BuckWylde

I can confirm that what GrapheneOS said works. I just got everything working again!

mousetrapreplica

GrapheneOS this worked. T-Mobile MVNO user. Thanks.

tRexDestroyer

GrapheneOS
This worked thank you. I'm using Google Fi

pfbangs

My original report here
https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/1071

Worked for whatever duration between now and the beta release the team referenced would fix it (it did).

I was removed from all RCS group chats from the original downtime (30 day GMess threshold, forced removal from all RCS group chats- I was offline for 32 days). Folks trying to re-add me to those groups simply created segmented/splintered conversations @ SMS/MMS (it was ugly). Other (iDevice) users creating new groups with me included also created splintered group comms across MMS/SMS. But when I created replacement RCS conversations/groups as the only Android user, all function worked. New group chats created slowly, as needed with family and friends, and worked until yesterday. Intentionally didn't create numerous new until at least some number of weeks went by providing some amount of confidence.

BETA gOS update installed yeterday (build #2025102301). Can't send RCS any more. RCS settings in GMess shows Verizon <phone number> Status: Connected. "Not sent" error on Send-- can resend as SMS. Really don't have the bandwidth/energy to give to this again. Will follow this and hope the thread/issue is re-opened. May need to make a decision I don't want to make re: security & user profile functionality vs reliable RCS function. I'm happy to deal with it, but involves many others who don't have related patience or knowledge of related.

GrapheneOS

pfbangs

would/should this be the first TSing step should future builds see similar behavior?

No, it was a one time issue because we didn't know updating GmsCompatLib out-of-band would be detected by Google Play as some kind of tampering occurring. It appears that it's detected by DroidGuard and other apps may also be detecting it either through Google Play or on their own. We'll need to avoid doing out-of-band GmsCompatLib updates unless we resolve this. That's quite unfortunate since it would be a nice way to quickly ship fixes for sandboxed Google Play compatibility layer issues including regressions caused by recent updates to their apps without needing to do an OS update. It would have been a good way to quickly fix compatibility issues with RCS in particular, but it seems we won't be able to use it without making changes to it.

« Previous Page Next Page »