SirBlain Only three days? That seems normal. I'm on Visible as well. Longest I had it stay connected was a week. Finally gave up on it. Seems unlikely to get fixed at this rate, but who knows.
Using RCS with Google Messages on GrapheneOS
Looks like this issue (with a generic reference to "custom ROMs" rather than GrapheneOS specifically) is getting some coverage: https://9to5google.com/2024/02/29/google-messages-rcs-rooted/. Not sure how well-researched the article is but curious if people thought this is off-base or some consensus emerging around a new restrictive approach that Google's taking.
Gramsci ugh, I have been wondering about this for a few weeks now. It does seem like Google is trying to tie RCS to hardware in a way that graphene prevents. Well I don't understand all of the technical details, it is a little understandable from the point of view of wanting to have absolute control over a device/person and wanting to prevent spoofing.
It's an uphill battle, but it's going to push me further towards third party E2EE options, and I'll just have to deal with getting my friends onto those platforms.
I suppose the other approach is that somebody could come up with a way to implement RCS outside of Google messages. I know that's been a very rocky situation.
- Edited
I am on the latest Stable release of GrapheneOS (can't find version number), and have had issues with RCS in early January, but it's been working for a few weeks. Might be whatever change that breaks RCS hasn't hit Stable yet? I have Google Play installed (in the sandbox) for what it's worth.
Is it working for anyone else? I imagine most of those for whom it's working won't be checking this forum...
I've successfully setup rcs.
First time it wouldn't read any section within the RCS (this device is not supported or something like this).
Then removed the app, and re-installed it (no need for Carrier for me), and gave the minimal permissions (phone, network, sms + out of convenience also for Contacts).
For Play services + GSF + Play store = only network (no phone permission)
Took the settings to use rcS without google account.
Registered within 3-5 minutes maybe.
Used LTE during registration, dc/ed from wifi.
They're likely trying to crack down on spam. They may be using the Play Integrity API failing to pass as a spam signal. Play Integrity API is unfortunately inherently anti-competitive. The correct way to approach this would be using hardware attestation, not a trivially bypassed approach. Hardware attestation supports permitting specific alternate operating systems. The reasonable way for Play Integrity API to work would be solely using hardware attestation and permitting alternate operating systems preserving the security model regardless of whether they follow an extremely arbitrary list of non-security-related rules which are often counter to the goal of privacy and security. It's unlikely Google will do this on their own, but they could be forced to do it by a regulator.
Still working.
But recently checking out the mobile contract I have, it also says RCS-Chats.
RCS started working again today. I don't know why.
I use airplane mode often (which deregisters RCS after some time), and I like to enable the option to block connection without VPN (which seems to block the connection and eventually will deregister RCS as well). Unless there is a clear fix for this, I am giving RCS a break.
GrapheneOS Are we to understand this comment to mean that RCS is not expected to reliably work in GrapheneOS until Google changes (or is forced to change) their ways? And consequently, everyone posting their "been working for 2 days" / "doesn't work" / "worked for three weeks!" Etc is an ambiguous and misleading waste of time?
That's how I'm understanding it honestly. I've stopped trying to reactivate until there's some update workaround from GrapheneOS or Google
thed0ctor We can't work around services requiring Google certification via Play Integrity API.
vcavallo They may stop messing around with intermittently blocking non-Google-certified operating systems in which case it should work perfectly without repeated failures.
RCS just connected this morning out of the blue. I didn't do anything on my end. Let's see how long it lasts.
Just came here to say I've been using Google's messenger app in hopes of using RCS, but after months stuck on "verifying phone number" I kinda doubt it will ever work
Mines working just fine on Google Fi.
I was on the same phone and phone number when I switched to GOS, I wonder if that makes difference? I don't think I had to activate it again after installing GOS.
- Edited
FlipSid I had to download over mobile data (n o t wifi) and have the VPN deactivated.
Otherwise it would not work.
From Play store. Version now is:
20240123_01
- What exactly did you "download over mobile data"?
- What carrier are you on?
- Did you also do the steps of downloading the old beta version, edit the ACS config, and then update? Or did you just install the latest version of the app?
SirBlain I turned off WiFi since it seemed more people got verified using cellular data.
I uninstalled current Messages version.
Installed version: messages.android_20220131_05_RC00.phone.opebeta_dynamic
Opened, gave network permission, set as default, opted into RCS I think they called it dynamic messaging.
After that I got the standard "connecting" in the RCS menu. It would either sit on "connecting" or "trying to verify" for weeks regardless of what version I tried.
Sidenote: xyzzy debug enabler would immediately disable in this version.
Went to App Info menu for Messages, clicked 'force stop', went back to Messages and my number was now verified and connected, for the first time in months.
Upgraded through store to latest version, and I am still verified.
I should mention, I tried almost every method available before this. So I am surprised my simple method worked. I tried the debug menu tricks but could never get a version installed that would give me the ACS menu to manually insert a link for my carrier to activate RCS.
It has now been three days, I'll keep my eye on it.
- Is it still working for you?
- Where did you download
messages.android_20220131_05_RC00.phone.opebeta_dynamic
from? - "xyzzy debug enabler would immediately disable" What do you mean by this?
- What carrier are you on?