Yes I was also wondering what settings people used for optimum memory management.
For optimum and correct memory management REMOVE auto killer all together.
Google "Why task killers are bad" have fun!
Auto killer isn't a normal taskiller. it doesn't artifically shut down apps. It tweaks the numbers Android itself uses to naturally shut down apps.
So in the case of ATK I agree with you, but this is nothing like ATK. Auto killer is like over clocking the Android memory management system (not a perfect analogy)
Auto killer isn't a normal taskiller. it doesn't artifically shut down apps. It tweaks the numbers Android itself uses to naturally shut down apps.
So in the case of ATK I agree with you, but this is nothing like ATK. Auto killer is like over clocking the Android memory management system (not a perfect analogy)
Well first the actual process that Android uses to physically "kill" an app is different than something like ATK uses. Autokiller tells Android when to do its own native app killing process.It kills task based on memory and also has the ability to kill important task. If you are killing safe apps you are doing nothing to help your system those apps are just setting there are will be killed by the system if it needs memory.
Free memory is wasted memory.
Which do you think takes more power, loading your app once or every time auto killer kills it? Which could be many many times a day.
Just reading the docs for it basically tells you the apps you're going to kill does nothing for you.
Android kills apps based on memory. By default say on the DROID 1 android without any tweaks will kill empty apps and content providers at <= 32mb Hidden apps at 28mb secondary Servers at 24 visible app at 12 and yes even the foreground app at 8
this is how the system works, while in general yes Free memory is waster memory but even native Android feels the need to keep at the very least 8mb free at all times. It feels that this is so important that it will actually kill every app running to maintain that.
Think of the free memory as swap memory, i guess (not technically what it is). there is a balance Android plays between guessing what you might open and having enough unassigned memory to quickly open (or continue to run) something it didn't guess.
It's quicker to load something into empty memory then it is to unload something and load another thing, even true with the "empty apps". I'm not saying adjust the numbers to be constantly killing everything, but tweaking it can give you an actually performance boost.
Android is tweaked to be the best on the average phone, but your phone my not be that completely average phone (or maybe you don't want it to be) and my take non standard minfree settings.
You're making assumptions that are just wrong.
For one you don't have to actually unload an app you simply clear a pointer to free the memory. Probably about 4 ops codes that take about .00000000001 of a second or less. Two I'm sure Android knows more about how to handle the memory than you.
Auto killer is a task killer plain and simple they just go about identifying what to kill differently.
However I see your fully convinced so I'll leave you with your believes. But I'll bet if you removed it you wouldn't noticed any difference in preference, other than a possible improvement.
I can show you many many many articles from people that know far more than you or me that tell us over and over these things are BAD. Find me one that says they are GOOD.
take care.
wow dude chill out and maybe take one second to actually listen to what I am saying instead of spouting your in-vogue mantra about task killers. Maybe it is possible that you don't entirely understand what this app does?
Auto Killer DOES NOT KILL APPS. you continue to assume that this app is the same as any of the other task killers out there. It is not, plain and simple. Those Identifiers for killing apps I outlined above are not Auto Killers Identifiers, they are ANDROID'S. Again Auto killer does not contain a single piece of code that kills apps, in fact ALL it does is change numbers in a text file.
Auto killer allow you to adjust the parameters used by Android to manage memory. And I am telling you Android KILLS APPS WHEN MEMORY GETS BELOW 32mb. If you don't believe me go a head and open up your file system and check out sys/module/lowmemorykiller/parameters/minfree
that is the system directory and file for the android app kill thresholds. If there is zero benefit to having any free memory why does Android come built with a process that frees memory?
This doesn't kill apps it allows you to tweak Androids memory setting and frankly thats one of the major benefits of root, an ability to decide for myself whether Google's presets actually work better then my own.
What if I decided to lower the thresholds so in actuality there would never ever be free memory (i.e. more stringent then Android comes boxed with) would you have a problem with that as well?
when you said second tab I released that I didn't currently have "Auto Killer" installed but rather "Minfree manager" which also is minfree file tweaker but with out secondary tabs ( but i've used both)But there is in fact two tabs on the apps called processes and one called services. A quick look shows this to be nothing more than your standard app killer. Press the app GONE puff! .
Well I'm looking at the docs and it says you can kill hidden_apps "because you can't see them so it can be killed without disruption"
HOW THE HECK DO YOU KNOW WHAT THAT HIDDEN APPS WAS REALLY DOING? How can that be good? I wonder what happens if you set it to 1?
Want to test it?
Wouldn't you have to up them?
You'd obviously screw it up if you prevented Android from working properly Just like you would if you go adjusting stuff way down or killing task manually.
Let the OS do it's job it doesn't need you.
Show me one article that proves freeing more memory manually or with a third party app does anything to help Android work better.
exactly, but maybe my phone runs better when android does its thing a little sooner (or later!)
Look I know I don't know everything, but I do see that Google decided to have android keep 32mb of free memory (I believe the "free" memory is used for VM Cache) so clearly it is some what important, but that is almost irrelevant because I'm talking about making adjustments to let Android better fit MY phone and MY use habits. Nothing wrong with that. Google told Android when to kill, now I'm making some slight adjustments to that to see if I can get it even faster. Maybe instead of 32mb my phone runs better at 45mb or maybe it runs better at 25mb, who knows but there is ZERO harm in finding out
That's the same setting I use and its working great for me. I don't understand why piiman has such a hard on for auto killer. My phone lags so bad after an hour of being on, when I use auto killer I never notice lag. Most people tell me the lag is from a "bad app" but it lags STOCK with nothing else installed.So despite the differences in opinion here I started using Autokiller memory manager per some recommendations. It is a great ROOT app, and it does seems to make simple to use tweaks to the system.
To some of the points above, used diligently it will help your performance. Like all tools and settings, it can be used wrongly and hurt performance. Likewise while I like what Android OS does, and it does well, but that doesn't mean it can't be tweaked to your usage better.
ALL THAT SAID
I find using the Optimum with a stock rom, rooted, with some apps removed, works very well for me. Now that I have used the presets I am looking to tweak further.
I was hoping others would post up what they use and how it works. I suspect on other ROM's there will be vast differences.
That's the same setting I use and its working great for me. I don't understand why piiman has such a hard on for auto killer. My phone lags so bad after an hour of being on, when I use auto killer I never notice lag. Most people tell me the lag is from a "bad app" but it lags STOCK with nothing else installed.
I was using Autokiller on 2.1 on my Captivate. Even on the most aggressive settings, it seemed to work fine for me, and cause no problems. And subjectively seemed like if I had more memory available, it was faster.
Now, I am on a 2.2 ROM, and it seems that no matter what I set it at, I have 50-65 MB of memory. So, at the moment, I don't have it on the phone.
Does anyone have any idea if the theory is the same on 2.2?
Mine does not drop below my setting of 90MB at all on 2.2.
Your app list is a bit smaller than mine. But ATM, I don't have them all installed...probably 65 or so, and have 67MB now, w/o using Autokiller.
Are you using Autokiller?
Just for grins, I may install it again while I don't have all apps installed and see how it goes.
Seems like Piiman as been at his anti-"anything that says killer in the title of the application" kick for a bit. BTW great job of explaining exactly what this app does VIO and Beasley
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.