https://bugs.kde.org/show_bug.cgi?id=461083
Bug ID: 461083
Summary: KDE Connect doesn't reconnect to device after powering
the PC on
Classification: Applications
Product: kdeconnect
Version: 22.08.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
### SUMMARY
***
My Android phone gets disconnected (or actually becomes unavailable) from KDE
Connect after my desktop loses some power to sleep, reboot or shutdown. It has
been happening for so long! The mobile app has battery optimization turned off,
even so it keeps disconnecting from the PC app. It doesn't unpair, thankfully,
unlike in another bug case, but I have to turn
the phone screen on and unlock it to get availability back, and this is
inconvenient and forgettable!
I read somewhere that this is a problem with Android 11, but if that were the
case, the Micro$oft app Phone Link I used
back on Windows would disconnect too upon every sleep or reboot, and it didn't!
Therefore it's a kdeconnect bug that
needs to be fixed.
I love KDE Connect! It's way better than Phone Link, plus it's free software
that doesn't spy on you. This is the one
and only major problem I found on it, for sure, and I hope it gets fixed soon.
***
STEPS TO REPRODUCE
1. Open KDE Connect plasmoid (or application) on PC
2. Shutdown, reboot or sleep the PC.
3. Turn it back on and look at the system tray.
OBSERVED RESULT
KDE Connect doesn't automatically reconnect, saying "paired device is
unavailable" instead. I have to turn the phone
screen on and even unlock it to make it available again.
EXPECTED RESULT
Said app would reconnect automatically, not requiring manual intervention from
the user.
SOFTWARE/OS VERSIONS
Linux: 6.0.2-arch1-1 (64-bit)
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
KDE Connect: 22.08.2 (PC); 1.19.1 (phone)
ADDITIONAL INFORMATION
It has happened on Kubuntu and Arch Linux, and it even happened on XFCE with
KDE Connect installed. I don't recall
correctly if it happened with GSConnect on Ubuntu, but maybe it did, because of
the shared codebase, or maybe not
because Gnome developers may've fixed this already, but not upstream.
--
You are receiving this mail because:
You are watching all bug changes.
