• Off Topic

  • Using RCS with Google Messages on GrapheneOS

Macarena5429 It would occasionally drop back to SMS in the past, and take a few hours to a day to re-verify. But this time it's been stuck verifying to the better part of a week.

It's not just me I knew I wasn't going crazy!!
SMS is fine, I can't remember what I did to enable the first time but trying to get it back on lately is impossible! So far I've tried just about everything from:

  • play with APN settings
  • reset network settings
  • toggle airplane then reboot
  • cleared cache from Carrier Services & RCS Services in app settings
  • cleared Google Play services cache
  • cleared Google framework cache
  • toggle LTE only then reboot

I'm about to go nuclear and completely remove & re-install Google & related services from the Apps app. After that only thing left I think is to factory reset.
In theory another user profile might work due to how new user profile configuration is implemented ; another fresh, never used before profile could theoretically rule out factory reset.
But I'm not familiar with the deeper access Google Messages/RCS requires or that a user profile is even permitted to allow access to.

      • [deleted]

      • Post #69

      N3rdTek

      Don't do it ! Already tried to reset the phone and it changed nothing

        Just an FYI, ran into the same issue with status:"setting up". What I did was click/press on the line above that message. The line that shows the vendor and phone number. The message changed immediately to status: connected

        • [deleted]

        • Post #71

        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]

                • Post #73
                • 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.