https://bugs.kde.org/show_bug.cgi?id=512595
John <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from John <[email protected]> --- Glad to see another report about this problem on Android 16. As I was testing with Lineage OS 23.0 ( wich is based onAndroid 16), KDE Connect and AFWall+ from F-droid and it didn't work for me. At that that I didn't even know that there is a MDNS toggle in the settings. So I made a bug report to bring awareness that it doesn't work and to ask / figure out which one of all these is the culprit. Nobody ansswered: https://bugs.kde.org/show_bug.cgi?id=512315 So I still don't know if it's Android 16 itself? Is the the LineageOS version of the Android 16 (version 23.0)? Is the fact that I used AFWall+ appliction firewall only with LAN permission for KDE Connect? Is the fact that I didn't knw about MDN and I didn't turned it on? In my opinion, the app should do a better job at informing us of what is doing exactly, which processes is calling, on which ports and what are their results / return values! There is no point to hide so much information in an open source app. Especially when the things are not working and you have to figure out if the problem it's at the Android OS itself, the application firewalls or VPNs installed on it or on the other side, at the computer. Please give us more information about what happens behind the scenes when the app starts its discovery process! -- You are receiving this mail because: You are watching all bug changes.
