Database Info

Kernel conflicting with AutoKiller app?

I just flash a OC kernel to my sprint* hero. I am running Fresh 2.4 with the 710 OC kernel (chose 710 thinking it will be more stable, yes/no?). Before flashing this Kernel I was using AutoKiller on Optimum mode to help keep the phone in line. I am wondering now if AutoKiller is conflicting with my OC'ing of the phone. Should I uninstall the AutoKiller, or maybe change the mode to Chuck Norris? I just dont want the phone to act like a PC does with 2 anti-virus programs installed on it!
thanks

IN my opinion no one should have an autokiller app on there phone. The Android OS kills apps when it needs the space for another app. If it helps i use a program called FAST REBOOT that works pretty good. when the phone starts feeling sluggish i just fast reboot and it makes it run better.
on a side note....this is a Question and it belongs in the Q&A section not here in development.

Thanks for the input. I will try without it and check out Fast Boot!
Mods Please move thread to Q and A

t12icky0 said:
IN my opinion no one should have an autokiller app on there phone. The Android OS kills apps when it needs the space for another app. If it helps i use a program called FAST REBOOT that works pretty good. when the phone starts feeling sluggish i just fast reboot and it makes it run better.
on a side note....this is a Question and it belongs in the Q&A section not here in development.
Click to expand...
Click to collapse
The fact you called it "an autokiller app", as well as your explanation why you shouldn't have it, shows you really have no clue what AutoKiller is.
What you are referring to is a TASK killer, and I agree ... no one needs it because the internal memory manager does the same function much more fluidly and does not require an extra running process, hence is lighter on the system. AutoKiller (the actual app) simply allows you to customize the settings for that internal memory manager. This is pretty much necessary because the settings for this manager haven't changed at all since Android first debuted, and these settings basically leave you with around 25 MB remaining. That may be awesome for a G1, but for more powerful devices like our hero it is SLUGGISH, so upping the internal settings just performs the exact same function with more effective results for our devices.
To answer the original question, the only conflict that could exist is if the kernel itself has its own memory manager embedded. I've been on CM6 for some time, so I'm not sure if the kernel you chose has such a memory manager. If it does, however, it most likely has the same upgraded settings as you would hope to attain with AutoKiller. In this case, there is no need.
Hope this answers your question more completely.

tquetano said:
The fact you called it "an autokiller app", as well as your explanation why you shouldn't have it, shows you really have no clue what AutoKiller is.
What you are referring to is a TASK killer, and I agree ... no one needs it because the internal memory manager does the same function much more fluidly and does not require an extra running process, hence is lighter on the system. AutoKiller (the actual app) simply allows you to customize the settings for that internal memory manager. This is pretty much necessary because the settings for this manager haven't changed at all since Android first debuted, and these settings basically leave you with around 25 MB remaining. That may be awesome for a G1, but for more powerful devices like our hero it is SLUGGISH, so upping the internal settings just performs the exact same function with more effective results for our devices.
To answer the original question, the only conflict that could exist is if the kernel itself has its own memory manager embedded. I've been on CM6 for some time, so I'm not sure if the kernel you chose has such a memory manager. If it does, however, it most likely has the same upgraded settings as you would hope to attain with AutoKiller. In this case, there is no need.
Hope this answers your question more completely.
Click to expand...
Click to collapse
It does, Thanks! I do have the Advanced Task Killer (everyone has or had at one point! lol) and will lose that app right away! With the advanced task killer I still drop in free memory, so it doesnt seem to be doing anything, or what I want it to do. Just kills a few apps, like you said android will do that on it own. The Kernel I have is Darchstars Kernel vUV2 710mhz for roms using 2.1 RUU. It states in big letters "BUGS IN zIMAGE FREEMEMKILLER" just wondering if the AutoKiller has the same issues as the FreeMeKiller? My memory will drop to 50 right now, that is with autokiller set to optimum, I want to raise it higher to keep more free memory, didnt want a conflict though.

