How to limit RAM usage per application - Android General

Is there a way to set hard limits on how much RAM individual Android apps can use? Seems most apps are greedy, and I'm running out of RAM, which makes switching between the apps I am currently using slow.

I used Titanium Backup to freeze all apps I don't use frequently, and now my ram usage is down to about 50%, where it used to be around 90%.
I also use an app called Auto Memory Manager, which controls Android's own memory management. You can tell it to free memory sooner than later, for different types of memory categories. But what made the most difference was freezing apps with Titanium Backup.
I'd still like to know if there is a memory policing app, but the aforementioned are good solutions.

Related

[Q] Need technical review of "Guide to Android OS Memory Management"

Otherwise known as "Why Newer Android Phones Don't Need Task Killers".
This is straight ASCII cut-and-paste from my Evernote page, so any spelling and grammar mistakes are mine. I have looked over various apps such as AutoKiller, Advanced Task Killer, various threads on memory management in Android, even a few bits of Android source code. I know about compcache, minfree, swap, kernel, and more.
This is aimed at an Android owner who knows the basics, but is trying to optimize their device. They may have experimented with ROMs and kernels based on recommendations, but don't know about serious internal tweaking.
I realize what I wrote will probably have the techies screaming "no, no, that's not quite right"... That's why I want a tech review. If I had committed any serious misunderstandings, please let me know. If you have more references, please list them. Would prefer a bit more detailed comments than "sucks" or "great".
-------
Memory Management in Android: the myths and the facts
Introduction
The Android OS, now at V2.3 "Gingerbread", is widely misunderstood, due to lack of hardware specifications and the open nature of system, has created a wide set of myths regarding how the memory is managed, and how one can best achieve good performance on an Android device.
This article will attempt to explain just how Android OS manages memory, dispel some myths regarding Android memory, and show you some techniques that will help you keep your system running smoothly while achieving good performance.
However, first, here's some technical stuff about Android memory and applications. Trust me, all this is necessary to understand how the whole thing works.
Android OS Memory Management Basics
Android OS, as of V2.2 (and 2.3) have two general types of memory: internal storage (sometimes known as application stroage), and SD card (which may be flash memory that works like SD card, but not physical SD card, such as in the Nexus S)
All apps (in the form of APKs) are loaded into internal storage. Each program can also request additional space as "data" and/or "cache".
All apps (in the form of APKs) are loaded into "app storage" part of the "ROM" (actually flash RAM). Part of the ROM is the boot ROM which loads the system. The other half of the ROM is "app storage". For example, in Motorola Droid, 256MB is RAM, and 512MB is ROM. Out of 512MB ROM, 256MB is Android System itself (actually a bit less), and the rest is "app storage", to max of 256MB.
With Android 2.2 and "Move2SD", a portion of the APK can be moved onto the "SD card", but main portion must remain in internal app storage. The size of the main portion that stays would depend on the app. Some apps cannot be moved or will not function if moved. "Protected" apps cannot be moved. Apps that primarily consist of a service and a widget may not work if moved. add Services or widgets needed for startup should not be moved.
For example, If you have a 256MB system (shows as 262MB due to 1024 vs. 1000 KB size difference) and have 130MB of apps and data/cache loaded, then that leaves about 130MB for the system to actually RUN programs. That sounds like a lot, but in reality that is not enough, since the system itself takes 50-80MB, and services will take up another 30-50MB, leaving almost nothing.
addedIn a 256MB RAM phone such as my Moto Droid, AutoKiller shows...
acore : 4.55MB (system)
dialer: 8.95MB (system)
system: 20.38MB (system)
autokiller:5.68MB
messaging: 3.41MB (system)
Swiftkey: 6.59MB
JuiceDefender 4.14MB
Calendar Storage 4.1 MB (system)
acore: 7.7MB (different pid) (system)
smart taskbar 3.81 MB
seePU 3.44MB
Screebl 4.38MB
SetCPU: 3.83MB
ATK Froyo 3.01MB
gapps: 7.79MB (system)
and 2 more at 4.66MB and 3.56MB
That adds up to... 99.88, or 100 MB.
But that is supposed to leave 156MB, right? Wrong. The system itself takes about 100 MB by itself, in addition to loaded programs, according to this thread about T-Mobile G1 (which has 192 MB of RAM, and has about 96000 KB after booting)
UPDATE: I found an article that explains how to read "MEMINFO". You can get MEMINFO app, or if you have SetCPU the overclocking widget it shows MEMINFO as well. Mine says roughly:
MemTotal: 231740 KB, or 226MB
MemFree: 3376
Buffers 272
Cache: 34960
SwapCache: 0
So the system (before OS kernel) uses about 30MB leaving about 226 MB
Cache itself used another 35 MB. , leaving about 189 MB
Minus 100 MB of auto-loaded apps, and you get... 89 MB.
If you run any programs that need more than that, programs and services will be killed to make room.
(see Redhat's explanation on what meminfo is supposed to mean)
SIDEBAR: native vs. Dalvik
There are two types of Android programs... "Native" programs, and VM programs.
Native programs are written for the specific CPU in the machine. While this gives better performance, this is much harder to achieve, so most people write program for the VM, or "Virtual Machine".
A "virtual machine" is basically a CPU emulator. You feed it a program, and it will run this program, as if it's a real CPU. The good thing about using a VM is it doesn't matter what the actual physical CPU the device uses. You write the program once, and never have to worry about converting it to other CPUs.
Android's VM is called Dalvik, and it is similar to Java's virtual machine. (In fact, Sun/Oracle sued Google for violating Java copyrights on JVM)
Different pieces of a single app
Most apps have either just an activity, or activity along with a service.
"Activity" is basically the user interface that takes your inputs and displays something back. Foreground app would be an activity.
"Service" is a background program that updates something. Common services includes input, widget updates, mail notification, and so on. Other services include Bluetooth, network updates, and so on.
(Actually there are two more types: broadcast receiver, and content provider, but those are not that pertinent to our discussion)
An app can use a widget, and the widget can use a lot of memory, usually several MB at once. You can see the different services and how much memory they are taking under Settings / Applications / Manage Services
How Services Use Memory
As explained above, Android OS have to run programs from within the limited space available, which, on older phones, isn't much. From within that much memory, it needs system work space to load all the services (you probably have a dozen loaded, taking up at least 30 MB) System itself uses about 60-70 MB (acore, phone, gapps, messaging, etc.) That's 100 MB used. That doesn't leave much memory for anything else, if you have 100 MB of apps loaded. (256-100-100=56) 100MB for system itself, about 100MB used for apps and services, and you got almost nothing left.
If you look at the services screen, at the bottom, there's a bar: red, yellow, and green. There is a number in the red section and some in green. Your services adds up to the number in the green section. The yellow portion is some memory that can be freed. The red stuff are system stuff and can't be moved.
What Happens When System Runs Out of Memory
When the system needs to load programs, but don't see enough available, it will start killing programs and services (to the system, they are all considered "process") from memory based on the following priority:
Empty App: the app is in standby, not being used, but is still in memory. These can be killed without any effect.
Content Provider: process that provides content to the foreground, such as "contacts content provider", "calendar content provider", and so on. Various "storage" are also content providers. Those can be restarted when needed.
Hidden Application: apps not visible, but still running in the background. These are not exactly running, so killing them should have no serious consequences.
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. If these are killed there may be some problems, such as the playback is interrupted, background sync stops, widget no longer updates, and so on.
Visible app: the app is running and visible, but due to multi-tasking or such is not currently "on top". Any program with a display in the notification area is considered "visible". Android OS will not kill these programs unless absolutely necessary, but it can happen.
Foreground app: you see this app on screen, currently running, but also includes the system itself and "phone". These are never killed. In any case, system and phone have much higher priority than any app to make sure those are never killed.
Each category above has a certain number associated with it, sometimes known as a "minfree" value (in either "pages" or megabytes, depending on the app). When Android OS free memory drops below the minfree value for that category, apps in that category are killed. The killing starts Empty App group as that has the highest number. if that's not enough, it then starts killing apps in the Content Provider Group, and it keeps going until it has finally freed up enough memory to load the app and all related processes (such as services).
NOTE: Having a constant "notification" in the notification area makes the program "visible app" instead of "hidden app", thus making it less likely to be killed by the system to make room for other apps.
A lot of problems with Android device occur when the system tries to make room by killing "secondary server" processes that are needed. Playback of audio (music or podcast) stopped, download stopped, location services stopped... etc. This especially happens on phones with little RAM. First Android phone, T-Mobile G1 / HTC Magic, has 192MB of RAM. Moto Droid have 256MB of RAM. Second generation of Android phones, like HTC Wildfire, got 384MB of RAM. Recent phones, like Droid X, Galaxy S, and so on got 512MB.
NOTE: Some apps, like web browser, can exit but still save the URL you were browsing. So when the process reloads, it is almost as if it was never unloaded. Unfortunately not all apps can do that.
So what is the solution?
There are two approaches to the problem: make more memory available, or pre-empt the auto-kill by killing apps yourself.
Making More Memory Available
There are four ways to make more memory available short of exchanging the phone for a more powerful one.
1) Free up more app storage / internal storage
Either uninstall the apps altogether, or move2sd as much as possible. Keep in mind move2SD may not work for all apps, and amount that can be freed varies greatly. Uninstall an app is best, as it both frees up the space itself takes, and if it loads a service, that service is loaded either, saving even more space.
While it's true that the app that wasn't run won't take up any space, every widget is served by a service, and a small app can load a HUGE service by calling existing libraries and declare a large buffer for downloads. And just because you don't actually use the app doesn't mean the system will not load it. The only way to make sure the app will NOT be loaded is to uninstall it (or if you have Titanium Backup premium, you can "freeze" the app)
2) VMHeap
VMHeap adjusts the the amount of memory that can be dedicated to the Dalvik Virtual Machine (VM). In general this should not be touched, and does not really make more memory available. It is available only for experimentation purposes.
This usually is NOT tweakable without mod ROM such as Cyanogen Mod. And benefits are unproven so far. Don't change anything yet.
3) CompCache
CompCache, or "compressed cache", is handled by the Linux kernel. It takes a portion of your memory, and use it as a cache space, but compressed. By using on-the-fly compression it is able to make your memory appear to be a bit larger than it actually is. However, the result is slower performance.
This is usually NOT tweakble without mod ROM such as Cyanogen Mod. The kernel also must support this feature, and not all do. This also slows your phone.
4) Swap file or partition
Linux kernel allows the OS to use the SD card as swap space by either creating a swap file or a swap partition. This adds a lot of read/write action to your SD card and may substantially decrease its usable life. However, it is a reliable way to "add" a lot of memory to your system.
Root access is required to swap the kernel, and the kernel must support this feature as well. Not all do. This really slows your phone. Beware.
Pre-emptive Killing of Tasks
The other way to avoid auto-kill is to kill the processes yourself via an app, so the auto-kill is not triggered. This is why apps like Advanced Task Killer and all the other "task killers" are created.
Basically, the task killers automate the task of killing apps, so it will free up memory thus auto-kill is NOT triggered. And because Task Killers have ignore lists, you can add your specific app to be ignored, and hopefully it will still run.
The best known one is ATK (advanced task killer) by ReChild, but there are plenty of others on the market. They usually have tweakable settings, like killing apps every time the screen is turned off (eeks!) or just at timed intervals (every 30 minutes), and so on.
On a phone with 512MB (or more) of memory, there should be no need for task killers, as the phone should not run out of memory. On phones with 256MB or less of memory, ATK may be necessary to keep the phone "free" for other apps.
Recommended Actions
If you have one of the older phones with little memory (256MB or less), load only the bare minimum of apps you need. uninstall the rest. You need to minimize your memory usage as much as possible to leave as much space for the apps. Keep 100-150MB available for the system is best. After system and services loaded, there should be at least 50MB left to load other programs and such.
You can use archivers like Titanium Backup or AppMonster to archive the apps to SDcard, and only reactivate them when you need them. Or you can delete them altogether, only redownload them from the Market when you need them. This will even work for purchased apps.
You can also purchase Titanium Backup which allow you to "freeze" apps, which makes leaves them in memory but NOT loaded. You can also uninstall built-in apps that you don't use, such as Amazon MP3, saving even more space.
If that is not enough. you can try using CompCache and/or Swap. However, those are not exactly recommended, and thus are only methods of last resort if you can't kill enough apps to matter. Try 18% compcache or even 26% compcache. If that doesn't help, try 128MB swap, or even 256MB swap if that still doesn't help.
For phones with 384MB or more RAM, you should not have to be so stingy, but no need to overload either. With extra 128MB -384MB you can load extra 50-100MB of apps and a few more services. The idea is still to keep 100-200MB available (depending on the phone). You do not need task killers and all that.
I was looking on the explanation for OOM priorities, and there it is. Thanks. I'm wondering why there are no replies to this thread. Oh wait, it's a question.
thanks for the most awaiting tutorial abt RAM.n yes i was wonderng y this thread hasnt got applause...

