• Off Topic

  • Using RCS with Google Messages on GrapheneOS

If this issue is completely carrier dependant, with some carriers needing access to the IMEI to work at all, some needing it to work reliably, but also some not needing access to the IMEI at all, I think it would be really useful if everyone reading this thread (who uses Google messages) would also report if they have had no issues at all, and what carrier they use.

Obviously people are already reporting when they have had issues but it might be useful for people to know if there are any carriers that are friendly to GrapheneOS (without needing to give device identifiers / IMEI) as I bet there are people who would switch simply on that basis.

Personally I just use a data sim and don't use RCS yet, however my friend uses GOS and Google Messages and they are pretty sure they've never had issues and haven't had to give access to IMEI.

They are on o2 (in the UK)

When I have a chance I might grab some other SIMs and test them out with RCS support, each for a month or so, and report back for anyone reading this thread who is in the UK.

    FirstNet / AT&T - Had to enable identifiers per the AppOps process before Google Messages would allow RCS.

      roamer4223

      Good idea.

      As I said above, RCS worked instantly on a Graphene device using a T-Mobile MVNO in the US. Same device on Verizon, it's stuck on verification.

        dcc The steps are around comment 317ish.

        • dcc replied to this.
        • dcc likes this.

            NightSky

            I just used adb to give permissions to Messages actually to Play Services~:

            $ adb shell appops set com.google.android.gms READ_DEVICE_IDENTIFIERS allow

            Check if it worked:

            $ adb shell appops get com.google.android.gms | grep READ_DEVICE_IDENTIFIER
READ_DEVICE_IDENTIFIERS: allow; rejectTime=+26m54s324ms ago

            It didn't make RCS work though.

            Per the message you are talking about, it looks like I need to give them to Play Services. I don't know how to do that with adb - I'll play around a bit.
            https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/343

            EDIT: looks like that's what I did, actually.
            com.google.android.gms = Play Services. Right?

              Hi All,

              I am facing similar issues, RCS activates fine, however when I try to initiate a chat with any contact (who I know RCS works with) it just says SMS.
              It works on stock OS just not GOS, which is a shame, did anyone ever find a way around this?

              Thanks

                NightSky No, they are a samsung user, and I know their RCS is working because it works on stock :)

                  epileptic055

                  Try reinstalling your client But first, deregister your number with Google messages and re-register it with them, By Enabling RCS On the re-install client.

                    15 days later

                    I haven't had any luck getting this to work with US Mobile Verizon gets stuck in verifying. I gave it permissions modified the additional permission for play services with app opps and tried installing the google app for phone number verification. I did see this article not sure if it explains what I am seeing. Right now I could switch back to Tmobile or move to at&t since US Mobile allows you to move carriers. Has anyone had better luck with at&t or Tmobile recently?
                    https://www.androidauthority.com/p-3421652/

                      I had my RCS stop on US AT&T about a week or two ago. Gave play and messages all the permissions back, cleared the cache for all the apps, cleared data for messages, added my number back in message settings advanced and rebooted. I forked around with it for a bit but it re-verified after the 2nd or 3rd reboot.

                      inquisitorStutzz

                      You could switch carriers but I would first turn off RCS in messages, deregister your number with Google for RCS them re download the messages app allow permissions and retry RCS. You seem like from your post you have everything set up , so I would try what mentioned and let it cook for a bit

                        epileptic055 I'm having the same issue. I've done ALL the steps above, granting all the permissions including Read Device Identifiers, tried uninstalling/deleting appdata for messaging and all the google apps, restarting, redoing the whole process, multiple times.

                        Messages setting says RCS is Connected, but it still only let's me send SMS to contacts I know have (stock) Pixels with working RCS. Even checking RCS Connection State in the app's Debug menu (enable it by typing *xyzzy* in the Messages search box) shows it as connected, with the correct ACS url and everything. I'm really at a loss of what else to try...

                          OfflinePuffin Thanks I unregistered and put my number in the website from the disable-chat. I think uninstalled the messages app and re-installed it and RCS was enabled. I tested with my samsung phone RCS appears to be working. I removed carrier services and using app ops set most of the play services to ignore and everything seems to be working.

                            I didn't need to give Play Services more privileged access to get RCS to work. I guess it is because my carrier has native support. A bit ironic because they don't support VoLTE/WoWiFi on Pixel phones yet.

                            I don't want to give Google more data, but I also think SMS should be deprecated and every messaging app should be compatible with RCS even if they prioritize their own implementation (similar to iMessage).

                            • IHD likes this.