• Off Topic

  • Using RCS with Google Messages on GrapheneOS

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.

    yaomtc Well 2 days after posting this RCS stopped working for me again. It now says "Setting up... Trying to verify [my phone number]". I guess the changes to Messages/Google RCS were being rolled out gradually.

      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.

        11 days later

        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

              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.

                FlipSid still working. Just posting follow ups for reference.
                Have you guys checkt with your carrier?
                Mine excitedly states >RCS Chats<

                  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.

                  5 days later

                  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

                  1. What exactly did you "download over mobile data"?
                  2. What carrier are you on?
                  3. 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.

                  1. Is it still working for you?
                  2. Where did you download messages.android_20220131_05_RC00.phone.opebeta_dynamic from?
                  3. "xyzzy debug enabler would immediately disable" What do you mean by this?
                  4. What carrier are you on?

                        hemlockiv
                        Download from Google Playstore, VPN off, with Mobile Data (not over Wi-fi).
                        Carrier would not help you, unless you are in Germany?

                          hemlockiv
                          I really don't care too much about RCS unless it starts encrypting messages between iPhone and Android. I do like doing some minimal tinkering to try to get things to work though. I just cleared the cache on the Carrier Communications App, forced stopped it, restarted my device and turned on RCS. It took about 5 minutes to activate. T-Mobile with latest release of messages.

                            Hi everyone, new user here, but I got RCS to work. If you haven't already, try going into the settings for sandbox Google play services and give Google permission to automatically verify your phone number. As soon as I did this, RCS started working. I also have all 3 sandbox Google services installed, I'm logged in, i installed carrier services from the play store, and gave many recommended permissions to google play services and google messages. But i have a feeling the automatic number verification was the big one and may start removing permissions until something breaks.

                            Open settings - Apps - Sandboxed Google Play - Google Settings (logged in) - All Services (tab) - Mobile Data & Messaging - Phone Number Verification, and then toggle Automatically Verify Phone Number(s)

                            You may be able to untoggle it afterwards and get it to still work, not sure. But hopefully this helps people who just want RCS to work in Google messages. Part of me thinks the varied responses of people saying it works and others saying it doesn't work (or stopped working) despite similar permissions is because some people verified their number with Google and others didn't.

                            If anyone wants to play around to see what the minimal permissions and configurations are while still getting it to work with this, that would be super helpful.

                              Sbpr
                              The only permission I have for Play Services is Network. Haven't changed it before activating or after. For Messages everything except Location, the two storage permissions and sensors are allowed