https://bugs.kde.org/show_bug.cgi?id=368438
Matt Whitlock <k...@mattwhitlock.name> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |UNCONFIRMED
--- Comment #5 from Matt Whitlock <k...@mattwhitlock.name> ---
This failure mode has recurred several times since I last commented.
• I can always bring functionality back by rebooting my phone, but obviously I
should not need to do this.
• Merely stopping the app's "BackgroundService" and then relaunching the app's
main activity does not fix the problem.
• Force-stopping the app entirely and then relaunching its main activity also
does not fix the problem. (Although the app's uptime does reset upon the Force
Stop request, the app immediately restarts to start its "NotificationReceiver"
service. The "BackgroundService" is not started until the app's main activity
is launched.)
• Disabling the notifications permission allows the app to be fully stopped.
(It disappears from the list of running services upon a Force Stop.)
Relaunching the main activity still does not fix the problem.
To reiterate, the problem is that the KDE Connect app does not communicate with
the computer unless its main activity is in the foreground. The background
services continue running, but they do not maintain connectivity with the
computer. Rebooting the phone restores background connectivity.
The failure mode always seems to begin when the phone is removed from the WLAN
for a while. Upon reconnecting to the WLAN, the app's background service does
not maintain connectivity with the computer.
--
You are receiving this mail because:
You are watching all bug changes.
