I have been using advanced task killer free for a few days and have not noticed any difference in battery life. Shall i keep or uninstall?
same here, but its not bad, and its kill some appz and spece memory - so way not ?
google states that Android Users do not need to use task killers. Programs are left in memory for latter use, the system will even load programd you haven't used yet if the system thinks you might use it. These programs stored in memory use very little power and might actually use more because the program has to reload every time its used. I used task killers for a little. But now i don't.
Sent from Conical .07
Android doesn't need task killers really, if memory gets low then Android will close apps to free up memory, I find that if an app is using to much memory though...like a bad app the task killer is useful ..
To find out if an app is leaking memory you can donwload Watchtower for free to take a look whats going on..
I wouldn't uninstall it, just no need to use it so often..Android usually looks after itself..most of the time.
Task killers are actually a very bad idea. Many apps are making use of a background services, killing them as well (what most blind killers do) will result in a totally unpredictable behavior.
As a developer I really hate them. I have one app which totally depends on a background service. I get sometimes really weird error reports... questioning a little further always reveils that taskkillers have blown away the back-end of this app.
Task killers are stupid. Android has a linux base. The linux way is to cache a bunch of data into memory to allow apps to start and run faster.
How much free memory you are showing is actually meaningless because should an app require more memory the kernel will reallocate memory to the active task, automatically stripping it from idle tasks.
If you are trying to save power what its relevant is which apps are using cpu cycles. As fat as I know the only task killer type app which monitors cpu usage instead of memory usage is Watchdog.
Sent from my Desire HD using Tapatalk
Related
I have noticed behaviour pointing to a memory leak on the X10 - After turning the phone on, I get less and less free memory after running ATK - over 110 MB right after turning the phone on to ~70 MB after 24+ hours.
The phone is heavily modified/customized, so it may not be an SE sw bug (ADW, Smart Keyboard, handcent, k9, etc...)
What's the best process tool you can recommend to look into this?
Let the phone handle the memory. dont worry.
+1 on that. Android its linux based and us meant to work like that. Empty memory is wasted memory.
-------------------------------------
Sent from my X10i
Android may be Linux based, but if *after killing all idle processes* memory is systematically dwindling, that means/may mean that one or more of these processes is allocating memory which it is then NOT being released - either by the process (more probable) or the system itself (less probable).
In other words, for the same set of running processes/applications , the memory usage should *not* systematically go up over time.
Linux itself has no automatic GC. Android does (Dalvik VM), but it takes some care from developers for that to work properly - no "loose" pointers to unused but still-referenced data, etc....
acmbc said:
Android may be Linux based, but if *after killing all idle processes* memory is systematically dwindling, that means/may mean that one or more of these processes is allocating memory which it is then NOT being released - either by the process (more probable) or the system itself (less probable).
In other words, for the same set of running processes/applications , the memory usage should *not* systematically go up over time.
Click to expand...
Click to collapse
I disagree, as processes are used/exercised the kernel will allocate the memory they need, after switching on the phone the processes are idle and occupy a small amount of memory. As they are used the process size will grow in main memory as they store or cache common data used by the process. That is why applications such as facebook may be slower at start off as the data needs to be supplied, once this data is cached it will run much faster as the data is already in main memory.
Linux/Android works on the principle that it's a waste not to use as much memory as possible.
Not to get into a GC flame war here: The principle you mention is right, its just that after one KILLS these processes (facebook for example) ALL OF the memory allocated by facebook should be relinquished to the system (ergo, appear as free).
I.e. if I start up my phone, and just have processes A B and C running and have lets say 120 MB free, and after using the phone for a while kill everything and *restart* ONLY processes A B and C, then I should have 120 MB free. At least tendentially (may have a different set of resident libs at the 1st and 2nd points in time, some other minor stuff may be different, etc..). However, I find that doing this over and over results in less and less free memory being available as time passes.
I am not saying I am *right* but a good process inspection tool would help to ascertain what is going on.
acmbc said:
Not to get into a GC flame war here: The principle you mention is right, its just that after one KILLS these processes (facebook for example) ALL OF the memory allocated by facebook should be relinquished to the system (ergo, appear as free).
I.e. if I start up my phone, and just have processes A B and C running and have lets say 120 MB free, and after using the phone for a while kill everything and *restart* ONLY processes A B and C, then I should have 120 MB free. At least tendentially (may have a different set of resident libs at the 1st and 2nd points in time, some other minor stuff may be different, etc..). However, I find that doing this over and over results in less and less free memory being available as time passes.
I am not saying I am *right* but a good process inspection tool would help to ascertain what is going on.
Click to expand...
Click to collapse
Wrong.. it should NOT be returned to the system.. but it should be marked as "disposable" IF another process wants to use it. That is the way linux usually do.. That is why the "Free"-value is misleading. As the "Free"-value is not the sum of "Free" and "Cached" values. when you "unload" a lib it is not completely removed from memory, it is just marked as "cached" instead. Saving tremendous ( ) amount of battery and time when, if, the user wants to use it again before overwritten by another memory-hungry application..
Regards // OwL
does all this mean we don't really need advanced task killer?
or does the advanced task killer kill the cpu process? ( as a result longer battery life)
robbyf66 said:
does all this mean we don't really need advanced task killer?
or does the advanced task killer kill the cpu process? ( as a result longer battery life)
Click to expand...
Click to collapse
advanced task killer kills the application itself, so that nothing more is executed by that application thread(s). wether dependent libraries are kept loaded or not does not affect battery time when not used. Advanced task killer does not actually unload any libraries it only kills the process.
I personally hardly never use advanced task killer, as it is not needed as long as you make sure to run applications that does not keep the phone from going into sleepmode. Those programs are just simply bad coded.. I instead have a CPU-meter application in the task-bar and if I see that the CPU-time is extensivly used after the application has been put to background, then I might use a taskkiller to stop the bad application. But that scenario is rare... I usually get 50h+ of battery time per charge, whatever I do with it.
Regards // OwL
Good day!
I've tried a few different apps now, Memory Usage, Advanced Task Killer, and I seem to hover between 110m to 25m. I kill some apps and it jumps back up to 110 and then slowly works its way back down to the mid 20's. Is this normal?
Tips? What is your available memory like?
To sum it up: Free memory is useless memory. You should have as little memory free as possible.
Explanation. Android handles memory management really well. When an app is opened and needs more memory it will shut down unused processes and free up memory on an as needed basis. For apps this can be everything from pausing individual functions all the way to saving an apps state to disk and restoring it the next time it's opened.
Task killers are mostly solutions looking for a problem, I've been running without one for months and my amount of free memory fluctuates as expected when surfing the web and things like that but so far there haven't been any times where I've had to free up memory. So don't stare yourself blind on memory meters and try freeing up memory. Android handles that well enough on its own.
+1..
The message you have entered is too short. Please lengthen your message to at least 10 characters.
That's good info! I kinda knew I was making something out of nothing with the numbers. The phone has been fine in terms of performance.
my 2 cents....i typically have between 30-60mb free. phone does not lag or anything. i used task-killer for a few days when i got phone, then actually thought about what it was doing and the way the system (linux based) is designed. i ditched it and have not looked back!
ps. my phone is rooted R2BA024 firmware, fwiw.
I usually have like 80 mb free ram just for the case and i use task manager to kill apps that are using data connection when i dont need them
I got totally obsessed with task killing but having read a lot of the lads reports on here I am on my third day of not touching it and I have to say my phone is doing fine all by itself!
goth50 said:
I usually have like 80 mb free ram just for the case and i use task manager to kill apps that are using data connection when i dont need them
Click to expand...
Click to collapse
I think you'd be better off setting up data synchronisation properly. I'm assuming you're talking about background syncing of course. So that you don't accidentally kill an app in the middle of a sync which might cause corruptions. I've had that happen when synching my gmail to a linux machine and the network went down, the cleanup required was insane and I lost a whole months worth of mails from the google servers.
ddewbofh said:
To sum it up: Free memory is useless memory. You should have as little memory free as possible.
Explanation. Android handles memory management really well. When an app is opened and needs more memory it will shut down unused processes and free up memory on an as needed basis. For apps this can be everything from pausing individual functions all the way to saving an apps state to disk and restoring it the next time it's opened.
Task killers are mostly solutions looking for a problem, I've been running without one for months and my amount of free memory fluctuates as expected when surfing the web and things like that but so far there haven't been any times where I've had to free up memory. So don't stare yourself blind on memory meters and try freeing up memory. Android handles that well enough on its own.
Click to expand...
Click to collapse
Heh...handles memory very well, but how about the battery life!? The more apps you have- the less power you've left.
mymagicmyhero said:
Heh...handles memory very well, but how about the battery life!? The more apps you have- the less power you've left.
Click to expand...
Click to collapse
That's debatable, most background apps drain miniscule amounts of power. The exception naturally being things that makes use of the hardware while backgrounded by playing music, syncing, calculating pi or things like that. Most apps though, just hang out in memory not really doing anything. A lot of the time, if not most, it's more efficient staying there as opposed to shutting it down and starting it up again later.
+1 yes, just hanging out idle in memory wont cost you any battery, the memory will be on an base current either way, what does cost you battery is the read and write actions to memory so if you frantically clean out that memory your phone will have to write alot more to it working with your different apps resulting in a slower (less prepared) device sucking more battery then neccessary. Leave the memory handling to your device ;-)
Sent from my X10i using XDA App
How much memory do you have free on your device at a time?
I use Advanced Task Killer to kill some apps, but ignore some for widgets and such. How much memory do you have free, I have ~100M
I usually have 75M free I don't kill any apps, i only use the task killer to kill games that don't close.
after i use my task killer minus ignoring my messenger app it varies from about 100-120+
Sorry for the newb question, but where do you see how much memory is being used/is free?
Does any one know if there is away to defrag the phone, or its there really no need for that?
Maybe it is better to ask what is the best way to clean up your phone
its linux man, the way they organize their files is more efficient then window. defrag only happen in window because of the way they frag their files everywhere, so short answer no you dont need to. i dont even think you need advance task killer, because i ran my phone without it and i dont see the difference when i have advance task killer
Task killers are no good. Don't use them.
Sent from my T-Mobile G2 using XDA App
No need to defrag internal storage or SD card.
Why exactly are you looking to "clean up" your phone? are you running out of storage?
If you've been moving a lot of files to/from your SD card over a long period of time and you think its getting messy, you can always format your card and start over. I do this every once and a while because I am so often flashing multiple ROMs and moving things around.
As far as task killers go, if you're running Android 2.2+, there is no need for a task killer. Task killers actually hurt your battery life MORE than letting programs run in the background or stay in memory. The simplest way to put this is that not only does the task killer have to constantly run, eating battery; but also, the programs its killing are simply restarting over and over again to get done what they need to do. I use Watchdog Lite. Look it up in the Market, in the app description it will link to the web page to explain why simply monitoring for overactive programs is more productive than blanket killing every app.
I used to be a big advocate of task killers until i realized my battery was better once I stopped using them.
hope this helped;
Hi friends,
trick for increment ram free exsist? sorry my bad english
Thanks
Get yourself a task manager and kill all unnecessary processes, but I don't really know what would you use that free RAM for
Graveir said:
Get yourself a task manager and kill all unnecessary processes, but I don't really know what would you use that free RAM for
Click to expand...
Click to collapse
ok friend,
for you the best task manager?
double thanks
Use task killer its free in the market, as for me im using System panel.
allgsmnetwork said:
ok friend,
for you the best task manager?
double thanks
Click to expand...
Click to collapse
advanced task manager is the best ,but check this article out
http://phandroid.com/2011/06/16/android-psa-stop-using-task-killer-apps-now/
Android system (2.2 and 2.3--> 2.1 is not too efficent in this) frees the memory itself, and caches things like Windows 7 (but in a far effective way). If you start a software that needs more RAM, then Android frees it for the app (or it tries to free it up: sometimes you have to run more than once a memory hog app to get it started), else it's precaches system things to fasten up the phone. So. If you have a lot of memory free, it's not always good.
Note that the problem starts if the CPU "can't rest". Then will come the less battery time, slowness, choppiness, etc. So: If there is an Application that has been loaded into memory, and runs in background and eating CPU cycles, then it's not good. In this case you have to close it manually. But not for the more RAM. You have to close it because Android itself MAYBE won't close it, because it recognizes as a running task (so it isn't an idle task) that is in use, and it keeps eating the CPU-->battery.
Hope this helps for the memory-geeks