• Off Topic

  • Using RCS with Google Messages on GrapheneOS

6 days later

Sad, I just refuse to have GPS installed on my main profile or have it exposed to my texts

    graphosor Agreed. I also don't like the idea of google getting access to your contacts, which I presume (?) would allow them to figure out who you are.

        Bootlace1170
        I think it's needed beacuse a part of the RCS standard talks about checking if the recipients number is also using RCS. I will have to check on this as they can get your SMS conversations and numbers with the SMS permissions.

        It might just be add contact pictures and other info locally ,

        Now if they are sending that data of device I can not say as I don't know

          9 days later

          For the people that have it working:

          1. What's that minimum amount of permissions you need to give to Google to get RCS to work, across all necessary apps?
          2. Does it need to be on the owner profile?
          3. Can you have SMS messages go to other profiles as well or would that mess it up? If you can, which SMS app should I use since Google messages won't work on a profile without play services?
          4. Do you need to be logged into a Google account?
          5. Will I have problems with Verizon (US Mobile)?

          I'm trying to see if it's worth trying to get Google Messages. RCS is far superior to SMS/MMS and offers encryption with other Android users. But if I have to hand over too much data to Google to get it to work, it may not be worth it.

          Is it possible to use RCS on a work profile or is this only working on owner profiles? Also does anyone use Google phone and does it improve call quality over the standard graphene phone app?

          20 days later

          I'm stuck at "setting up" and verifying the phone number in the RCS settings.

          1) Is there a source of truth for instructions to get RCS working? The instructions seem to be all over the place in this thread. I don't know what the latest is.

          2) is it possible to set up RCS on a user profile or only the owner profile (or both)?

          3) Are the any known problems getting RCS working on Verizon (in the US)? I saw some point fingers at Verizon in another thread but it wasn't confirmed.

            This is an incredibly long thread. I feel if someone
            really needs RCS, it might be better just to move back to stock.

              I just got it working after my previous post. To get RCS working I followed steps in this thread. The last thing I tried that made it work was enabling the "read_device_identifiers" permissions for Google Messages app via adb. Right after, I disabled usb debugging. I'm on Verizon.

              I couldn't get it working on a different user profile though. Anyone get it working on a different profile that's not owner?

                glare8217 I believe it's an OS limitation that messaging can only be accessed from the Owner profile, but I don't use multiple profiles so I can't confirm this personally.

                And yeah, READ_DEVICE_IDENTIFIERS is what made it connect immediately for me.

                    hemlockiv I can text (sms / mms) fine from both a user profile and the owner profile. It's just enabling RCS on a user profile. I wonder if it'd be different with an eSIM vs a physical one.

                      7 days later

                      Cold_Beer This is an incredibly long thread. I feel if someone
                      really needs RCS, it might be better just to move back to stock.

                      No need for that.

                      glare8217 1) Is there a source of truth for instructions to get RCS working? The instructions seem to be all over the place in this thread. I don't know what the latest is.

                      Yes see @chenxiaolong's post https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/352

                      No doubt you needed:

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

                      I haven't tried on anything but the owner profile.

                            Maybe a bit off topic question but, for all the hassle to set this up, what is there to gain?
                            According to Google to get E2E encryption you need:

                            • both parties using Google Messages app
                            • both parties having RCS enabled
                            • both parties having access to network via mobie data or Wi-Fi

                            At that point isn't it more reliable to just use another communicator alltogether? I know few people use Signal but pretty much everyone uses WhatsApp from where I come from.

                              Byku Yes, Whatsapp is pretty much the default here, even with iphone users. Compared to RCS, I’m curious as to which would be considered the most “private”.

                                Byku

                                Once iPhone adopts, RCS in IOS 18 , and encryption is standardized It should be a suitable replacement to have on every device. The biggest draw is that the user doesn't have to install a new piece of software. It can be integrated right into the operating system, And have support by the telecom carriers.

                                    OfflinePuffin Yes that does sound good. Although I think one of the reasons people use Whatsapp over imessage is because it can handle bigger file sizes with photos and videos. Or so I’ve been told. I just use it mostly to message.