Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

If I keep one or more app minimized in my Android Phone (Samsung Galaxy Y) will my mobile's battery will be consumed faster than if I had not minimized any application at all?

share|improve this question
    
This seems like it is covered in Background apps and the battery –  eldarerathis Aug 3 '12 at 17:51
    
"Minimized" is a Windows concept. I assume you mean running in the background. –  Al E. Aug 3 '12 at 20:05
    
@AlEverett You are correct. –  user221287 Aug 4 '12 at 15:43
add comment

1 Answer

up vote 7 down vote accepted

If an app does not run in the foreground, it is usually "frozen"; this means, its memory structure is kept (so you can "recall" it faster, and no additional I/O + CPU is needed to restart it) -- but gets (almost) no CPU-cycles assigned. There might be some exceptions when it needs to do things while backgrounded, but usually that would require the app to use a "service".

Thus, the "overhead" is minimal -- compared to the need of restarting it every time the user needs to access it. As for memory, the Android system is quite efficient in maintaining it: To explain it in easy terms, apps are put into different groups having different "priorities". Together with some other criteria, this decides which app can be killed if the system runs "Out Of Memory": The OOM-Killer (again, "Out Of Memory Killer") comes into action then and checks: Obviously, essential system processes should not be killed at all, the users foreground-session (which he is working in) should be the last to consider. But "closed" apps are first candidates, "background apps" the next, and not-so-essential services come after those.

Again, that is a simplified way to put it -- in reality, this looks a bit more complicated :)

BUT: if you think of task-killers to "improve battery life": Forget about that before starting to think about. They are usually rather contra-productive, as they work against the system. Few exceptions apply in terms of a malfunctioning app (e.g. consuming all your CPU and there's no other way to stop it).

share|improve this answer
    
+1 from me. Here's a good picture illustrating the technical lifecycle of foreground apps which are composed of "activities", i.e. viewable components. Only active components (the current viewed activity, e.g. some settings screen) run at a time. –  ce4 Aug 3 '12 at 18:33
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.