1. Download the #1 Android News App:   EarlyBird - News for Android
    Dismiss Notice

Freeing up RAMSupport

Last Updated:

  1. Iowabucks

    Iowabucks Member

    Hey everyone, My MT runs off of CM7, and runs pretty good. I have had it for maybe 3 weeks. Quite a step up from the super slow Samsung Intercept i had before.

    I know it has 512mb's of RAM. I keep an eye on it through a clock widget on my homepage. For the most part after reboots, i may see it in the 200mb range. After it's been used awhile it sometimes gets lower than 50mb. Thats when it starts to get laggy. Do these numbers sound about normal for you Triumph users?

    I had Advanced Taskiller on my Intercept which seemed to do a good job of freeing up RAM on a phone that never had much RAM in the first place. I see where most people say to stay away from appkillers for it may do more harm than good.

    I only have maybe 10 extra apps after what CM7 and Googleapps installs. Doesn't seem like enough to slow it down but it does eventually.

    Are there other ways to free up RAM to keep my Triumph running fast?

  2. Unforgiven

    Unforgiven -.. --- - / -.. .- ... .... Moderator

    It isn't the lack of RAM that is causing the phone to become laggy, it is the task killer.

    Android is optimized to run at near memory capacity for both better responsiveness and battery life. The task killer interferes with this optimization.

    Android preloads the apps you use most into memory which uses no more battery when full than empty. They are not using processor power while in memory, they are just sitting there. When you are ready to use the app, it will load faster because it is already loaded. Over time Android will learn what apps you use most, and load those before it loads ones you may not use.

    When you use a task killer, Android will recognize the empty memory and refill it (possibly with the recently killed apps) in order to maintain optimal performance. In essence the task killer and android are "fighting" with each other over the memory and using processer time in the battle. This makes fewer processor cycles available for the app you are trying to use, hence, the laggy feeling.

    I hope this makes sense.
  3. Iowabucks

    Iowabucks Member

    Ok, i understand what your saying. But i don't use Taskiller with my Triumph, just the last phone i had, the Intercept.
  4. Unforgiven

    Unforgiven -.. --- - / -.. .- ... .... Moderator

    Sorry, must have misread your post. I haven't used CM7 in a bit, but I seem to remember the being a setting in there that allowed you to set the amount of free memory android would maintain. That might do what you are looking for.
  5. agentc13

    agentc13 Daleks Über Alles VIP Member

    Usually on the Triumph, I would see about 80mb free (give or take), although sometimes less and sometimes more. Don't use a task killer, it is completely unnecessary and counterproductive.
    You can manually kill apps if you really feel like it is needed by going to menu>settings>apps(click on the running tab) press on the app and there shuld be an option to stop it in there. I am not sure if the menu options are exactly as I have listed, but it should be close enough for you to figure out easily.
  6. agentc13

    agentc13 Daleks Über Alles VIP Member

    Also like Unforgiven said there is a file you can edit to adjust those settings.
    Here is a link from the original CM7 thread with instructions (although with the current build they may have enabled an easier way):
    Unforgiven likes this.
  7. b_randon14

    b_randon14 Well-Known Member Developer

    CM7 has a memory leak in our build, and you need really aggressive minfree setting to keep some ram free.

    I wouldn't use an auto task killer but I keep advances task killer on my phone set to not autokill as an easy interface to manually kill apps I don't need running.

    Honestly I think androids internal memory manager is garbage. It always keeps apps in memory too much and when you go to launch a new one you get lag while it swaps out unused pages for the ones you need. Even with aggressive might free settings, the internal task killer don't work like it should. You don't need alot of free memory but once the memory free gets close to the suze of the Vm heap, its starts having trouble managing swapping out memory pages. I think Google needs a redesign of the memory managing code in the os.

Share This Page