Summary: | Some phone models, ROMs or Apps don't report SMS History | ||
---|---|---|---|
Product: | [Applications] kdeconnect | Reporter: | Andy Holmes <andrew.g.r.holmes> |
Component: | messaging-application | Assignee: | Simon Redman <simon> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andre.ros2, brian, bugs.kde.org, bugzylittle, cgku, cotkocot, cyberalex4life, dev, dougshaw77, dualprodu, fubu666, gabriel, grizzly, ItsRogueRen, jack, josh.phelps2011, jrdavis42, jrmz, kdebugs, keith, kingofgamesyami, kn, lg_ninjalo, lxkuba, marcin, nikunjbhatt84, pczekalski, philippe.roubach, poperigby, ricardo.e.p.rodrigues, s.seletskiy, SepulchreWraith, simon, skarlupkaa, tcolley, voncloft, wdw19071976, zionad, zirkovski |
Priority: | NOR | ||
Version: | 1.10 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/network/kdeconnect-android/commit/876d1fa3db9a7f9a136ae2cabe38bc81194b6dfd | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: |
Exception in SMSPlugin's onPacketReceived()
Complete Error Report from Nokia 5 Android 8.1 vanilla Complete Error Report 2 from Nokia 5 Android 8.1 vanilla Logs from Samsung Galaxy Xcover 4 logcat entry from Samsung S9 New error on Samsung S9 after compatibility check fixed attachment-11896-0.html attachment-22088-0.html attachment-25904-0.html KDE Connect SMS Window |
Description
Andy Holmes
2018-12-03 00:03:24 UTC
Nokia 7 Plus, stock Android 9, default Messages app (by Google) with updates installed. Relevant part of logcat: https://hastebin.com/rigevixipa.cs Created attachment 116788 [details]
Exception in SMSPlugin's onPacketReceived()
The code is trying to call Integer.parseInt() on a THREAD_ID of 9223372036854775807
(In reply to Keith Calvelli from comment #2) > Created attachment 116788 [details] > Exception in SMSPlugin's onPacketReceived() > > The code is trying to call Integer.parseInt() on a THREAD_ID of > 9223372036854775807 Good catch! I think this is an un-related issue. Could you open a different bug ticket against it (and assign me if that is an option) In the bug, please report your KDE Connect version on the Android device and your Android version, plus the device model name (In reply to Simon from comment #3) > (In reply to Keith Calvelli from comment #2) > > Created attachment 116788 [details] > > Exception in SMSPlugin's onPacketReceived() > > > > The code is trying to call Integer.parseInt() on a THREAD_ID of > > 9223372036854775807 > > Good catch! I think this is an un-related issue. Could you open a different > bug ticket against it (and assign me if that is an option) > In the bug, please report your KDE Connect version on the Android device and > your Android version, plus the device model name Entered bug as requested (https://bugs.kde.org/show_bug.cgi?id=402032). Looks like you updated the code on github about 15 minutes ago, so that should fix this when released. I have the same issue with the Samsung J7 Perx (SM-J727P), using Google Messages. Android 8.1.0 & Samsung Experience 9.5. It is worth noting that Samsung Messages is also installed, and cannot be removed nor disabled. Issue: SMS List/History, isn't visible in gsconnect. Phone model: Samsung S8 (SM-G9850U) ROM: Official Samsung - Android Version 8.0.0 -Samsung Experience 9.0 Build: R16NW.G950USQU5CRK1 - Baseband: G950USQU5CRK1 Android Kernel: 4.4.78-14473909, dpi@21HHAG21 #1, Wed Nov 7 18:52:19 KST 2018 SMS Apps: Samsung Messages (primary), Google Messages (backup app). Both Apps present the behavior, and do not display the text message history. Other details: Just in case that it's relevant.I'm part of the T-mobile Digits program, but no secondary numbers on my phone, just use it to send messages from the T-Mobile Webapp sometimes. Created attachment 117644 [details]
Complete Error Report from Nokia 5 Android 8.1 vanilla
Please advise if passwords or sensitive data leaked!
Created attachment 117645 [details]
Complete Error Report 2 from Nokia 5 Android 8.1 vanilla
Please advise if passwords or sensitive data leaked!
(In reply to CYBERALEX from comment #7) > Created attachment 117644 [details] > Complete Error Report from Nokia 5 Android 8.1 vanilla > > Please advise if passwords or sensitive data leaked! So this bug also occurs on my Nokia 5 phone with Android 8.1. Currently from what I know, Nokia 3 also received Android 8.1 said to be vanilla. I suspect a lot more Nokia phones might have this issue. Wiko JERRY2, Android 7.0 vanilla, everything works except sms history. I use the default sms app "messages" provided by google (I've tried some others but nothing changes). I'm sorry but I don't understand how to "Send a kdeconnect.sms.request_conversations packet to the device". I've tried by adding this command line from gsconnect on my computer and then tun it on my phone on "execute a command line" but it doesn't do anything. Thank you in advance for your help Created attachment 119933 [details]
Logs from Samsung Galaxy Xcover 4
Phone: SM-G390F
ROM: stock Android with latest updates (8.1)
SMS App: default (Messages v4.4.30.41)
If you are affected by this problem and you are able to build the Android app from source (instructions in the wiki: https://community.kde.org/KDEConnect#Android), could you please build my new merge request (https://invent.kde.org/kde/kdeconnect-android/merge_requests/77) and test whether you now see SMS history? Git commit 418e1a813e8a3c60f4841e9a770ae4291ac66db8 by Simon Redman. Committed on 22/06/2019 at 00:49. Pushed by sredman into branch 'master'. Potentially fix SMS/MMS access on Samsung devices According to some information I stumbled across while working on a different issue, Samsung devices do not support the content provider I was using to populate the list of SMS conversations. This is very annoying, but nevertheless there appears to be a workaround. Many users with Samsung devices have reported problems using the SMS plugin. Hopefully this will fix the SMS plugin on Samsung devices. https://invent.kde.org/kde/kdeconnect-android/commit/418e1a813e8a3c60f4841e9a770ae4291ac66db8 Adding to this, with version 1.12.93 on Android, with a Samsung Galaxy S9, running the latest firmware, an error is still occurring when fetching conversations. Seems that the request to the phone isn't returning what the code is expecting, and is throwing a NullPointer exception in the onPacketReceived handler Created attachment 121408 [details]
logcat entry from Samsung S9
Git commit ffbceb9b8e2ed0031b5d23c2cdae31ab8a577635 by Simon Redman. Committed on 09/07/2019 at 09:15. Pushed by sredman into branch 'master'. Reorder the Samsung special case to take effect before the case handling all other devices M +11 -7 src/org/kde/kdeconnect/Helpers/SMSHelper.java https://invent.kde.org/kde/kdeconnect-android/commit/ffbceb9b8e2ed0031b5d23c2cdae31ab8a577635 Right, I've made some further changes. The MANUFACTURER string on Samsung is not capitalised, at least on my phone. However, even once that's been changed, it still errors when retrieving MMS content as msg_box isn't available in the database for MMS messages Note that I haven't uploaded these changes, not entirely certain of myself regarding pushing fixes to this project. The change was simply to make the .equals call convert any manufacturer string to all lower-case, and change the compared value from "Samsung" to "samsung" Created attachment 121653 [details]
New error on Samsung S9 after compatibility check fixed
(In reply to SepulchreWraith from comment #18) > Note that I haven't uploaded these changes, not entirely certain of myself > regarding pushing fixes to this project. The change was simply to make the > .equals call convert any manufacturer string to all lower-case, and change > the compared value from "Samsung" to "samsung" Do you want to make the commit? If so, go to invent.kde.org/kde/kdeconnect-android, sign up for an account, fork that repository, push to a branch in your fork and make a merge request. If you don't care, then I can make the change Xiaomi Redmi Note 5 I can send SMS but don't receive any reply on my computer and no history conversation. Ping is ok. This is also an issue on my huawei p9 and I'd suspect it is the same on all of pX and probably other models as well. I've been debugging it and it turned out that `content://mms-sms/conversations` constructs an invalid query; there is no `group_sent` field. By searching the github for "huawei sms mms" I found a few projects which seem to be decompiled huawei framework and found a solution, but I need to play around it more.. I'll open the PR when I'm done with it and also test this on huawei p20 which I have access to as well. (In reply to cotkocot from comment #22) > By searching the github for "huawei sms mms" I found a few projects which > seem to be decompiled huawei framework and found a solution, but I need to > play around it more.. I'll open the PR when I'm done with it and also test > this on huawei p20 which I have access to as well. I'll be happy to see that merge request when you're ready to show it! It has been suggested that we should make subclasses for the changes needed by affected devices (possibly including refactoring larger methods into smaller ones in order to override them) and a factory method to choose between them. If that seems sensible then consider doing it that way Moto G6 Play: No attempt with signal (Send, but no receive or history on Moto E4) Pulse, Google Messages: Send + contacts sync, but no receive or history (In reply to Andre Ros from comment #21) > Xiaomi Redmi Note 5 > I can send SMS but don't receive any reply on my computer and no history > conversation. > Ping is ok. Work perfectly with KDEConnect 1.12.7 Sms,contacts and history sms not visible in sms window. Anyway messages can be send. Huawei Mate 20 Pro and Manjaro Linux. Sms,contacts and history sms not visible in messages window. Doesn't seem to connect to local address book even after "contacts" in settings are un-ticked. O if it connects the contacts nor the sms are visible in the "messages" window which does open, but empty. Ubuntu 19.10, Android 9 on Samsung A6, Kdeconnect on android version 1.13.2., Gsconnect 28 (last version updated today). Great app btw, thank yo very much Andy! (In reply to Karel from comment #27) > Sms,contacts and history sms not visible in messages window. Doesn't seem to > connect to local address book even after "contacts" in settings are > un-ticked. O if it connects the contacts nor the sms are visible in the > "messages" window which does open, but empty. > Ubuntu 19.10, Android 9 on Samsung A6, Kdeconnect on android version > 1.13.2., Gsconnect 28 (last version updated today). > Great app btw, thank yo very much Andy! Correction: The application apparently does connect to contacts (to my local address book I assume as "contacts" are unticked in settings), because a pop-up alert on incoming message shows details about contact name. However, the "messages" window remains empty. (In reply to Karel from comment #28) > (In reply to Karel from comment #27) > > Sms,contacts and history sms not visible in messages window. Doesn't seem to > > connect to local address book even after "contacts" in settings are > > un-ticked. O if it connects the contacts nor the sms are visible in the > > "messages" window which does open, but empty. > > Ubuntu 19.10, Android 9 on Samsung A6, Kdeconnect on android version > > 1.13.2., Gsconnect 28 (last version updated today). > > Great app btw, thank yo very much Andy! > > Correction: The application apparently does connect to contacts (to my local > address book I assume as "contacts" are unticked in settings), because a > pop-up alert on incoming message shows details about contact name. However, > the "messages" window remains empty. I have exacly same problem on Manjaro Linux 18.1.2 GNOME with Android 9 on Huawei Mate 20 pro with Kdeconnect 1.32.2, Gsconnect 28. Im using Google Messages app. Apologies for making so much noise, but yet another correction: With upgrading to Gsconnect 28, the contact list (local, I assume) actually does show when I compose a new message. I didn't notice that before writing my first report - sorry for that. So the only issue that remains is that the sms log doesn't load. Otherwise all works perfect. Thank you for this excellent appkication! (In reply to Karel from comment #28) > (In reply to Karel from comment #27) > > Sms,contacts and history sms not visible in messages window. Doesn't seem to > > connect to local address book even after "contacts" in settings are > > un-ticked. O if it connects the contacts nor the sms are visible in the > > "messages" window which does open, but empty. > > Ubuntu 19.10, Android 9 on Samsung A6, Kdeconnect on android version > > 1.13.2., Gsconnect 28 (last version updated today). > > Great app btw, thank yo very much Andy! > > Correction: The application apparently does connect to contacts (to my local > address book I assume as "contacts" are unticked in settings), because a > pop-up alert on incoming message shows details about contact name. However, > the "messages" window remains empty. Xiaomi Redmi Note 7 working with this commit: https://invent.kde.org/kde/kdeconnect-android/commit/4a0c53610f5b8f82162bda0a2ac81d789f00e64a Current "Samsung compatibility mode" (https://invent.kde.org/kde/kdeconnect-android/blob/master/src/org/kde/kdeconnect/Helpers/SMSHelper.java#L111-119) causes problems (SQLiteException: no such column: address) on Samsung devices with custom ROMs (eg. LineageOS): https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/699#issuecomment-554772433 *** Bug 415182 has been marked as a duplicate of this bug. *** Another user reported that the Moto G5 Plus with the QKSMS app does not work Yep. Only the full SMS app is being affected though, replying to a notification works fine. Problem: KDE Connect-SMS App never syncs SMS messages STEPS TO REPRODUCE 1. Click on KDE Connect in the system tray 2. Click the 3-dot menu 3. Select 'SMS Messages' OBSERVED RESULT The loading icon stays spinning forever, and no messages are synced. EXPECTED RESULT All messages on the targeted phone are synced. SOFTWARE/OS VERSIONS Phone: Moto G7 Power Android Version: 9 SMS app: Stock "Messages" App KDE Connect Version: 1.4.0 (Desktop); 1.13.5 (Android) Linux: 5.3.13-200.fc30 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.12.5 *** Bug 415424 has been marked as a duplicate of this bug. *** same problem with Samsung S2 Plus LineageOS 14.1 (android 7.1.2) kdeconnect android 1.13.6 google messages openSuse Leap 15.1 Argon kdeconnect kde 1.4 kde apps 19.12.1 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Samsung Galexy S9 Android 10 Samsung Messages 11.0.00.291 KDEConnect Android App 1.13.7 Gnome Version: 3.34.2 DISTRIB_ID=ManjaroLinux DISTRIB_RELEASE=19.0.0 DISTRIB_CODENAME=Kyria DISTRIB_DESCRIPTION="Manjaro Linux" GSConnect 31 Legacy Message Support = Disabled I am able to view and send text messages from messaging menu. I can see full chat history and contacts. I can respond to messages and view conversation scroll-back. Previously I could only see or reply to a sms message via the notification pop-up. It's still not working for me on my Moto G5 Plus. I still cannot view my message history. Samsung Galaxy S8 KDE Connect Android app 1.13.7 GSConnect 31 *** Bug 418992 has been marked as a duplicate of this bug. *** Hi, I have the same problem. I can't read sms history bu I can send sms. This is my logs from KDE Connect app from android device (Huawei P30) Here is my logcat debug message ---------------------- adb logcat --pid=$(adb shell pidof -s org.kde.kdeconnect_tp) --------- beginning of main 03-26 12:19:32.952 4557 7891 E KDE/Device: Exception in SMSPlugin's onPacketReceived() 03-26 12:19:32.952 4557 7891 E KDE/Device: android.database.sqlite.SQLiteException: no such column: group_sent (Sqlite code 1 SQLITE_ERROR): , while compiling: SELECT date, subject, ct_t, reply_path_present, body, type, msg_box, thread_id, sub_cs, retr_st, locked, exp, m_id, date_sent, read, ct_cls, rpt_a, sub_id, pri, group_sent, resp_txt, ct_l, group_fail, d_rpt, person, error_code, _id, m_type, status, rr, sub, group_all, is_secret, read_status, risk_url_body, resp_st, text_only, retr_txt_cs, st, m_size, address, tr_id, time_body, m_cls, addr_body, group_id, v, service_center, network_type FROM (SELECT thread_id AS tid, date * 1000 AS normalized_date, date, NULL AS subject, ct_t, NULL AS reply_path_present, NULL AS body, NULL AS type, msg_box, thread_id, sub_cs, retr_st, locked, exp, m_id, date_sent, read, ct_cls, rpt_a, sub_id, pri, NULL AS group_sent, resp_txt, ct_l, NULL AS group_fail, d_rpt, NULL AS person, NULL AS error_code, _id, m_type, NULL AS status, rr, sub, NULL AS group_all, NULL AS is_secret, read_status, NULL AS risk_url_body, resp_st, text_only, retr_txt_cs, st, m_size, NULL AS address, tr_id, NULL AS time_body, m_cls, NULL AS addr_body, NULL AS group_id, v, NULL AS service_center, network_type FROM pdu_restricted WHERE ((recipient_ids NOT IN (select _id from canonical_addresses where address like '%UNKNOWN_SENDER%')) AND ((msg_box != 3 AND (m_type = 128 OR m_type = 132 OR m_type = 130)))) GROUP BY thread_id HAVING date = MAX(date) UNION SELECT thread_id AS tid, date * 1 AS normalized_date, date, subject, NULL AS ct_t, reply_path_present, body, type, NULL AS msg_box, thread_id, NULL AS sub_cs, NULL AS retr_st, locked, NULL AS exp, NULL AS m_id, date_sent, read, NULL AS ct_cls, NULL AS rpt_a, sub_id, NULL AS pri, group_sent, NULL AS resp_txt, NULL AS ct_l, group_fail, NULL AS d_rpt, person, error_code, _id, NULL AS m_type, status, NULL AS rr, NULL AS sub, group_all, is_secret, NULL AS read_status, risk_url_body, NULL AS resp_st, NULL AS text_only, NULL AS retr_txt_cs, NULL AS st, NULL AS m_size, address, NULL AS tr_id, time_body, NULL AS m_cls, addr_body, group_id, NULL AS v, service_center, network_type FROM sms_secret WHERE ((recipient_ids NOT IN (select _id from canonical_addresses where address like '%UNKNOWN_SENDER%')) AND ((type != 3))) GROUP BY thread_id HAVING date = MAX(date)) GROUP BY tid HAVING normalized_date = MAX(normalized_date), (OS error - 2:No such file or directory) ------------------ I have this as well on an S8+ on the stock Samsung ROM. Has a fix been pushed or are you still needing testers to build this and try it out? (In reply to sparkie from comment #44) > I have this as well on an S8+ on the stock Samsung ROM. Has a fix been > pushed or are you still needing testers to build this and try it out? There is no fix yet. Someone would need to "adopt" Samsung and figure out what needs to be changed. It's probably not significant coding work, but will require significant amounts of research to find the documentation or find another open-source app which already supports other devices (for instance, qksms is said to already work: https://github.com/moezbhatti/qksms) This is a core feature that I want for an app like this. Until this is fixed I don't think anyone with a galaxy S8 should use this app. They should find an alternative. Problem: KDE Connect-SMS App never syncs SMS messages STEPS TO REPRODUCE 1. Launch KDE Connest-SMS from application menu 2. Begins to refresh as soon as it launches OBSERVED RESULT The loading icon stays spinning forever, and no messages are synced. EXPECTED RESULT All messages on the targeted phone are synced. SOFTWARE/OS VERSIONS Phone: Samsung Galaxy Note 8 Android Version: 8.0.0 Oreo SMS app: Textra KDE Connect Version: Current as of 05/07/2020 (desktop); 1.14.12 (Android) Linux: Pop!_OS 20.04 LTS with KDE Plasma DE Wanted this as a Linux replacement to Microsoft's Your Phone on my Windows install but the SMS features don't work, which was the whole point. (In reply to Andy Holmes from comment #0) > SUMMARY > > GSConnect has started shipping its SMS application, which has resulted in a > number of users reporting devices that don't report SMS history. > > I've opened this bug to help collect a list of these phones, ROMs or SMS > apps which don't currently support SMS history. > > > STEPS TO REPRODUCE > 1. Send a kdeconnect.sms.request_conversations packet to the device > 2. Wait for a kdeconnect.sms.messages packet > > > OBSERVED RESULT > > Some phone models (especially Samsung) or SMS apps (especially Signal) > return an empty list of SMS messages. Some phones don't seem to respond at > all, possibly indicating a different bug that may have useful messages in > logcat. > > > **USERS DIRECTED FROM GSCONNECT** > > Please be a good neighbour to the KDE Connect team. Keep this report limited > to phone models, ROMs, SMS apps and share logs as attachments. > > Please do not post "me too" or "+1" comments and don't repeat duplicate > information. I get the same with my Pixel 4 XL worked until I updated GSConnect then no sms chat history, I'm using the standard google SMS app (In reply to Andy Holmes from comment #0) > SUMMARY > > GSConnect has started shipping its SMS application, which has resulted in a > number of users reporting devices that don't report SMS history. > > I've opened this bug to help collect a list of these phones, ROMs or SMS > apps which don't currently support SMS history. > > > STEPS TO REPRODUCE > 1. Send a kdeconnect.sms.request_conversations packet to the device > 2. Wait for a kdeconnect.sms.messages packet > > > OBSERVED RESULT > > Some phone models (especially Samsung) or SMS apps (especially Signal) > return an empty list of SMS messages. Some phones don't seem to respond at > all, possibly indicating a different bug that may have useful messages in > logcat. > > > **USERS DIRECTED FROM GSCONNECT** > > Please be a good neighbour to the KDE Connect team. Keep this report limited > to phone models, ROMs, SMS apps and share logs as attachments. > > Please do not post "me too" or "+1" comments and don't repeat duplicate > information. I get the same with my Pixel 4 XL worked until I updated GSConnect then no sms chat history, I'm using the standard google SMS app This is my latest proposal to resolve this issue: If someone watching this thread with an affected device could test it and leave comments on the PR, it would be appreciated: https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 (In reply to Simon Redman from comment #50) > This is my latest proposal to resolve this issue: If someone watching this > thread with an affected device could test it and leave comments on the PR, > it would be appreciated: > https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 I'm happy to test. How can I do it? (In reply to poperigby from comment #51) > > I'm happy to test. How can I do it? If you already have Android Studio installed, you can build using that, otherwise you can install Android Studio or build using gradle https://developer.android.com/studio/build/building-cmdline I've had pretty much 0% success sharing .apks built from my development session, so I can't provide a pre-built one, sorry (In reply to Simon Redman from comment #52) > (In reply to poperigby from comment #51) > > > > I'm happy to test. How can I do it? > > If you already have Android Studio installed, you can build using that, > otherwise you can install Android Studio or build using gradle > https://developer.android.com/studio/build/building-cmdline > > I've had pretty much 0% success sharing .apks built from my development > session, so I can't provide a pre-built one, sorry Ok. I'll do it soon when I have time. (In reply to Simon Redman from comment #52) > (In reply to poperigby from comment #51) > > > > I'm happy to test. How can I do it? > > If you already have Android Studio installed, you can build using that, > otherwise you can install Android Studio or build using gradle > https://developer.android.com/studio/build/building-cmdline > > I've had pretty much 0% success sharing .apks built from my development > session, so I can't provide a pre-built one, sorry Trying to test this tonight but I have never done anything with Android Studio before. Is there a guide on how I'm supposed to do this? Also, what do I need to even edit? Do I download the source code of kdeconnect-sms from github? (In reply to TheRogueGrunt from comment #54) > > Trying to test this tonight but I have never done anything with Android > Studio before. Is there a guide on how I'm supposed to do this? Also, what > do I need to even edit? Do I download the source code of kdeconnect-sms from > github? The instructions for how to download the patch in question are on Gitlab: https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 under the button labeled "Check out branch" I don't remember the exact process to set up Android Studio, but if I recall correctly there was some way to open or import an existing project (In reply to Simon Redman from comment #55) > (In reply to TheRogueGrunt from comment #54) > > > > Trying to test this tonight but I have never done anything with Android > > Studio before. Is there a guide on how I'm supposed to do this? Also, what > > do I need to even edit? Do I download the source code of kdeconnect-sms from > > github? > > The instructions for how to download the patch in question are on Gitlab: > https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 under > the button labeled "Check out branch" > > I don't remember the exact process to set up Android Studio, but if I recall > correctly there was some way to open or import an existing project I... cannot make any sense of any of this. Its just a whole ton of code that I have no idea what it does or even what is what. I have the folder "kdeconnect-android-use-simple-conversation-interface" and everything inside it, but how the hell do I make that an .apk to put on my phone? (In reply to poperigby from comment #53) > (In reply to Simon Redman from comment #52) > > (In reply to poperigby from comment #51) > > > > > > I'm happy to test. How can I do it? > > > > If you already have Android Studio installed, you can build using that, > > otherwise you can install Android Studio or build using gradle > > https://developer.android.com/studio/build/building-cmdline > > > > I've had pretty much 0% success sharing .apks built from my development > > session, so I can't provide a pre-built one, sorry > > Ok. I'll do it soon when I have time. If you make the apk, can you share it? I've just tried to and I broke Android Studio so badly even a full reinstall didn't fix it. You should be able to build the .apk by going to the directory where the branch is checked out and doing `./gradlew installDebug` without using Android Studio (Assuming ADB is set up and your phone is connected) I am going to merge this latest patch in a day or so in any case, since it at least seems to work as well as it previously did for all phones and it has been reported to work on a few phones which didn't previously work. Nobody with a Samsung device has been able to test which is the big one, but I am hopeful that it will work in any case (and I have read online that it should) Git commit 876d1fa3db9a7f9a136ae2cabe38bc81194b6dfd by Simon Redman. Committed on 10/06/2020 at 03:58. Pushed by sredman into branch 'master'. [SMS Helper] Use simple=true parameter for fetching the list of all conversations ## Summary Use `content://mms-sms/conversations?simple=true` instead of just `content://mms-sms/conversations` which should work for more devices (and is reported to work on Samsung devices) For some reason, this misses exactly one conversation on my phone and throws back one invalid thread ID -- I suspect this indicates that my message database is corrupt :shrug: ## Test Plan ### Before: Lots of devices were not able to retrieve conversations. See [bug 401677](https://bugs.kde.org/show_bug.cgi?id=401677) ### After: Hopefully all devices are able to retrieve conversations. At minimum, hopefully there are no regressions :) M +42 -17 src/org/kde/kdeconnect/Helpers/SMSHelper.java https://invent.kde.org/network/kdeconnect-android/commit/876d1fa3db9a7f9a136ae2cabe38bc81194b6dfd (In reply to Simon Redman from comment #58) > You should be able to build the .apk by going to the directory where the > branch is checked out and doing `./gradlew installDebug` without using > Android Studio (Assuming ADB is set up and your phone is connected) > > I am going to merge this latest patch in a day or so in any case, since it > at least seems to work as well as it previously did for all phones and it > has been reported to work on a few phones which didn't previously work. > Nobody with a Samsung device has been able to test which is the big one, but > I am hopeful that it will work in any case (and I have read online that it > should) This is why I'm trying so desperately to test it, I have a Samsung Note 8. I'll try this and if I can't figure it out I'll just wait for the merge. (In reply to Simon Redman from comment #58) > You should be able to build the .apk by going to the directory where the > branch is checked out and doing `./gradlew installDebug` without using > Android Studio (Assuming ADB is set up and your phone is connected) > > I am going to merge this latest patch in a day or so in any case, since it > at least seems to work as well as it previously did for all phones and it > has been reported to work on a few phones which didn't previously work. > Nobody with a Samsung device has been able to test which is the big one, but > I am hopeful that it will work in any case (and I have read online that it > should) That command has failed miserably so I'm just gonna wait for an apk I can just install. I'm not an app developer and I barely know enough to use Linux so all of this is WAY over my head and it honestly hurts to try to figure out (In reply to Simon Redman from comment #50) > This is my latest proposal to resolve this issue: If someone watching this > thread with an affected device could test it and leave comments on the PR, > it would be appreciated: > https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 This is working on my Samsung Galaxy Note 8 (Android 8.0 Oreo) (In reply to TheRogueGrunt from comment #62) > (In reply to Simon Redman from comment #50) > > This is my latest proposal to resolve this issue: If someone watching this > > thread with an affected device could test it and leave comments on the PR, > > it would be appreciated: > > https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 > > This is working on my Samsung Galaxy Note 8 (Android 8.0 Oreo) Do you think you could give us the APK? (In reply to poperigby from comment #63) > (In reply to TheRogueGrunt from comment #62) > > (In reply to Simon Redman from comment #50) > > > This is my latest proposal to resolve this issue: If someone watching this > > > thread with an affected device could test it and leave comments on the PR, > > > it would be appreciated: > > > https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 > > > > This is working on my Samsung Galaxy Note 8 (Android 8.0 Oreo) > > Do you think you could give us the APK? I can tonight after work (In reply to poperigby from comment #63) > > Do you think you could give us the APK? Since I actually checked the change in, you can try with the latest nighty build from the Binary Factory: https://binary-factory.kde.org/view/Android/job/kdeconnect_android/lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ Sorry I didn't mention this before, I forgot that it existed Oh. That's useful. Jun 12, 2020, 11:49 AM by bugzilla_noreply@kde.org: > https://bugs.kde.org/show_bug.cgi?id=401677 > > --- Comment #65 from Simon Redman <simon@ergotech.com> --- > (In reply to poperigby from comment #63) > >> >> Do you think you could give us the APK? >> > > Since I actually checked the change in, you can try with the latest nighty > build from the Binary Factory: > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > Sorry I didn't mention this before, I forgot that it existed > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You voted for the bug. > (In reply to Simon Redman from comment #65) > (In reply to poperigby from comment #63) > > > > Do you think you could give us the APK? > > Since I actually checked the change in, you can try with the latest nighty > build from the Binary Factory: > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/ > lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > Sorry I didn't mention this before, I forgot that it existed Okay, I just tried the APK and it seems to work! (In reply to poperigby from comment #67) > (In reply to Simon Redman from comment #65) > > (In reply to poperigby from comment #63) > > > > > > Do you think you could give us the APK? > > > > Since I actually checked the change in, you can try with the latest nighty > > build from the Binary Factory: > > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/ > > lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > > > Sorry I didn't mention this before, I forgot that it existed > > Okay, I just tried the APK and it seems to work! How did you get it to load? I keep getting the error "App not installed" after it goes through the progress bar. Im on a Note10+ (In reply to zionad from comment #68) > (In reply to poperigby from comment #67) > > (In reply to Simon Redman from comment #65) > > > (In reply to poperigby from comment #63) > > > > > > > > Do you think you could give us the APK? > > > > > > Since I actually checked the change in, you can try with the latest nighty > > > build from the Binary Factory: > > > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/ > > > lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > > > > > Sorry I didn't mention this before, I forgot that it existed > > > > Okay, I just tried the APK and it seems to work! > > How did you get it to load? I keep getting the error "App not installed" > after it goes through the progress bar. Im on a Note10+ All I did was click on the app in my file manager. Weird that it's not working for you. (In reply to zionad from comment #68) > (In reply to poperigby from comment #67) > > (In reply to Simon Redman from comment #65) > > > (In reply to poperigby from comment #63) > > > > > > > > Do you think you could give us the APK? > > > > > > Since I actually checked the change in, you can try with the latest nighty > > > build from the Binary Factory: > > > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/ > > > lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > > > > > Sorry I didn't mention this before, I forgot that it existed > > > > Okay, I just tried the APK and it seems to work! > > How did you get it to load? I keep getting the error "App not installed" > after it goes through the progress bar. Im on a Note10+ You may need to enable side loading in your settings Created attachment 129362 [details] attachment-11896-0.html Unknown sources is enabled for My Files app which is where Im accessing it from. Is there another setting? On Jun 14 2020, at 12:57 pm, TheRogueGrunt <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=401677 > > --- Comment #70 from TheRogueGrunt <nerdakio@gmail.com> --- > (In reply to zionad from comment #68) > > (In reply to poperigby from comment #67) > > > (In reply to Simon Redman from comment #65) > > > > (In reply to poperigby from comment #63) > > > > > > > > > > Do you think you could give us the APK? > > > > > > > > Since I actually checked the change in, you can try with the latest nighty > > > > build from the Binary Factory: > > > > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/ > > > > lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > > > > > > > Sorry I didn't mention this before, I forgot that it existed > > > > > > Okay, I just tried the APK and it seems to work! > > > > How did you get it to load? I keep getting the error "App not installed" > > after it goes through the progress bar. Im on a Note10+ > > You may need to enable side loading in your settings > -- > You are receiving this mail because: > You are on the CC list for the bug. > (In reply to Simon Redman from comment #65) > (In reply to poperigby from comment #63) > > > > Do you think you could give us the APK? > > Since I actually checked the change in, you can try with the latest nighty > build from the Binary Factory: > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/ > lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > Sorry I didn't mention this before, I forgot that it existed I tried it out. I can see all my SMS messages, but it fails to send them. By this I mean the message gets to the phone and the messaging app, but it immediately fails to send it. I'm using default Android on a Samsung S10e. How can I debug the issue? And thank you for your work! SMS browse is working on S8+. You will need to enable side loading and uninstall the current version of KDE Connect. I still can not send messages from the SMS screen on my computer, but all of my messages loaded up. (In reply to sparkie from comment #73) > SMS browse is working on S8+. You will need to enable side loading and > uninstall the current version of KDE Connect. I still can not send messages > from the SMS screen on my computer, but all of my messages loaded up. If you are using GSConnect perhaps this issue discussion might help: https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/876 My inability to send SMS is an issue of the SMS messages cache that gives the wrong number to GSConnect. This fix seems to be working on my Galaxy S7- able to load SMS history and send SMS. Thanks, this is an awesome fix! I hate using the little keyboard on my phone, so you just made my life a little better! I still am not able to side load these new builds. I just keep getting "App not installed" after it offers to update KDE Connect. I tried a fresh install with the same results. Yes unknown sources is enabled. Did you uninstall the previous version of KDE Connect? I was getting that error, too, till I uninstalled it. Created attachment 130016 [details] attachment-22088-0.html Thanks, that got it to work. Unfortunately, I still can't view or send SMS on this Note 10+. On Thu, Jul 9, 2020 at 6:36 PM Doug <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=401677 > > --- Comment #77 from Doug <dougjshaw77@gmail.com> --- > Did you uninstall the previous version of KDE Connect? I was getting that > error, too, till I uninstalled it. > > -- > You are receiving this mail because: > You are on the CC list for the bug. I get an S7, good news. Phone: Moto G7 Android Version: 10 SMS App: QKSMS 3.8.1 KDE Connect App Version: 1.14.2 OS: Arch Linux KDE Connect SMS Version: 1.4.0 I'm having this issue as well. I get notifications about new messages and can respond, but when I open the KDE Connect SMS app, it just spins and spins and never loads anything. Same problem with Samsung Galaxy Note 8 (In reply to pczekalski from comment #81) > Same problem with Samsung Galaxy Note 8 KDE Connect App version is 1.14.2 I have same problem with Huawei Mate 10. I tried both Play Store published app and latest nightly build from Jenkins (https://binary-factory.kde.org/view/Android/job/kdeconnect_android/709/). While trying Play Store published app there was the SQL exception in the adb logcat from ticker https://bugs.kde.org/show_bug.cgi?id=421338, but nightly release doesn't produce this exception when I open kdeconnect-sms, but SMS history still not visible. What can I do to help to debug this issue? (In reply to Stanislav from comment #83) > I have same problem with Huawei Mate 10. > > I tried both Play Store published app and latest nightly build from Jenkins > (https://binary-factory.kde.org/view/Android/job/kdeconnect_android/709/). > > While trying Play Store published app there was the SQL exception in the adb > logcat from ticker https://bugs.kde.org/show_bug.cgi?id=421338, but nightly > release doesn't produce this exception when I open kdeconnect-sms, but SMS > history still not visible. > > What can I do to help to debug this issue? Sorry to hear that you're still having this problem. If you're not seeing *any* exceptions when using the build from Binary Factory, then I don't know what's going on.. Pretty much the code has to return something or throw an exception. It's possible it's returning empty, but that would be strange. When did you download the nightly build? I actually touched this codepath over the weekened. (In a fairly significant way which I would expect to be supported by most/all devices) *** Bug 421338 has been marked as a duplicate of this bug. *** (In reply to Simon Redman from comment #84) > > Sorry to hear that you're still having this problem. > > If you're not seeing *any* exceptions when using the build from Binary > Factory, then I don't know what's going on.. Pretty much the code has to > return something or throw an exception. It's possible it's returning empty, > but that would be strange. > > When did you download the nightly build? I actually touched this codepath > over the weekened. (In a fairly significant way which I would expect to be > supported by most/all devices) Thank you for the swift reply, Simon! I tested build #709 yesterday, and I also tried build #710 today. What I do is to install APK, allow SMS (and other permissions), run `adb logcat --pid=$(adb shell pidof -s org.kde.kdeconnect_tp)` and then run `kdeconnect-sms`. It stays in the loading state forever, and I do not see *any* messages that appear right after running `kdeconnect-sms`. Note that when I was trying Play's version of the app, I saw the SQL error from the linked ticket. Other functions of `kdeconnect` work without a problem. I tried to test it with a different device (with Play's version of the app though), and `kdeconnect-sms` was able to display messages instantly, so I suppose it's a problem with the device itself. Could you create a debug build with additional debug/trace level logging enabled for the relevant code path so that I can provide `adb logcat` output? Created attachment 131723 [details] attachment-25904-0.html I have a note 10+ and also am not able to see message history. I tried that build from jenkins with no success. Is there somewhere I can look to see if an error code is being returned, which I could post here? On Sep 16 2020, at 7:24 pm, Simon Redman <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=401677 > > --- Comment #84 from Simon Redman <simon@ergotech.com> --- > (In reply to Stanislav from comment #83) > > I have same problem with Huawei Mate 10. > > > > I tried both Play Store published app and latest nightly build from Jenkins > > (https://binary-factory.kde.org/view/Android/job/kdeconnect_android/709/). > > > > While trying Play Store published app there was the SQL exception in the adb > > logcat from ticker https://bugs.kde.org/show_bug.cgi?id=421338, but nightly > > release doesn't produce this exception when I open kdeconnect-sms, but SMS > > history still not visible. > > > > What can I do to help to debug this issue? > > Sorry to hear that you're still having this problem. > If you're not seeing *any* exceptions when using the build from Binary Factory, > then I don't know what's going on.. Pretty much the code has to return > something or throw an exception. It's possible it's returning empty, but that > would be strange. > > When did you download the nightly build? I actually touched this codepath over > the weekened. (In a fairly significant way which I would expect to be supported > by most/all devices) > > -- > You are receiving this mail because: > You are on the CC list for the bug. > Created attachment 132304 [details]
KDE Connect SMS Window
On opening the KDE Connect SMS through the icon of KDE Connect, I am seeing the window as per this attached screenshot https://bugs.kde.org/attachment.cgi?id=132304. The loader animation is animating forever. Then I closed the window and opened it through terminal using "kdeconnect-sms" command. The following messages appeared in the terminal: qrc:/qml/ChatMessage.qml:63:29: Invalid property assignment: string expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt. qrc:/qml/main.qml:36: ReferenceError: _initialMessage is not defined QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken I tried settings Microsoft SMS Organizer as default SMS app and also Google Messages app in the Android phone, but same problem occurred with both. The phone is Moto X Play, having Android 7.1.1. The laptop's info is: Operating System: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 Kernel Version: 5.8.8-200.fc32.x86_64 OS Type: 64-bit Processors: 4 × Intel® Core™ i3-5005U CPU @ 2.00GHz Memory: 7.2 GiB of RAM (In reply to Nikunj Bhatt from comment #89) > On opening the KDE Connect SMS through the icon of KDE Connect, I am seeing > the window as per this attached screenshot > https://bugs.kde.org/attachment.cgi?id=132304. The loader animation is > animating forever. > > Then I closed the window and opened it through terminal using > "kdeconnect-sms" command. The following messages appeared in the terminal: > > qrc:/qml/ChatMessage.qml:63:29: Invalid property assignment: string expected > - Assigning null to incompatible properties in QML is deprecated. This will > become a compile error in future versions of Qt. > qrc:/qml/main.qml:36: ReferenceError: _initialMessage is not defined > QGridLayoutEngine::addItem: Cell (0, 0) already taken > QGridLayoutEngine::addItem: Cell (0, 1) already taken > QGridLayoutEngine::addItem: Cell (0, 0) already taken > QGridLayoutEngine::addItem: Cell (0, 1) already taken > QGridLayoutEngine::addItem: Cell (0, 0) already taken > QGridLayoutEngine::addItem: Cell (0, 1) already taken > > I tried settings Microsoft SMS Organizer as default SMS app and also Google > Messages app in the Android phone, but same problem occurred with both. > > The phone is Moto X Play, having Android 7.1.1. > > The laptop's info is: > Operating System: Fedora 32 > KDE Plasma Version: 5.18.5 > KDE Frameworks Version: 5.73.0 > Qt Version: 5.14.2 > Kernel Version: 5.8.8-200.fc32.x86_64 > OS Type: 64-bit > Processors: 4 × Intel® Core™ i3-5005U CPU @ 2.00GHz > Memory: 7.2 GiB of RAM I forgot to mention that the KDE Connect SMS is unable to load messages but I can reply to messages from the reply button and the window appears for replying. (In reply to Simon Redman from comment #65) > (In reply to poperigby from comment #63) > > > > Do you think you could give us the APK? > > Since I actually checked the change in, you can try with the latest nighty > build from the Binary Factory: > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/ > lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > Sorry I didn't mention this before, I forgot that it exists I downloaded the apk and installed it. I opened it up and gave it permission to send/receive SMS messages. Then I paired it and opened up my messages in the paired pc. I am able to see messages people have sent me and I am able to send messages. But I am not able to see messages that I have sent to other people in the past. New messages that I send are visible. Pop OS 20.10 GSConnect 44 Samsung Galaxy S8 SM-G950U Android 9 Kernel version 4.4.153-17214672 (In reply to zirkovski from comment #91) > (In reply to Simon Redman from comment #65) > > (In reply to poperigby from comment #63) > > > > > > Do you think you could give us the APK? > > > > Since I actually checked the change in, you can try with the latest nighty > > build from the Binary Factory: > > https://binary-factory.kde.org/view/Android/job/kdeconnect_android/ > > lastSuccessfulBuild/artifact/kdeconnect-android/build/outputs/apk/debug/ > > > > Sorry I didn't mention this before, I forgot that it exists > > I downloaded the apk and installed it. I opened it up and gave it > permission to send/receive SMS messages. Then I paired it and opened up my > messages in the paired pc. I am able to see messages people have sent me > and I am able to send messages. But I am not able to see messages that I > have sent to other people in the past. New messages that I send are visible. > > Pop OS 20.10 > GSConnect 44 > Samsung Galaxy S8 SM-G950U > Android 9 > Kernel version 4.4.153-17214672 The Kernel version is the kernel version on my phone with 1.15.1 there is some progress with my Samsung s7. i get the history for the first time. But also i get deleted conversations ! button "New" stays in grey and is disable. same on huawei smart p z not loading sms, not sending sms , do nothing. but the open soucre "simple sms" apk works (not import in silence) (gsconnect on manjaro) (In reply to Nikunj Bhatt from comment #90) > (In reply to Nikunj Bhatt from comment #89) > > On opening the KDE Connect SMS through the icon of KDE Connect, I am seeing > > the window as per this attached screenshot > > https://bugs.kde.org/attachment.cgi?id=132304. The loader animation is > > animating forever. > > > > Then I closed the window and opened it through terminal using > > "kdeconnect-sms" command. The following messages appeared in the terminal: > > > > qrc:/qml/ChatMessage.qml:63:29: Invalid property assignment: string expected > > - Assigning null to incompatible properties in QML is deprecated. This will > > become a compile error in future versions of Qt. > > qrc:/qml/main.qml:36: ReferenceError: _initialMessage is not defined > > QGridLayoutEngine::addItem: Cell (0, 0) already taken > > QGridLayoutEngine::addItem: Cell (0, 1) already taken > > QGridLayoutEngine::addItem: Cell (0, 0) already taken > > QGridLayoutEngine::addItem: Cell (0, 1) already taken > > QGridLayoutEngine::addItem: Cell (0, 0) already taken > > QGridLayoutEngine::addItem: Cell (0, 1) already taken > > > > I tried settings Microsoft SMS Organizer as default SMS app and also Google > > Messages app in the Android phone, but same problem occurred with both. > > > > The phone is Moto X Play, having Android 7.1.1. > > > > The laptop's info is: > > Operating System: Fedora 32 > > KDE Plasma Version: 5.18.5 > > KDE Frameworks Version: 5.73.0 > > Qt Version: 5.14.2 > > Kernel Version: 5.8.8-200.fc32.x86_64 > > OS Type: 64-bit > > Processors: 4 × Intel® Core™ i3-5005U CPU @ 2.00GHz > > Memory: 7.2 GiB of RAM > > I forgot to mention that the KDE Connect SMS is unable to load messages but > I can reply to messages from the reply button and the window appears for > replying. With last update of either KDE Connect App desktop app or the SMS Organizer app it started working on the Moto X Play. BTW, I have now stopped using Moto phone and now using Nokia 5.3 with Android 10, and all functions are working fine with it. As a workaround I use Google Messages with Android associated to messages.google.com with my PC. With Chrome I create a progressive web app with messages.google.com. Progressive web app is a feature in Chrome which installs a site as a desktop app, creates an item "Chrome Applications" in kde menu and an item "Messages" in "Chrome applications" (In reply to Philippe ROUBACH from comment #96) > As a workaround I use Google Messages with Android associated to > messages.google.com with my PC. > > With Chrome I create a progressive web app with messages.google.com. > > Progressive web app is a feature in Chrome which installs a site as a > desktop app, creates an item "Chrome Applications" in kde menu and an item > "Messages" in "Chrome applications" Why would you tell them you did a work around now these lackies won't fix anything. Phone: Oppo (R15) CPH1835 Android Version: 10 SMS App: Textra Version 3.49 KDE Connect App Version: 1.17 OS: Ubuntu 20.04 GSConnect Version: 1.4.0 I am using an Oppo phone with Ubuntu laptop and GSConnect, as per specs immediately above. I get very inconsistent responses around SMS sync and send when using the GSConnect interface: - SMS send can take from 1 second to several minutes to be sent after send instruction - SMS Messages window can display (a) no messages, (b) a small subset of messages, or (c) all messages - Closing the Messages window happens several seconds after clicking close icon I will log this report with GSConnect as well. Since this issue has not been reported in awhile, I am going to believe that my "solution" is working for all devices. If you are having the issue described here where NO messages load when you launch the KDE Connect or GSConnect SMS chat apps even though you have the latest Google Play / FDroid version of the KDE Connect Android app please post on this issue. (Reminder that, by design, Signal and other secure/encrypted messaging apps will not work with KDE Connect) If you are having a different issue (intermittent loading, pictures not loading, etc.), please make a new bug (check for duplicates first!) (In reply to Simon Redman from comment #99) > Since this issue has not been reported in awhile, I am going to believe that > my "solution" is working for all devices. > > If you are having the issue described here where NO messages load when you > launch the KDE Connect or GSConnect SMS chat apps even though you have the > latest Google Play / FDroid version of the KDE Connect Android app please > post on this issue. > (Reminder that, by design, Signal and other secure/encrypted messaging apps > will not work with KDE Connect) > > If you are having a different issue (intermittent loading, pictures not > loading, etc.), please make a new bug (check for duplicates first!) this is not repored but it still not works on any phone i have like huawei p smat z (In reply to Simon Redman from comment #99) > Since this issue has not been reported in awhile, I am going to believe that > my "solution" is working for all devices. > > If you are having the issue described here where NO messages load when you > launch the KDE Connect or GSConnect SMS chat apps even though you have the > latest Google Play / FDroid version of the KDE Connect Android app please > post on this issue. > (Reminder that, by design, Signal and other secure/encrypted messaging apps > will not work with KDE Connect) > > If you are having a different issue (intermittent loading, pictures not > loading, etc.), please make a new bug (check for duplicates first!) Issue persists for me, Huawei P30 Pro, I can see received SMS notification with message preview, I can send sms and they persist in phone, however I cannot browse messages. KDE Connect installed via Play Store on 4.10.2021, GSConnect installed 3 minutes earilier. Does anyone else with a *non-Huawei* device still have trouble accessing SMS history? If the only remaining problematic device family is Huawei, I am tempted to open a new bug to discuss those devices in particular. (In reply to Simon Redman from comment #99) > Since this issue has not been reported in awhile, I am going to believe that > my "solution" is working for all devices. > > If you are having the issue described here where NO messages load when you > launch the KDE Connect or GSConnect SMS chat apps even though you have the > latest Google Play / FDroid version of the KDE Connect Android app please > post on this issue. > (Reminder that, by design, Signal and other secure/encrypted messaging apps > will not work with KDE Connect) > GSConnect still communicates very unreliably around SMS history with my phone, Oppo (R15) CPH1835. So this issue is not limited to Huawei phones. See my previous details from Comment #98. My symptoms: - The message screen on my computer takes several minutes to populate with historical message data. - If I try to send an SMS from my computer, the transmission to the phone and sending of SMS can take several minutes, and may not happen at all. - The message screen intermittently (approximately once per minute) displays an error message blue banner near the top that says "Device is disconnected". It typically lasts only for a few seconds. Hi Tom, Responses inline (In reply to Tom Colley from comment #103) > (In reply to Simon Redman from comment #99) > > Since this issue has not been reported in awhile, I am going to believe that > > my "solution" is working for all devices. > > > > If you are having the issue described here where NO messages load when you > > launch the KDE Connect or GSConnect SMS chat apps even though you have the > > latest Google Play / FDroid version of the KDE Connect Android app please > > post on this issue. > > (Reminder that, by design, Signal and other secure/encrypted messaging apps > > will not work with KDE Connect) > > > > GSConnect still communicates very unreliably around SMS history with my > phone, Oppo (R15) CPH1835. So this issue is not limited to Huawei phones. > See my previous details from Comment #98. My symptoms: > - The message screen on my computer takes several minutes to populate with > historical message data. This is a truism of the current implentation of KDE Connect's SMS interface. See https://bugs.kde.org/show_bug.cgi?id=442918 for more explanation. > - If I try to send an SMS from my computer, the transmission to the phone > and sending of SMS can take several minutes, and may not happen at all. This isn't related to this bug, feel free to open a new bug (I don't believe there is one open for this) > - The message screen intermittently (approximately once per minute) displays > an error message blue banner near the top that says "Device is > disconnected". It typically lasts only for a few seconds. I can't specifically comment on GSConnect's behavior, but this sounds like it is briefly losing connection. Possibly due to Android's inherent behavior of wantonly killing KDE Connect... Samsung S7, google Messages I get a history, but it is composed of recent dialogs and old and very old deleted dialogs. (In reply to Philippe ROUBACH from comment #105) > Samsung S7, google Messages > > I get a history, but it is composed of recent dialogs and old and very old > deleted dialogs. Hi, Are you *missing* any conversations? If not, then you are experiencing a different bug. If a conversation has actually been deleted, it would not be possible to retrieve it (it's deleted... It's gone). Are you sure you haven't archived it? Archival/Spam/etc. are all functions of Google's Messages apps and can't be accessed from any other application. Some conversations were archived. I deleted them. I don't need them, except one. Others are blocked or spam. It's not normal you display them. "Google messages" does not display them. (In reply to Philippe ROUBACH from comment #107) > Some conversations were archived. I deleted them. I don't need them, except > one. > Others are blocked or spam. > > It's not normal you display them. "Google messages" does not display them. This almost definitely a bug in GSConnect and not KDE Connect. GSConnect effectively has "ghost" maintainers now, but I'd advise you to open a bug there or just clear the cache using the device settings window. >> just clear the cache using the device settings window.
There is no command to clear the cache in kdeconnect settings
i sent a bug report. https://bugs.kde.org/show_bug.cgi?id=443657 >> This almost definitely a bug in GSConnect and not KDE Connect
you speak about gsconnect but gsconnect is not installed.
(In reply to Philippe ROUBACH from comment #111) > >> This almost definitely a bug in GSConnect and not KDE Connect > > you speak about gsconnect but gsconnect is not installed. Sorry, I was following the conversation earlier and thought you were the same reporter. Making as resolved since nobody appears to be having problems post my workaround. I have the same issue. I have read the thread, but the link for the apk is outdated and no longer available. I am desperate to fix this, but I am not an expert. It is marked as resolved/fixed HOW? PLEASE. KDE Connect works well, except for when I click on "SMS messages". The GUI opens, but the message history never appears, and the window just hangs with a spinning logo. Device Information: Manjaro KDE HUAWEI P30 lite Please advise. (In reply to jackdinn from comment #114) > ... > > Please advise. All the fixes discussed in this thread have been integrated into the release version of the app for at least a year. Given that, any discussion involving problems you are having are probably different. Please make a new bug, share your desktop information (version, OS, etc.) as well as your Android device information (make and model, KDE Connect version, etc.) and Android logcat (https://userbase.kde.org/KDEConnect#KDE_Connect_Android_app_crashes) (To anyone who finds this bug in the future: Same request to you. Please search for open bugs involving your exact symptoms, or make a new bug.) |