cordell12 said:
It does, Thanks! I do have the Advanced Task Killer (everyone has or had at one point! lol) and will lose that app right away! With the advanced task killer I still drop in free memory, so it doesnt seem to be doing anything, or what I want it to do. Just kills a few apps, like you said android will do that on it own. The Kernel I have is Darchstars Kernel vUV2 710mhz for roms using 2.1 RUU. It states in big letters "BUGS IN zIMAGE FREEMEMKILLER" just wondering if the AutoKiller has the same issues as the FreeMeKiller? My memory will drop to 50 right now, that is with autokiller set to optimum, I want to raise it higher to keep more free memory, didnt want a conflict though.
Click to expand...
Click to collapse
If you are using a kernel made for 2.1, you should not be using it. CyanogenMod 6 is built on Android 2.2, so either use the stock kernel or UncappedKernel from Decad3nce. Second, having the processor clocked at 710Mhz will NOT make the phone more stable. If anything, it will become unstable because of the added heat and power needed to run the processor. A good overclock that I've found that should be stable on our phones is from 650-690Mhz. Although I've been running my phone at 590Mhz, and I haven't found any real-life difference in the speeds. Like said above, tweaking the minfree (the Android internal task killer) is perfectly fine. What you do NOT want to do is use a program like Task Killer or Advanced Task Killer, since those will both end unnecessary processes, which will then have to be restarted, in effect using more battery and CPU cycles. So the best way, if you want, is to tweak the minfree settings with a program like Autokiller.

mrinehart93 said:
If you are using a kernel made for 2.1, you should not be using it. CyanogenMod 6 is built on Android 2.2, so either use the stock kernel or UncappedKernel from Decad3nce. Second, having the processor clocked at 710Mhz will NOT make the phone more stable. If anything, it will become unstable because of the added heat and power needed to run the processor. A good overclock that I've found that should be stable on our phones is from 650-690Mhz. Although I've been running my phone at 590Mhz, and I haven't found any real-life difference in the speeds. Like said above, tweaking the minfree (the Android internal task killer) is perfectly fine. What you do NOT want to do is use a program like Task Killer or Advanced Task Killer, since those will both end unnecessary processes, which will then have to be restarted, in effect using more battery and CPU cycles. So the best way, if you want, is to tweak the minfree settings with a program like Autokiller.
Click to expand...
Click to collapse
I am using Fresh 2.4, not CyanogenMod 6. I think there is a lower OC than what I am using. I will have to check, I knew the 768 would be way to much so I chose the 710 (middle option), so yes there is a lower OC. I have uninstalled the advanced task killer, it seems to be doing fine with AutoKiller set to "Strict" that keeps my memory around 60, before it would drop to low 40s I am new to all this so trial and error on my part will help me find a happy medium. I am getting a lot of help here and at android forums, thats how I found this site My wife has the same phone and is jealous of my speed but is scared to let me flash a rom to hers. She watched me stressing out when I was getting stuck in boot loops! I kept trying to partition my SD card to get apps2sd working, every time I after my partition I would get stuck in a dang boot loop. Seems after I partition the SD I need to re-flash my rom in order to get Fresh to see the partition. Or I think thats the issue? As of now I dont have a class 6 SD card, just found out I will need one so I am gonna wait for the apps2sd thing.
thanks

691 is the lowest Kernel, so either 691, 710, or 768. Will the 691 make that much of a difference than the 710? Stock is 528 I think

tquetano said:
The fact you called it "an autokiller app", as well as your explanation why you shouldn't have it, shows you really have no clue what AutoKiller is.
What you are referring to is a TASK killer, and I agree ... no one needs it because the internal memory manager does the same function much more fluidly and does not require an extra running process, hence is lighter on the system. AutoKiller (the actual app) simply allows you to customize the settings for that internal memory manager. This is pretty much necessary because the settings for this manager haven't changed at all since Android first debuted, and these settings basically leave you with around 25 MB remaining. That may be awesome for a G1, but for more powerful devices like our hero it is SLUGGISH, so upping the internal settings just performs the exact same function with more effective results for our devices.
To answer the original question, the only conflict that could exist is if the kernel itself has its own memory manager embedded. I've been on CM6 for some time, so I'm not sure if the kernel you chose has such a memory manager. If it does, however, it most likely has the same upgraded settings as you would hope to attain with AutoKiller. In this case, there is no need.
Hope this answers your question more completely.
Click to expand...
Click to collapse
yea my bad..lol. i had a brain fart. thought it said task killer.

