https://bugs.kde.org/show_bug.cgi?id=425381
shiro_c...@protonmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |shiro_c...@protonmail.com
--- Comment #5 from shiro_c...@protonmail.com ---
I have the same bug using v1.14.2 (Google Play and f-droid) and Android 10
(Pixel 3a). I've seen a few people with the same bug:
https://old.reddit.com/r/kde/comments/goxx2k/kde_connect_cant_add_a_trusted_network/
https://forum.kde.org/viewtopic.php?f=18&t=166179
This bug is already fixed on master branch as I can only reproduce it using
Play Store version. Given that the last release (v1.14.2) was 4 months ago the
changes didn't trickle down yet.
This commit 1a247eac
(https://invent.kde.org/network/kdeconnect-android/-/commit/1a247eacc9264c325715529e8749860c6dccfaba)
"Fix trusted networks on Android 10" is most likely the fix.
Android 10 changed the way privacy permissions work
(https://developer.android.com/about/versions/10/privacy/changes).
ACCESS_FINE_LOCATION permission is now needed to access WiFi information and
v1.14.2 only requests ACCESS_COARSE_LOCATION.
--
You are receiving this mail because:
You are watching all bug changes.
