Bug 433871

Summary: FRE: SMS plugin - multi SIM support
Product: [Applications] kdeconnect Reporter: Marcin Orlowski <mail>
Component: messaging-applicationAssignee: Simon Redman <simon>
Status: RESOLVED WORKSFORME    
Severity: normal CC: shikaruko-ryukan
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Marcin Orlowski 2021-03-02 19:41:09 UTC
[This most likely assigned to wrong component. Please edit as I am unable to tell what should be the right one]

SUMMARY
KDE Connect SMS plugin does not support multi SIM devices and always sends from 1st SIM without any option to select

STEPS TO REPRODUCE
1. Get any multi SIM device (OnePlus etc)
2. Compose SMS - no option to select SIM to use for sending

OBSERVED RESULT
Message is always sent using 1st SIM card.

EXPECTED RESULT
As this is FRE it would be great to see plugin detecting multi SIM device and offer option to select which one to use for the outgoing message.
Comment 1 Simon Redman 2023-01-16 21:56:46 UTC
KDE Connect SMS will reply to messages using the same SIM card as the most-recent message in the conversation. So the app does have multi-SIM support.

I don't remember when multi-SIM support was added. At the time this bug was created, maybe it was not supported, in which case we should just resolve this bug, as it has indeed been resolved. If you are having issues with the current implementation, please create a new bug with the symptoms and we can have the discussion there.

We made the simplifying decision when adding that support, to not add support for selecting subscriptions when sending. It is massively more difficult to ask Android "what SIM cards are currently available?" than it is to use the last-active subscription, and I do not believe there is a usecase to "hop" between outgoing phone numbers within one conversation. If someone has a case where you need to be able to reply to a conversation with a subscription other than the last one, please open a new bug and describe that use case.

(One valid use-case, would be to at least display the subscription which KDE Connect will use to reply.)