Bug 377868 - no option to send an sms
Summary: no option to send an sms
Status: RESOLVED DUPLICATE of bug 362516
Alias: None
Product: kdeconnect
Classification: Applications
Component: plasmoid (show other bugs)
Version: 1.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-21 07:08 UTC by Philippe ROUBACH
Modified: 2017-07-13 23:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2017-03-21 07:08:11 UTC
opensuse leap 42.2
kdeconnect 1.0.3

android 6.0.1
kdeconnect 1.6.1
google messenger

i saw that in ubuntu systray indicator menu there is an option to send sms.

in the kde plasmoid menu there is no option to send an sms
Comment 1 Ivan Stanton 2017-03-21 22:44:50 UTC
Should be at wishlist priority. It's not a bug, it's the lack of a feature
Comment 2 Albert Vaca Cintora 2017-03-27 17:31:04 UTC
On version 1.6.3 you can use the command line interface for that:

kdeconnect-cli --send-sms <message> --destination <number>
Comment 3 Philippe ROUBACH 2017-03-27 17:57:11 UTC
thanks
but there is a problem.

i send the command
@linux-9vc6:~> kdeconnect-cli -n 'Samsung Galaxy S2 Plus' --destination '+33 1 23 45 67 89' --send-sms 'coucou essai'
@linux-9vc6:~> 
but
google message displays a new conversation with the right first and second name of contact and the right text but with a red comment "message not sent. touch to retry".

if i touch then same problem
Comment 4 Albert Vaca Cintora 2017-03-27 18:24:12 UTC
Mmmm, try removing the spaces from the phone number?
Comment 5 Philippe ROUBACH 2017-03-28 17:47:04 UTC
sending sms with kdeconnect-cli works well with international number as +33 1 23 45 67 89

it's a pity that kaddressbook crashes when transmitting the sms to kdeconnect-cli
see https://bugs.kde.org/show_bug.cgi?id=375296
Comment 6 Aleix Pol 2017-07-13 23:46:28 UTC

*** This bug has been marked as a duplicate of bug 362516 ***