cordell12 said:
I am using Fresh 2.4, not CyanogenMod 6. I think there is a lower OC than what I am using. I will have to check, I knew the 768 would be way to much so I chose the 710 (middle option), so yes there is a lower OC. I have uninstalled the advanced task killer, it seems to be doing fine with AutoKiller set to "Strict" that keeps my memory around 60, before it would drop to low 40s I am new to all this so trial and error on my part will help me find a happy medium. I am getting a lot of help here and at android forums, thats how I found this site My wife has the same phone and is jealous of my speed but is scared to let me flash a rom to hers. She watched me stressing out when I was getting stuck in boot loops! I kept trying to partition my SD card to get apps2sd working, every time I after my partition I would get stuck in a dang boot loop. Seems after I partition the SD I need to re-flash my rom in order to get Fresh to see the partition. Or I think thats the issue? As of now I dont have a class 6 SD card, just found out I will need one so I am gonna wait for the apps2sd thing.
thanks
Click to expand...
Click to collapse
Like I said, I'm on CM6, but I run Aggressive with no problem. In reality, either Strict or Aggressive works well, but if you up it above that then it basically starts interpreting every application running in the background as an extraneous app and kills it aggressively whether you're using it or not. Also, because the system is constantly trying to increase the memory thats available to meet the thresholds, it is constantly working to close programs that aren't there, and then it becomes a bog on the system again. Long story short, stick to Strict and you should find that perfect balance and remain smooth.

Question about RAM

I am running Froyo from Samsung web site.
Anyways, I know froyo was supposed to free up 512 ram. I know about 100 goes to gpu. However my phone is left with 339 ram to use (as seen in task manager). However it is always using at least 220mb, even when I close everything and restart the phone. When I open up advanced task killer it says 116m free. Why so little? How can I get more easily? without having to use ROMs or kernels?
Or is this how it is for everyone? I feel kind of cheated!

First of all, you should never need to use anything like Advanced Task Killer now that you have froyo. There are legitimate uses, but its really something you can go without. See http://www.reddit.com/r/Android/comments/cwovf/in_light_of_all_the_discussions_right_now_about/ for a good writeup.
Your phone, just like a computer, uses an optimal amount of RAM at all times. That does not mean minimal. Android phones dynamically allocate RAM for applications and the OS. Why have 200MB of RAM free when you can instead have 100MB free and have the phone be more responsive? 2.2+ manages memory more effectively, and if you are not using an application, will close it. Its fairly difficult with any normal usage scenario to cause your phone to run out of memory.
In short, you don't really need to worry about it because its that way on all Android devices (and generally any modern computing device), and that if is not affecting the usability then its not an issue

Completely agree With first comment. Everyone is concerned about keeping as much ram free as they can but it does not speed their phone up at all. Ram its just like quadrant scores a useless numbers if the phone is response and speedy in actual use
Sent from my SAMSUNG-SGH-I897 using XDA App

U could try reading this: Android Memory Management

your ram usage does seem a little high, you may have an app that is using a lot of it. the 339mb available is normal. some kernels will show quite a bit lower than that but the never seeing more than 116 free is odd. the rom im curently on fluctuates from about 140mb used to 240mb used. i only know that because i clear ram before running benchmarks, have you tried clearing ram in the built in taskmanager? or are you only going off the task killer? because the task killer doesnt necessarily clear ram.
all i know is task killers are pretty useless unless you have an app that freezes and for that the taskmanager built in to many of the samsung roms should be enough for that though it does not show every process that is in a saved state or system processes. task killer programs do more harm than good but i cant seem to get people off them. danm verizon store sets people up with them and poeple use them religiously. i figured out in the first few days of using android on my aria that getting better speed and battery life by killing tasts was a futile effort. there are few market apps that use resorces when running in the background and if you exit the app with the back button it doesnt save the state or run in the background. not that saved state is a problem. i only found that the phone uses more battery restarting processes that are designed to be running and has more lag than when you just use the phone and ignore the running processes.

