So if an app was killed and starts back up, you didn't hurt anything by killing it did you? Just curious.
Did it cause damage? Probably not. But background apps like that might be checking mail, tripping alarms, or syncing in the background. Killing them will halt that feature until they are restarted by some other OS action. If you miss an important message or alarm, that might "hurt something."
Why the heck would amazon mp3 be running automatically when i never launched the program?
There's probably some feature of another program that uses a dynamic link library native to the Amazon MP3 download program. Marketplace and Music Player would be likely suspects. There may be other, less obvious candidates. Remember, Google has a lot of alliances in the development of this phone and it's software.
Killing an app to have it reboot will cause more CPU cycles, thus consume more memory. Your phone will Automatically clear up the needed memory when it needs it and programs running in the background will NOT consume enough battery to be worth killing.
Your phone doesn't need a task killer unless you have a poorly coded app (and if the app is coded poorly you should uninstall it). I haven't run a task killer on my OG Droid (that has less ram and a slower processor) in going on four months with no issues. My battery lasts just as long, if not longer.
You could always make them randomly boot up whenever someone asks a question that's answered in them.. Maybe Rick roll them if people ask the same thing twice?
I'm sure Jerry could figure it out.
That's a terrific idea
I was just joking around though (mostly). The task killer discussions are always the most common. I think because all of us have or had a mentality of using them after our Blackberry and Windows Mobile experiences. It doesn't help that we have Verizon stores out there telling people to use them either.