-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
dissabling background processes
- Thread starter stvs
- Start date
MLSS
Android Expert
Some apps need to run in the background for your device to perform at optimal levels. Some apps "run" in the background but use little to no resources until you or the device needs it to.
I'm not sure what kind of device you have so if you are having problems with your device lagging or running slower than you think it should/usual, tell us what kind of device you have along with what OS it is running and how much RAM you have.
I'm not sure what kind of device you have so if you are having problems with your device lagging or running slower than you think it should/usual, tell us what kind of device you have along with what OS it is running and how much RAM you have.
That option is really for development troubleshooting and not to boost performance. What you will probably do is to either reduce performance by having processes continually load an unload as your use calls for them, or cripple the phone by having necessary background processes fail to to load when needed.
If you are having performance issues, freeing ram is not the place to look. Android makes every attempt to use all available ram all the time, which is a good thing.
Let us know if this is a general question out of curiosity or you are actually having a problem. (and as @MLSS said, let us know device and Android version.
)
If you are having performance issues, freeing ram is not the place to look. Android makes every attempt to use all available ram all the time, which is a good thing.
Let us know if this is a general question out of curiosity or you are actually having a problem. (and as @MLSS said, let us know device and Android version.
)
Going to respectfully disagree in part guys. 
HTC has actually advised using that option in a number of cases.
For a ram-limited phone that goes into ram thrashing on trying to multi-task large memory apps, it's a pretty good solution.
Uses Android task management, just tightens up the multitasking parameters under the hood.
No service orphans, and within bounds of the rules.
But - use judiciously. Start at the most and work your way down.
And pretty much not at all if your device is not experiencing a real multitasking problem.
^ On this point we all agree.
HTC has actually advised using that option in a number of cases.
For a ram-limited phone that goes into ram thrashing on trying to multi-task large memory apps, it's a pretty good solution.
Uses Android task management, just tightens up the multitasking parameters under the hood.
No service orphans, and within bounds of the rules.
But - use judiciously. Start at the most and work your way down.
And pretty much not at all if your device is not experiencing a real multitasking problem.
^ On this point we all agree.
Okay. 10-4. Understood. A wink is as good as a nod to a blind man.
Just for argument's sake, let's say I check the box ... well, it's not really a box, and there is no check mark, but you know what I mean ... next to limit to 2 process and my phone requires 3 to do what I'm asking it to do?
Does it task switch? or does it fail at the unloaded process task?
Just for argument's sake, let's say I check the box ... well, it's not really a box, and there is no check mark, but you know what I mean ... next to limit to 2 process and my phone requires 3 to do what I'm asking it to do?
Does it task switch? or does it fail at the unloaded process task?
Now we enter the charted waters of overloaded terms - where the words mean different things at different times.
We often separate processes as apps and services.
Or say that apps are really apps and service processes.
Or etc etc etc.
So what does developer options mean by the term processes?
Let's ask it about process stats and see what we get -
We get apps - not service processes.
And you don't need many simultaneous apps being run in the background.
Two becomes an obvious limit if you want a keyboard with something.
Three might be a good idea if you want the phone to keep working (although, the phone is on its own priority, so it always wakes and launches no matter what you're doing). Having the launcher still alive while using a browser and a keyboard is probably a good idea but not actually required.
Could this have other consequences I didn't cover?
Yeah.
But minor if faced with a phone going through thrashing and things crashing randomly.
So as I said - only when necessary and used judiciously. And not at all if not necessary.
PS - you can do quite a bit with one foreground app and just four in the background.
Apps get cached by this so it's just shuffling a smaller deck into active memory.
Faster?
No.
Working when otherwise broken due to a ram-app issue?
Often yes.
Last edited:
So you want to know what's in this thread -
http://androidforums.com/threads/pu...k-killers-ram-optimizers-and-the-like.896663/
No. They're really not.I don't think so. Some of your apps need background processing so i guess it's a bad idea. Why don't you try other ways like System boosting apps. They are helpful