Personally the only time you should be ever worried about ram is when watching a flash video or viewing a webpage with a lot of stuff. Other than that, as said, if the phone runs smooth, who cares about ram?

(Q) Droid Charge ram 328 or 512?

Sorry if this question has been answered somewhere, but I searched and couldn't find a reliable answer. When I go to task manager, it always shows memory usage out of 328mb available. Everything I read prior to purchase indicated there was 512mb ram. If I'm going to be locked in contract for any extended period of time I definitely need more than 328. 512 is already low by today's standard, but 328mb is ridiculously bad. Anyone that knows the answer and a way to verify would be greatly appreciated as all the searches I do come up with both answers.
Thanks for the help guys.
Sent from my SCH-I510 using Tapatalk

In addition to the above mentioned issue... I frequently have 250+ out of the available 328 used even when task manager indicates no apps running. Is there that much going on in the background? In case this helps I'm running the ED2 debloated rom so I can't imagine how bad it would be if I still had all the bloat in there.
Thanks again for the input
Sent from my SCH-I510 using Tapatalk

The phone has 512MB total, with some of that allocated to the system that can't be used by apps. This memory goes to thinks like the GPU to give you that stellar video performance. Sucks that it can't be changed really, but that is how it's setup. I believe that we can get a few MB back from the system, but you won't get all of it back.

imnuts said:
The phone has 512MB total, with some of that allocated to the system that can't be used by apps. This memory goes to thinks like the GPU to give you that stellar video performance. Sucks that it can't be changed really, but that is how it's setup. I believe that we can get a few MB back from the system, but you won't get all of it back.
Click to expand...
Click to collapse
Thanks a lot for the response. Makes me a lot more comfortable with holding on to this guy. There must be some serious bacground processes going. because I've yet to see anything lower than 180mb used (about 150 available) and that's with autokiller at extreme preset, which I normally wouldn't set so high...I just wanted to see if any additional mb's would free up.
Sent from my SCH-I510 using Tapatalk

Ok, android 101:
Android uses smart caching and background process management to keep your apps available and running smoothly. As such the more RAM you have free the more you are WASTING. This system is designed to run up to 99% RAM use before turning off any running apps/background processes.
Ever since android 2.2 it has been HIGHLY efficient at doing so. Using autokillers to keep RAM free is pointless, as most apps don't even use ANY CPU when in background, unless they perform background checks for things like is it your turn on words with friends, etc. Unless you have an app that uses too much background data like this (in which case I'd just get rid of the app...) then using killers is pointless, let the OS run the way it is designed to do. Ever since I listened to a ROM dev and stopped using task killers my battery life on my original droid has nearly tripled, and I'm overclocking it from 566 to 1200mhz!
Android is not windows 95, you don't need to hold its hand and make sure things are closed, doing so actually defeats the advanced features of the OS, decreases battery life in all but a very few cases, and increases your app startup times, keeps you from getting background updates properly, etc.

