https://bugs.kde.org/show_bug.cgi?id=471313
--- Comment #5 from Pedro V <voidpointertonull+bugskde...@gmail.com> --- The minimal adb experience should already cover the majority of needs as if adb is already working for you, then the logcat part should be trivial, but just to have everything for starting from scratch, here's what's needed to get the adb part covered: https://developer.android.com/tools/adb#Enabling Then logcat is really easy to deal with as there's even a dedicated adb command for it. I just went with the following to be able to handle all the output easily: adb logcat | tee adb.log This way you get to have a log file you can process more conveniently with your preferred text editor instead of looking around in the terminal which usually offers more limited ways to deal with the amount of text you'll get spammed with. KDE Connect messages are apparently generally prefixed with "KDE/", and most messages about KDE Connect generally contain "org.kde.kdeconnect", although the later isn't that interesting in this case. On the "KDE Connect Devices" screen there's a "Refresh" menu point which should trigger the issue conveniently without the need of fiddling with network connections. If you are affected by the same problem I've seen, then you'll see something like: ``` KDE/BackgroundService: onNetworkChange KDE/LanLinkProvider: identity packet received from a TCP connection from [...] KDE/LanLinkProvider: Starting SSL handshake with [...] trusted:true LanLinkProvider: Starting handshake KDE/LanLinkProvider: identity packet received from a TCP connection from [...] KDE/LanLinkProvider: Starting SSL handshake with [...] trusted:true KDE/LanLinkProvider: Handshake as client successful with [...] secured with TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA KDE/LanLinkProvider: Creating a new link for device [...] updateDeviceInfo: Updating supported plugins according to new capabilities LanLinkProvider: Starting handshake ``` Then later there should be quite noisy "Socket closed" and "Socket is closed" errors, but there's a whole lot more sign of life in-between confirming that things are getting fired up for real, even if not for long. The point is to see whether the issue is the originally suspected "won't detect" problem, or it's really the stays connected only for a few milliseconds because of silly issues problem I'm seeing. -- You are receiving this mail because: You are watching all bug changes.
