Help How do I exit apps and stop them...?

[shantytownbrown]

Without going into menu-->settings--->apps--->manage apps---> and selecting force stop for running apps that should have been stopped when i left them...?

Or am I screwing things up by hitting "force stop"

e.g. espn app, cbssports fantasy football app, Network app...

none of these have a menu choice to "exit" or stop when i am done with them...

is this just an android issue...

OR...should i not worry about it 'cause its really not causing much battery drain?

thanks -in-advance

shanty

 

[probinson]

I use a program called SystemPanel. It displays all the programs in memory (active or not) and I can terminate any that I care to.

 

[whtge8]

Those apps running in the background are not actually "running". It is just sort of on standby, to be able to launch quicker. Manually exiting these programs will not do a thing for battery life. Leave em alone.

 

[sitlet]

Those apps running in the background are not actually "running". It is just sort of on standby, to be able to launch quicker. Manually exiting these programs will not do a thing for battery life. Leave em alone.

Yep, Android is not like what you are used to in Windows. When android loads something into the cache or memory, it literally just sits there until you open the app. Its not using any cpu, and force closing it will just cause it to reload itself, using more battery.

That being said, I also use the System Panel Lite app. Once in a while I will go through and make sure nothing is using too much cpu. It also comes in handy for the once in a while app that locks up, I can go in here and close it.

 

[brushrop03]

the back button. don't use the home button

 

[shantytownbrown]

the back button. don't use the home button

I usually do, but sometimes I am finding I am hitting the back button way too many times...gets old, so I just hit home...

thanks all for the explanations

 

[novox77]

Using the back button immediately puts an app into inactive state.

Using the home button puts the app into background state.

Neither modes drain battery (unless the app is designed to process something or use the radio in the background). Apps in background will automatically go to inactive state if you don't go back to them within 30 minutes.

 

[takeyouriphoneandshoveit]

Incorrect, when Android loads your programs back up, it is using CPU. That is why they make a task killer.

 

[jamesmckeephx]

Incorrect, when Android loads your programs back up, it is using CPU. That is why they make a task killer.

froyo doesnt need em

 

[sitlet]

Incorrect, when Android loads your programs back up, it is using CPU. That is why they make a task killer.

Yes, when it loads them it uses cpu, but once the program is loaded, it just sits there, not doing anything until you open the program back up. And yes, froyo doesnt need a task killer.

 

[Mr. Ed]

"most" apps play nice with android's task management.

Others do not.

like facebook's fiasco of an update and some other apps I have recently tried that keep the phone in an "awake" state.

OP, I'd say that most of your apps aren't causing any issues, however it isn't impossible to get a rogue app that is indeed running the cpu/services

the real question is...are you actually experiencing battery drain issues, or does it just bother you to see all of those apps running?

what are your awake vs up times compared to what you have actually had the phone "awake"