Android 3.1 introduces Launch controls on stopped applications. However, there are no such features on android 2.3, some 4.X devices didn't implement it well. Furthermore, there are some way for apps to wakeup some stopped apps.
"Prevent Running
" hajacks several system API to prevent not-in-use apps in prevent list
from running or keep running. Furthermore, it applies to system apps too, specially, support google-family apps(GAPPS
).
Not-in-use packages in prevent list
can only run:
NOTE: When Google Play Services(GMS
) and related apps are in prevent list
, only GAPPS
and GCM
-apps can use it. However, you cannot receive GCM
message if GMS
is not running.
WARNING: Don't prevent system
apps nor daily apps, otherwise, you may miss important message.
WARNING: Don't prevent "Xposed Installer
", otherwise the module won't active when you update it.
"Prevent Running
" should work from android 2.3 to 6.0. However, I mainly use 5.1.
Prevent Running
", activate it in "Xposed Installer
", reboot.Prevent Running
", then add/remove application to/from prevent list.back
or remove it from recent task to exit, and press HOME
for pause."Prevent Running
" would keep non-"service" processes, of cource it cannot turn to "service".
This process contains background code that is expendable.
This process is empty of any actively running code.
This process is running the foreground UI; that is, it is the thing currently at the top of the screen that the user is interacting with.
This process is running a foreground service, for example to perform music playback even while the user is not immediately in the app. This generally indicates that the process is doing something the user actively cares about.
This process does not exist.
This process is not something the user is directly aware of, but is otherwise perceptable to them to some degree.
This process is contains services that should remain running. These are background services apps have started, not something the user is aware of, so they may be killed by the system relatively freely (though it is generally desired that they stay running as long as they want to).
This process is running the foreground UI, but the device is asleep so it is not visible to the user. This means the user is not really aware of the process, because they can not see or interact with it, but it is quite important because it what they expect to return to once unlocking the device.
This process is running something that is actively visible to the user, though not in the immediate foreground. This may be running a window that is behind the current foreground (so paused and with its state saved, not interacting with the user, but visible to them to some degree); it may also be running other services under the system's control that it inconsiders important.