Bug 435047

Summary:	Manual option for starting and stopping of KDE Connect service
Product:	[Applications] kdeconnect	Reporter:	Paralel <paralel.nonrecurently>
Component:	android-application	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	REPORTED ---
Severity:	normal	CC:	aoeui, cwo.kde, liqsliu, pankajsunal123, sherkhan30452, xzntytb
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Android
OS:	Android 10.x
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Paralel 2021-03-28 04:35:52 UTC

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

Comment 1 cwo 2024-08-05 23:35:07 UTC

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

Comment 2 cwo 2024-08-05 23:38:46 UTC

*** Bug 490294 has been marked as a duplicate of this bug. ***

Comment 3 cwo 2024-08-05 23:38:48 UTC

*** Bug 479012 has been marked as a duplicate of this bug. ***

Comment 4 cwo 2024-08-05 23:38:53 UTC

*** Bug 474290 has been marked as a duplicate of this bug. ***

Comment 5 cwo 2024-08-05 23:38:56 UTC

*** Bug 439435 has been marked as a duplicate of this bug. ***