[deleted]
billinmtl Android is a set of operating systems based on aosp; gos is not Android, but it is based on aosp.
Using RCS with Google Messages on GrapheneOS
I would be wary to give an outdated app from APK mirror sensitive permissions by making it your default sms app.
This is on Google's side, dozens of reports on Reddit have the same thing happen on stock or major OEM OSes. Best to just have Google resolve this before starting to use this with workarounds.
- Edited
I was weary of trying that fix (outdated beta APK with "pegasus" in the file name), but it did work with the caveat that it got hung up again until I cleared the storage/cache. I was then able to update it to the latest version via play store and revoke some permissions.
EDIT: shortly after updating the APK from the play store my RCS became unregistered again. Gonna chalk this one up to a Google problem vice a graphene problem.
Hazelfoot I updated Google Messages with no issues.
- Edited
samsepi0l
I also don't like the thought of Pegasus spyware, any stranger sending me messages to my phone directly and Google collecting metadata, so I bought a separate MiFi-router (a mobile router) for that.
It has a web-based interface for recieving SMS messages. (You connect to the device through the web browser)
I kinda use it as a pager for carrier-related messages.
I use Molly-FOSS for for chats and a web-based E-Mail client for recieving E-Mail.
I am even considering switching to Briar messenger instead of Molly.
[deleted]
Pocketstar I tried briar but never managed to add a correspondent
Syberkonda This solution looked hopeful for me, except that I was not receiving any G- code. This is not too surprising since I no longer receive a code when I try to deactivate RCS through the website that sends the code, if you no longer have the device it was registered to. I may have to look at waiting 10 business days before trying again.
- Edited
[deleted]
There are two methods to add a contact; locally and remotely, I never tried remotely myself, locally worked just fine, I did enable Bluetooth and WiFi however, not sure if those are requirements.
Briar also logs out after rebooting the phone, that might not be convienent for contacts not willing to put in their passwords. (Or simply forgetting about it)
Briar is usually meant for whistleblowers and people in need for extreme security, it does make the app a little harder to utilize for daily usage, I should have mentioned that before I recommended it.
I use it for emergencies in case the internet goes out and as a secure alternative to Molly-FOSS, if there are enough Briar users connection might still be established (although delayed) from device to device, even during a blackout.
It also uses TOR (in online mode) even with the possibility for bridges. (Sort of a TOR-obfuscation)
The app is also nice for local forums and blogs that you don't want to share in the open like on Facebook.
Please do not go off-topic and continue to do so. I would rather an admin not come and close this thread after all this time.
7 days later
I would also like to leverage RCS through an web app, but I don't want to involve Google for that. Is there an alternative way that is open source?
Carlos-Anso I have almost all perms enabled for all google services. I've used RCS before on the same carrier as mentioned in an earlier post/comment. I do in fact use DNS filtering via nextdns but I believe I've whitelisted what is required; since losing device and taking the the time to use replacement as stock to compare, it now works. But I don't have DNS filtering enabled yet. Will report back...
- Edited
Syberkonda
Are you able to achieve this with developer mode on official Messages from store without using the linked APK? I swear I've seen the very same ACS URL entry somewhere in Dev options
To access dev mode open messages and click the search on top right. Enter the following and press enter when done:
*xyzzy*
Go to main screen of messages, click profile icon top right. You'll now see dev options.
CAREFUL PLAYING WITH SOME SETTINGS IF YOU AREN'T AWARE OF THEM.
It is possible to fill your migrating SMS messages with testing messages with a number 5555550001 going all the way up to 5555559999 so 10,000 texts that will NOT be removed by deleting the app. It will follow you to every other sms app.
Only perform what the support rep mentioned then to disable the developer mode re-enter the same code in the search bar
*xyzzy*
This menu isn't completely dangerous, it's possible to actually enable flags for upcoming features, just perform due diligence before playing with random entries like I did trying to learn about them.
- Edited
I tried another carrier and nada. However, since I did, I noticed that Carrier Services actually had data to clear. It might be a coincidence since Grapheneos updated a couple of times and may have included CS in the apps it was optimising. RCS works on all of the carriers for those on their respective stock OS.
Syberkonda @Ninja4694 try this out.
- 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.