-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Um...why not kill one app at a time and then see if there's an improvement after each one?
I tried reading your post but didn't really understand it :S
This is another interesting thread, as I learn more about my phone.
I downloaded Taskiller, as recommended in the sticky at the start of this section of the forum, together with a number of other apps.
The phone ran slowly very quickly after they were installed.
I noted from the 'manage application' task that there were some quite large (relatively) apps.
I removed some.
I have now let Taskiller work in its auto mode and things seem to have speeded up again.
I'll stick with it for a week, anyway.
Regards.
I downloaded Taskiller, as recommended in the sticky at the start of this section of the forum, together with a number of other apps.
The phone ran slowly very quickly after they were installed.
I noted from the 'manage application' task that there were some quite large (relatively) apps.
I removed some.
I have now let Taskiller work in its auto mode and things seem to have speeded up again.
I'll stick with it for a week, anyway.
Regards.
jUsT2eXy
Android Enthusiast
But like I said in the post.. after you kill that 1 app... you will be like OMG THIS APP WAS CAUSING THE LAGG because obviously killing any app when there are many open will result in memory being free'd up followed by the phone becoming faster.
So unless (like I said in my post above) you quit every app that's open then select an app individually and see if it is making the phone lagg could you properly (scientifically) single out one app that causes lagg.
Did that make sense?
But like I said in the post.. after you kill that 1 app... you will be like OMG THIS APP WAS CAUSING THE LAGG because obviously killing any app when there are many open will result in memory being free'd up followed by the phone becoming faster.
No! That's exactly the point...free memory does not equal everything else being faster!! That is not how things work on Android. Free memory = wasted memory!
Even if lots of apps have been opened, once memory runs low new apps will simply replace "older" ones (that is, those that have been asleep the longest).
At least, that's my understanding of it.
jUsT2eXy
Android Enthusiast
As I have said in my previous post(s) I do not disagree with the ideology that Android/Linux has good memory management. But the very fact that the phone is more responsive and smoother when processes / apps are killed via taskmanager do little to support the claim. May be on paper.. but .. visually...not in this case IMHO.
rizzla
Well-Known Member
Another thing that has to remembered is in a multitasking system there isn't really real multitasking, just process slicing. Even if an app is doing nothing it still maybe checking things or doing something in the background. The OS has to jump between these tasks constantly. Less programs running less jumping , how that affects the system is hard to tell.
But as i said before in previous post I seem to notice when I feel the need to to use taskkiller and check the memory values it almost always seem to be at around the 23mb mark.
It would be interesting to know what exactly is going on. linux may purported to work it a certain way and though that may work well for Pc's doesn't mean the same is true for mobiles.
So is it memory, multitasking processor slicing, bad app programming or a combination of the three?
But as i said before in previous post I seem to notice when I feel the need to to use taskkiller and check the memory values it almost always seem to be at around the 23mb mark.
It would be interesting to know what exactly is going on. linux may purported to work it a certain way and though that may work well for Pc's doesn't mean the same is true for mobiles.
So is it memory, multitasking processor slicing, bad app programming or a combination of the three?
Ok I've just got rid of my taskpanel. And seriously Woah!!!
Before today just about the best I got on moderate use (little if any wifi or gps) was 20 hours.
Today with no taskpanel and no Graphical Battery Stats Monitor I've just gone 24 hours and still have 70% battery left.
My misgivings are that it takes an age to open up the market and a few other apps.
It certainly does reveal a few things.
Before today just about the best I got on moderate use (little if any wifi or gps) was 20 hours.
Today with no taskpanel and no Graphical Battery Stats Monitor I've just gone 24 hours and still have 70% battery left.
My misgivings are that it takes an age to open up the market and a few other apps.
It certainly does reveal a few things.
NewYorkLaw
Member
If android / linux uses 99% of the memory, whatever amount is in the system, then why do I have different "available memory" readings from time to time? Sometimes I have 60mb free, other times I have 30mb free.
I know nothing and am not saying the people espousing the 99% theory are wrong, I just do not understand. Please educate me.
Pete
I know nothing and am not saying the people espousing the 99% theory are wrong, I just do not understand. Please educate me.
Pete
bzzzz happy to hear you are doing OK 
NYL, that is because it is a running system, linux if I may rephrase attempts to use all the memory, but this simply is not possible as the system is runnig if that makes sense.
you can read this to understand further, by the way Android uses the 2.6.xx kernel
of Linux
Linux Howtos: System -> Linux Memory Management
NYL, that is because it is a running system, linux if I may rephrase attempts to use all the memory, but this simply is not possible as the system is runnig if that makes sense.
you can read this to understand further, by the way Android uses the 2.6.xx kernel
of Linux
Linux Howtos: System -> Linux Memory Management
NewYorkLaw
Member
Most helpful, thanks.
Pete
Pete
bzzzz happy to hear you are doing OK
NYL, that is because it is a running system, linux if I may rephrase attempts to use all the memory, but this simply is not possible as the system is runnig if that makes sense.
you can read this to understand further, by the way Android uses the 2.6.xx kernel
of Linux
Linux Howtos: System -> Linux Memory Management
Hey guys, I've been reading up on the forum as to what is the best/your favourite task killer/manager thingy,
basically just want to stop background tasks that stay open and consume cpu and battery.
what do you think is the best? been running advanced task manager free and that was great but had to reset phone cos HTC sense and system kept force closing, so i think that might have something to do with it.
what do you reckon
basically just want to stop background tasks that stay open and consume cpu and battery.
what do you think is the best? been running advanced task manager free and that was great but had to reset phone cos HTC sense and system kept force closing, so i think that might have something to do with it.
what do you reckon
@Steelie, I have been running a couple of different ones to get a feel for it. Advanced Task Manager Free is what I am using, but for the issues your having, what you have to do (and this is with most task managers) is after you install it, reset your phone, start any apps you would usually want running (just go in and back out of them) and then open ATM from the All Programs screen, and click every app running and select "Exclude", then do the same under the Service tab.
Now anytime you wanna free your mem without messing up what you usually run (or what's vital) you can now happily hit that kill widget on your home screen
There should really be a sticky for this or it's probably in the tips and tricks section because it's what you should do with any task killer.
Now anytime you wanna free your mem without messing up what you usually run (or what's vital) you can now happily hit that kill widget on your home screen
There should really be a sticky for this or it's probably in the tips and tricks section because it's what you should do with any task killer.
Zbig
Newbie
In my case - none.
Have you verified they consume significant amounts of your CPU and battery or just guessing and simply don't like the fact they're there? If the latter, I would recommend you to just get over the fact that someone smart designed it that way and there's a reason. If former, just find out which app doesn't play nice and get rid of it. If it ain't broken... But that's me.
mjcritchie
Member
The to-kill-or-not-to-kill app debate seems to go round and round, with no discernible proof of which is the best way.
I use the free TasKiller app, which you can set to ignore certain apps (mine is set to ignore all the startup apps, assuming that they are necessary and Android can manage them on its own) and has a handy 1x1 widget to kill all other apps, which I use only if things slow down.
This to me seems like the best of both worlds. Android can manage most apps the way it wants to and I have the ability to kill all other, potential phone-slowing, apps with one tap of the screen.
I use the free TasKiller app, which you can set to ignore certain apps (mine is set to ignore all the startup apps, assuming that they are necessary and Android can manage them on its own) and has a handy 1x1 widget to kill all other apps, which I use only if things slow down.
This to me seems like the best of both worlds. Android can manage most apps the way it wants to and I have the ability to kill all other, potential phone-slowing, apps with one tap of the screen.
bluenova
OK Computer
Whilst I agree that using a task killer aggressively is counterproductive there is still a need for one to kill the odd laggy app (stock browser comes to mind).
I personally use ‘Process Manager’ mainly because it’s quick and easy for killing those apps like the stock browser that do not have a quit button and cause my home screens to lag.
I personally use ‘Process Manager’ mainly because it’s quick and easy for killing those apps like the stock browser that do not have a quit button and cause my home screens to lag.
daveybaby
Android Expert
I agree with bluenova: you shouldnt need one on a day-to-day basis, but it is occasionally useful in certain scenarios (i use it to kill some of the crap that loads on bootup, e.g. footprints).
I've found Taskpanel X to be pretty good for this purpose.
If youre going to install one then you should set up an extensive ignore list for it, and any auto-kill functionality is a definite no-no IMO.
I've found Taskpanel X to be pretty good for this purpose.
If youre going to install one then you should set up an extensive ignore list for it, and any auto-kill functionality is a definite no-no IMO.
Question: What's the best taskkiller (manager) for the HTC phone (or any linux based phone)?
Answers:
Task managers usually do more harm than good.
The reason is, Linux attempts to use all memory (RAM) no matter what, [even if you have 64GB verse 128MB]
and Free memory = wasted memory.
Lag is not caused by lack of memory. Lag is caused by a faulty app (Ex. apps made for better hardware, apps with faulty coding, apps that uses too much cpu that with faulty coding, etc
Answers:
Task managers usually do more harm than good.
The reason is, Linux attempts to use all memory (RAM) no matter what, [even if you have 64GB verse 128MB]
and Free memory = wasted memory.
Lag is not caused by lack of memory. Lag is caused by a faulty app (Ex. apps made for better hardware, apps with faulty coding, apps that uses too much cpu that with faulty coding, etc
Fair point, i disagree to a degree, the autotask killer does speed up my phone at times and task killer is usefull if you've jumped through a large number of apps in quick succession (looking for a game you feel like playing....)
What i am looking for is a log of apps auto killer to let me know what tends to open from time to time thus allowing me to weed out apps that slow the phone