Keep app running in the background

[pennilessSplatter]

Is your feature request related to a problem? Please describe.
Man. It's very annoying that sd maid se seems to kill itself of I were to close it using the recent apps menu. Regular sd seemed to just remain running and if it completed a task it would remain open for when you need it so you don't have to do another scan all over again. It's really convenient when you need it. And unfortunately it's just missing from sd maid se. Sd maid se should really aim to be more like regular sd maid but with some optimizations for modern android. Like if it ain't broke don't fix it lol. But I'm still greatful this app exists so don't get the wrong idea

Describe the solution you'd like
Keep the app running or store the cache responsible for the finished scans. idk. Just make it so that when I close the app it doesn't just forget everything it scanned for. (of course if it's forced stopped and it forget, that's fine).

Describe alternatives you've considered
Regular Sd maid

I have considered making the coffee myself but both me and myself decided against it.

Describe why this would be in the interest of all users
A little convenience can go a long way. There is no sich thing as dimishing returns (sometimes)

Additional context
Thanks for the support of this app!

[d4rken]

Isn't the expected behavior for an app to be killed if you swipe it from recents?

That this does not kill SD Maid 1 is more of a bug than a feature 😅.
SD Maid 1 uses older mechanisms with a foreground service that is already starting to behave differently on newer Android versions.

Google is aggressively working against any type of "long running" operations or "foreground" apps. All in the name of improved battery life (because some devs abuse this).

I predict Google coming down even harder on foreground and long-running operations. Building a solution based on that is not future proof.

The right approach would be to cache the results, but this is getting complicated, fast. Some brainstorming:

• The device constantly changes. Working with cached data can lead to false-positives.
  • If you delete based on old (old could be something we define though) results the device may no longer be in a state later, where these files should be deleted.
  • SD Maid might not be in the same state anymore.
  • Previous scans could have been performed with permissions that are no longer available.
  • Does this "cache" need to be deleted between updates?
  • Corpse files belonging to apps that are already installed again?
  • Duplicates that are no longer duplicates.
• Saving the results would require serializing them.
  • The current data structure are not all serializable.
  • How large are the results from users? Is the user low on space, do we have enough space?
  • How long does it take to save/load the data? Loading indicators? Can this be cancelled?

It's a lot of upfront work, and then on-going work to keep data cacheable... Not sure this is worth it 🤔

I'll look a bit into result notifications and whether this can keep the app in memory longer, but prevent the app from being killed when swiped from recents, seem like an anti-feature 🤷

[Zoli1959]

Üdv. Samsung s21 Android 14 6.1 one UI. használom a SD Maid Se pro programot az automatizált törlés nem fut végig a végén nekem kell törölnöm ..shizukut használom..van ötletetek mi lehet a gond. Köszönöm

[lawson85]

Follow steps at dontkillmyapp.com it may help but is not gaurenteed.

An alternative for our developer is if we can set SDM2 as a device administrator or device assistant, it would be less likely to be killed