Related
Raphael is brutally closing programs!
I really dunno why is this happening... I have 50% of RAM free and it lets me run just 3-4 programs together. When I run one more... it occasionally selects one thats previously ran and kills it silently... I really wouldn't like to "Clear Storage" from settings
I also had this problem when I first got my TP. It's a simple fix - you need to disable AutoKill. With a registry editor, go to HKCU\Software\HTC\TaskManager, and change the value of “EnableAutoKill” to “0".
^ yes this a good fix. I remember I couldnt switch between opera and replying to a text message, I felt like I was back to a feature phone, with one thing at a time capability.
There is also a registry tweak that instead of killing apps you can change the threshold at which the system starts auto-killing, same registry path.
You guys are amazing! THANK YOU! BUT... I still have the problem
Any other ideas?
You can refer to this thread:
http://forum.xda-developers.com/showthread.php?t=426585
In the section of "Tips", there is a tweak which solved the problem perfectly
Thank you. Tried that caches tweak, it made whole system run much faster. But still - i cannot seem to get 4 proggies to run at the same time. Always the first dies... flip flop
This thread is turning into a copy of few others around here. Only this is new and alive.
Please help me out.
I've tried:
1) The HTC Task Manager registry tweaks
2) The cache sizes maximizing
and...
3)?
Maybe the ugly 32MB/32Process limit (http://msmobiles.com/F/viewtopic.php?p=36334&highlight=&sid=c6b5982e059ec35ce19fd3cd952bd683) is still present in WinMo6.1?
Hello!
OMFG! After disabling autokill my TP started to act almost like desktop in case of multitasking
I was able to run around 12 programs at a time, but i've also made changes to memorytreshold, the value i set was 173015040 (1.5 times the default value).
The funny thing was that TP was still responsive to commands and even opera ran smoothly when surfing throu light web pages.
First app closed after memory usage peeked around 65%, but the rest was still responsive.
Hope this helps
BHole
Thats my point. Same limit like 65% because I have customized my device with launchers, hardkey remapper, Wktask etc. Now I can have (only) five apps running at a time... Is there a sort of free RAM threshold inside the WM6 or HTC-s stock (1.9) ROM. Maybe it is still the 32 process limit from the old times?
Hello!
It looks like there is some kind of limit to number of proceses or memory used by them but if you customized your pda maybe you should disable some of the oryginal programs that are runing in the background. I saw some registry entries in taks manager that hid some of the runing aps maybe not all of them are nesesery for you and can be disabled to lower proces count.
BHole
Yeah.. but I would like to USE the RAM the device has.... I'd like to run manymany programs so the RAM load would be for example 95%. Why is not that possible?
Running Applications
Hi, im considerably new to the whole android development i have a g1 since early december and have upgrade it to the modded JFC 1.31 ADP. I also have the adp spl i think thats what u call it .
My question relates to the running processes/tasks/programs. I am concerned about the amount of programs that run in the background. Is there a way to cut down on this?
I have already removed Calendar, Amazon, Calculator, Calendar Provider seeing as how i do not intend on using these as for calculator i have installed a scientific calculator.
Its more or less Facebook, Craigslist, Imeem. The other bckg progs Gmail, Messaging, Alarm Clock are all smth i use so therefore i have no issue on that but ive tried editing settings on Craigslist, Facebook, Imeem and others to change the update interval and have maxed those out but still tend to run in the background i use the programs but i dont need them to update themselves.
Edit: I have also stopped the auto sync on Calendar, Gmail, Contacts Seeing as for Calendar i dont need it, Gmail i check it often, Contacts i dont use on my gmail service.
Have you got the task manager app from the app store? Thats what I do, and kill all the apps I don't need active.
TimSykes said:
Have you got the task manager app from the app store? Thats what I do, and kill all the apps I don't need active.
Click to expand...
Click to collapse
Yes i have, however they keep coming back up!
yeah I know some of them do. to me I don't know why alarm does. I don't even have a alarm set on my phone.
They come back due to the way android handles and saves tasks. The OS will keep resurrecting them thinking they are just dormant and were axed by them.
ArronL said:
They come back due to the way android handles and saves tasks. The OS will keep resurrecting them thinking they are just dormant and were axed by them.
Click to expand...
Click to collapse
So is there a way around this or not?
yeah.. im having the same problem, i shut them all down via task manager, but after like 1 minute i go back in there and they all come back up, is there any way to make them be off permanentally till you use them again?
tbh, the way the android works, if it keeps bringing these programs back they're probably not eating up too much memory.
in fact, no matter how much crap is running in the background i've never experienced any lag or anything. makes me wonder if there's any point in killing apps, except for ones that may be constantly connected to the internet.
Meltus said:
tbh, the way the android works, if it keeps bringing these programs back they're probably not eating up too much memory.
in fact, no matter how much crap is running in the background i've never experienced any lag or anything. makes me wonder if there's any point in killing apps, except for ones that may be constantly connected to the internet.
Click to expand...
Click to collapse
Well i definitely notice a lag, although i agree with you on the applications i removed like 80% of them now just using ones i need and just installed the 1.41 everything works great. But run about 10apps let them run in the bckgs and slide the main application tab on the home screen up and down and scroll through the programs. Then kill about all apps but 3 to account for ones you need and try it again you should most likely notice a difference.
Not on lag but background processes use up battery to, I did a wipe and have like four apps on my phone: aim astro any cut and ak notepad (wow must like A's) but my battery life is noticible better than before, I can go a whole day with out having to charge vs having to charge every few hours
does anyone know of a startup manager for the G1 for EG when i reboot or start up my phone i get a lot of services and programs which i use but do not want to start on boot.
i can use task manager to close them once the phone is started but wouldt be happy for something that disables these from the start.
Has anyone found a way to modify what OEM apps boot at startup?
So using Task Manager for Root Users we get this peek into what's ?running? on our phone. or am i sadly confused..
upon initial boot and after letting the phone boot fully (about 3 minutes) i get this list in my taskmanager..
Task Manager ---not oem
Service Viewer ---not oem
MyFaves storage
Messaging
Voice Dialer
Google Talk
Maps
Calendar
Alarm Clock
Power Manager ---not oem
Missed Call ---not oem
Messaging
Phone Recorder ---not oem
MyFaves Storage
Voice Dialer
Google Talk
Maps
The list remains the same even after several refreshes..
...oddly only after killing a few tasks this is added?
Gmail
note: at this point in service viewer/tasks, only taskmanager, launcher and service viewer are present..
After killing every process through multiple refreshes messaging (which I assume is a critical app tied to the notification bar) is the only thing that remains until i load something else..
First question..are the apps listed in task manager actual hurting my battery/memory/cpu performance?
Secone question..Is there any way to auto-kill these tasks upon boot, other than by removing them? Or is there some boot.ini type file that could be editted?
sry for the long post, just curious if something can be done...
Yeah id also like to know how to manipulate what starts up on boot.
Any dev should be able to tell us.
Plenty of apps start at boot.
Seriously I would LOVE the answer to these questions. Thanks
Now while this isn't coming from a dev, when I look at the running app list I often see things I haven't touched, but they won't start unless the phone's been idle. I think what happens is it actively fills empty ram with programs so they will start faster, so I think it's just in the nature of Android.
Fushichou said:
Now while this isn't coming from a dev, when I look at the running app list I often see things I haven't touched, but they won't start unless the phone's been idle. I think what happens is it actively fills empty ram with programs so they will start faster, so I think it's just in the nature of Android.
Click to expand...
Click to collapse
yes but dont they use up cpu/memory/battery? plus i dont think the programs are so resource heavy that they would need a process running.
An answer from a Dev is what we need
I think what we need is an explaination as HOW a program can autostart on boot. If every program on my phone (stored to sd) started automatically when I turned on my phone I'll be waiting a week for it to start up. There has to be a script that these programs add to or something to run these program automatically. Either that or it's the programs themselves that are set up to start up by themselves. Where if that's the case I think we're screwed.
I'm also VERY interested in this.
Also, how to keep apps from auto-restarting once you kill them. PixelPipe has a background service that, once you start the app after reboot, it won't die. Their app support guy states otherwise tho, heh.
Also, I like how the OS says a program has "died"
I wouldn't really worry about it. For one most of those processes will be sleeping. They use no CPU time when they're in this state. Some processes register an event with the kernel and just sleep forever until that event occurs and the kernel reactivates the process. Some processes sleep for a specific amount of time, wake up and do some task, then go back to sleep. In both cases the number of CPU cycles being used are likely negligible. Most of those start-up programs will fall into one or the other category. The stuff that does take up a fair amount of CPU cycles are things like the multimedia system, the UI system, messenging, etc. In other words, the stuff you want to keep running.
Also, I wouldn't pay too much attention to those memory usage numbers. There's heavy use of shared libraries in the system. Ordinarily processes are only allowed to access memory that is allocated to them. This memory is where the process stores the bits that make up its code (stuff that doesn't change) and where it stores its working data (stuff that does change). Its actually more complicated than that but this will suffice for now. Libraries that are not shared are accessible only to the process that is using it and is stored in the memory allocated to it. Libraries that are shared can be used by multiple processes. These shared libraries are allocated to one place in RAM and when an app needs to use one of them the kernel takes care of mapping the location of the library so the app can access it as if it was in its own memory space.
The memory usage numbers you are seeing do not take into account these shared libraries. An app may be using only 1 or 2 MB of RAM but since it uses a shared library the RAM being used to hold the library is also counted and the size could be shown as 20 or 30 MB higher that what it actually is. You could kill a process and recover some memory but its probably not enough to be worth it since more than likely most of the RAM being used was in shared libraries and they'll still be there after the process is gone.
numerik, thanks for the info. But now I guess my bigger concern would have to do with this part:
Some processes sleep for a specific amount of time, wake up and do some task, then go back to sleep.
Click to expand...
Click to collapse
Similar to the problems we run into in windows. Some lame program gets added to msconfig (be it a m$ app or wicked virus), it sits there idle when you fire up your computer uses a minimal amount of cpu amd memory then does who knows what whenever it wants.
If i understand Android correctly, it sends applications into a "background" mode when switching tasks? I would like to prevent that. There are some apps (like games or browser) that need quit a bit of time restoring the last state so this would be usefull for some tasks.
Is this possible ?
TyrionWarMage said:
If i understand Android correctly, it sends applications into a "background" mode when switching tasks? I would like to prevent that. There are some apps (like games or browser) that need quit a bit of time restoring the last state so this would be usefull for some tasks.
Is this possible ?
Click to expand...
Click to collapse
Well, switching to background mode just marks the application as not displaying anything. The way memory management on Android works, if foreground apps (i.e. apps that are actively displaying on the screen) need memory and there's none available, then background apps will be put into a stored state that frees up memory for the foreground apps. Coming back from that stored state is probably what you're noticing. Android also tries to keep a certain amount of unused memory around and will put background apps into stored state to achieve that. We do have pretty limited memory available on this device so some level of pausing is always going to happen. See also: http://andrs.w3pla.net/autokiller/details
You may be able to reduce how many background tasks are put into storage by tweaking the minfree parameters (using e.g. Autokiller Memory Optimizer from the market) to tell Android to aim for a smaller pool of free space.
Mioze7Ae said:
Well, switching to background mode just marks the application as not displaying anything. The way memory management on Android works, if foreground apps (i.e. apps that are actively displaying on the screen) need memory and there's none available, then background apps will be put into a stored state that frees up memory for the foreground apps. Coming back from that stored state is probably what you're noticing. Android also tries to keep a certain amount of unused memory around and will put background apps into stored state to achieve that. We do have pretty limited memory available on this device so some level of pausing is always going to happen. See also: http://andrs.w3pla.net/autokiller/details
You may be able to reduce how many background tasks are put into storage by tweaking the minfree parameters (using e.g. Autokiller Memory Optimizer from the market) to tell Android to aim for a smaller pool of free space.
Click to expand...
Click to collapse
Thanks, i'm will give it a try. Is it also possible to max out swap before sending apps to background? I think restoring the ram-state from sd would still be faster for several apps.
Edit: reading your post again, i'm not talking about a tasking switch delay, but apps that completly reload themselves when switching tasks (DolphinMini page load,DungeonHunter as examples). Just to prevent any confusion...
TyrionWarMage said:
Thanks, i'm will give it a try. Is it also possible to max out swap before sending apps to background? I think restoring the ram-state from sd would still be faster for several apps.
Edit: reading your post again, i'm not talking about a tasking switch delay, but apps that completly reload themselves when switching tasks (DolphinMini page load,DungeonHunter as examples). Just to prevent any confusion...
Click to expand...
Click to collapse
Oh... Sorry I misunderstood. I don't know anything relevant to that case.
I've spent a few hours trying to find how to make certain Droid apps maintain their foreground state when put in the background with no luck. Perhaps it just can't be done.
I'm thinking of the Cydia iPhone app called Backgrounder which lets you choose which apps maintain foreground state when put into the background.
This is necessary, for example, with a note application where you are switching between taking notes and looking up info. Every time you switch back to the note app, you need to go back into your note, put it in edit mode and navigate to the section of the note you were editing. If it were acting like a foreground app in the background, when switching back to it it would already have your note open and be in edit mode with the cursor where you left off.
K9 mail has a similar problem where if you have an email open, switch to another application, when you go back to K9 it takes you to your inbox again where you have to navigate to the email you had open before switching.
Is there a tool similar to Backgrounder for Android?
Thanks.
nheacock said:
I've spent a few hours trying to find how to make certain Droid apps maintain their foreground state when put in the background with no luck. Perhaps it just can't be done.
I'm thinking of the Cydia iPhone app called Backgrounder which lets you choose which apps maintain foreground state when put into the background.
This is necessary, for example, with a note application where you are switching between taking notes and looking up info. Every time you switch back to the note app, you need to go back into your note, put it in edit mode and navigate to the section of the note you were editing. If it were acting like a foreground app in the background, when switching back to it it would already have your note open and be in edit mode with the cursor where you left off.
K9 mail has a similar problem where if you have an email open, switch to another application, when you go back to K9 it takes you to your inbox again where you have to navigate to the email you had open before switching.
Is there a tool similar to Backgrounder for Android?
Thanks.
Click to expand...
Click to collapse
Looking for such tool too. Making app to stick with its foreground state even though it is actually in the background. (Make it appear in notification?)
ZDBox is a useful tool... you can download from market its free and the app has the abbility to:
★ Traffic counter: Monthly/daily mobile data usage overview, shows remaining data traffic, detailed data usage information for each app.
★ Do not disturb: Just set days and the time when you need your privacy and you won’t be disturbed by your phone. Set phone to silent, vibration or airplane mode.
★ App lock: Protect apps with a password or pattern, for exmaple your contacts, Facebook, Twitter, Whatsapp,Gmail and so on
★ Task killer: Kill all apps at once, define protected apps which won’t be killed, set auto kill when screen gets locked, mark single or multiple apps to kill
★ history eraser：clean your（Browser history,market search history,Google Map search history,Gmail search history,Clipboard）
★ Notification bar: One tap on the bar shows remaining battery time, running apps, how much data traffic is left and if app lock is active or not. A tap on these informations starts ZDbox.
★ Uninstaller: Shows used/available internal and SD card memory. Apps can be easily uninstalled. Single or multiple (batch) uninstall possible.
★ App to SD: Move apps to your SD card. Single or multiple (batch) move possible. Only for Android 2.2 and 2.3.
★Cache Cleaner:With Cache Cleaner you can clean your cache of phone.protect your secret without a trace.
I hope you can use for keep your running applications with that app...
sorry for my english...
davidequiz said:
★ Task killer: Kill all apps at once, define protected apps which won’t be killed, set auto kill when screen gets locked, mark single or multiple apps to kill
Click to expand...
Click to collapse
This will not help since the task killer which kills the background apps in inside the android system not an external one.
We must find a way to control the internal one then...
nheacock said:
I've spent a few hours trying to find how to make certain Droid apps maintain their foreground state when put in the background with no luck. Perhaps it just can't be done.
I'm thinking of the Cydia iPhone app called Backgrounder which lets you choose which apps maintain foreground state when put into the background.
This is necessary, for example, with a note application where you are switching between taking notes and looking up info. Every time you switch back to the note app, you need to go back into your note, put it in edit mode and navigate to the section of the note you were editing. If it were acting like a foreground app in the background, when switching back to it it would already have your note open and be in edit mode with the cursor where you left off.
K9 mail has a similar problem where if you have an email open, switch to another application, when you go back to K9 it takes you to your inbox again where you have to navigate to the email you had open before switching.
Is there a tool similar to Backgrounder for Android?
Thanks.
Click to expand...
Click to collapse
Guys, I'm so much looking for a solution of this same thing. The closest I came to is Ram manager. Has a xda threat and can be found in the play store. But it also can't manage to lock an app and prevent its killing (although it helps a lot). I need my navigation always running and it is silently killed or stopped while I'm looking at my mail or have a phone call. This is ridiculous. Have you found a solution. Some way to protect an app from killing and lock it in the foreground. I mean how are they able to do it for the apps which are in the system tray!? Like antivirus apps and tons of other. I can't believe xda experts don't know how...
I would think that Antivirus apps run a service.
In Mioze's CM6 there are build prop edits that might work, but I never tried them.
Code:
# apps to be kept in memory (specified by process name)
# use with caution, RAM is limited!
sys.keep_app_1=
sys.keep_app_2=
I am not an expert and can't tell the difference between service and an app running. What you're saying makes sense, but I need clear instructions somewhere to make an app protected from killing. Thanks for helping.
Sent from my HTC One X using xda premium
Wrong forms this milestone xt720.
Sent from my SGH-T759 using xda premium
I pretty much fixed android multitasking - even on ense 4.0 and 4.1
http://forum.xda-developers.com/showthread.php?t=1900626
Testers welcome.
And for locking an app in a foreground state, my SuperCharger can do that via BulletProof Apps menu.
zeppelinrox said:
I pretty much fixed android multitasking - even on ense 4.0 and 4.1
http://forum.xda-developers.com/showthread.php?t=1900626
wI
Testers welcome.
And for locking an app in a foreground state, my SuperCharger can do that via BulletProof Apps menu.
Click to expand...
Click to collapse
I tested that and almost became an expert. I'm not so sure if it is completely solved, although I have to admit that you have done a great and recognized job.
Just tell me can the script for bulletproof apps work alone, without the supercharger script. Many ROMs have their own memory settings and one is afraid to cover them with supercharger script settings.
But if bulletproof script can run and do the job on itsown then the problem is really fixed.
Yeah its separate.
Alot of devs say dont supercharge because they dont want to be showed up and scare their users lol
But hundreds of roms come supercharged anyway.
zeppelinrox said:
Yeah its separate.
Alot of devs say dont supercharge because they dont want to be showed up and scare their users lol
But hundreds of roms come supercharged anyway.
Click to expand...
Click to collapse
Thanks for answering!
So I'm going to try running only the bulletproof script without the supercharger script and set an app to be UNbillable.
Should I set it to run on startup!? I'm using custom ROM. The last revolution HD.
The init.d script would run automatically.
So you dont need to configure anything.
Whatever app is in the hitlist will get bulletptoofed soon after running the app.
zeppelinrox said:
The init.d script would run automatically.
So you dont need to configure anything.
Whatever app is in the hitlist will get bulletptoofed soon after running the app.
Click to expand...
Click to collapse
I am trying to get this configured. But I only want to run the bulletproof script, not the 99SuperCharger script. I just want to keep my rom's memory settings, cause I am OK with them.
But both of the scripts (99SuperCharger and bulletproof) are going to reside in the init.d folder of my custom rom. So they will both be started, aren't they?
How can I make only bulletproof script run at boot. Should I just delete 99SuperCharger from init.d?
How Android manages Memory
Android groups all apps into 6 groups, from highest priority to lowest:
Foreground app - you see this app on screen, currently running, but also includes the system itself and "phone"
Visible app - the app is running and visible, but due to multi-tasking or such is not currently "on top"
Secondary server - services that stay in background and apps such as Launcher (or other home replacements). Most services go here, like music player, clock updater, background sync, and so on, that's not built into the OS.
Hidden Application - apps not visible, but still running in the background
Content Provider - process that provides content to the foreground, such as "contacts content provider", "calendar content provider", and so on. May also known as "storage".
Empty App - the app is in standby, not being used, but is still in memory.
How to manipulate this to get the best performance
We can manipulate our OOM values for each of these categories using the app "System Tuner Pro" (not sure if it works with the free version or not) or "Auto Memory Manager", there may be others too. After installing from the market, open it and click on "Memory" - you will then be able to change OOM values. Having a lower OOM value for a category, means android will wait longer until killing apps from that group.
From what I have experienced, the more open apps in the "Empty App" category, the slower and more sluggish the phone. Having these apps open is basically a waste of memory, because they are in standby and not being used. A high OOM value should therefore be set for "Empty App".
Processes that fall into the "Content Provider" category are also a waste of space; they only actually get used when running the application that service belongs to. This means that often the service will be running in the background when it doesn't actually need to be. A high OOM value should therefore be set for "Content Provider".
The other four categories all contain apps actually being used by the user. When multitasking you want these apps to stay open. A low OOM value should therefore be set for "Foreground App" "Visible App" "Secondary Server" and "Hidden Application"
Doing this is similar to what the SuperCharger Script does, but in my opinion this solution is simpler to implement and easier to change depending on the users needs.
I have attached a thumbnail of my setup, but everyone uses their phone differently so you may want to alter some of the values.
Click Thanks if you tried this and it helped!
BUMP
Thanks for the guide, trying this out to see if I notice some improvement in my phone.
how do you get the values to stick? I duplicated what you did and backed out and the original presets came back after a reboot. I did not see a "save" option. thanks.
steve austin said:
how do you get the values to stick? I duplicated what you did and backed out and the original presets came back after a reboot. I did not see a "save" option. thanks.
Click to expand...
Click to collapse
After applying the limits, there's a button at the bottom of the page called boot settings.
On the menu this takes you to, click reapply memory settings and then check on boot completed
Sent from my HTC Sensation using XDA
sorry for the noob question, but are u sure its not the other way around? i mean, setting a higher value would mean the app is going to stay running in the background for a longer time?
alireza_simkesh said:
sorry for the noob question, but are u sure its not the other way around? i mean, setting a higher value would mean the app is going to stay running in the background for a longer time?
Click to expand...
Click to collapse
I had this EXACT same initial thought. However, once I stepped back and looked at it again, I realized that he is correct in what he originally posted.
What the high values in his screenshot are basically saying is "When I get to less than 256mb free memory, I am going to dump all the applications of this type" and the low values are basically saying "When I get to only 3mb of free memory then I am going to dump all the applications of this type."
So if you set it HIGH like the original poster said then it will dump those out of memory faster than if you set them to 100mb because then you'd have to have more things filling up memory before they would be dumped.
Hopefully that clears things up a little for you (and others who I'm sure will have the exact same question).
-- Zeustopher
Zeustopher said:
I had this EXACT same initial thought. However, once I stepped back and looked at it again, I realized that he is correct in what he originally posted.
What the high values in his screenshot are basically saying is "When I get to less than 256mb free memory, I am going to dump all the applications of this type" and the low values are basically saying "When I get to only 3mb of free memory then I am going to dump all the applications of this type."
So if you set it HIGH like the original poster said then it will dump those out of memory faster than if you set them to 100mb because then you'd have to have more things filling up memory before they would be dumped.
Hopefully that clears things up a little for you (and others who I'm sure will have the exact same question).
-- Zeustopher
Click to expand...
Click to collapse
Yes that's exactly right, sorry I should have probably explained that a bit better initially.
Zeustopher said:
I had this EXACT same initial thought. However, once I stepped back and looked at it again, I realized that he is correct in what he originally posted.
What the high values in his screenshot are basically saying is "When I get to less than 256mb free memory, I am going to dump all the applications of this type" and the low values are basically saying "When I get to only 3mb of free memory then I am going to dump all the applications of this type."
So if you set it HIGH like the original poster said then it will dump those out of memory faster than if you set them to 100mb because then you'd have to have more things filling up memory before they would be dumped.
Hopefully that clears things up a little for you (and others who I'm sure will have the exact same question).
-- Zeustopher
Click to expand...
Click to collapse
Yea i get it now.
the program developer must make the interface a bit more clear
thanks. I will apply it today and see what happens.
Notification improvement in smoothness in UI.
But setting too high minfree in empty application cause alot of launcher redraw.
cwk_and said:
Notification improvement in smoothness in UI.
But setting too high minfree in empty application cause alot of launcher redraw.
Click to expand...
Click to collapse
That's odd, the launcher usually sits in visible or secondary server... what launcher are u using?
Sent from my Sensation using XDA
I am using Auto Memory Manager for this, thanks for the write up.
mf2112 said:
I am using Auto Memory Manager for this, thanks for the write up.
Click to expand...
Click to collapse
No worries
Didn't know that app existed, will add it to the guide thanks!
I applied your settings to see what happens.....I hqve a question for you. In cm9 and aokp there is setting for Max background process limit.....would you suggest any modification here as well?
dmeinder said:
I applied your settings to see what happens.....I hqve a question for you. In cm9 and aokp there is setting for Max background process limit.....would you suggest any modification here as well?
Click to expand...
Click to collapse
You could give it a shot and see if it helps but I doubt it will. If anything, it will limit multitasking because apps will get closed before OOM values are reached.
Hope that helped
Sent from my Sensation using XDA
this is nice trick but it realy save battery and perfom cpu.
As far as I have heard oom values are not these memory settings you mention. OOM is a specific value for each app. The lower it is, the less prone the system is to kill it off.
I have System Tuner pro but couldn't find how to change the oom value. Only app that could change it is autokiller and those settings don't stick or even work.
My memory settings are killing off some apps that I would like to keep in memory.
making empty app so high means no multitasking at all it will kill almost every app once you exit it, tried these and as sson as i leave browser it closes itself, for multitaskers use 45 for hidden, 70 for content provider, 85 for empty app, do not set it lower than 85 or you may encounter a lag that you can't get rid without taking the battery off because you won't be able to close an appliation with that lag. By the way other three values are not that important set them 7-15-20 no problem at all.
Tom200 said:
As far as I have heard oom values are not these memory settings you mention. OOM is a specific value for each app. The lower it is, the less prone the system is to kill it off.
I have System Tuner pro but couldn't find how to change the oom value. Only app that could change it is autokiller and those settings don't stick or even work.
My memory settings are killing off some apps that I would like to keep in memory.
Click to expand...
Click to collapse
I don't know what ur on about, the tweaks in system tuner pro are for OOM values.
You need to do some more research mate.
Sent from my Sensation using XDA
I found an application named AutoKiller Memory Optimizer by which applying its tweaks It makes my phone more smoothly and saves my battery very well!
There are some reviews below links:
http://forum.xda-developers.com/showthread.php?t=622666
http://andrs.w3pla.net/autokiller
http://andrs.w3pla.net/autokiller/details
http://andrs.w3pla.net/autokiller/kernel
If anyone has installed this application plz give your opinion !
Task killers are pointless, just use Autostarts and Greenify.
That combo will be far more efficient
It's not a regular task killer! I suggest to try it!
Listy2021 said:
Task killers are pointless, just use Autostarts and Greenify.
That combo will be far more efficient
Click to expand...
Click to collapse
It's not a regular task killer! I suggest to try it!
ehsan453 said:
It's not a regular task killer! I suggest to try it!
Click to expand...
Click to collapse
Yes it is, it's just filled with other guff to make it look more advanced or whatever
Listy2021 said:
Yes it is, it's just filled with other guff to make it look more advanced or whatever
Click to expand...
Click to collapse
You have not test it yet, therefore you can't understand what i mean!
ehsan453 said:
You have not test it yet, therefore you can't understand what i mean!
Click to expand...
Click to collapse
How do you know I haven't tested it before?
The whole reason I can make a judgement on task killers (including this one) is that before using Autostarts & Greenify I tested other options, therefore my opinion is valid :good:
Listy2021 said:
How do you know I haven't tested it before?
The whole reason I can make a judgement on task killers (including this one) is that before using Autostarts & Greenify I tested other options, therefore my opinion is valid :good:
Click to expand...
Click to collapse
It's not a task killer. It's an app that modify your lmk and add some tweaks. But you can kill some apps from this app.
What is so special about this task killer? No, I am not gonna test it.
Vit5000 said:
What is so special about this task killer? No, I am not gonna test it.
Click to expand...
Click to collapse
First Plz read reviews in first post and also these two reviews:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Releasing RAM With Autokiller Memory Optimizer
Have you ever wished to speed up your Android, but now known how? Have you tried task killers, but found it hard to tell whether you made an improvement? In this post, we’ll look at Autokiller Memory Optimizer, an app that gives you more control over how Android releases its system resources.
“You shouldn’t be using a task killer with Android” clearly explains why the task killers are not a good solution to fasten up your system in the Android interface. Briefly, we might say that the reason that task killers are no good for Android is that the same system regulates itself for releasing RAM memory. Process are not killed when you close the app; instead the process stays open until the system itself realizes it needs more memory to run a new process. This way, you can actually gain some speed when you restart the app, as its resources may still be in memory.
Just like a computer, a smartphone uses Random Access Memory (RAM) for processing the functionality of softwares and apps. When you are running low on RAM, your phone will start to slow down, because it needs more memory than is available. As a solution to this problem, Android devices has an autokiller that automatically shuts apps down when the memory used is close to the limit. Obviously this limit depends on the capabilities and configuration of your phone.
If you root your phone (and I totally recommend you to do that) you can use apps for changing your system parameters like the RAM auto killing. One of this apps is Autokiller Memory Optimizer available on the Android Market.
As the developer says: “AutoKiller Memory Optimizer is designed to fine-tune Android system’s inner memory manager routines to keep your device fast and smooth. It also features a full-powered process manager which lets you control your whole system.”
Warning: Messing around with system configurations like this is potentially dangerous to your phone, and not for the faint-hearted! Check out our other How To articles for safer tips on improving performance.
Going for It
The system itself divides the process into six different types, and here’s where it gets technical. The six types are as follows.
FOREGROUND_APP: This is the process running the current foreground app. We’d really rather not kill it! Value set in system/rootdir/init.rc on startup.
VISIBLE_APP: This is a process only hosting activities that are visible to the user, so we’d prefer they don’t disappear. Value set in system/rootdir/init.rc on startup.
SECONDARY_SERVER: This is a process holding a secondary server — killing it will not have much of an impact as far as the user is concerned. Value set in system/rootdir/init.rc on startup.
HIDDEN_APP: This is a process only hosting activities that are not visible, so it can be killed without any disruption. Value set in system/rootdir/init.rc on startup.
CONTENT_PROVIDER: This is a process with a content provider that does not have any clients attached to it. If it did have any clients, its adjustment would be the one for the highest-priority of those processes.
EMPTY_APP: This is a process without anything currently running in it. Definitely the first to go! Value set in system/rootdir/init.rc on startup. This value is initialized in the constructor, careful when refering to this static variable externally.
For every type of app, the system has a limit of pages (1 page=4 kilobytes) predefined. Autokiller Memory Optimizer allows you to modify this.
For the changes you can make you have the freedom to set as you wish, but there is a lock on the three first types of apps (this can be removed in the Preferences tab) and there isalso a list of presets configuration as follows (the numbers corresponds to megabytes remaining before shutting apps in the last 3 types of apps): Moderate (30, 35, 40), Optimum (40, 50, 60), Strict (60, 70, 80), Aggressive (82, 90, 98), Extreme (150, 160, 170), Ultimate (200, 225, 250) and (a wink from the developer about the TV series) Lost (4, 8, 15, 16, 23, 42).
Autokiller presets
Within these presets, you should try different ones, because every phone has its own RAM capacity and it would not be a good idea to set a killing parameter that is very close to your RAM total capacity as your phone would be killing apps constantly and you wouldn’t be able to use it at all.
Processes list
The app also categorizes the running apps in the six types and you can kill them manually for RAM release in the tab processes and the same occurs with the services in the current tab.
Services list
This app has also a donate version with some more features like the Chuck Norris mode when you can configure the app to use aggressive killing to release memory. It also gives the ability to set a different preset when the screen of the phone is off (this is very useful because when the screen is off you do not need memory to run new apps, but it still consumes battery).
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Tweak your system thanks to AutoKiller Memory Optimizer
Summary
Relax, I’m not trying to fool you into thinking that a task killer is really a tweak. Don’t be fooled by the ‘AutoKiller’ part of the app’s name, focus on the other words instead, because AutoKiller Memory Optimizer will allow you to fiddle around and make a few adjustments. Read on and find out what kind of adjustments I’m talking about, and whether the app is worth your time.
Features & Use
AutoKiller Memory Optimizer is there to help you bring your system up to par by conducting a bit of fine tuning. The app comes with a task manager. Use the task manager to get rid of lagging processes, the logic behind this being that if you’ve got something running that’s not really doing anything useful, but does consume 98% of the CPU as well as a hefty chunk of memory you should really unload energy hoggers. Your system will thank you by running smoothly. The task manager also displays the oom_value for ever app—more details below.
The app allows you to regulate the settings for the OOM killer, the automatic killer integrated in every Android device whose role it is to create more memory space wherever possible. As you know, in the Android world applications are never halted or shut down, they are merely rendered inactive—until the memory pipes up and the Out Of Memory Killer rears its head. But when does memory shortage become critical? And who decides which apps should be banished, and when should this occur? If you want to make these types of decisions yourself take a look at AutoKiller Memory Optimizer.
Android divides running apps into six categories ranging from the app that you’re currently working with to ‘empty apps’ (i.e. apps that you left by hitting the back button at some point). Once RAM space becomes too low the OOM killer will start by banishing said empty apps, and, if need be, continue working its way up. AutoKiller Memory Optimizer lets you decide how much free RAM space is required for your device run smoothly. There are different presettings to pick from (‘moderate’, ‘aggressive’, etc) and you can check out the developer’s website to read up on user experiences.
Bottom line:
AutoKiller Memory Optimizer affords you easy access to essential systems settings, allowing your Android to perform as optimally as possible. How essential this kind of app is is contingent on lots of factors: which device you’re working with, how good the manufacturer’s presettings are and what can be done to adjust them.
Screen & Controls
AutoKiller Memory Optimizer is set up in a very logical way. While high skilled, expert knowledge of Android isn’t essential in order to get the best performance out of the controls, it doesn’t hurt to have some experience. You can find in depth information and details regarding the settings options on the developer’s website, which means that you really don’t need much background knowledge in order to get something out of this app.
If you have a bit of experience you will find that the app’s controls are intuitive; if you’ve never worked with tweaking before I recommend that you give this app a miss.
Speed & Stability
AutoKiller Memory Optimizer is fast, stabil and dependable. I’ve been using the app for just over a month and it hasn’t crashed once so far.
EDIT: repeated
This actually helps very much with memory management. I've been using it alongside Greenify and Autostarts for several months now.
Those individuals banging on about it being just another task manager clearly did not use this app as it is intended to be used.
Sent from ThePureHeart's I9300 Boss Edition
If i use the "ultimate" preset, will it drain my battery faster?
AzizWahid said:
If i use the "ultimate" preset, will it drain my battery faster?
Click to expand...
Click to collapse
Best preset is optimum
Its 2018 now. Is it still useful?