https://bugs.kde.org/show_bug.cgi?id=464654
--- Comment #3 from Rafael Linux User <[email protected]> --- Three years later, bug not fixed SUMMARY When sending a message from the KDE Connect desktop interface via the SMS plugin, the phone always sends the message as a traditional SMS, even when: - The recipient has RCS enabled - The default messaging app on the phone supports and is currently using RCS As a result, messages are sent with SMS limitations (no advanced encryption, no read receipts, length constraints) and may incur additional costs, instead of using RCS when available. STEPS TO REPRODUCE 1. Pair an Android phone with KDE Connect 2. Ensure RCS is enabled in the phone’s default messaging app 3. From KDE Connect on the desktop, open the Messages window 4. Send a message to a contact known to have RCS enabled OBSERVED RESULT The phone sends the message as SMS/MMS regardless of RCS availability. EXPECTED RESULT KDE Connect should delegate message sending in a way that respects the transport available on the phone (RCS when available, SMS only as fallback). SOFTWARE/OS VERSIONS PC --- Operating System: openSUSE Tumbleweed 20260209 KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.2 Kernel Version: 6.18.9-1-default (64-bit) Graphics Platform: Wayland Smartphone -- Samsung S20FE (SM G780G) Android 13 One UI 5.1 KDE Connect 1.35.5 The SMS plugin may be invoking Android’s SMS APIs instead of delegating to the default messaging app in a way that allows RCS-capable transports, which forces an SMS fallback. -- You are receiving this mail because: You are watching all bug changes.
