https://bugs.kde.org/show_bug.cgi?id=410316
--- Comment #4 from leftcrane <leftcr...@tutanota.com> --- CONCLUSION: ========================================================= I've unpaired the device on in the Android app and then repaired. The connection works now and persists after resume from suspend. Problems still persist however: I've just unpaired the device again, to test - and now again I can't pair it back (the PC is not visible from the app). Experiencing the same crashes with kdeconectd. So clearly the pairing the extremely fragile. ========================================================= RELATED: I would strongly suggest adding an "soft unpair" feature, one that merely disconnects but saves all the permissions: 1. This would allow users to quickly unbork the app, which is important given the high failure rate of pairing. 2. Furthermore, the current "unpair" button is just dangerous, since users are given no warning that if they tap it all their app permissions will be lost. Many users will attempt to tap it in the hopes of re-establishing the connection - I know I did and was surprised when I had to re-enable all the permissions and settings (at least 20 taps, quite tedious) I have filed a separate bug for this here #410360 -- You are receiving this mail because: You are watching all bug changes.
