tripop
Damn it worked. Finally. Thanks mate. Creating an account just for this. Can I now :
- disallow the read device identifiers permission to Play services
- Disable wireless debugging
- Uninstall Shizuku
- Uninstall apps ops
Thanks
tripop
Damn it worked. Finally. Thanks mate. Creating an account just for this. Can I now :
For people that got this to work (for however long that may be), what's your profile setup? Given how many permissions you need to hand over, it probably makes sense to keep this in its own dedicated profile with other intrusive Google apps.
Do you share SMS with other profiles? If I install another SMS client on another profile, will it mess up RCS in the google profile? Will my RCS messages appear in the other SMS apps?
My RCS was working just fine for a long time on Google Messages Beta with Carrier Services Beta installed. Until today, when i had constant pop ups that my messages may not have been received because the other person appears offline. Trying to rectify this situation, assuming it was a bug in a beta update, I uninstalled the beta and installed the most recent stable version from the play store. Now it doesn't give me the RCS toggle option and instead says that RCS is not available for my device. I think they've killed it with the Play attestation as mentioned above. Bummer.
eatinggrumble84 its still working for me. If you're using Google Messages while logged in, try doing this first:
Confirm all Sandboxed Google Framework and Google Play Services are installed on that profile. Make sure play services has access to at least Network, SMS, Notifications.
Install the actual Google app from the Play Store if not installed already. Give it access to at least Network , SMS, Notifications.
For Google Messages, give it at least Network, SMS. notifications. I also gave it access to contacts and phone, but it may not be necessary. You may need to reinstall the app if it's not letting you try to verify.
I do not have Google's carrier services app installed.
After doing everything above, close google messages (to be on the safe side). Open the Settings app on your phone. Go to:
-> Apps
-> Sandboxed Google Play
-> Google Settings
-> All Services tab (for the google account you're using with Messages)
-> Mobile data & messaging
-> Phone Number Verification
Toggle Automatically Verify Phone Number (s) to on.
Afterwards, re-open Google Messages and go to the RCS section of settings. It may already say connected or try to verify again and see if it connects this time.
Hope this helps!
I appreciate the help. I believe my issue was related to outdated Google Play Services. A couple apps had difficulty showing maps, indefinitely stuck on a screen showing "Google Play Services Updating...". After updating GrapheneOS today to 2024060500, my RCS enabled itself immediately and I've had no further issues.
Reading through peoples problems makes me appreciate my experience.
The various Play services have their settings as per initial instructions from original GOS install.
I downloaded the google messenger for RCS.
I had to go to the sim settings to make sure my number was set.
I then went to GM wherein I entered my number and had to "verify". A couple of hours later, all connected.
It has now been over month, without any issue from the start. Yet when I tried to invoke it on my Xiaomi, it took a couple of weeks even though it was the same network. I think the sim settings and number recognition are important, especially if you have recently ported your number
I'm not crazy about using Google's Messages app for texting, but my threat model is low and with iMessage implementing RCS the Apple Fanboys in the family will only become more resistant to using Signal.
It appears as though RCS is working for me on Mint Mobile, though it remains to be seen if I'll disconnect after a few days. Is there anything definitive Privacy wise I need to do if I'm going to use the app as my primary SMS/MMS/RCS?
Sbpr
This menthod worked for me. The Google app must be used to pull down a config or verify something about the device. I was able to keep my connection to googles RCS network after deleting the Google app. Hopfully its not needed to keep RCS enabled
OfflinePuffin Did this work on the newest version of messages?
I've been using Messages for about a week...thus far, my Mint Mobile eSim hasn't lost connection to RCS (knock on wood). I did not download the Google app beforehand to activate, but I did disconnect from VPN and WiFi during the initial activation.
So far working well, I don't really like using Google's Messages app but my family won't download Signal and I'm sick of the iPhone users complaining about texting Android users.
5rlyn with unlimited texts as part of a normal deal, how is messaging any better sending a text?
Are people so desperate to have instant proof I've ignored their message?
RCS has a lot of advantages over sms like advance message features.
Also if you messaging another android user your chats are encrypted (thankyou you google). Also the RCS standard also can support crossplatform video calls, better group messaging and much more if implemented
Hey matchbox since there is a solution can we pin it somehow to the top of this thread? Or have a Current way to enable RCS topic pinned to the fourm?
Can someone leave a post here that explains in detail exactly what one needs to do?
About 2 weeks ago I was running stock Google with root and Google decided it's perfectly fine to block messages and some calls. You can read about multiple people having that issue on xda. That is not OK, who knows what that call or message may have been about, how important it might be. Messages used to fallback to standard sms/mms which you'd at least get them. My advice, get far away from Google and stay there.
PaulDavis actually I've got a brother who is very very busy and very very bad at responding, so it does help to know if he's seen a message or not.
I also have nieces, and when a video of them is sent via SMS, it looks pixelated and crappy. When sent via Signal/RCS/Imessage, the compression and loss is lessened.
I used this method linked above