there is a RCS system file, what's it purpose? can I use the GOS default message app for RCS?. if not, is there any 3rd party msg app that can be used besides google msg app?
Using RCS with Google Messages on GrapheneOS
tomz
You cannot use the built in messaging app for RCS. I think the Google app is the only one at the moment, or at minimum it's the best and most feature rich.
Google messages is the only RCS app that is Interoperable at the moment. Messages improve might be, but they haven't updated They're app since September 2023.
If your in Japan you should have an RCS app call Messages plus, I believe?
I think the system file hold config data
- Edited
jeffcodes
Did you enable the permission regarding READ_DEVICE_IDENTIFIERS with adb ?
NetRunner88
That's is the only thing I haven't done. I'll have to go back through previous posts and remind myself which apps need it. Just G-Play Services, or Play Store too? I don't recall. I'll try sometime this weekend.
- Edited
Trying this out myself. Mint Mobile user. Still in limbo ATM:
- Installed messages through Aurora Store (no SB Play Store login, but I add add SMS permissions across the board)
- Initially was getting an "RCS chats aren't available for this device" message.
- Updated my APN settings & disabled RCS chats manually via the 'disable rcs' webpage. (I did this before I wiped my Pixel, but I guess it didn't take?) After 1-2 restarts, RCS became a toggle-able option
- Currently stuck on 'Setting Up...Trying to verify your number...' for about 20-30 minutes.
There's an option on the page: 'Verify your number' which allows me to put in my phone #, but the fine print suggests it just speeds up the process. I will try that in 2 hours if nothing changes but I would prefer not to give that info is possible.
Also, for those troubleshooting, search is wonky on the thread, and even Ctrl + F is imperfect, so use something like this to search for keywords. (Tried something other than Google but the thread wasn't properly indexed)
- Edited
naibed
I tried the restarts and updating APN via MM instructions. Oddly enough, when I was trying to get RCS going, MM sent me a texts suggesting updating APN if I was having trouble with MMS and sending pictures.
¯\(ツ)/¯
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.
- Edited
Oh, WiFi off so it was only using mobile/carrier services.
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.
jeffcodes I have been able to get this working without using ADB.
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.
Will RCS work in private space?
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.
- Edited
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
OfflinePuffin We do have that app in Japan, but each person needs to have it installed, and even then it's not the most reliable.
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)