SUMMARY I'm using the lastest version available in F-Droid. Even if it wasn't originally running before being turned off, the application starts on its own every time the phone is turned on. Same thing happens if it's charging. Is this intended? Even if so, it would be nice to have the option to turn it off or prevent it from happening. STEPS TO REPRODUCE 1. Turn the device off | Plug device 2. Turn the device on | Skip to next step 3. App starts running OBSERVED RESULT App starts running for no apparent reason and can only be closed by force stopping it. EXPECTED RESULT App doesn't run unexpectedly and/or app has an option to stop itself. SOFTWARE/OS VERSIONS Android: 10 KDE Connect: 1.16.0
There are several feature requests about this; let's consolidate them into one. This one is the oldest I've found so far; I'm editing the Summary so that it fits more broadly. Things to keep in mind from merge requests regarding this: https://invent.kde.org/network/kdeconnect-android/-/merge_requests/115#note_22781 https://invent.kde.org/network/kdeconnect-android/-/merge_requests/269#note_716759
*** Bug 490294 has been marked as a duplicate of this bug. ***
*** Bug 479012 has been marked as a duplicate of this bug. ***
*** Bug 474290 has been marked as a duplicate of this bug. ***
*** Bug 439435 has been marked as a duplicate of this bug. ***
*** Bug 490886 has been marked as a duplicate of this bug. ***
I would like to add some additional context from recent testing across different Android devices. On several devices, the only reliable way to fully stop KDE Connect interaction is unpair the device, which requires pairing again later. Some vendor-specific Android variants (for example Samsung) provide partial system controls, but this behavior is inconsistent and not available on many devices. Because of this, users currently lack a simple, temporary way to disable KDE Connect without breaking the trusted pairing relationship. This creates friction for situations such as: * temporarily avoiding notifications or file transfers * conserving battery or background network usage * privacy when connected to public or mobile networks A Quick Settings tile that pauses/resumes KDE Connect locally—without removing pairing information—could provide a consistent cross-device solution aligned with modern Android interaction patterns. If this direction is considered acceptable from a UX and architectural perspective, I would be interested in working on an implementation for the Android client. I would appreciate any guidance from maintainers regarding feasibility or preferred design approach.
(In reply to Deeptangshu Saha from comment #7) > I would like to add some additional context from recent testing across > different Android devices. > > On several devices, the only reliable way to fully stop KDE Connect > interaction is unpair the device, which requires pairing again later. > Some vendor-specific Android variants (for example Samsung) provide partial > system controls, but this behavior is inconsistent and not available on many > devices. > > Because of this, users currently lack a simple, temporary way to disable KDE > Connect without breaking the trusted pairing relationship. > This creates friction for situations such as: > > * temporarily avoiding notifications or file transfers > * conserving battery or background network usage > * privacy when connected to public or mobile networks > > A Quick Settings tile that pauses/resumes KDE Connect locally—without > removing pairing information—could provide a consistent cross-device > solution aligned with modern Android interaction patterns. > > If this direction is considered acceptable from a UX and architectural > perspective, I would be interested in working on an implementation for the > Android client. > > I would appreciate any guidance from maintainers regarding feasibility or > preferred design approach. Goal is to match Phone Link UX: • No persistent notification • No foreground service • No “1 active app” • Full OFF state Pairing remains intact. Should this be implemented as: A) Full service stop B) Pause connections but keep service
A potential fix for the Quick Settings tile and background service lifecycle issues described in this report has been implemented and tested. Summary of changes: * Ensured the background service performs a complete shutdown when the tile is toggled off. * Prevented unintended automatic restarts caused by broadcast or network events while the user-paused state is active. * Aligned the Quick Settings tile UI state with the actual service state to eliminate delayed or phantom state changes. * Verified correct behavior across the primary usage flows: * Tile toggle ON/OFF * Opening the application resumes the service as expected * Manual shutdown does not trigger automatic restart * Network/broadcast events while paused do not restart the service A release-signed APK containing the proposed fix is available for testing at: https://invent.kde.org/network/kdeconnect-android/-/raw/c5faeaf06a7a8563e4e4f54a39f50c3d4a6c68e9/kdeconnect-android-quick-tile-implemented-release.apk This build is based on current master with only the service pause/resume behavior modified. Feedback, additional testing, or guidance on upstream integration would be appreciated.