[Q] RAM observations - Nexus S Q&A, Help & Troubleshooting

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!

Related

Memory leaks?

My Cappy starts with about 165mb of free RAM, but it quickly goes away as I use apps. I have Task Killer installed and set to kill apps every 30 minutes, but once I get down to about 90mb of RAM it is impossible to get anywhere near what I boot with free. I'm used to memory leakage on my WinMo phones, but this is way worse. I had CleanRAM on my Tilt 2 (from XDA) and it worked pretty good and allows scheduling. Is there a similar app for Android?
I'd get rid of Task Killer, you don't need it.
its not leaking memory...it handles memory differently than windows of yore....stop fretting about how much memory you have available and just reboot your phone once every few days....thats not needed, but if it makes you feel better to look at useless numbers...
Yeah you need to stop looking at this as either a windows pc or an old device (think g1). Get rid of the task killer and never look at how much free ram you have again. Its not important at all. I've had this phone for months and I literally have no idea how much ram it uses on average because I have never checked or cared. My phone has been running smooth since day one. Yours will too.
Sent from my SAMSUNG-SGH-I897 using XDA App
Available RAM is a useless number? Having unused apps continue to run in the background is nothing to worry about?
Does anyone have anything usefull to respond with?
Miami_Son said:
Available RAM is a useless number? Having unused apps continue to run in the background is nothing to worry about?
Does anyone have anything usefull to respond with?
Click to expand...
Click to collapse
If you look at Window 7, there is a concept called pre-fetch. This allows the OS to load the programs into memory based on past usage, and frequency of usage. This lets us open the program much faster, than fetch when requested. This info is loaded to memory, and kept there, until some other program comes in that needs more memory.
And just 'cos a program is present in RAM doesn't mean it would use CPU.
And, based on my observation of android, I see that I have close to 180 MB free when the phone boots up. But this quickly reduces to around 120-150 in less than an hour based on what I use. After like a day this I see that free RAM is about 80-120 MB. And even after 3-4 days of no reboots, the free memory is still present at the same 80-120 levels. I am not sure what kind of memory management android uses, but its very effective, and never caused any noticeable lag in the system.
And, I do not use any task killers, not free up RAM in task manager.
Your concerns are flawed in the fact that the Linux kernel handles memory different than what you are used to. Simply speaking, Linux keeps memory used by applications on need to basis. It keeps it loaded until something else needs to use it. It will take from something else at the required time. A system actually performs faster when there is less memory available because that means that applications are able to be recalled quicker. It's not like it can only load from what is left available.
You will also notice that many applications take up memory but are using 0 CPU. This speaks to the fact that it simply loaded into memory and not taking up resources required for other operations.
Sent from my SAMSUNG-SGH-I897 using XDA App
Lot to learn about this Android, I see. So, why are there so many task killers on Market and other RAM-related programs if it is not important? Should I really not be concerned when I see a program I hardly use being shown as running on startup?
Miami_Son said:
Lot to learn about this Android, I see. So, why are there so many task killers on Market and other RAM-related programs if it is not important? Should I really not be concerned when I see a program I hardly use being shown as running on startup?
Click to expand...
Click to collapse
When I got my android phone, the first thing I did was put up things like task killer, start up auditor, etc. But as weeks passed, I realized these were more of deteriorating performance, than improve it. So got rid of them. Android can handle itself.
Autokiller optimises memory by changing values in android rather than kills apps. I reccomemd it, definately makes the phone faster. Set it to agressive.
Sent from my GT-I9000 using XDA App
Miami_Son said:
Lot to learn about this Android, I see. So, why are there so many task killers on Market and other RAM-related programs if it is not important? Should I really not be concerned when I see a program I hardly use being shown as running on startup?
Click to expand...
Click to collapse
It started with the combination of old versions of android (think cupcake and doughnut) and phones like the G1. Older versions didn't handle ram as well as they do in eclair and up. If you combine this with the fact that those older phones had less ram, and likely didn't use any gpu acceleration (unsure of this though), then task killers and other programs were considered necessary to get a fluid feeling experience.
They are still in the market now for 2 reasons.
1. Because some people still have those old phones and still run old versions of android. (less likely)
2. Habit. If people are used to using them and tell others they are necessary because they've always worked, why would a developer pull his money making app from the market? (much more likely)
So when Pandora or Grooveshark freeze, which happens all the time, and leaves my phone utterly useless until they're done doing whatever it is they're doing, how is using a task killer to...kill the process...not useful? It's much faster than rebooting the phone. I also think it's much faster than going into each application's individual settings to use the 'force stop' command. Is there a different way to kill a stuck app other than these methods?
Miami_Son said:
My Cappy starts with about 165mb of free RAM, but it quickly goes away as I use apps. I have Task Killer installed and set to kill apps every 30 minutes, but once I get down to about 90mb of RAM it is impossible to get anywhere near what I boot with free. I'm used to memory leakage on my WinMo phones, but this is way worse. I had CleanRAM on my Tilt 2 (from XDA) and it worked pretty good and allows scheduling. Is there a similar app for Android?
Click to expand...
Click to collapse
Along with what everyone else said, remember that a memory leak is a LEAK, something that is continuously draining, not a one-time thing. So, if memory goes to 80MB free and holds, that's not a leak, that's simply memory that is being used. If free memory drops to 75, then 60, then 55, 50, 45, and so on, then you have a true leak to worry about.
Well, what we Windows Mobile users often also refer to as leaks is the bad habit of some apps to not release their memory when closed. For instance, a program that carves out 25mb of RAM when started and returns less then half of that when closed.
jaju123 said:
Autokiller optimises memory by changing values in android rather than kills apps. I reccomemd it, definately makes the phone faster. Set it to agressive.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Anyone else know much about "Autokiller"?
i used to use a task killer with my G1, and continued to do so with my captivate but i saw a few things like this: http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ and decided to get rid of my task killers and my phone seemed actually a little faster and seemed my battery life increased.
matt310 said:
So when Pandora or Grooveshark freeze, which happens all the time, and leaves my phone utterly useless until they're done doing whatever it is they're doing, how is using a task killer to...kill the process...not useful? It's much faster than rebooting the phone. I also think it's much faster than going into each application's individual settings to use the 'force stop' command. Is there a different way to kill a stuck app other than these methods?
Click to expand...
Click to collapse
It is useful in those situations but realistically when people give that argument they are just looking for a reason to keep it. Android has the ability to kill tasks built in. If you're on 2.1 then yeah it's buried deeper in the menu but not a big deal. I can't imagine an app freezing enough to warrant having a task killer for. If you're on 2.2 it's much more easily accessible.
When we talk about task killers we're talking about people using them to kill open tasks that aren't causing issues simply to see more free ram available.

