22

I find myself using force stop for every application once I have finished using them. Is this a good practice? Are there any performance or security benefits of doing this? Is force stopping an app necessary to get it out of RAM?

  • 9
    Well I do have a similar habit as you, but mostly for battery life and peace of mind (screw the constant notifications) instead of RAM. IMO, forcing them out of RAM, especially out of "cached" (not "running") state will increase loading power consumption / time. I use most apps very sparingly so I wouldn't care, though. – Andy Yan Jul 17 '17 at 8:32
25

TL;DR:

No, it's not a good or advisable idea.

Explanation and some background:

Force-stopping apps is not intended for "routine use", but for "emergency purposes" (eg. if an app runs out of control and cannot be stopped otherwise, or if an issue causes you to clear cache and delete data from a misbehaving app). Generally spoken, it's neither a "performance booster" nor a "RAM optimizer".

In many cases it won't save battery life either, but rather deplete the battery even faster. Apps don't only start when you tap their icon, they can also get started via intents or broadcasts (eg. on battery low, network changed, USB device connected – but also on many more). So when you "force-stopped" it, on its next start it will have to do a "full init" (loading from the storage(s) and the network) instead of just going back to its "last state" still stored in RAM (unless the system had to clear it out – see our oom-priority tag-wiki for details on that process) – what Andy described as "will increase loading power consumption / time" in his comment on your question.

  • 1
    Would this also apply to iOS? Or should that be asked as a separate question on Ask Different? – Stevoisiak Jul 17 '17 at 19:52
  • 2
    @StevenVascellaro Definitely a separate question. – Matthew Read Jul 17 '17 at 20:19
  • I would also add that users who want to make sure they close out of an activity/app completely should use the back button instead of the home button, as using the home button may leave it running in the background for multitasking purposes. – oldmud0 Jul 17 '17 at 22:56
  • @oldmud0: Not "Running", it gets stopped. But it remains, yes. – Mooing Duck Jul 17 '17 at 23:06
  • Some apps misbehave on a pretty regular basis - for example, the official youtube clients, some messengers. Is it possible that they keep doing some faulty crap in the background, depleting the battery? I have a strong (albeit not backed up by any statistics) feeling that they do... – Headcrab Jul 18 '17 at 10:54

protected by beeshyams Nov 20 '18 at 6:09

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

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