5rlyn That’s great, thanks for the response. Did you grant, Phone, SMS permissions to both Play Services and Google Messenger? It does sound like those are universally required.
Using RCS with Google Messages on GrapheneOS
I did, yes. Although some of the Play Services permissions were already in place so I could get google wallet to work (for Ticketmaster events, not payments)
I wanted to avoid using anything Google related, however, recently none of my immediate family members were getting any texts from me, or they would get my initial text (sms) but I would not get responses. After about two weeks, I am not sure but assuming it has to do with my family using iphones and all messages going through RCS to me (which on thier end would fail). I used the Graphene OS apps to install Google Play services, I did not sign into my Google account and even my G profile (from my computer) does not have my phone number. I have had 2 weeks now of using Google messages with RCS, not signed into Google and Google store is enabled but no permissions are set. Google Play services only has Network permission, everything else is denied. I would really love to NOT use Google Messages just to get RCS working, but for now this works. Also, just to confirm, when I got to my work computer and check my Google devices (my company I work for uses their services) and check My Devices, it only shows my home computer (Linux based) and no other devices. So to summarize, I have done:
Installed Google Play / Play services through Apps
Did not sign into Google account
Google Play store - all permissions denied
Google Play Services - Network is the only permission enabled.
Hopefully this helps someone. I DO NOT have Carrier Services installed and I am on Tmobile USA.
Renewably3997 5rlyn
I am on MM as well, but I cannot get my number to verify. I've tried with and without carrier services as well.
I made sure that Messages, G-Play Services, and G-Play Store had permissions to Network, Phone, and SMS. That did not work, so I added permissions for Contacts (with and without scopes), and with and without Call Logs for G-Play Services.
I tried all those combos with Carrier Services as well.
With every different iteration of adjusted permissions, I started without Messages uninstalled, then I set all permissions prior to downloading Messages, and then set Messages permissions before opening it and doing the rest of setup.
Still, my phone number will never verify. I did make sure RCS turned off before I stared (I have never activated it anyway).
Can one, or both of you, please confirm the exact permissions you have allowed for:
Messages
g-play services
g-play store
carrier services, if you're using it
Also, how quickly did your phone number verify?
Maybe I'll try one more time, then I'm just going to give up.
Thank you!
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?
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.