Quote:
Originally Posted by Diversebydesign
When an app is "force closed" for all intents and purposes that app will NOT load into memory again unless you start it or something else does right? It cannot just arbitrarily open itself like an app could if it was just closed normally. Is that correct?
|
Not correct. Many apps can restart in memory again. If you look at a list of your currently running apps, and force close all but the system apps, you'll see a lot of them start up again. Usually they're monitoring something, like the weather apps will stay running to auto update info, mail apps will start up on their own to periodically check for new email, etc. Some, though, will run for arbitrary reasons simply because the programmer thought their app will run better. These are the apps I'll freeze until I need them, or will simply uninstall them as a matter of principle.
Quote:
Originally Posted by Diversebydesign
And what exactly does "locking" an app accomplish? I can assume what it means, but I would like to hear the actual function from someone who knows.
|
Locking apps will keep others from using them without the correct passcode. That's pretty much it. It can still run in memory and whatnot on its own.
But if you meant locking like completely shutting it down and not allowing it to run whatsoever, that's called "freezing." You can do this with a variety of app managers. It's a great way to take your bloatware completely out of the picture without losing the ability to restore them. When you're informed that an Android update is available (OTA update) you have to unfreeze them. Android needs all the stock bloatware to be present to perform a successful update.