Smooth Edges (name pending) - Let's Fix the Bugs That Drive You Mad
-
@arubislander said in Smooth Edges (name pending) - Let's Fix the Bugs That Drive You Mad:
What formats can or cannot be played on the device is also dependent on the codecs the device comes with.
You seem to imply that it is a device specific problem and that it's all a matter of what the Android version could support. I just tested a fix for my phone not being able to play .amr files and it did not imply any Halium trickery, I'm pretty sure that any UT phone has the same problem and that the fix would apply for all.
-
@gpatel-fr Aha, so for audio codecs it is a question of the right flags and necessary libraries. I will amend my answer then.
-
it is not the case for video codecs either
indeed. This week-end I tried seriously to add ffmpeg codecs to my FP5 with 24.04-1.2 stable and basically succeeded, see https://gitlab.com/ubports/development/core/lomiri-messaging-app/-/issues/359#note_3122981838
So it is possible to play ALAC files with the existing UT applications (mediaplayer...). The fact that it is slower than when accelerated by the hardware is true of course, but a not too old processor like the FP5 one is powerful enough to handle simple video files without acceleration (did not try 4K though). -
L libremax referenced this topic on
-
Yesterday all of our SIP in Germany stated, that they will shutdown MMS at the end of June. So it's important to have an alternative as RCS for people who need this kind of service.
-
Since we're in July, MMS is no longer available in Germany. So for now, we're not able to send Photo/Video/Audio without relying to any of these instant-messenger out there.
-
Since we're in July, MMS is no longer available in Germany. So for now, we're not able to send Photo/Video/Audio without relying to any of these instant-messenger out there.
I think RCS should be a top priority for UT, as it is currently one of its most important missing feature!
-
Is it even possible to implement RCS in a completely open source way at the moment? Since it seems to be stuck inside Play Services, and Apple just doesn't care about it? Like, could I go out and buy some random Nokia feature phone for 80 EUR and would it work with RCS?
RCS was supposed to be a replacement for SMS, which means it should Just Work (TM) at the SIM level after the implementation is done in the code for the thing that manages the SIM (ofono, in this case). But it seems like in reality it has been implemented in some weird way where Google somehow controls it entirely on Android, and not all RCS connections play nicely together? The whole thing is a mess.
-
@projectmoon I question IA about android ROM's : you are right :
The answer :
In summary: the RCS protocol is very difficult to deploy on most alternative Android ROMs independent of the Google Play Store. Here's why:
Main Technical Issues
- RCS heavily depends on Google services
The standard RCS stack uses Google's proprietary Jibe backend
It requires Play Services to function properly
The Google Messages application is virtually indispensable, as most carriers only authorize it through this app
2. Blocking integrity checks Recently, Google has implemented Play Integrity API attestations that prevent using Google Messages on modified systems like:GrapheneOS: explicitly states that "RCS is practically impossible" without Google services
LineageOS without GApps: the default AOSP messaging app does not support RCS because it is not open source
Possible Alternative Solutions
Option 1: Installing microG + Google Messages has low viability due to being blocked by Play Integrity checks.
Option 2: Self-hosted RCS server remains theoretical since there is currently no mainstream open-source implementation available.
Option 3: Using partial GApps offers medium viability but represents a compromise on the privacy you sought when choosing an alternative ROM.
Conclusion
To use RCS reliably, you are practically forced to keep some form of Google services. If your priority is privacy (hence the choice of an alternative ROM), this represents a notable compromise between modern messaging features and de-googling your system.
Fully open solutions exist theoretically but severely lack operational implementations accessible to average users.
Maybe possible but very difficult !
-
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:
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