Question about RAM

I am running Froyo from Samsung web site.
Anyways, I know froyo was supposed to free up 512 ram. I know about 100 goes to gpu. However my phone is left with 339 ram to use (as seen in task manager). However it is always using at least 220mb, even when I close everything and restart the phone. When I open up advanced task killer it says 116m free. Why so little? How can I get more easily? without having to use ROMs or kernels?
Or is this how it is for everyone? I feel kind of cheated!
First of all, you should never need to use anything like Advanced Task Killer now that you have froyo. There are legitimate uses, but its really something you can go without. See http://www.reddit.com/r/Android/comments/cwovf/in_light_of_all_the_discussions_right_now_about/ for a good writeup.
Your phone, just like a computer, uses an optimal amount of RAM at all times. That does not mean minimal. Android phones dynamically allocate RAM for applications and the OS. Why have 200MB of RAM free when you can instead have 100MB free and have the phone be more responsive? 2.2+ manages memory more effectively, and if you are not using an application, will close it. Its fairly difficult with any normal usage scenario to cause your phone to run out of memory.
In short, you don't really need to worry about it because its that way on all Android devices (and generally any modern computing device), and that if is not affecting the usability then its not an issue
Completely agree With first comment. Everyone is concerned about keeping as much ram free as they can but it does not speed their phone up at all. Ram its just like quadrant scores a useless numbers if the phone is response and speedy in actual use
Sent from my SAMSUNG-SGH-I897 using XDA App
U could try reading this: Android Memory Management
your ram usage does seem a little high, you may have an app that is using a lot of it. the 339mb available is normal. some kernels will show quite a bit lower than that but the never seeing more than 116 free is odd. the rom im curently on fluctuates from about 140mb used to 240mb used. i only know that because i clear ram before running benchmarks, have you tried clearing ram in the built in taskmanager? or are you only going off the task killer? because the task killer doesnt necessarily clear ram.
all i know is task killers are pretty useless unless you have an app that freezes and for that the taskmanager built in to many of the samsung roms should be enough for that though it does not show every process that is in a saved state or system processes. task killer programs do more harm than good but i cant seem to get people off them. danm verizon store sets people up with them and poeple use them religiously. i figured out in the first few days of using android on my aria that getting better speed and battery life by killing tasts was a futile effort. there are few market apps that use resorces when running in the background and if you exit the app with the back button it doesnt save the state or run in the background. not that saved state is a problem. i only found that the phone uses more battery restarting processes that are designed to be running and has more lag than when you just use the phone and ignore the running processes.
Personally the only time you should be ever worried about ram is when watching a flash video or viewing a webpage with a lot of stuff. Other than that, as said, if the phone runs smooth, who cares about ram?

