Created attachment 138311 [details] kdeconnect add wifi button not showing up in trusted networks menu SUMMARY So i want to add my wifi to trusted network, but the "Add WiFi" button isn't showing up even though I'm connected to wifi, disabling allow all, and allowing location. It only happened on my sansung a6 phone, not my other phone. STEPS TO REPRODUCE 1. Open KDE Connect (on android). 2. Goto settings > trusted networks. 3. Connect to wifi. 4. disable "allow all". 5. Make sure to grant location permission to kde connect. OBSERVED RESULT The "Add WiFiName" Button didn't show up. EXPECTED RESULT The "Add WiFiName" Button should show up on the bottom. ADDITIONAL INFORMATION im sorry if my explanation bad.
I think that it isn't the same problem that asalmaubijiayam is facing, but in my case (Android 13) the button doesn't appear, because TrustedNetworkHelper.currentSSID() always gets "<unknown ssid>" as the Wi-Fi SSID. The currently used API (https://developer.android.com/reference/android/net/wifi/WifiManager#getConnectionInfo%28%29) was deprecated in Android 12 (API level 31) and the SSID of current network on newer systems (Android 12+) can be obtained by registering a callback with FLAG_INCLUDE_LOCATION_INFO.
A possibly relevant merge request was started @ https://invent.kde.org/network/kdeconnect-android/-/merge_requests/356
I first thought I just couldn't find the option, but it seems I am affected by the same bug. This is on a Fairphone 3 with Android 13. The App has Location permission (including precise location). I thought maybe running NetGuard might be the problem (thinking maybe the app only sees the local VPN but not the WiFi), but after disabling it, I'm still not seeing an option. This also to my knowledge has never worked for me going back to Android 9 that it originally shipped with.
I can confirm the absence of such a button too. There seems to be no way to use the Trusted Networks feature at this moment. Device: Xiaomi Mi MIX 2S "polaris" OS: Android 15 (LineageOS 22.2) App Version: 1.34.3 (but I had the same issue in all previous versions for at least a year, including when I still was running Android 13)