warriorprophet said:
Ok, android 101:
Android uses smart caching and background process management to keep your apps available and running smoothly. As such the more RAM you have free the more you are WASTING. This system is designed to run up to 99% RAM use before turning off any running apps/background processes.
Ever since android 2.2 it has been HIGHLY efficient at doing so. Using autokillers to keep RAM free is pointless, as most apps don't even use ANY CPU when in background, unless they perform background checks for things like is it your turn on words with friends, etc. Unless you have an app that uses too much background data like this (in which case I'd just get rid of the app...) then using killers is pointless, let the OS run the way it is designed to do. Ever since I listened to a ROM dev and stopped using task killers my battery life on my original droid has nearly tripled, and I'm overclocking it from 566 to 1200mhz!
Android is not windows 95, you don't need to hold its hand and make sure things are closed, doing so actually defeats the advanced features of the OS, decreases battery life in all but a very few cases, and increases your app startup times, keeps you from getting background updates properly, etc.
Click to expand...
Click to collapse
I was always of the impression that an app such as autokiller differed from a standard task killer in that it modified the values at which android natively kills off processes vs me going in and manually closing an app (which i never do). I too have read articles that task killers are pointless and do more harm than good, but I always thought autokiller was a different sort of "tweak" if you will. I've even seen several devs promote that they've modified androids native memory management to be more aggressive, etc...which is what I thought autokiller accomplished. Autokiller simply seemed necessary to me with the Charge because I was experiencing lag and lockups even with a debloated rom and voodoo kernel. Clearly there could be several culprits to this this and I was simply testing out different fixes and seeing what the results were. Thanks for the heads up though...learn something new every day.

Autokiller memory opimizer (not a task killer)

What is the verdict on these memory optimizer type apps?
http://andrs.w3pla.net/autokiller/faq

I can't recommend Autokiller highly enough on Samsung Froyo phones. It was a must use, even with Voodoo, on my old SGS i9000, and the same thing on my Droid Charge.
True story: just this morning I was ready to throw my Charge against the wall in frustration. Ever since upgrading to EE4 the damn thing was LAG LAG LAG city, even with Voodoo. Phone was snappy as heck after a reboot, but after a couple of hours use, it started to lag, and then would get so laggy it was almost unusable. Seriously, opening apps would take 10 second. Auto-rotate the screen took 4-5 seconds.
I enabled Autokiller, set it "aggressive" and the phone's a speed demon again.
Try it, can't hurt your phone with it, might help it exponentially.

waiting for the phones built in lowmem killer is useless, use autokiller and you will notice an immediate improvement in phone response time. heres a point for ya, without it installed i have 78mb ram free,,,with installed 158ram. thats huge. for a phone. plus they dev just updated to reduce memory usage of the app itself, plus there are tweaks in the settings menu to make the IO scheduler more aggressive, improve sd card reads, battery life, wifi, networ,...its layered man. and free....whats more to love. the only other way i have found to improve phone speed feelwise is with kangfucius kernel and set that terd up to 1500hz with cfq. shazaam.

elucid said:
What is the verdict on these memory optimizer type apps?
http://andrs.w3pla.net/autokiller/faq
Click to expand...
Click to collapse
Basically what you're doing is tweaking the settings for how Android frees up your memory. In theory, it should be good, because the defaults that were picked with the Android release aren't going to be appropriate for everyone. Just be careful not to be too aggressive or you might start losing functionality you want, such as alarms or background email checks.

chadness said:
Basically what you're doing is tweaking the settings for how Android frees up your memory. In theory, it should be good, because the defaults that were picked with the Android release aren't going to be appropriate for everyone. Just be careful not to be too aggressive or you might start losing functionality you want, such as alarms or background email checks.
Click to expand...
Click to collapse
Good point on not being too aggressive. The higher you set it, the more sticky sports ate pushed out of memory, so with the settings I have right now the phone kills some things that in the oat would have been running when I went back to them. I'm going to drop down from aggressive to strict and see if that's a better balance for how I use the phone.
Sent from my SCH-I510 using Tapatalk

Call me crazy but...
Android is linux based right? I.E. it uses a linux kernel? I was under the impression that was true. If so, unless you're running into the problem of completely filling RAM and having to wait for stuff to be cleared, this kind of thing will not help you!
Linux intentionally leaves commonly used items in RAM in order to decrease access time. It is perfectly normal for such a system to run at 70-80% memory usage. It is, in fact, a GOOD thing, because it means more memory is actually being put to a potentially useful purpose.
That being said, if you're actually running out of RAM I suppose something like this could help.

