December 12th, 2011, 11:57 PM
|
#8 (permalink)
|
|
New Member
Join Date: Sep 2010
Posts: 2
Device(s):
Thanks: 0
Thanked 0 Times in 0 Posts
|
Never Addressed Concern
Quote:
Originally Posted by wayrad
Not so. Apps cached in memory do not use CPU cycles or battery power, except for the tiny amount required to load them into memory. Of course, if you use a task killer to constantly kill them, forcing them to constantly reload...well, those tiny bits will mount up amazingly.
In the atypical case that you truly have a runaway app that is eating battery because it is poorly coded, you should identify it with something like System Panel, and then delete it.
|
You simply stated what you already know to be fact, and never addressed the concern of the poster. Here it is again.
The running apps use up RAM. Not CPU Cycles or battery power as you stated, but RAM. When we kill the running apps, memory is freed up and the app I am trying to run works better or just works. For example, if too much RAM is used up with these background apps, then Netflix has problems and lags or does not run. When I do task killer and free up 200+ MB of RAM, Netflix runs flawlessly. How do we stop apps like Contract Killer, etc. from running when we are not trying to use them? is the question.
|
|
|