Smooth Edges (name pending) - Let's Fix the Bugs That Drive You Mad
-
Thank you the information!
-
@pparent It was nothing ! But, that's not the kind of answer I like to hear from AI !! More brakes which could become problems if text messages stop ONE day !!
-
I don't understand that UE lets Google do that. They passed a law to force a private actor to interconnect with competitors like Matix. But there fine with the telephony standard being phagocytosed by a foreign actor like Google.
I think some actors like Matix, alternative Rom providers, Ubports, Jolla, should unite to demand that the service be interconnected with an independent server compatible with FOSS clients.
-
RCS seems like a tricky thing to implement. I think it's even disaed in the carriers in my country
-
It does work on Apple devices from iOS 18.
If there is only Googles implementation of the open standard available then it will be difficult to move forward on it. I can't see carriers running the backend to support "alternative" OS devices.
I'd be happy with just XMPP working within Messages if RCS is not feasible. -
Intersting informations from Graphene on RCS:
-
@pparent too much the word google inside !!!
-
Ok, when RCS is really relying on proprietary Google-services (I can't believe this) then this kind of communication isn't interesting for me. I think the most of us are here, because they don't want to use services from big tech.
-
Intersting informations from Graphene on RCS:
Thank you for that link, even though, combined with @domubpkm info, it is depressing...
I appreciate having the relevant info that suggests how large (and therefore unlikely to be solved by small UT team) a problem RCS support really is. -
AI 2 : RCS and Ubuntu touch : little hope !
RCS on Ubuntu Touch: Technical Feasibility and Possible Solutions
Your Question
Can the RCS protocol be easily ported to the alternative ROM Ubuntu Touch based on Ubuntu 24.04 or 26.04? Are there technical solutions?
Direct Answer
Yes, Ubuntu Touch presents favorable technical opportunities for porting RCS, but no solution is currently officially operational.
Favorable Architecture of Ubuntu Touch
Unlike AOSP-based ROMs, Ubuntu Touch relies on a Linux-native architecture with Qt/QML technologies for its applications. The official messaging app uses a history-service backend and currently only supports SMS/MMS, but its modular design offers the flexibility necessary to integrate an RCS stack without the constraints imposed by the Google Play Services ecosystem.
Three Identified Technical Paths
1. Native Qt/QML RCS Client
This approach would allow directly implementing GSMA specifications within Ubuntu Touch's open code. However, this would likely require GSMA certification and potentially direct agreements with telecom operators to access their RCS servers.
2. Waydroid as Android Container
Ubuntu Touch already includes experimental support for Waydroid, allowing Google Messages to run isolated in an Android container within the Linux system. This would provide full RCS functionality while maintaining the de-googled base system, although this maintains some indirect dependency on Google services.
3. Porting Third-Party Applications via Click/OpenStore
Ubuntu Touch's Click package system already allows deployment of complex applications like Delta Chat. A compatible RCS client could therefore theoretically be ported to this ecosystem without resorting to proprietary frameworks.
Prerequisite Conditions Required
Regardless of the chosen approach, several conditions remain essential:
- Access your operator's specific RCS servers as they vary by region
- Obtain GSMA certification if developing an independent client rather than using Google's
- Manage history integration with the existing history-service backend to ensure data consistency between SMS, MMS, and RCS
Current Status and Outlook
As of today, no official RCS implementation is available on Ubuntu Touch. These proposals are based on technical discussions documented within the UBports community which identified these possibilities. True viability will depend on mobilizing active contributors with the necessary knowledge in telecommunications protocols and Qt/QML development. Without dedicated community investment, these technical paths will remain theoretical despite their demonstrated architectural feasibility.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login