• Off Topic
  • Using RCS with Google Messages on GrapheneOS

  • [deleted]

I don't know for Macarena5429 and N3rdTek but pressing on the vendor or phone number or whatever line does not do anything.
Before your message, I had juste abandoned.
Now I have exhausted my maximum number of validation attempts

    Apologies, was not trying to screw up anyone's validation attempts - just wrote what worked for me.

    Good luck !

      • [deleted]

      • Edited

      billinmtl

      Relax ! Bot your fault. It already happend to me to exhaust my number of attempts. Then you just have to wait one day to retry
      Thanks you for thé advise

      [deleted]
      I see no line. I see a toggle to turn off RCS however.

      As it is, I think some change in GrapheneOS has messed up RCS for Google messages. I have deregistered my number using Google's online form, which did send me a code. After submitting, and turning off for a couple days, I still encounter issues verifing. It simply won't.

      Funny thing tho is I can tell the app is functioning and downloading additional content in the background. I watched the text field box change orientation, placement, even the whole design. It seems also Google messages now has support for photomoji, or basically got react to messages with your own picture which becomes cropped and lifted out of the image submitted and used as a tiny emoji

      BUT STILL NO RCS

      I now have reason to believe SOMETHING has changed within the OS to cause all these RCS issues.

      I just got done re-downloading my SIM from my carrier. Everything seems to function and operate basically the same from before I deleted the SIM and redownloaded, however they confirmed not only do they not have RCS rolled out or implemented, I asked them if they have heard any other such problems of subscribers trying to get their devices activated and/or verified. They informed me that I am more or less the only person that has been experiencing this within a while they didn't give a time frame but I'm assuming over last 6 months as they stated that was their personal belief based on experience.

      Now I have read and understand that the verification process can take anywhere from 24 to 48 hours although that is quite rare, I'll go ahead and leave RCS on for now and I will report back in 2 days but I have very little faith as I've tried practically everything and I'm seeing this issue spreading faster and faster at least within our community that is.

        I've been having this problem (suddenly became unregistered and can't re-register) for five days or so now. I've tried every guide and advice out there, even went through the Google Messages debug menu to forcibly unregister and try to re-register. Nothing works.

        Similar issue here. I had RCS disabled for a while since I was skeptical of Google Messages, but I decided the pros outweigh the cons. When I tried to enable it, it refused to activate and I've tried basically everything suggested online. I'm currently trying to wait two weeks with RCS deactivated; I'll report back on the 29th.

        5 days later

        just install google messages and already enjoying the full feature aspect of messaging.

        not sure about the RCS and dont really care. just want a modern texting experience.

          The rcs doesn't work for me either.

          N3rdTek I now have reason to believe SOMETHING has changed within the OS to cause all these RCS issues.

          The Google RCS implementation entirely relies upon Google apps and services. The OS has little to do with RCS it is all done by the apps. It is far more likely the change that broke this for you happened somewhere other than in the OS.

          As this does not appear to be hitting everyone there must be something common with the people encountering this issue.

          It could be that some dynamite modules need to be downloaded into Messages. Do you have network granted to all three Google Play apps? If one of them has it it does not make much sense to deny it to the others. Play Store updates dynamite modules.

          It could be something related to your carrier. Have you tried installing the Carrier Services app ?https://play.google.com/store/apps/details?id=com.google.android.ims&hl=en_US&gl=US

          Do you have DNS filtering that could be blocking a critical connection? If so you could try disabling that.

            jufstp i am referring to the app. every other 3rd party app seems hacky or limited etc.

            Carlos-Anso Hello, I just reinstalled Android stock to test if RCS works, and well they activated immediately. I don't know if it's a problem with grapheneos but it's something to look into.

              jufstp In stock Pixel OS, the Google apps are configured to work fully with all their functionality out of the box. In GrapheneOS they have to be manually installed and configured with the necessary permissions to give the required functionality.

                I wonder if it could be the cellular provider causing the issue. I've installed the three google apps and the messages app and RCS is active after a minute or two. Turn RCS off, turn it back on and it is active again within a minute or two. I delete all the apps from GOS, restart phone then reinstall and start over - RCS activates.

                I did a factory reset on my GOS Pixel 7A and then proceeded to start from scratch and again RCS activated within minutes.

                The three Google apps from GOS apps app, messages and minimal permissions and RCS works.

                It's the weirdest thing reading all the issues with other GOS users

                  billinmtl Which apps (Google) did you install? Are any of those apps beta versions? What permissions do they have? Was it activated on Wi-Fi or cellular data? Did you have to add your number to the app to verify, or did it show up without the need to? Did you navigate away from the verification screen before it was complete? Are you on any VPN (on device or otherwise)? Any DNS settings applied (on the device or otherwise)?