1. Check out our companion app, Forums for Android! Download from Google Play

Support help please. new using autokiller memory optimizer/overclock widget.

Discussion in 'Android Devices' started by Cervantes13, Mar 25, 2011.

  1. Cervantes13

    Cervantes13 New Member
    Thread Starter

    Mar 25, 2011
    i rooted my evo 4g using unrevoked. and its worked perfectly i installed a new kernal that's suppose to help with overclock widget. my settings for that are 128 min and 806 max. i want my phone to not be extremely slow but also have good battery life which stock evo does not. also, i'm using autokiller memory optimizer and have it set on aggresive. i'm not sure if that increases speed or slows down phone or increases batter or drains. i would like some help figuring out the perfect settings in which my battery doesn't drain in 4 hours heavy use and doesn't make my phone extra slow while surfing web or other things. making it not lag. thank you.

    i'm also not currently using and sort of task killer either.

    Does setting optimizer on strict drain battery or help it.


  2. lordofthereef

    lordofthereef Well-Known Member

    Nov 11, 2010
    I haven't tweaked overclock, but I can tell you task killers are worthless. They simply aren't necessary. Do a search here on task killers and you will see the reason why. namely, a "background" app isn't actually draining your battery at all and is supposed to be there.
  3. rtfmoz

    rtfmoz New Member

    May 18, 2011
    F5 Instructor
    Its a pretty safe statement to say all task killers are garbage, unfortunately you are wrong.

    Android has it's own built in low level task manager but it is far more tweakable than its default settings. Autokiller Memory Optimiser taps into this and provides a series of task management profiles which improve how this built-in process works. I can tell you it works because I use it and it definately improves the responsiveness of the operating system.

    There are also advanced tweaks which are related to overall Android performance are very nice, albiet a tad more dangerous.


  4. ardchoille

    ardchoille Well-Known Member

    Mar 8, 2011
    Ordained Minister
    I develop Android apps so I though I'd explain why a task killer isn't needed on an Android system.

    Android apps use activites to preform tasks. For example, if you use a file manager to send a picture via email, the file manager calls the send activity within an email app, passes the file name to it and the email app sends the picture.. not the file manager. This will result in seeing the email app as "running" even though the user didn't actually launch that email app.

    Smaller apps
    Using activites helps developers design smaller apps. A file manager app that contains every bit of code needed to do everything a file manager does would likely be so large that no one would want to install it. Developers know that an android phone more than likely has an email app so there is no need for the developer to include email code in his/her file manager to send a picture when he/she can call an activity in an existing email app to do the job. This results in a smaller file manager app since there is no need to include email code or any other code for an activity that can be done via an app that is already present on the phone. This also alleviates redundant code. When you install an app outside of the android market, also known as sideloading, the file manager app calls the package installer (already present in Android) to install the requested app.

    Running apps vs. cached apps
    The "Manage Applications" list included in many android devices lists running apps as well as cached apps. Cached apps don't use any CPU or battery, they're cached so they will load faster the next time you need them. Killing cached apps results in those apps requiring more time to load the next time they are launched.

    System management
    By default, every android application runs in its own Linux process. Android starts the process when any of the application’s code (activities) needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.

    * Android is hard coded to automatically kill a task when more memory is needed.
    * Android is hard coded to automatically kill a task when it’s done doing what it needs to do.
    * Android is hard coded to automatically kill a task when you haven’t returned to it in a long time.
    * Most services (while possibly running in the background) use very little memory when not actively doing something.
    * A content provider is only doing something when there is a notification for it to give. Otherwise it uses very little memory.
    * Killing a process when it isn’t ready only causes it to have to reload itself and start from scratch when it’s needed again.
    * Because a task is likely running in the background for a reason, killing it will only cause it to re-spawn as soon as the activity that was using it looks for it again. And it will just have to start over again.
    * Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few.
    * The only true way to prevent something from running at all on your phone would be to uninstall the .apk.
    * Most applications will exit themselves if you get out of it by hitting “back” until it closes rather than hitting the “home” button. But even with hitting home, Android will eventually kill it once it’s been in the background for a while.

    If you see an app running that you didn't launch, it's most likely because an activity within that app was called by another app to perform a task. If you kill the app you didn't launch, the system has to relaunch that app in order to complete its task. This is why some people kill a task and then see it immediately running again. When a user kills an activity, the system is forced to restart that activity from scratch in order to complete the task it was trying to complete before the user killed it. If the user continues to kill that activity the system will continue restarting it. This creates a situation in which the user is constantly battling the system and the system will win because it is doing what it was designed to do.

    Android is Linux
    Android is not a Windows-based OS, it is based on Linux. Many of the apps you think are running aren't actually running, they're cached, this is typical with a Linux operating system and is much more efficient than other systems. Cached apps don't use any CPU or battery, they're cached and will load faster the next time they're needed.

    You're better off without a 3rd party task killer and letting the system do what it was designed to do.
  5. BigMamma


    May 16, 2011
    Boooyoooow, that developer just shot down this post. I'm going to go with the guy who graduated from school and actually does this for a living rather than allow anyone to adhere to your post. Please do not post lies in this forum. Thx

Share This Page