Fossify
Replies: 8 comments 69 replies
|
Maybe the code in https://android.googlesource.com/platform/packages/services/Telephony/+/refs/heads/main/testapps/TestRcsApp/ can be observed |
|
I saw that too, may be worth looking into as there are no open-source players in the RCS game, and when RCS becomes more popular, people will have no choice but to use Google Messages. One caveat is the internet permission. |
|
Oh man, I would support the heck out of this! A legitimate FOSS RCS client is literally #1 on my wish list, especially considering that even Apple is adopting it later this year. I would gladly grant internet permission to Fossify if it could make it happen. To be fair, I know "support" from a non-programmer is mostly cheap talk. But I could build code, test code, donate an old phone, donate money... anything to help make it happen! |
|
Also this was mentioned in SMT https://github.com/android-rcs/rcsjta. Did somebody try it? |
|
^That's a very stale repository - I imagine it wouldn't still be useful. https://github.com/Hirohumi/rust-rcs-client seems to be a bit more current, but I couldn't tell you the first thing about how complete (or useful) it is. |
|
Here's all the documentation from GSMA from 28 February 2025 for RCS Universal Profile 3.0 with MLS E2EE (latest): If you're looking for the MLS document specifically, it's RCC.16. Available open source implementations of MLS: |
|
Here's all the documentation from GSMA from 18 July 2025 for RCS Universal Profile 3.1 with MLS E2EE (latest): |
|
This client claims to support RCS: https://github.com/vidit135g/Replify-Messenger |
@Shad0wL3g3nd, is standard RCS encryption really E2E? That might be vendor-specific. 1 Footnotes |
|
Google implies there is E2EE as they reference iPhones NOT having it, therefore RCS does support it. |
|
Okay, if you expand it, it says: "Google Messages offers end-to-end encryption for your RCS messages with other Google Messages users. The GSM Association (GSMA) sets Mobile and RCS standards and we are currently working to define security standards cross platform." So it at least offers E2EE between Android Devices using Google Messages. The source may be using old code that doesn't support it either way. |
Thanks, @naveensingh. It appears that it was previously vendor-specific, but is now standard: 1
Footnotes |
|
A maintained RCS compatible messenger would be killer, I'd donate for that. |
|
Honestly, set up a gofundme or something. |
|
Could Google's RBM(RCS Business Messages) be messed with a little to support this? It looks fairly similar, just more of an automotive version of such, so it could be reverse engineered possibly to work? Honestly, take this with a grain of salt.
|
|
@KitCatLove Bro Really Said "Dump The Theory, Take The Implementation." ☠️ Jokes Apart, This Is Great, Only If There Is No Vendor Lock-in, And E2EE Is Maintainable As Well. Also, They Seem To Abandon This Code For Some Reason. Check Out Readme From It's Main Branch. |
Good point, but it would at least get base encryption. Even if it's out dated |
|
Guys, it's just the AOSP messaging app. There's no encryption there. |
|
@naveensingh, |
|
Oh, you meant literally |
|
So if I have understood everything here correctly, is RCS support not yet being implemented or what is the status? |
No. I don't recall seeing it to be honest? |
@webdingspowah, I tried to, but it was incomprehensible to a layman like myself. If you look at my past comments here, I explicitly asked the thread's participants whether your documentation explained the E2EE specification, but was informed by someone that it didn't anymore due to its age. I don't consider myself to be an authority on the matter, so I believed them. Thank you for the new documentation. |
|
Well, good luck. Because whoever is brave enough to take on this monumental task is going to need it. The new document for the E2EE specification alone is another 90 pages of information that will need to be read and implemented, on top of all the other documentation that outlines the specification. Not even Google and Apple have this completed yet. At the time of writing this message, nobody in the world is on RCS version 3.0. At the moment, Apple is on version 2.4, and Google is on 2.6 with partial support for 2.7. Which means Google is two and a half years behind, and Apple is nearly six years behind. |
I do remember it looking back; sorry... |
|
FYI apparently it might be integrated into /e/ at some point: quik-sms/quik#124 (comment) |
|
I'm new to Fossify and would love to use it as my primary app, but without the ability to react to texts, it is lacking. |
|
I'm right there with you, but let's not make it sounds like Naveen is slacking off. Currently, there is no usable RCS client for Android other than Google Messages - it is not technically feasible for any FOSS client to implement at this point. |
|
I think Samsung's messaging app has RCS compatability as well. |
|
@KitCatLove,
|
|
This will be an interesting thread to follow. RCS as part of microG? Yes, please! EDIT: I misread the request. The bounty is for microG to allow Google Messages to use RCS, not for a broad-based implementation of RCS within microG that other apps could connect to. |
|
Given the direction Google is taking android, they will block any attempt at implementing RCS outside google messages. Sideloading will be thing of the past soon too. It was fun while it lasted. |
Hey, at least they were considerate enough to allow ADB installs. |
For now at least, but not for long I suppose |
|
They Are Restricted To Official Androids. Stuff Like Lineage OS, Etc. Are Safe. Also, Most Phones Are Now Compatible With Project Treble. You Can Sideload A GSI Image From Any Of Your Own Favourite AOSP (Un)Maintained Fork, And Enjoy Android Restriction Free. |
|
@atikattar1104, how does that relate to RCS? |
Uh oh!
There was an error while loading. Please reload this page.
Is RCS possible?
All reactions