[Q] RAM observations

I have my Nexus S for over two weeks now, and I'm incredibly happy with it. Theming is a lot of fun, and you can do very cool stuff even without root and custom roms!
However, there is one (strange) thing I've noticed. It's about the RAM.
For your information: I use Go Launcher which has a tab in the App Drawer with running applications, and a button to close all (you can exclude certain apps). When I boot up my phone, I have 170-180 MB free RAM. The following programs (and widgets) are running in the background (I have excluded them from the close all list): Go SMS Pro (widget, notifications), WhatsApp (notifications), Lookout, Extended Controls (widget), Wiget Locker (I made it look like the MIUI lockscreen) and Clockr (widget).
There are two more apps that are on constantly, and those are the Miren Browser and PlayerPro. I don't know why Miren Browser keeps turning itself on. When I check how much MB it uses, it says 0,00 dB... As for PlayerPro, I use a widget called Phantom Music Control, a widget that hides itself when no music is being played. I also use it on my lockscreen. This widget controls PlayerPro, so that is probably why PlayerPro has to be running all the time (so that it can start up quickly when needed).
There are some Google apps that turn themselves on, like Gmail and Places, and they actually use RAM according to Go Launcher. I don't want them to be running, and synchronization is turned off with Gmail. When I want to know if I have mail, I open Gmail. It doesn't have to be running all the time. I've never used Places, and I never will use it, so I don't know why that has to be running all the time.
Every once in a while I hit Close All (with Go Launcher). However, I've noticed that over time my free memory keeps lowering. When I boot up my phone it is around 175 MB, but at the end of the day the free memory is 100 MB, 70 MB or even 50 MB, and yes, even after I've hit the 'Close All' button.
I know I don't use my phone very efficient, with programs like Go SMS, Widget Locker and that Music Control widget, and I will flash a custom rom later. My RAM memory will probably increase then (I've read something about Supercurio's kernel including a boost RAM management). It just bothers me that I don't have control over what programs are running (Gmail and Places), and that my free memory decreases over time. I haven't noticed any slow downs, I'm just worried. Or shouldn't I?
I don't know about the rest, but you shouldn't be concerned about free memory.
Android is designed in a way that all programs keep running (sleeping actually) in the background even when you don't use them at the moment. They are automatically killed when the system needs memory for something else. Any program that is sent to the background (e.g. by pressing back or home) can be killed by the system at any time and is (should be) ready for it.
Basically, the less free memory you have, the better. That means that many of the apps you use are running and you can return to them without delay.
There are some articles floating around the web about the architecture of android and process/application life cycle. They explain that better then me, and in more detail.
cgi said:
I don't know about the rest, but you shouldn't be concerned about free memory.
Android is designed in a way that all programs keep running (sleeping actually) in the background even when you don't use them at the moment. They are automatically killed when the system needs memory for something else. Any program that is sent to the background (e.g. by pressing back or home) can be killed by the system at any time and is (should be) ready for it.
Basically, the less free memory you have, the better. That means that many of the apps you use are running and you can return to them without delay.
There are some articles floating around the web about the architecture of android and process/application life cycle. They explain that better then me, and in more detail.
Click to expand...
Click to collapse
First of all, thanks!
So I don't have to be afraid of any slow down? And what about Gmail and Places turning themselves on every time, even if I don't use them?
And why does the free memory decrease over time, but increases again when I turn off and boot up my phone?
Androyed said:
So I don't have to be afraid of any slow down? And what about Gmail and Places turning themselves on every time, even if I don't use them?
Click to expand...
Click to collapse
More like the opposite: your RAM is being put to good use.
When your PC get's low on RAM it will start swapping and trashing around. Your smartphone has no swap and is optimized for it. If it get's low on RAM, it will just kill some stuff in the background. All this happens without you noticing anything (if the app is programmed correctly).
I don't know about Gmail and Places. Most likely they are running because they registered broadcast receivers or something.
Androyed said:
And why does the free memory decrease over time, but increases again when I turn off and boot up my phone?
Click to expand...
Click to collapse
Every app is running in its own dalvik virtual machine process. Since creating a new VM process is expensive (in terms of processing time), the VM processes are reused to some degree. One app is unloaded, the new one is loaded.
There is more stuff going on behind the scenes, of course. There are likely some spare VMs sleeping in the background waiting for an app to use them.
However, the heap (dynamically allocated memory of a process) of a VM can only grow and never shrink (don't ask me why). So after a few apps or so a VM process is restarted, too.
To come back to your question: When your device boots up, only the processes needed for boot are running. That will be the launcher, some widgets and so on. So basically, this is the moment with the most free RAM. However, this is also when your device is slowest, because every new app you launch has first to be loaded into memory and executed.
While you use your device, many of the apps you used will be kept around in the background, so when you start them again, they will reappear instantly, because the whole "create vm process --> load app from storage --> execute and initialize app" chain has already happened.
"Free memory is wasted memory."
When you open an app, the system loads it into ram. When you close it, the system should not bother to remove it from ram because there is a good chance you will use that app again and having it pre-loaded makes it open significantly faster.
Just because ram is "used" doesn't mean it can't be re-allocated for something more important.
That being said, it is entirely possible that some of your apps have memory leaks. Does it get worse after two days, or three days?
d-h said:
"Free memory is wasted memory."
When you open an app, the system loads it into ram. When you close it, the system should not bother to remove it from ram because there is a good chance you will use that app again and having it pre-loaded makes it open significantly faster.
Just because ram is "used" doesn't mean it can't be re-allocated for something more important.
That being said, it is entirely possible that some of your apps have memory leaks. Does it get worse after two days, or three days?
Click to expand...
Click to collapse
I turn my phone off every evening, so I don't know. It's not a problem by any means, I'm just curious.
I've left my RAM alone today, and I didn't noticed any slow down. It was on 110 MB free RAM when I left it alone, and when it was at 35 MB RAM, I decided to hit the close all button (there was no slow down btw). Guess what? My RAM went back up to 140 MB! Not as much as when I boot my phone up, but it's still strange: when I hit close all when the free RAM is very low, I get more free RAM then when I hit close all when my free RAM is around 100 MB (I only get 5 or 10 MB free RAM extra then).
Thanks by the way, good first post!

Whats Best way to free up the ram???

Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Rooting and freezing apps doesn't give you more RAM, since there is only 512MB of RAM and the OS takes part of that to run.
You can free up internal app storage space, by deleting bloatware, or cut/paste the bloatware into a folder on the SDcard (I call mine VZWBloat) and that will save you space.
You can run a task killer to kill off apps that you don't need but you have to be careful, Android does need certain apps to be available in the background and it will just reopen automatically and that will put them into a cycle and drain the battery.
rcb929 said:
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Click to expand...
Click to collapse
Please do not post Questions or problems in Android Development
Moving to General
RaptorMD said:
Rooting and freezing apps doesn't give you more RAM, since there is only 512MB of RAM and the OS takes part of that to run.
You can free up internal app storage space, by deleting bloatware, or cut/paste the bloatware into a folder on the SDcard (I call mine VZWBloat) and that will save you space.
You can run a task killer to kill off apps that you don't need but you have to be careful, Android does need certain apps to be available in the background and it will just reopen automatically and that will put them into a cycle and drain the battery.
Click to expand...
Click to collapse
Hey im using root explorer when im in system/app/ how do i single out the bloatware apps?
rcb929 said:
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Click to expand...
Click to collapse
Freeing up that much RAM is probably detrimental to the overall efficacy of the memory management system, I've never seen mine at 185MB, and if I did I'd worry something was wrong.
If you really want to free up more RAM, for no benefit whatsoever, use something like Advanced Task Killer and set it to allow killing of the lowest level processes it can, then kill everything. Bam, tons of free'd up RAM. Again, this has pretty much no benefit whatsoever and for a short time will probably make your phone more sluggish and slow.
In Android (Linux) free memory is considered wasted memory.
That said, I remember on my galaxy S that the phone ran snappier when I tweaked the memory management of the phone.
Task killers are generally considered a bad idea on android, so I would avoid using one of them to free up memory. However, there is a poorly named app called auto killer that is actually just an interface to tweaking androids built and memory management. I recommend giving it a try, here's a link: http://market.android.com/details?id=com.rs.autokiller
Note that it is not a task killer per se, it is just a tweak for android phone memory management schemes.
I haven't used it on my droid charge yet, but play with the settings maybe starting with aggressive. Good luck and let us know how it works for you.
Sent from Thunderbolt
I don't have my phone with me right now, but you need to make the folder read/write and then hit menu and multi-select or select multiple. This thread http://forum.xda-developers.com/showthread.php?t=1082588 shows what is ok to freeze, but I am not familiar enough with those to say you can remove all of them. Typically I would look for the Verizon specific apps, games like lets gold, guitar hero etc. If you remove anything related to touch wiz (widgets) you need to remove both of the associated files. I am pulling this from memory on my previous TB.
These are the ones I recognize, but the others in that long list I would like to see better clarification of what they are and how they are tied into the TouchWiz UI so we don't get errors. Please exercise caution when doing this.
• Bitbop 1.0
• Blockbuster 0.6
• City ID 1.1.4
• Lets Golf 2 3.2.2
• Rhapsody 1.0
• Rock Band 4.4.3
• Slacker 2.1.170
• TuneWiki 2.2
• VCAST Media Manager 4.2.96.3
• VVMService 1.0.30
• VZ Navigator 7.1.2.87
• WeatherBug Clock 11.04.07.01
rcb929 said:
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Click to expand...
Click to collapse
BY FAR.... BAR NONE.... The best way to free up memory and keep it free without messing with task killers is to use a program called startup auditor. This app prevents apps from starting up automatically on startup and throughtout the day without interfering with normal app processes. You can shut down or enable any app you want.
Even cooler, if you select the option menu and hit disable all, it only disables programs that won't interfere with the phone operation so it knows which apk's are critical for phone integrity. PRETTY COOL!!!
burningembers said:
Freeing up that much RAM is probably detrimental to the overall efficacy of the memory management system, I've never seen mine at 185MB, and if I did I'd worry something was wrong.
If you really want to free up more RAM, for no benefit whatsoever, use something like Advanced Task Killer and set it to allow killing of the lowest level processes it can, then kill everything. Bam, tons of free'd up RAM. Again, this has pretty much no benefit whatsoever and for a short time will probably make your phone more sluggish and slow.
Click to expand...
Click to collapse
NEVER USE ADVANCE TASK KILLER... See other post
http://forum.xda-developers.com/showthread.php?t=1106265
RaptorMD said:
Rooting and freezing apps doesn't give you more RAM, since there is only 512MB of RAM and the OS takes part of that to run.
You can free up internal app storage space, by deleting bloatware, or cut/paste the bloatware into a folder on the SDcard (I call mine VZWBloat) and that will save you space.
You can run a task killer to kill off apps that you don't need but you have to be careful, Android does need certain apps to be available in the background and it will just reopen automatically and that will put them into a cycle and drain the battery.
Click to expand...
Click to collapse
DON"T USE A TASK KILLER ON ANY SAMSUNG DEVICE. See other post
http://forum.xda-developers.com/showthread.php?t=1106265
I wasn't really condoning the use of task killers. I disagree with them 99% of the time (there are some edge cases). I just gave the OP an option if he really, really wanted to for no reason whatsoever.
@OP: I would recommend leaving the pasture gate open.
rcb929 said:
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Click to expand...
Click to collapse
There is an app called Greenify. Its available on Play store.
Just check it out.
It also helps to maintain the juice of the battery.. !!
To Free Ram
A more easy way to delete a minimum of 1gb of space which by doing so also frees up ram is to delete the dump state log cat. See every time your device has an error or force close issue, date is collected / written to the log file and this can take up ane enormous amount of space which when space is low also means your device user more ram. To do this go to your dial pad and type in *#9900#
This will automatically brings up options and then just choose to delete the dump state/log cat. Let it clear for a few minutes and that's it's. Try seeing how much space you have before and after and you'll realise this is a blessing.

[Q] strange ram available

Hello everyone
i have noticed something strange about the RAM available, if I go into settings-applications-services running: ram, 211 MB used 80MB free.
If you instead use Android system info I see: 37 MB free RAM
Why this? I have 2.3.4 stock
sorry my bad engish
try terminating cached programs. also, remove unnecessary apps. dont use task killers/managers etc. they are unnecessary. linux is smarter than us. dont use security services unless you frequently visit suspect sites and dl apps w/out research. see which programs are consuming ram and search for solutions. last resort, hard reset. if it persists or low ram issues arise when stock, time for a new one. good luck.
The nexus S has 345MB for the OS and apps, rest is used by the hardware (mostly by the GPU), you will never have access to it.
Your situation is perfectly fine, the biggest memory hog is the browser. I recommend auto memory manager (free on market) and set the empty application line to 80mb.
The services are killed automaticly by android, no need for task managers, but the limit is set to 80mb instead of 24mb. You will still run into memory leaks eventually, but not really at 30mb left.
Thanks to all
I do not use task killer, using linux for 4 years , i try Auto Memory Manager. see if the situation improves.

Available RAM Dilemma on the Droid Charge

I'm currently running EP1F Debloated with Gummy Charged
The phone typically says that, out of 312MB of accessible RAM, there is 60MB or less of free RAM.
i'm running GO Launcher EX, and on it's RAM meter, it's almost always in the Red (signifying that it's almost Maxed out in available RAM)
is this normal?
of course, any time i quit all open applications, the usuals always reload, but then sometimes odd programs will run in the background (i.e., netflix, google+, music, amazon appstore, picasa, ustream, etc). These are programs that I haven't even loaded or ran. they just like to load themselves up and run in the background. so because of this, my available Free RAM tends to sit at 39-55MB. that seems VERY low to me. and may be the reason why my phone tneds to bog down a bit and lag every now and then, when i'm going from app to app.
I know EP1F doesn't have voodoo lagfix yet (like it did on EE4), but this unusually high consumption of RAM seems odd to me.
does anyone have any input on this?
appreciate it
If you havent ran, and don't run those programs just get rid of them
no no no... I definitely run them. but it's probably a few times a day, sporadically.
but i don't need them to be running in the background, hogging RAM. whereas, i'm totally fine with an app like Gmail to always be running, since i check that all the time.
I use Autokiller Memory Optimizer, set to "optimal" preset. It's not a task killer, it just changes Androids settings to close programs at different trigger points. Keep some free ram and keeps the system from bogging down.
I also use Autostarts, which disables programs from starting up at startup or for other notifications that are set. Some programs still start themselves but it helps.
Why do you want free RAM? Unused RAM is doing nothing for you, Used is holding a program ready to launch so it's faster and needs less CPU to launch. Ideal RAM usage is 100% because the system will automatically make room for a new program to run.
Have you ever gotten a message that an app can't launch due to low RAM? Using RAM doesn't mean using CPU or battery. It just means ready to run faster.
Sent from my (currently) stock Verizon Fascinate ed04 using XDA App.

Categories

Resources