-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Music and others keep running; why?
- Thread starter KHarper
- Start date
lennyjew
Android Enthusiast
It's part of the way Android works. It's not really using battery life or anything.
It's just a memory paging system, keeping certain programs data in memory for quicker starts when you decide to open them.
Using a task killer is actually going to drain your battery faster since it's going to constantly fight the system settings, opening and closing the same apps endlessly.
It's just a memory paging system, keeping certain programs data in memory for quicker starts when you decide to open them.
Using a task killer is actually going to drain your battery faster since it's going to constantly fight the system settings, opening and closing the same apps endlessly.
RichSz
Not Entitled
Just because something is loaded into memory does not mean that it's running. Or maybe a better way to word it is to say it's not using CPU.
This is a concept a lot of new Android users (including me) seem to have a hard time accepting. Android manages its memory pretty well and will load things up so they start running faster. When you try and take over that role from the operating system you tend to make things worse because it will often restart what you killed which DOES eat your CPU cycles. Also if the operating system needs more memory, it will happily kill off what it needs to in order to get that memory.
By saying it's a tough concept to accept, I mean no insult. I can't tell you the task killer wars I used to have with the operating system because I didn't feel that some particular app should be running. All I ended up doing was making a lot of needless work and aggravation for myself. In my opinion, task killers are only useful for getting rid of a rogue app which seldom happens.
This is a concept a lot of new Android users (including me) seem to have a hard time accepting. Android manages its memory pretty well and will load things up so they start running faster. When you try and take over that role from the operating system you tend to make things worse because it will often restart what you killed which DOES eat your CPU cycles. Also if the operating system needs more memory, it will happily kill off what it needs to in order to get that memory.
By saying it's a tough concept to accept, I mean no insult. I can't tell you the task killer wars I used to have with the operating system because I didn't feel that some particular app should be running. All I ended up doing was making a lot of needless work and aggravation for myself. In my opinion, task killers are only useful for getting rid of a rogue app which seldom happens.
AngryHatter
Android Expert
Vista introduced this concept into windows.
A "1" in ram costs the same amount of energy to keep as a "0."
So they load programs to keep it ready, anticipating your needs.
Throw the ATK out.
A "1" in ram costs the same amount of energy to keep as a "0."
So they load programs to keep it ready, anticipating your needs.
Throw the ATK out.