- Edited
NightSky What is the App Ops process? I see it referenced but no explanation of what it is or what the steps are. Thanks!
Nevermind - looks like it's here: https://appops.rikka.app/guide/#what-is-appops-in-android
NightSky What is the App Ops process? I see it referenced but no explanation of what it is or what the steps are. Thanks!
Nevermind - looks like it's here: https://appops.rikka.app/guide/#what-is-appops-in-android
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.
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
epileptic055 if the other person is iOS, they have to update to iOS18 and enable RCS.
Wanted to post this link to Mint Mobile subreddit explaining the infrastructure and additional work needed to implement RCS. Looks to be no small thing, but once in place will provide the foundation to mature the service.
https://www.reddit.com/r/mintmobile/comments/1ffcq01/iphone_16_and_ios_18_compatibility_rcs_order_and/
NightSky No, they are a samsung user, and I know their RCS is working because it works on stock :)
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.
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.
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
https://messages.google.com/disable-chat
Here is the link for the deregistration process
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.
Has anyone gotten it working using a work profile?
Following this comment https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/348, when I open Shizuku, it just says "Shizuku is not running"
I've tried a few different things, but thinking it's wasteful to keep spending time on it if no one else has gotten RCS working in a work profile.
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).
Dealing with this a few months ago on my P8P when I could not get graphene to remain RCS registered.
I switched to a P9P on release and kept stock Google for about two weeks before switching to Graphene and it has been working flawlessly. I have play services and messages installed, but no other google applications. No carrier services. I am using Verizon. Play has access to calls/SMS/contacts/phone.
Interesting that using the same phone number, Google account, and carrier can work on one device but not another.
Did anyone else get deactivated about a week after upgrading to Android 15?
I have not can you reactivate? If you do a fresh-install of messages