Hehe yeah, this persisted over several days and through several reboots and on two different phones. No clue what changed as I understood iptraf to simply help me diagnose. But a run directly before and after running iptraf for the first time had different results, and now I am reproducing it every time.
I'll look closer into this when I'm back at the computer in about an hour. In the post on the KDE forum, they seem to get an error complaining about the version though, while in my case they don't show up at all when I attempt to pair. I've checked the things listed on the KDE Connect wiki, but those checks pass.
EDIT: UDP discovery was turned off on my phone, and turning it on allowed connection. All is good now!
Sweet! Here comes a random tidbit now that your problem is solved.
Easy screen mirroring of android to linux:
Prereqs:
Setup DHCP to always assign the same IP to the phone.
Install adb and scrcpy on the Linux machine.
Allow the linux machine to usb debug the phone.
Allow wireless debugging in the phone settings.
.bashrc function: #Connect to Android and view phone screen #Tip: If using PIN on lock screen you can unlock by entering PIN + Enter even if screen is black function phoneconnect(){ sudo adb start-server adb tcpip 2233 adb connect <phoneIP>:2233 scrcpy }
Simply write phoneconnect in terminal when both devices are accessible on the LAN and you can remote control your phone. Some applications will blacken the screen on the computer if sensitive data is shown.
Cheers, that's pretty cool! I've looked into scrcpy before, but never got around to testing it. The way you present it is super easy, so I will definitely give this a shot!
Regarding my problem, it seems it wasn't as fixed as I thought :p The connection issue described in the original post still comes once in a while, not sure what triggers it, but it usually resolves if I ping the device and run iptraf to monitor the traffic. Probably superstitious, seems weird to me that it should fix it. It also happened once between my laptop and my new machine, so it was not isolated to the phone after all.
I've already done that after having had very slow speeds in a room far away from the WiFi hotspot. But another thing I've noticed is that the TxPower-setting is very low (3 dBm), which I believe was the real culprit for the slow speeds. I think the max allowed value of this is 20 (according to a line in the dmesg output), so I've been wondering if I could just change this to a higher value. It is now placed close to the router, so I am thinking of connecting it by cable (I just don't have one at the moment) - maybe that could solve my other problem as well.
This is yet another problem, but do you know if the TxPower-setting could affect the Bluetooth-capabilities? I use a keyboard connected by Bluetooth. When I run the Dolphin Emulator, where I've set it to emulate a Bluetooth-adapter and search continuously for my Wii-remotes, it seems to interfere with the keyboard-signals.
I would try a LiveUSB with Fedora or another distro with a more up to date kernel and test my wireless card there, if wifi and bluetooth plays nice then you can install a new kernel on Linux Mint and probably have it solved that way.