https://bugs.kde.org/show_bug.cgi?id=523424
Bill <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Bill <[email protected]> --- Reproduces on current master. Adding my test here since it covers Simon's ask for a modern version. Setup: - Desktop: kdeconnect-kde master aee1439f8 (2026-11-04), daemon and SMS app run straight from the build dir. I had to leave out the mousepad and shareinputdevices plugins because Ubuntu 24.04's libei is too old for them. Neither touches SMS. - Phone: Pixel 10 Pro XL, GrapheneOS 2026110201 (Android 17), KDE Connect Android 1.37.0. Default SMS app is the bundled Messaging app (com.android.messaging). Steps: 1. Open a conversation with another person in the KDE Connect SMS window. 2. Send a text. 3. Check the phone, check the desktop. Result: the text shows up in Messaging on the phone, but doesn't show up in the desktop conversation. It only appeared after I enabled the app-op workaround (below). Analysis: On the phone, every message sent from the SMS window since July is stored with creator=org.kde.kdeconnect_tp and restricted=1. Everything Messaging writes is restricted=0. That includes a reply I sent from the desktop notification's quick reply (on my regular, older build): the phone hands that one to Messaging, the row ends up creator=com.android.messaging restricted=0, and it echoed to the desktop in about a second. Same desktop, same phone, same conversation. The only difference is who wrote the row. To make sure the desktop wasn't dropping anything, I put a log line in the desktop SMS plugin where the packet comes in and asked the phone for the 10 newest messages in that conversation. The packet had the 10 newest restricted=0 messages, including sent ones written by Messaging, and none of the 7 restricted=1 messages in that range. So they never leave the phone. The desktop version can't matter here. This is a different problem from bug 517659, which I reported in March. That one was the echo stopping after a WiFi reconnect. Here the messages are missing even when the desktop explicitly requests the conversation. Workaround from comment 1 works for me (tested on my regular build): adb shell appops set --uid org.kde.kdeconnect_tp READ_RESTRICTED_MESSAGES allow adb shell am force-stop org.kde.kdeconnect_tp After relaunching the Android app, messages sent from the SMS window echo again, and the ones that were hidden showed up too. I haven't tested whether it survives a reboot yet. For timing: in my SMS database the last KDE Connect row with restricted=0 is from 2026-07-01 and the first with restricted=1 is from 2026-07-07. All 246 KDE Connect rows before that are restricted=0, all 44 since are restricted=1, and no row written by Messaging is flagged. That lines up with the original report in comment 0 (July 23, "working fine a few weeks ago"). ### All testing and debugging (and this comment) relied heavily on Fable 5.1 Medium. I had Claude review and tune many times. This may have errors but it is not slop, and I understand what I'm posting (to the degree I am able as a non-coder) -- You are receiving this mail because: You are watching all bug changes.