(Q) Droid Charge ram 328 or 512?

Sorry if this question has been answered somewhere, but I searched and couldn't find a reliable answer. When I go to task manager, it always shows memory usage out of 328mb available. Everything I read prior to purchase indicated there was 512mb ram. If I'm going to be locked in contract for any extended period of time I definitely need more than 328. 512 is already low by today's standard, but 328mb is ridiculously bad. Anyone that knows the answer and a way to verify would be greatly appreciated as all the searches I do come up with both answers.
Thanks for the help guys.
Sent from my SCH-I510 using Tapatalk
In addition to the above mentioned issue... I frequently have 250+ out of the available 328 used even when task manager indicates no apps running. Is there that much going on in the background? In case this helps I'm running the ED2 debloated rom so I can't imagine how bad it would be if I still had all the bloat in there.
Thanks again for the input
Sent from my SCH-I510 using Tapatalk
The phone has 512MB total, with some of that allocated to the system that can't be used by apps. This memory goes to thinks like the GPU to give you that stellar video performance. Sucks that it can't be changed really, but that is how it's setup. I believe that we can get a few MB back from the system, but you won't get all of it back.
imnuts said:
The phone has 512MB total, with some of that allocated to the system that can't be used by apps. This memory goes to thinks like the GPU to give you that stellar video performance. Sucks that it can't be changed really, but that is how it's setup. I believe that we can get a few MB back from the system, but you won't get all of it back.
Click to expand...
Click to collapse
Thanks a lot for the response. Makes me a lot more comfortable with holding on to this guy. There must be some serious bacground processes going. because I've yet to see anything lower than 180mb used (about 150 available) and that's with autokiller at extreme preset, which I normally wouldn't set so high...I just wanted to see if any additional mb's would free up.
Sent from my SCH-I510 using Tapatalk
Ok, android 101:
Android uses smart caching and background process management to keep your apps available and running smoothly. As such the more RAM you have free the more you are WASTING. This system is designed to run up to 99% RAM use before turning off any running apps/background processes.
Ever since android 2.2 it has been HIGHLY efficient at doing so. Using autokillers to keep RAM free is pointless, as most apps don't even use ANY CPU when in background, unless they perform background checks for things like is it your turn on words with friends, etc. Unless you have an app that uses too much background data like this (in which case I'd just get rid of the app...) then using killers is pointless, let the OS run the way it is designed to do. Ever since I listened to a ROM dev and stopped using task killers my battery life on my original droid has nearly tripled, and I'm overclocking it from 566 to 1200mhz!
Android is not windows 95, you don't need to hold its hand and make sure things are closed, doing so actually defeats the advanced features of the OS, decreases battery life in all but a very few cases, and increases your app startup times, keeps you from getting background updates properly, etc.
warriorprophet said:
Ok, android 101:
Android uses smart caching and background process management to keep your apps available and running smoothly. As such the more RAM you have free the more you are WASTING. This system is designed to run up to 99% RAM use before turning off any running apps/background processes.
Ever since android 2.2 it has been HIGHLY efficient at doing so. Using autokillers to keep RAM free is pointless, as most apps don't even use ANY CPU when in background, unless they perform background checks for things like is it your turn on words with friends, etc. Unless you have an app that uses too much background data like this (in which case I'd just get rid of the app...) then using killers is pointless, let the OS run the way it is designed to do. Ever since I listened to a ROM dev and stopped using task killers my battery life on my original droid has nearly tripled, and I'm overclocking it from 566 to 1200mhz!
Android is not windows 95, you don't need to hold its hand and make sure things are closed, doing so actually defeats the advanced features of the OS, decreases battery life in all but a very few cases, and increases your app startup times, keeps you from getting background updates properly, etc.
Click to expand...
Click to collapse
I was always of the impression that an app such as autokiller differed from a standard task killer in that it modified the values at which android natively kills off processes vs me going in and manually closing an app (which i never do). I too have read articles that task killers are pointless and do more harm than good, but I always thought autokiller was a different sort of "tweak" if you will. I've even seen several devs promote that they've modified androids native memory management to be more aggressive, etc...which is what I thought autokiller accomplished. Autokiller simply seemed necessary to me with the Charge because I was experiencing lag and lockups even with a debloated rom and voodoo kernel. Clearly there could be several culprits to this this and I was simply testing out different fixes and seeing what the results were. Thanks for the heads up though...learn something new every day.

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.

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