SUMMARY After connection (KDE Connect with my smartphone) I receive first SMS. I click into Notifications (icon with number in circle) and see message and 2 buttons: "reply" and "close". I reply and send. Fine. I receive next SMS. I do the same and I see only "close" button". For all next SMS happens the same. I see only "close" button. In "Status and Notifications -> Notifications" I see the same. Is it possible to add "reply" button to every received SMS? Please notice that I see "reply" button related with last received SMS when I click into "KDE Connect" icon, but all previous is visible only "close". STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
This is probably because your phone is in doze mode when the second message comes in. The notifications seem to behave strangely then. Check if this happens when the phone is plugged in as well since that typically blocks doze mode.
What do you mean saying "doze mode". For sure screen was turned off. I didn't activate it after I received first SMS. And as I said "reply" was available in "KDE Connect", whereas in Notification only "close". So if in KDE Connect works, then why in "Notification" doesn't?
Today it happened again. I wasn't able to reply on received SMS. I turned on screen and unlocked device. It immediately connected with my PC. And in result were appeared couple popup notifications (including SMS). Unfortunatel I didn't make click on "reply" button on time and they have been moved into "Notification". BTW. I found that is possible to change time after what popup will be hide, but seems this is global time - for popups coming from all application. I need to have time to click "reply" for SMS, but don't need look too long on some other notifications. And back to Notifications itself. I click into it and again I don't have "reply" button. After I clicked into KDEConnect icon and here was also missing "reply" button. I'm not sure if my phone went into "doze mode" or not only for sure screen was turned one and device blocked. Time between I clicked into Notification was short, more or less 1 minute. Is it possible to activate/add "reply" button in SMS messages placed in Notification? In this moment I can only read it and to reply I need to use my smartphone.
Sorry that this keeps happening to you. If you see a notification with a reply button, it should also be the case that the notification in the list of notifications from the phone has a reply option. I don't know why that isn't working for you because I have never had trouble with that particular connection. Version 1.4 is coming soon which has lots of feature upgrades including a much-improved SMS experience. I hope you will find that useful when that gets to you!
Ok. I hope new version will work much better in case of SMS function. This current one is not reliable in case of sending SMS. I'm not sure what is wrong with kdeconnect or with my phone (Sony Xperia X Compact with Android 8.0.0). Just before couple minutes I replied on three SMS. Firstly appeared popup 3 windows (one by one), so clicked on every three in "reply" button. Phone of course had turned off screen. I wrote messages and clicked "send" being sure that every message has been sent. I was very surprised when I opened on phone SMS application (standard one) and I wasn't able to find my sent messages. Now I don't know if something has been sent or not. Anyway I need to reply again on all three SMS in not comfortable way. This is happened couple times. Today wasn't first. I cannot rely on function sending SMS from KDE Connect :(.
(In reply to Piotr Mierzwinski from comment #5) > ... Sorry to hear that you're having trouble with sending messages too. I have not had a case where a message does not send, though sometimes it takes awhile (long after the message was received by the other party) before it appears in the Android messaging app. I suppose those apps are not designed for handling messages being delivered outside of them. I will soon need to change the message-sending process in KDE Connect so hopefully when that happens it will get rid of these problems too.
This time when I tried to reply on SMS KDEConnect just crashed. I don't have useful backtrace, probably because I don't have installed debug package. Anyway I did something like this - received SMS - clicked "Reply" (popup window) - wrote and sent, all fine - received another SMS - clicked "Reply" (popup window) - started typing - my phone notified my that I received another SMS, but KDEConnect didn't report it. In Notification I saw only old one. - clicked "Send" and then KDEConnect crashed with not useful (for The crash handler) backtrace. Anyway I put it below: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81de174380 (LWP 1334))] Thread 4 (Thread 0x7f81cfebe700 (LWP 8989)): #0 0x00007f81e1dbe415 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007f81d42bff5c in ?? () from /usr/lib/dri/i965_dri.so #2 0x00007f81d42bfb58 in ?? () from /usr/lib/dri/i965_dri.so #3 0x00007f81e1db857f in start_thread () from /usr/lib/libpthread.so.0 #4 0x00007f81e2a950e3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f81d6e33700 (LWP 1375)): #0 0x00007f81e11fd36c in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #1 0x00007f81e11fd9a6 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007f81e11fdb51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007f81e302b9bc in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #4 0x00007f81e2fd25ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #5 0x00007f81e2e052f5 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x00007f81e2e06520 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x00007f81e1db857f in start_thread () from /usr/lib/libpthread.so.0 #8 0x00007f81e2a950e3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f81d7634700 (LWP 1373)): #0 0x00007f81e2a8a667 in poll () from /usr/lib/libc.so.6 #1 0x00007f81e11fda80 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007f81e11fdb51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007f81e302b9bc in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #4 0x00007f81e2fd25ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #5 0x00007f81e2e052f5 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x00007f81e3263b37 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x00007f81e2e06520 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x00007f81e1db857f in start_thread () from /usr/lib/libpthread.so.0 #9 0x00007f81e2a950e3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f81de174380 (LWP 1334)): [KCrash Handler] #6 0x00007f81e4260edd in ?? () from /usr/lib/libkdeconnectcore.so.1 #7 0x00007f81e42604c6 in KdeConnectPlugin::sendPacket(NetworkPacket&) const () from /usr/lib/libkdeconnectcore.so.1 #8 0x00007f81d581a592 in ?? () from /usr/lib/qt/plugins/kdeconnect/kdeconnect_notifications.so #9 0x00007f81e2fffb70 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #10 0x00007f81d580d3a8 in ?? () from /usr/lib/qt/plugins/kdeconnect/kdeconnect_notifications.so #11 0x00007f81d581fc2e in ?? () from /usr/lib/qt/plugins/kdeconnect/kdeconnect_notifications.so #12 0x00007f81e2fffb70 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #13 0x00007f81e3cd4879 in QDialogPrivate::finalize(int, int) () from /usr/lib/libQt5Widgets.so.5 #14 0x00007f81e2fffa11 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #15 0x00007f81e3c6c779 in ?? () from /usr/lib/libQt5Widgets.so.5 #16 0x00007f81e2fffa11 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #17 0x00007f81e3bc4663 in QAbstractButton::clicked(bool) () from /usr/lib/libQt5Widgets.so.5 #18 0x00007f81e3bc488c in ?? () from /usr/lib/libQt5Widgets.so.5 #19 0x00007f81e3bc5c92 in ?? () from /usr/lib/libQt5Widgets.so.5 #20 0x00007f81e3bc5e56 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #21 0x00007f81e3b0ecb6 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #22 0x00007f81e3acb4d5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #23 0x00007f81e3ad4c6c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #24 0x00007f81e2fd39c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #25 0x00007f81e3ad3d4b in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #26 0x00007f81e3b2b211 in ?? () from /usr/lib/libQt5Widgets.so.5 #27 0x00007f81e3b2e154 in ?? () from /usr/lib/libQt5Widgets.so.5 #28 0x00007f81e3acb4d5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #29 0x00007f81e3ad4a21 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #30 0x00007f81e2fd39c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #31 0x00007f81e34af789 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #32 0x00007f81e34b105b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #33 0x00007f81e348937c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5 #34 0x00007f81ddd24fec in ?? () from /usr/lib/libQt5XcbQpa.so.5 #35 0x00007f81e11fbcf4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0x00007f81e11fdb11 in ?? () from /usr/lib/libglib-2.0.so.0 #37 0x00007f81e11fdb51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #38 0x00007f81e302b9a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #39 0x00007f81e2fd25ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #40 0x00007f81e2fda326 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #41 0x00005653de1544a2 in ?? () #42 0x00007f81e29bfee3 in __libc_start_main () from /usr/lib/libc.so.6 #43 0x00005653de15471e in _start () [Inferior 1 (process 1334) detached] Sorry I continue this thread, probably I should open another bug report. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.13
After restart application (from "The crash handler"). KDEConnect stopped report new SMS receiving :/. I received SMS on my device (during typing another one) and KDEConnect noticed nothing. Connection was fine, because I checked it via controlling media extension and it worked.
Today (actually at 09/08/2019) I received update of KDEConnect for Android. I started application on device. It connected with my PC. After I received SMS. I found no any notification in KDEConnect working on PC. After ~half an hour appeared popup window informing about received SMS. I clicked into "Reply". Unfortunately nothing happened. I'm not sure if new update broke something or not. Tomorrow (or today) I'll try to retest it. Whole situation looks very strange.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Application from time to time crashes like I reported below. Recently it happened in case of last update (Android version). Android only notified about new version. I tried to send new messaged and afer send KDE application crashed. Another issue is split of longer messages. First part of message is collected in notifications (no possibility of reply), second (even one work) is present in second. Here I can reply, but I cannot see whole message, because is cut. It happens also that messages are duplicated in Notification. For example first part is placed twice. I hope new version will fix most issues current one.
Seems issue doesn't happen. Tested with: kdeconnect 20.04.0