https://bugs.kde.org/show_bug.cgi?id=425381
--- Comment #11 from Shiro K. <shiro_c...@protonmail.com> --- I think that is intended and correct behaviour. On Android 10+, Wifi information is directly tied to the location permission. If location is off on-device, KDE connect can't get the SSID. This is Android behaviour and it is due to the fact that a SSID (especially a unique one) can be traced to a location very easily. Unfortunately you need to keep location on if you use trusted networks, otherwise auto-discover does not work. You can circumvent this if you "Add devices by IP". Also current connected devices connections shouldn't be affected if you toggle location on/off. Also (this is unrelated to this bug) on Android 10+ for a app to get location when in background, a special permission is needed; ACCESS_BACKGROUND_LOCATION (shows as "Allow all the time" instead of only "Allow only while using the app"). KDE Connect currently doesn't ask for this permission. To get this permission onto the Play Store you need to be ask/review with Google with a good reason to get it (not sure if KDE Connect would be approved) (https://support.google.com/googleplay/android-developer/answer/9799150). So whenever you connect to a trusted network you need to open the app for autodiscover to kick in, because KDE Connect can't get the SSID when not open (in the background). You can build the app yourself with this permission to make KDE Connect connect to the PC even when your phone is locked. I should probably open a bug/pull request for this. -- You are receiving this mail because: You are watching all bug changes.