slight23 said:
Android is linux based right? I.E. it uses a linux kernel? I was under the impression that was true. If so, unless you're running into the problem of completely filling RAM and having to wait for stuff to be cleared, this kind of thing will not help you!
Linux intentionally leaves commonly used items in RAM in order to decrease access time. It is perfectly normal for such a system to run at 70-80% memory usage. It is, in fact, a GOOD thing, because it means more memory is actually being put to a potentially useful purpose.
That being said, if you're actually running out of RAM I suppose something like this could help.
Click to expand...
Click to collapse
Yes, yes, I frequently give the "in linux free memory is wasted memory" whenever people want to use some taskkiller app because they want a lot of free memory. This isn't about shooting for some high free memory number because we're Windows minded and think we need a lot of free memory, this is about finding the right settings for Android's own memory manager to keep the phone responsive. There's been something about my Samsung phones (except the Nexus S) where they just get laggy as hell with the stock memory manager settings.
As described above, my phone was almost unusable after a couple of hours booted up until I enabled Autokiller. Maybe something I'm running has memory leak; could be, but I pretty much run the same apps on all my phones, and the HTCs and Nexus S don't get laggy like the i9000 and Charge do.
This app, or the one named MinFreeManager really help. In the early days of the i9000 on MoDaCo site we were using the cat command to tweak the settings manually in our efforts to find a way to stop RFS lag before Voodoo came along.

I just installed this yesterday and configured it for strict mode. I also enabled all of the advanced system tweaks and so far I haven't noticed much if any difference, perhaps it depends on your individual usage and what apps, launcher, etc you're using. I'm going to leave it on and see how it goes though.

Any still using this? Any want to share what settings they use?

[MOD] Fixing N7's RAM issues

