• Off Topic

  • Using RCS with Google Messages on GrapheneOS

naibed NetRunner88 @Renewably3997 @5rlyn
For all you Mint Mobile folks, I was able to get mine to work as follows:

Use the this post (or thereabouts) to set READ_DEVICE_IDENTIFIERS for G-Play Services (com.google.android.gms).

Once that's done, set SMS and Phone permissions for G-Play Services and G-Play Store.
Download Messages, and set permissions for SMS and Phone, and whatever else makes sense for you.
Open Messages and go through setup.

At this point, RCS, was checked "on", but it wasn't really, so then I went into Settings > Apps and force closed and cleared cache for Messages, GP Services, GP Store.

Opened up Messages and check settings and it had the message that RCS was not available for this device. I restarted the device, and opened up Messages, and immediately received a text noting RCS was being setup, and it was done. RCS is now working, and confirmed with a message to an iPhone user on iOS 18.

I did NOT need Carrier Services.

Though I dislike using google services, I figured there is a balance here between encrypted message with too much metadata that can't be read, vs plain text chilling on MM (or other carrier's) systems.

Cheers.

        Oh, WiFi off so it was only using mobile/carrier services.

        naibed

        You have to install the Google Play version of Google Messages.

        Use the APN settings from your sim

        Make sure you enter your phone number in corrsponding messages setting before you set up RCS.

          OfflinePuffin
          Tried a lot of different ways, and until I did the ADB command to allow READ_DEVICE_IDENTIFIERS.
          ¯\(ツ)/¯

            Just wanted to chime in here with the results of some experimentation. I have a Pixel 8a on Graphene with a US Mobile eSIM on their Verizon network. I managed to use the AppOps method to get RCS working, after much bashing of head against the wall. This comment was the approach I used (it required granting Play Services access to device identifiers). RCS disconnected after a few weeks.

            I had seen some additional comments that suggested the device identifier requirement was Verizon-specific, so I switched my network to T-Mobile this morning (US Mobile allows you to switch between the big 3). RCS activated almost immediately without any problems and no access to device IDs.

            Bottom line - if you're on Verizon it's a hassle right now without granting Play Services the READ_DEVICE_IDENTIFIER permission via AppOps or ADB, as I think others have discovered. T-Mobile seems to work okay without that permission (though Google Messages still requires the identifiers, it seems). Just thought I'd chime in with my two cents.

              Got mines working yesterday. I think there's too many moving variables to be sure what was the definitive setup in getting it working. I used Messages from Aurora Store and tried the ADB fix but nothing changed initially. Played around and rebooted a few more times, then the results 'took' when I was tried clicking the verify my # button while connected to mobile data instead of wifi.

              If this helps anyone, I got RCS to work by turning off WiFi and using only cell data (I use T-Mobile btw), then make sure you turn off your vpn on your phone if you are using one. Then you can go to Message Settings > RCS Chats, and you'll see that it's connecting.

              Other than that, I installed Play Services., Play Store, and Carrier Services with access to Network, SMS, and Phone enabled. I assume you don't need some of these permissions enabled but this worked for me.

              job_shredder69

              I am not sure about that but I don't recall it working on another profile when I tested it so I would say no

                grittytea Bottom line - if you're on Verizon it's a hassle right now without granting Play Services the READ_DEVICE_IDENTIFIER permission via AppOps or ADB

                I dont think that's correct as I'm on Verizon and did not have to do that; I didnt have to do anything special - installed GOS on P9Pro XL, installed G dependencies, granted permissions it asked for, installed G messages - RCS activated immediately and has been on ever since (couple of months)

                  grittytea I have been using RCS on 8Pro Verizon with no issues. No special permissions, or work around needed. Only stops working when revoking network permission from messages app. Your situation seems to be isolated and nothing to do with Verizon.

                    Anyone know if you have to have Google Messages set up on the owner profile for it to work? I can only get close to have it working on the owner profile. The other user profiles do not seem to work at all for RCS support.

                    has anyone had a decline in the ability to send messages via browser recently? I use the QR code to text via computer, but lately, I often have to unlock my phone and open the Messages app to send/receive new messages.

                    It's as if the connection breaks and I have to re-engage it.

                    Bobby679

                    I am not sure, as when I tested it a long time ago it would not. I would suggest making sure Google messages is on both profiles and registing on the owner profile. Try to run it on the secondary profile...

                    Or you can register on the owner profile and then register Beepers RCS Bridge and push the beeper app to the secondary profile and log in. You would just have to turn off notification for Google messages on the owner profile

                        FYI, the new beta version of messages is offering me dual sim registration now. Both are still "setting up" status for me, but maybe dual sim RCS will work for others?