JuniorNA
Android Enthusiast
Hey , to answer your question...those applications are loaded because the phone rebooted and waiting on user interaction before it starts to close those programs down to make use of the applications you use. Do this for example, reboot the phone, then run ATK and look at all the apps "started"
- you'll see about 50 but youre memory will be running higher than average right? we'll get to that later. Open ATK and just kill ATK after you see those apps. Use the phone as normal, for about an hour. You will see fmscanner/peep/places/maps/youtube/ etc all starting to close on their own, you will even see googlevoice and skype not running at certain times *if you havent used the phone feature in a while* It's because those apps you think are running have started so you can start them up swiftly, once the OS sees you are not using them, they auto-close on you. For the phone feature, since skype is installed, just in case you are logged into skype, it needs to have skype on stanby mode (look at wit with aTK if you can click info, you'll see running time 0 minutes/0 seconds) Skype nees to start/or cache up when you get an incoming cal so it knows to route the phone to skype just in case, cityID starts up to tel you where the call is coming from, google voice comes up so that it's ready to use those services...if you don't use the phone feature for an hour say, those apps arent running anymore, which they were cached to begin with (there is even a debate about the apps cached or running also, debates everywhere).
The point is, you will see certain apps close on their own to make way for the apps you have been recently using. I watch ATK closely, and i Notice youtube goes away after a few minutes after a phone reboot, i notice fm scanner go away, places, google voice, etc. After about an hour, when i Run ATK to check, i only have a few things running, and they were my most recent apps. Now the kicker, if you change the process viewing level from medium to high, you will see even more services running in the background, messaging service, sync service, and other system processes which could drive you nuts probably and you'd want to close them all right? Well then you'd stop getting texts, your touch input would become unstable, you wouldnt be able to switch/flip through screens.
I change my viewing type to low, so i only see apps that are actually running and using CPU (not just lying dormant at 0%) and i close anything that might have an incorrect close code. For example, if i were to play a game, and i stll see it's running and using CPU % usage after i stopped 5 minutes ago, i would kill that game, but thats it.
Bottom line, those apps are running yes, but not in the fore-ground...they will eventually close for you, and only the apps you use will have a cpu % usage next to them, and will even show you an uptime if you use something like taskmanager or systempanel and you will see none of these programs you think are running have used any CPU usage.
Even when you use the camera, and then back out. You will see the camera running, but the counter has stopped for running time, and that will be set to 0% cpu, with uptime of 20 seconds, it's not really running, it's just in the back-ground, not foreground of your apps control center.
Confusing i know, and even the stuff i've said is debatable, but i have a good grasp on the apps and how they run in the foreground and background, what is actually running and what isnt. I've ready everything thread i could about this topic and learned a lot.
Read this link if you havent.
FAQ: Why You Shouldn’t Be Using a Task Killer with Android
hope i helped a little bit
