Skip to main content
replaced http://android.stackexchange.com/ with https://android.stackexchange.com/
Source Link

That's a really silly thing to do. Android will automatically kill background processes to make more RAM available when necessary. Most of the time it leaves background processes in RAM (but not running) to allow those apps to start up quicker next time, and to use less power (because it doesn't have to keep reloading the app into RAM). See the answers to this questionthis question for more info.

That's a really silly thing to do. Android will automatically kill background processes to make more RAM available when necessary. Most of the time it leaves background processes in RAM (but not running) to allow those apps to start up quicker next time, and to use less power (because it doesn't have to keep reloading the app into RAM). See the answers to this question for more info.

That's a really silly thing to do. Android will automatically kill background processes to make more RAM available when necessary. Most of the time it leaves background processes in RAM (but not running) to allow those apps to start up quicker next time, and to use less power (because it doesn't have to keep reloading the app into RAM). See the answers to this question for more info.

Source Link
Dan Hulme
  • 35k
  • 17
  • 91
  • 157

That's a really silly thing to do. Android will automatically kill background processes to make more RAM available when necessary. Most of the time it leaves background processes in RAM (but not running) to allow those apps to start up quicker next time, and to use less power (because it doesn't have to keep reloading the app into RAM). See the answers to this question for more info.