The following are two ram optimising scripts that actually do something. They will ensure a fluid experience by keeping a minimum of 100mb of ram free. Simple as that.
STEPS:
Download zip and extract files "boost" and "freeram".
On the tablet , use a root file manager
Paste files in /system/bin (system needs to be re-writable obviously)
Set permissions to rwxr--r--
Activate scripts manually after every boot using android terminal emulator:
1) free ram (to see ram usage)
2) su
3) freeram (no spaces)
4) boost
5) free ram (to see ram usage - compare to values in step1)
6) Profit
Explanation:
"boost" - activates Adrenaline Boost V3 (i take no credit for this script). What this does is clear the ram cache, freeing up ram storage.
"freeram" - a script i made, adjusts minfree values (android's built in ram manager) to kill off more empty apps from ram when ram usage exceeds certain values - not a task killer, so doesn't affect battery life
In android terminal emulator:
"su"
"cat /sys/module/lowmemorykiller/parameters/minfree"
-will show you the prior minfree values, "freeram" script adjusts these to 8192, 10240, 12288, 21000, 23000, 26000
Notes:
All changes reset on boot, so you'll need to to run everytime you reboot
check your ram usage before with: "free ram"
These two scripts will generally ensure about 300-400mb free ram always.
Removing widgets will improve this also.
If after a while nexus is feeling slow again, run "boost" script.
Fstrim or "lagfix" also helps with those having slow emmc issues
Enjoy more free ram

Or download an app called autokiller memory. Works miracles

mrazndead said:
Or download an app called autokiller memory. Works miracles
Click to expand...
Click to collapse
didn't know about that app.
This is more geeky and cleaner though, who doesn't want to use terminal??
And i don't think the app flushes the ram cache (similar to the adrenaline v3 script)

According to anandtech:
"I’m told that TRIM support has been part of the eMMC standard since around version 4.2, it was just a matter of enabling it in software. The result is that the new Nexus 7 shouldn’t have these aging affects at all. Better yet, fstrim support has also been added to the old Nexus 7 with as of the Android 4.3 update, so if you’ve got a Nexus 7 that feels slow, I/O performance should get better after fstrim runs in the background. I'm checking on whether the other Nexus devices have also had TRIM support added. I would consider the slow storage aging problem fixed as of now, and Google took the eMMC and storage I/O performance issues with the previous Nexus 7 to heart for this version."
Link: http://anandtech.com/show/7176/nexus-7-2013-mini-review/4
So that's good news for poorly ageing nexus 7's, just update to 4.3 instead of running lagfix

@mods: close/move the thread please.
this is another minfree / lowmemkiller script like Supercharger V6 which offers nothing more than actually less memory. What do I mean? It makes the device start killing apps/processes much sooner rendering it multitask-less. Provides a boost but at a terrible cost: much less mem available to apps...

I was able to multitask smoothly between 8 open apps without reloads. And I've been using this setup for 2mths or so.
I had memory issues with my n7, and this solved them, and I wanted to share as users (can't remember the thread name) were discussing slowness due to limited free ram, and this worked for me.
Mods feel free to close, sharing experiences is not appreciated obviously..

mpokwsths said:
@mods: close/move the thread please.
this is another minfree / lowmemkiller script like Supercharger V6 which offers nothing more than actually less memory. What do I mean? It makes the device start killing apps/processes much sooner rendering it multitask-less. Provides a boost but at a terrible cost: much less mem available to apps...
Click to expand...
Click to collapse
So basically, the Xda crowd is too dumb to make up their own minds?
Shouldn't it be up to the individual to try this (and any other) mod freely. Your personal experience with similar mods is welcome, but you trying to tell others what is best for them is way out of line imo.
IceColdJellied One X
Tapatalk 4 Beta

Shared knowledge = more knowledge imho
Thanks for sharing it! :beer:

On linux systems having a little amount of free ram is not necessarily a bad thing. it means that the apps you use most are available to be opened very quickly.
OP: what do you mean by "empty app"?

Appreciate your effort, OP. However, a more user-friendly way is to install an app like Rom Toolbox(and others) and change minfree. RT has presets, and set at boot features. I personally subscribe to the thought process that unused ram is wasted ram.

Nbsss said:
According to anandtech:
"I’m told that TRIM support has been part of the eMMC standard since around version 4.2, it was just a matter of enabling it in software. The result is that the new Nexus 7 shouldn’t have these aging affects at all. Better yet, fstrim support has also been added to the old Nexus 7 with as of the Android 4.3 update, so if you’ve got a Nexus 7 that feels slow, I/O performance should get better after fstrim runs in the background. I'm checking on whether the other Nexus devices have also had TRIM support added. I would consider the slow storage aging problem fixed as of now, and Google took the eMMC and storage I/O performance issues with the previous Nexus 7 to heart for this version."
Link: http://anandtech.com/show/7176/nexus-7-2013-mini-review/4
So that's good news for poorly ageing nexus 7's, just update to 4.3 instead of running lagfix
Click to expand...
Click to collapse
I wish My poorly aging Nexus 7 hasn't improved at all since the 4.3 update. In fact I think it's running even slower. I haven't run lagfix since the update though since I lost root and I'm waiting for Wug's updated toolkit to get it back. (I know I can restore root with other methods but I'm lazy and toolkits just make it easier.)
Aside from the TRIM issue I loved my old Nexus, but 16gb just wasn't enough space anymore and any time I dipped below 4gb of remaining storage it would lag so horribly I'd have to wipe the whole thing and start over if I wanted it to be buttery smooth again, even after using lagfix. Lagfix helped a bit, but it was still crawling compared to a freshly wiped tablet.
I've got a 2013 Nexus 7 on the way though so hopefully what you said about TRIM on the newer model is true and this one won't age as poorly as the original. Even if it does, having an extra 16gb of wiggle room can't hurt.

My thoughts
The most aggressive lvl on the minfree script is 26K ie 26,000*4/1024 = 101mb
Having less than 100mb of ram (ie over 90% ram used) slows down my n7 and its really bad when i have 19-45mb of ram left...
The fact that the script resets on reboot means i can easily compare the difference, for ME it helps and i can't notice an impact on multitasking (and thx for teaching me how to use terminal to check ram usage )

mrazndead said:
Or download an app called autokiller memory. Works miracles
Click to expand...
Click to collapse
Since i use this app my ram is always ok. Thanks so much, really improved a lot