https://bugs.kde.org/show_bug.cgi?id=512315
--- Comment #3 from John <[email protected]> --- (In reply to TraceyC from comment #2) > There isn't enough information to say this is the same bug as 439228, > removing as a duplicate. Thank you very much TraceyC! In the meantime I did a full / clean re-install of LineageOS 23 (Android 16) on my phone and started the pairing again. I noticed a few things about KDE Connect app on the phone: It doesn't detect the Wi-Fi being turned OFF! It doesn't detect the Wi-fi being turned ON, but not connected to any network! It doesn't detect the AFWall+ firewall being installed and turned on! It doesn't detect the LAN access rule being OFF (not ticked / checked) in AFWall+ firewall! Other things that I noticed is that the default device name that KDE Connect uses is the Phone model, like SM-*** instead of using the one that I specified in the Android settings control panel! The notification also shows "Request pairing from SM-*** instead of using at least the name that I have manually changed / set in KDE Connect app! I disabled both AFWall+ (which has been recently been updated to version 4.0.1 after 2 years without updates) on the phone and OpenSnitch (recently updated to version 1.8.0) and even like that, with both disabled, KDE Connect app from the phone cannot find anything initially. After a while the computer appeared in in the app on the phone and I could send a pairing request. It's either the temporary enabling of the MDNS services that fixed it or the disabling of both firewalls or all toghether. I tried to pinpoint it more exactly by cleaning the app cache + store / uninstall it and then installing it again from F-droid with firewalls being turned on and MDNS not being turned on and it can still find the computer. I think something remained cached from the first time. I would still like to have for the app on the phone the Wi-Fi adapter status, the Wi-Fi network connection status, AFWall+ installation status and AFWall+ rule for KDE Connect status detected by the app for the next time this happens. We cannot figure out which one is blocking this process, especially when there are multiple ones, like in my case: 1. Wi-Fi not being ON. 2. Wi-Fi network not being connected. 3. AFWall+ being installed and KDE Connect not having LAN access. 4. OpenSnitch being installed on the computer and KDE Connect not being allowed. Without more granular detections and error message is very hard to figure out which is the one or ones that is the culprit. -- You are receiving this mail because: You are watching all bug changes.
