4 ms·

The one thing I dislike, is the trouble to finish the application in a sane way: https://bugs.kde.org/show_bug.cgi?id=423497 https://bugs.kde.org/show_bug.cgi?

• goda90 11mo ago
  I can't say I'm experienced with Android development, but is there something about this issue that makes it hard for a volunteer to submit a PR? Seems like it should be just an OS API call or something.
  • immibis 11mo ago
    Android doesn't really have such a thing as quitting an app. You're meant to just stop doing stuff when off screen, and let your app be evicted in LRU order (or whatever order is actually used). If your app does background stuff you should have a settings toggle to do the background stuff or not, and when it's on and the phone is on, you do the background stuff.
    • ranger_danger 11mo ago
      This is not true: https://stackoverflow.com/a/40231289 https://stackoverflow.com/a/40231289
      • immibis 11mo ago
        This closes an activity - the user interface of an app - not an app. In Windows terms, this is DestroyWindow, not ExitProcess. You can also exit an Android process, of course. It's probably what you're looking for, but it's weirdly inconsistent with the overall user experience and you should try to make something consistent instead. Even closing a top-level activity is weird.
• alright2565 11mo ago
  This doesn't seem needed to me, I've never seen an android app have a way to close it. Or any kind of battery life impact from KDE Connect for that matter.