Syberkonda @Ninja4694 try this out.
Using RCS with Google Messages on GrapheneOS
- Edited
N3rdTek Thanks, this helped me figure out that the ACS URL is not received for some reason. So dropping to an earlier version and manually entering the ACS URL for my provider. I asked someone, who is already connected with our carrier, by using the xyzzy + enter method and under debug, RCS, Report RCS Connection State, and made a note of the ACS URL. From there, and using an old Google Messages version, I manually added the ACS URL through Activity Launcher.
bluesl33ves perhaps I misunderstanding but your post seems a little unclear, are you confirming that it now works after trying the suggestions?
N3rdTek It would seem so.
- Edited
ErnestThornhill fantastic! It seems we are finally beginning to make some headway with all of this. I had a feeling it couldn't be just graphene despite some of my posts, but this now just raises so many other questions like how has Google let it come this far and put no notices or made no changes? Why must we fiddle with developer options and install apps from the third party vendors that could contain who knows what? Why are they not informing carriers? why are carriers not informing customers? And furthermore why do kids love the taste of cinnamon toast crunch?!!?
Ahem, sorry I got a bit carried away... Where was I?
Even though I am on stock and I have had no issues getting RCS enabled, I still run the exact same apps with the exact same setup, I just now turned on both my VPN and my DNS which is next DNS. I expect errors could arise later as it attempts to phone home, but after enabling I have noticed no issues and everything continues to function as intended. I checked my ACS, and it matches what was listed.
Hopefully someone on the developer team or even Google themselves would be able to shed some more light on this as it is quite quite strange
I do not think it is Google's fault, at least not entirely. On stock OS', with the carriers here, almost everyone has RCS enabled and didn't even know it. When I was on stock Android 14, it only connected when I verified my number.
There seems to be something stopping the ACS URL from populating behind the scenes. This could be a block by the OS and/or the carrier failing to push the settings out when the device requests. The latter doesn't seem likely when there are so many individuals connected without challenge.
When I used the older version of Messages, I still had to use the Activity Launcher to manually enter the carrier ACS URL; it didn't populate on its own. Only then did the app ask me for my number, like Telegram or WhatsApp or Signal. The G- code was received, and it was automatically entered; however, it claimed there was an error and to try again. I ignored this message and immediately at the bottom, it said that RCS was registered to the carrier/sim card name.
Chats were switching to RCS messages, where applicable, some with a little lock and some without. When I connected to Mullvad VPN, the status changed to connecting. I looked at the status under debug mode, and the issue shown was due to a disconnection of the network; it did not reconnect until I disconnected the VPN. I can say that it is working since I added Messages to the split tunnelling list and connected.
Glad to see some progress being made. The method of installing the old application to load the correct ACS string works until google tries to auto-renew the lease on your phone #. I e. You have to do the process again every few days.
Right now I'm looking through the debug -> RCS -> Configure MobileConfiguration menu to see if I can find a similar variable on the "new" messages app. Unfortunately, there doesn't seem to be any documentation on what each of the variables do so it's a bit of a guessing game.
Hazelfoot I have to look out for the renewal and see what happens. Nothing happens when I force a manual configuration; it would be interesting to see the configuration behind the scenes.
Also hitting the auto renewal issue. The debug menu shows that the ACS URL is still correct. Going back to the old APK got it to re-register. Maybe it will stick but if it keeps happening I'd just as soon disable RCS altogether.
Uncertain of the best way to debug carrier services. On the latest update for the pixel 7 pro on Verizon carrier services never starts when messages initializes rcs or runs at all for that matter. Noticed it trying the force stop messages app and carrier services and clear appdata troubleshooting steps. When I plugin the acs URL using the old APK method it seems to start and function without it oddly enough.
- Edited
N3rdTek I do not see anything to do with the ACS URL. I also cannot find the necessary setting using ActivityLauncher. I am also having issues with auto-renewal.
Hazelfoot I don't see anything to do with the ACS URL under Configure MobileConfiguration. All I see is a button that says "Force Sync Mobile Configuration"
Syberkonda Got this working. I'm on a Pixel 7 Pro and used this specific variant of the old apk: https://www.apkmirror.com/apk/google-inc/messenger-google-inc/messenger-google-inc-20220214_00_rc02-release/messages-messages-android_20220214_00_rc02-phone_dynamic-3-android-apk-download/download/?key=b28cfb181ec0dccfe74d743d5ab3724ec2c40474&forcebaseapk=true Also had to install Activity Launcher https://play.google.com/store/apps/details?id=de.szalkowski.activitylauncher . I do not have Carrier Services installed. For Google Play I just have Network enabled. For messages I have all but location enabled. After following the instructions on the reddit thread and using the Verizon link provided in this post I got it working then immediately updated the app and rcs still worked. When I go into settings though it says it's disabled so not sure what's going on there. Will post back if it gets disabled and fails to activate. Not sure if others have tried this without carrier services installed
[deleted]
- Edited
Syberkonda
Hello everyone! I had made an account to report my findings. It seems my RCS on Google Messages stopped working around the same time as most people in this thread. I had followed a couple people's suggestions here and no avail. I decided to give Syberkonda's post a try and it actually worked! I followed the post pretty much to a 'T' but instead of grabbing the APK from apkmirror, I used Aurora store and the version code that's listed under the app variants. I matched my CPU architecture, went with the nodpi, openbeta build; version code: 52051140. After that, I followed the steps normally.
I am using a Pixel 7 on AT&T with the latest build. So instead of the Verizon ACS URL, I used "https://rcs-acs-att-us.jibe.google.com". It connected pretty much instantly and I was able to update the app with Aurora afterwards and still keep RCS connected.
Edit: I forgot to mention, I do not have carrier services installed.
Guys, my RCS hasn't disconnected nor dropped out. I disabled Carrier Services today to see if that will make a difference. The APK from APK Mirror is technically signed by Google and would have been an existing version at that time.
[deleted] does yours show rcs as disabled as well even though it works?
[deleted]
thed0ctor
It says "Connected" in green text followed by my phone number.
bluesl33ves Still connected.
bluesl33ves are you using Verizon?
Hazelfoot nope, I'm outside of the US.
It's still connected btw.