*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY on KDE connect 1.34.4 for Android, trying to connect to Steam Deck (SteamOS 3.7.17 Builld 20251027.1), running KDECOnnect (kdeconnect.app 24.12.0), the Android application cannot pair unless I enable MDNS device discovery that is noting that I need to file a bug, or using the Beta bluetooth connection. I am filing the bug due to the app asking me to in the settings. Also bluetooth pairing is not always working, as I need to first pair with MDNS and then enable Bluetooth to make it connect STEPS TO REPRODUCE 1. Install KDE connect 1.34.4 for Android 2. Open Steam Deck 3. Conenct to the same network for both devices 4. Optional - enable Bluetooth 5. Nothing appears in the Android app 6. GO to kdeCOnnect app settings in android and enable MDNS 7. Refresh the Android app (drag down) 8. Steam deck appears 9. Connect to Steam Deck 10. Disable MDNS 11. Enable Bluetooth 12. refresh Android app (drag top down) 13. Steam deck appears OBSERVED RESULT Please check steps above EXPECTED RESULT We should not have to change any settings and discover the steam deck by default SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: SteamOS 3.7.17 Builld 20251027.1 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 ADDITIONAL INFORMATION Please check Summary and Steps
I don't have a Steam Deck to try, but last time I tried, without MDNS (about 2 weeks ago), I had a similar problem to you. Besides trying with a laptop running latest KDE software, instead of a Steam Deck, the other differences were: Using KDE Connect 1.34.3 (one minor release behind you) from F-droid. and using the AFWall+ application firewall, from F-droid too. I got no response yet on my bug report, if the problem is the firewall or something else: https://bugs.kde.org/show_bug.cgi?id=512315