it is possible to manage auto start app/services ?

RegFor

i wonder if it is possible to block app to auto start in background (ex: binance)

Hulk

Hello,

There are several ways to block an app from being able to autostart:

Separate user profile. You can put the app in question in a separate user profile. By "ending session" of that profile, the app in question will not be able to autostart or run in the background.
Force stop. If you Force stop an app, it will not be able to run in the background or autostart.

Fay_Wilmont

Hulk Force stop. If you Force stop an app, it will not be able to run in the background or autostart.

Since this thread got revived, I just want to say that as far as I know, this is simply not true. Force stopped apps will still autostart after a reboot, and can automatically be restarted even before a reboot in certain scenarios .

DeletedUser28

I wonder about the opposite problem. Is there any way to get an to autostart after rebooting?

DeletedUser29

DeletedUser28 As far as I know, there's no system option to force it, but is instead depends on if the specific app supports it. E.g. Syncthing has a toggle for auto-start on boot to control that.

[deleted]

DeletedUser29 I used an Automation app off FDroid to detect when a certain app doesn't run and start it. It worked mostly. The only problem is, I can't get the Automation app start on boot.

Byku

I had this problem with KDE Connect. I wanted it to run only when in use and not to start on boot. The former can be achieved by disabling background permission in the battery setting. The latter however still occured. So I used Shizuku+App Ops to disable run foreground service permission. That seems to have stopped the app from autostarting on boot. Is there a better way? It is baffling that Android for all of its restrictive permission model allows just any random app to declare itself to autorun without asking the user first.

Fay_Wilmont

Byku It is baffling that Android for all of its restrictive permission model allows just any random app to declare itself to autorun without asking the user first.

Several vendors (e.g. Xiaomi, OnePlus) offer a toggle to disable autostart of apps on boot, but indeed it is not native to AOSP, and Google and Motorola for example don't have it. You'd think GrapheneOS would offer this functionality, but it doesn't? (I have yet to install it.)

mar2112

Fay_Wilmont I agree. Send like a security issue to have apps start on their own without operator permission.

Byku

Fay_Wilmont

You'd think GrapheneOS would offer this functionality, but it doesn't? (I have yet to install it.)

It doesn't.

Force stopped apps will still autostart after a reboot, and can automatically be restarted even before a reboot in certain scenarios .

Even if it'd work like that it would hardly improve anything. So now instead of manually stopping an app after reboot I have to manually stop it each time after use.

DeletedUser370

Fay_Wilmont You'd think GrapheneOS would offer this functionality, but it doesn't? (I have yet to install it.)

Well, there is a feature request for this specific feature, with a developer commenting on its relevance here: https://github.com/GrapheneOS/os-issue-tracker/issues/5710#issuecomment-3037271504

Please note that the GrapheneOS developers have expressed that, in general, users who want to "+1" or add their vote to a feature request, react to the feature request with an emoji instead of posting new "I want this too" comments. Please also note that I don't speak for the GrapheneOS project.

schweizer

DeletedUser370 This feature request is not about autostart. Is there a feature request already specifically for autostart?

It is bizarre that apps that are explicitely revoked background usage run im the background because they autostart. It is not only about privacy but also battery usage.

What does the background usage toggle do then? Does it only work after the first manual usage of the app or does it not do anything at all? Or does it only work on apps that do declare themselves as non-autostart?

GrouchyGrape

schweizer private space solves this issue nicely. Any apps I know I don't use often, get placed in there. It's only open while I'm using one of those apps, then is promptly closed afterward.

schweizer

GrouchyGrape private space solves this issue nicely.

No it does not. It is a workaround at best. Do the apps that autostart not autostart after unlocking private space?

I want to use private space for google apps. Private space may be on for a long time depending on usage.

GrouchyGrape

schweizer No it does not.

You say it doesn't, I say it does. Who's right?

schweizer

GrouchyGrape A solution is a method that fully resolves a problem by eliminating its root cause. The root cause is that the disallow background usage toggle is not working. A workaround is a temporary measure used to bypass or mitigate the impact of a problem when a permanent solution is not yet available. Such as using a secondary profile.