• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root AutoKiller Memory Optimizer killing HTC Sense

CYNICALifornia

Android Enthusiast
Running a rooted Evo (obviously) with OMJ 3.8.

I have Sense running with Itching Thumb(which I love).

For about a month or so I have been using Autokiller Memory Optimizer which has improved me phone's performance (I determined this in a sisde by side comparison with my wife's unrooted evo. I know this is not a perfect test, but as OMJ uses a stock kernel it's close enough, IMHO)

Since I have been running Itching Thumb I have notices when switching apps Sense will occationally get killed. I can only assume this is because of Autokiller.

When I looked on Autokiller Sense had an oom of 8, which with a memory use of 9mb and change makes it a candidate for being killed, I would assume. The oom for sense seems to bounce around a bit, it's usually 8, but I have seen 4 and 1 also.

This is a mild annoyance, waiting for Sense to restart, but if I could avoid it I'd like to. I've thought of a few possible fixes I would prefer not to do, which include:

Uninstalling Itching Thumb
Lowering the free memory threshhold on Autokiller
Temporarily lowering Sense's oom in Autokiller

What can I do to keep Sense from being killed? (I considered a bulletproof vest, but they didn't have one that fit) Can I lower it's oom? Any ideas? Or should I just suck it up and accept it and a byproduct of my tinkering?
 
Running a rooted Evo (obviously) with OMJ 3.8.

I have Sense running with Itching Thumb(which I love).

For about a month or so I have been using Autokiller Memory Optimizer which has improved me phone's performance (I determined this in a sisde by side comparison with my wife's unrooted evo. I know this is not a perfect test, but as OMJ uses a stock kernel it's close enough, IMHO)

Since I have been running Itching Thumb I have notices when switching apps Sense will occationally get killed. I can only assume this is because of Autokiller.

When I looked on Autokiller Sense had an oom of 8, which with a memory use of 9mb and change makes it a candidate for being killed, I would assume. The oom for sense seems to bounce around a bit, it's usually 8, but I have seen 4 and 1 also.

This is a mild annoyance, waiting for Sense to restart, but if I could avoid it I'd like to. I've thought of a few possible fixes I would prefer not to do, which include:

Uninstalling Itching Thumb
Lowering the free memory threshhold on Autokiller
Temporarily lowering Sense's oom in Autokiller

What can I do to keep Sense from being killed? (I considered a bulletproof vest, but they didn't have one that fit) Can I lower it's oom? Any ideas? Or should I just suck it up and accept it and a byproduct of my tinkering?


I'm not going to get into the whole you shouldn't use/need an auto killer debate (i use one...with very specific settings successfully)

can you not set autokiller to simply ignore sense?
 
Nope.

Autokiller is not a task killer. It modifies Android's memory management system to maintain more memory free for apps to use as cache. Thus, there is no ignore list.
 
Nope.

Autokiller is not a task killer. It modifies Android's memory management system to maintain more memory free for apps to use as cache. Thus, there is no ignore list.

I guess what I find confusing is that it sounds like it is doing that by prioritizing apps based off of memory usage and then killing tasks lol. it sounds like a more customizable task killer imo....again...I am NOT dissing you for using it, I have found the right combination of settings that result in almost no battery drain at all with screen off and have no reboot/foreclose issues so I can't agree with a "do not use a task killer memory manager" at all statement

I would first try adjusting the settings that you mentioned. That sounds like it will be the only way to keep autokiller and hopefully prevent it from killing sense
 
Methinks you are missing a 'not' there . . .

I guess I'll turn down Autokiller a bit. Do you have your configuration posted somewhere? I'd be interested to see what you have done?

haha yeah I had a customer come in mid sentence lol

I will see what I can put together for my set up...it is actually really simple

10am today 88% 2pm 88% had a 20 minute phone call, caught up on facebook and sent 5 texts...and now at 81%
 
Awesome.

Battery will always suck where I work though . . . phone says the 90%+ I have no signal. Can't do much about that than just plug in or shut down.
 
Awesome.

Battery will always suck where I work though . . . phone says the 90%+ I have no signal. Can't do much about that than just plug in or shut down.

airplane mode...you already know you don't have a signal lol :D I will get a list together of what I have done over the weekend
 
What is best settings to have Rooted evo to help increase battery life using autokiller memory optimizer? I currently have it on aggressize but I'm new at this so I don know it the higher the settings the more it saves or if t just makes phone faster or vise versa. i am alos using overclock set on min 128 and max on 806. Please help.
 
Back
Top Bottom