Hey Folks,
Just wanted to hear some opinions on whether having a task manger is worth it. I've heard from both sides of the camp, stating newer versions of android can handle the load fine, and that more and more apps are running unnecessary background services.
I just did a clean wipe and reload of CM7 and I'm wondering whether I want my advanced task manager anymore.
Thoughts?
For me, I prefer no task killer. If I must close apps I go into running services and stop them that way. Usually they stop without me doing that.
I don't use one, not needed.
i never ever felt the need of having a task killer on my Inc S
the apps close by themselves when not in use.
v6 supercharger
just use v6 supercharger it is better than all the taskillers you may find.
I don't use one. I'm running CM7 and as Saenzscene said, I stop programs in the running services menu. However I never really had the need to do it as RAM was never a problem.
But I have noticed while running certain programs that if you press the "home" button, the program may keep running in the background afterwards. Whereas if you press the "back" button it will close the program's running service. Can anyone confirm this?
Never had the need for a TaskManager with CM7 or ARHD.
/ Jess Kölner /
/ Sent from my phone /
if you're using a task manager or task killer since froyo, urdoinitwrong
I'm using advanced task killer simply to kill anything that may not be shut down even tho I mean to.
As someone said above, it's possible that some alps stay open and keep your phone awake. I have a large ignore list which I use to ensure nothing important gets closed down, only the rogue apps, now my phone never stays awake when it shouldn't.
Sent from my Incredible S using xda premium
No Task Manager. Using CM7 nightly 103.
System92 said:
I don't use one. I'm running CM7 and as Saenzscene said, I stop programs in the running services menu. However I never really had the need to do it as RAM was never a problem.
But I have noticed while running certain programs that if you press the "home" button, the program may keep running in the background afterwards. Whereas if you press the "back" button it will close the program's running service. Can anyone confirm this?
Click to expand...
Click to collapse
Yes, some apps like to run as a service process if you quit the app. FriendCaster is one example. I think they do this to handle sync process in the background.
I don't need anyone!
My choice is no task manager, android is good.
Related
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
It would be nice to have, say, long press back key to kill the current app.
Big_O said:
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You obviously didn't search for this:
http://forum.xda-developers.com/showthread.php?t=678205
You DON'T need to intervene with N1 memory management, since you don't know how it works. You assume wrong. And most bad gossips are created by people wrongly assuming something, thinking they know something while they actually don't.
My N1 runs equally well with 40MB and 250MB free. The only reason I use a task killer is to kill apps that I want to return to their "initial" state for some reason, or to kill apps that I suspect of wrongdoing.
Exactly, the nexus has no memory management issues. It is just your misunderstanding of how Android works. Leave your tasks alone.
If you have one or two particular apps that are bad citizens and should be shutting down in the background but don't... you can use "1Kill" from the market to create a home screen shortcut that kills that specific app when you press it.
Fring used to be a bad citizen - it would lock my wifi on even when I didn't want to be using it, and had no exit feature. So I'd always have to kill it after finishing up with it. Now it does have a proper exit, thankfully.
Jack_R1 said:
My N1 runs equally well with 40MB and 250MB free. The only reason I use a task killer is to kill apps that I want to return to their "initial" state for some reason, or to kill apps that I suspect of wrongdoing.
Click to expand...
Click to collapse
Ditto!
1 app running or 50 apps running they all still run the same.
I find it even funnier how iOS4 users in Apple-land are suddenly freaking out that so many applications appear to be open "in the background" and complaining that they have to spend so much time "killing" apps.
Big_O said:
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I think you have the memory management issues.
Before anyone gets tarred and feathered, that explains why many users on unrooted stock roms ha e frequent touchscreen lockups, hesitation and freezes. Guess theres a reason why the market has so many task killers. Maybe the devs should read this thread also lol. Instead of flaming, positive feedback is appreciated. I did search, but its a bit time consuming sifting through 5000 posts. Maybe you guys o rooted phones have no lockups, but google shows an azzload of people with similar issues.
Sent from my Nexus One using XDA App
1) You've been given some answers in the thread, if you cared to look.
2) App that loses focus goes to background. That's the way OS is built. If you want apps to be killed on losing focus, get iOS 3 to run on your device. Seriously, what kind of answer would you expect, if you want to turn multitasking OS into non-multitasking?
3) The market has task killers because they can be written for multitasking OS, and because they help dealing with bad apps. Not for any other reason.
4) The OS loads some of your most used tasks when it runs, even if you don't know about it. Just loads in the memory, and allocates no CPU time. If you leave your phone unattended, your free memory goes down by itself. Why? Because free memory is wasted memory. You can check the "EMPTY" processes in Astro, for example.
5) The best task killer is careful selection of your apps. You see hangups? Find out the app that's doing it and remove it, or kill it specifically after running if it's necessary.
6) Task killers are a good source of lockups and freezes too, did you know? I guess you didn't read that thread...
All this meant to say: instead of looking for a way to cripple your OS, learn to select your apps, and don't solve issues that you don't have.
cmstlist said:
I find it even funnier how iOS4 users in Apple-land are suddenly freaking out that so many applications appear to be open "in the background" and complaining that they have to spend so much time "killing" apps.
Click to expand...
Click to collapse
Yeah, I think Apple needs to tweak their multi-tasking still. I've played with my gf's iPhone a bit this week, and it's a little annoying how now you have to explicitly quit every app. For example, with the Settings app if I go to change a preference quickly then return to home Settings app is still in the running apps list. I think little utilities like that should be able to quit themselves automatically.
I know the app isn't wasting memory or CPU down there, but I just don't see why you would want it cluttering up your app switcher forever.
Oh well, it's progress though. At least now you don't have to quit everything else you're doing to listen to Pandora
well android does the same thing. if you go into the settings menu, then hit home button, the settings is still running in the background. of course andoird will kill it later when it needs to.
I been using Advanced Task Manager 4.1 before I updated to froyo and it killed all my unwanted apps very well. All the roms I tryed on 2.2 do this: they leave the apps connected to the internet open. It just wastes my battery. I tryed a bunch of other task killers and none of them work, the apps still stay open. I need to kill the apps untill the next time I open them. Anyone know a way to do that on 2.2 or what my prolem is?
Might want to state what your problem is or ask a question
I edited my post, any way you or someone else can help
artii829 said:
I been using Advanced Task Manager 4.1 before I updated to froyo and it killed all my unwanted apps very well. All the roms I tryed on 2.2 do this: they leave the apps connected to the internet open. It just wastes my battery. I tryed a bunch of other task killers and none of them work, the apps still stay open. I need to kill the apps untill the next time I open them. Anyone know a way to do that on 2.2 or what my prolem is?
Click to expand...
Click to collapse
For one thing you might want to download DroidWall and disable internet access to all unwanted apps. It is like Firewall for your android.
Also try Taskiller. I m using it and it kills apps and never let them start until screen turns on again.
-Sekhar
See thats the thing, I want them to be off untill I turn them on myself. I think I'll re-download DroidWall (I have known about it) and all task killers do the same thing I guess, which is kill the apps untill the next time you turn on your screen =/
Could you give us an example of these apps that are "staying connected" and some indication of what you're testing to know that they are staying connected?
Apps like: Bloo (Facebook), Hi IM, Android Market, Weather Bug, & others that dont use internet like Astrid Tasks, Startup Cleaner Pro, Titanium Backup, TeslaLED & toggle apps.
I just want them closed when I kill them. Right now I have a shortcut to managing apps so I click on the running tab and manually force close them but thats a pain.
INDICATION: killing weather bug and the notification with the temperature stays.
After killing the apps I have listed they pop up again in the task manager 30 seconds later.
I have cognition 2.2 beta7. I have made every attempt to remove that stupid task manager, but it's hijacked the long press home option even after I removed it. Anyone know what I would do to get back to the normal long press home thing?
xelaboy said:
I have cognition 2.2 beta7. I have made every attempt to remove that stupid task manager, but it's hijacked the long press home option even after I removed it. Anyone know what I would do to get back to the normal long press home thing?
Click to expand...
Click to collapse
The long press home has always brought up a dialog for selecting recently run apps as a sort of short cut to multitasking even in the stock eclair rom shipped by samsung. The only difference in the froyo leak is that dialog now contains a link to enter a new front end app to the task manager.
I don't know how to remove that link - I'm guessing you will have to edit something in the framework somewhere. And by the way - you may have or be able to remove the front end user interface app to the android task manager but you can't remove the actual android task manager and still have the phone be operational.
The long press home thing in android isn't exactly a "Task Manager" in stock android. It functions as a way of accessing apps.
The front end app, has hijacked that screen by adding it's button to it.
I was able to delete the app, but now I am stuck a task switcher screen that has a broken task manager link on it. (which if clicked happens to lock up the entire device.)
I'm sure I'd have to get down and dirty somewhere, but I just don't know where.
xelaboy said:
The long press home thing in android isn't exactly a "Task Manager" in stock android. It functions as a way of accessing apps.
The front end app, has hijacked that screen by adding it's button to it.
I was able to delete the app, but now I am stuck a task switcher screen that has a broken task manager link on it. (which if clicked happens to lock up the entire device.)
I'm sure I'd have to get down and dirty somewhere, but I just don't know where.
Click to expand...
Click to collapse
That dialogue was not hijacked by anything - the link was intentionally encoded by someone from samsung to be in the dialogue in froyo 2.2
Ugh. Why would they do that to us?
That link below is why I think it's stupid. (I'm not sure if I'm allowed to post links yet but I'll try anyway.)
http://androinica.com/2010/05/07/go...-imply-task-killermanager-apps-are-pointless/
xelaboy said:
Ugh. Why would they do that to us?
That link below is why I think it's stupid. (I'm not sure if I'm allowed to post links yet but I'll try anyway.)
http://androinica.com/2010/05/07/go...-imply-task-killermanager-apps-are-pointless/
Click to expand...
Click to collapse
Yes. While task managers have value in allowing someone to watch their phone learn what is going on with their and give them some knowledge and a tool for trouble shooting, far too many people are using them as a system resource management tool, killing processes and apps without really knowing what they are doing or that it is completely unnecessary. Often people are even doing more harm then good as they are going way too far in their zest to kill that they are keeping their phone from operating properly.
I think that is what samsung is probably attempting to accomplish with this limited front end app to the task manager that is being included in their froyo builds - trying to give people a tool to satisfy some of there (way over the top) task killing mania while keeping people safe from getting to deep in there task killing and causing problems.
Hopefully more and more people will start getting the message - quit all the arbitrary unneeded task killing - use your task manager keep tabs on your phone and to catch any problem apps that you may of installed - and leave the resource task managing to the actual built in OS task manager as it really does do a good job - so long as you don't have some poorly coded resource hog software installed.
I'm currently running Cognition 2.3b8, but I've seen this in Axura as well as older versions of Cognition. This leads me to believe this is either a SGS wide problem, or this is a Froyo "problem."
In 2.1, I used Advanced Task Killer to keep applications I wanted to run in the background (long press-> Ignore). The most important of which for me is BeyondPod.
In Froyo however, whatever process it is that keeps running and initiates the download of new podcasts is being killed. I tried using ATK for Froyo, and adding BP to the ignore list, but I have the same result. I've done a work-around where I use Tasker to start up the application five minutes before BP is scheduled to, but that seems like a lot of sugar for a dime.
Even if I have to completely get rid of the built in task manager (I find its relatively poor anyway), is there an application that will allow me to "defeat" Android's built in task manager and regain functionality similar to what I had with 2.1?
I deleted some stock apps with StockAppRemover but you can try this too with root explorer. Just got to /system/app and search for something like taskmanager.apk or com.Samsung.taskmanager. Then there should be no task manager left.
Sent from my GT-I9000 using XDA App
This seems to be a viable solution. To those who decide to solve their problems this way, keep in mind that the button for the task manager will still be in the pop-up box. DO NOT press it. It will lock your phone requiring a battery pull.
That said, I'm 90% content with this solution.
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
EverythingNook said:
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
Click to expand...
Click to collapse
Everything I've read says you don't need it with Android 2.2 and above.
I use it, nice quick and easy way to close things (like emulators that normally won't shut themselves off.)
dsf3g said:
Everything I've read says you don't need it with Android 2.2 and above.
Click to expand...
Click to collapse
me too but my friends have 2.3 and they use it.
I use it if videos start to stutter (ie youtube etc). It seems to help.
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
alright ill stay away from it thanks!
That about sums it up. The only time an app should be killed is if a bug causes it to hang or slow down severely. Otherwise, let the Android system handle things itself.
In my experience it's nice to have for when you need to kill off a specific game or resource intensive app that seems to be slowing things down.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
so would you recommended going into the app itself and picking the apps i want to be closed? or could i also use the widget to close all of them?
I would only recommend going into the app itself, long-pressing on the app you want to kill, and then pressing kill. Closing all of them just forces a large number of apps to restart. I really only use it to kill certain apps that are more difficult to close.