https://bugs.kde.org/show_bug.cgi?id=508820
--- Comment #7 from [email protected] --- Independent confirmation of the root cause from comment 5, on different hardware: Android 16, Xiaomi POCO F7 Pro (HyperOS), KDE Connect 1.36.0 from F-Droid, desktop kdeconnect 25.12.3 on Kubuntu 26.04 (BlueZ 5.85), pure Bluetooth, no common IP network. Every connection initiated by the desktop is dropped right after the identity exchange (desktop log: "Handshaking done (I'm the new device)" -> "It is a new device" -> "socketDisconnected"), so pairing over Bluetooth is impossible from the desktop side. The stale `sockets` entry left behind by the use{} close also seems to block the phone's own client path afterwards: before the fix, "Refresh" on the phone never reached the desktop (btmon on the desktop showed no SDP/RFCOMM traffic at all); with the fix it connects immediately. With master (e3394bbd) + the same change (no use{}, close only on failure, and also release connection and `sockets` entry on an invalid identity packet), built as debug APK: desktop connects and the link stays up, pairing over Bluetooth works, ping both ways, automatic reconnect after toggling Bluetooth on the phone (~20 s), refresh in the app connects directly. -- You are receiving this mail because: You are watching all bug changes.
