Samsung Galaxy S mysterious ram usage cm10.1 - Galaxy S I9000 Q&A, Help & Troubleshooting

Hey there, this problem might have been discussed before but I wasn't able to find it, so the problem is with ram usasage, I once went to the apps in settings and on the running apps I always see 250mb+ ram used by something, then I killed all the apps, but that just made a dliference of 50mb ram, It's real anoying because when I want to switch between apps it's slow and when I turn a browser back on after using aother app the page realoads which I guess wpuldn't happen with 300 mb ram, does anyone know the reason for this, I am currently running cm10.1.
Thanks!

ltkipras said:
Hey there, this problem might have been discussed before but I wasn't able to find it, so the problem is with ram usasage, I once went to the apps in settings and on the running apps I always see 250mb+ ram used by something, then I killed all the apps, but that just made a dliference of 50mb ram, It's real anoying because when I want to switch between apps it's slow and when I turn a browser back on after using aother app the page realoads which I guess wpuldn't happen with 300 mb ram, does anyone know the reason for this, I am currently running cm10.1.
Thanks!
Click to expand...
Click to collapse
What ROM and Kernel are you using?

Mango Polo said:
What ROM and Kernel are you using?
Click to expand...
Click to collapse
ROM; cm10.1 nigtly 20130330 galaxysmtd Kernel: 3.0.70-g7b668b [email protected] #1

Free RAM is useless. It just sits there sucking up power and being available in case you need it. It's pretty much a waste to have 300 MB of RAM and then only use 100 MB. Instead you should try to keep your RAM full at all times with the things you are likely to need in the near future. For example, if your phone is currently only using 20% of your RAM but already caches the browser in case you'll use it soon it will be faster to load the browser. If you decide to use the music player on the other hand the cached browser can be overwritten with the music player without requiring any additional time, so no harm is done.
Modern systems don't have "free" and "in use" RAM, they have "free" (wasted space), "in use" and "cached". You shouldn't look at the amount of free RAM but rather the amount of actually used RAM is a better indicator.
The reason you only gain 50 MB when you kill all apps is because only 50 MB will be actually in use by apps and all remaining unused space is used for caching things. If your phone is slow, this is not the cause of it. You may just have a slow phone or the ROM might be slow for some (other) reason.

Marshian said:
Free RAM is useless. It just sits there sucking up power and being available in case you need it. It's pretty much a waste to have 300 MB of RAM and then only use 100 MB. Instead you should try to keep your RAM full at all times with the things you are likely to need in the near future. For example, if your phone is currently only using 20% of your RAM but already caches the browser in case you'll use it soon it will be faster to load the browser. If you decide to use the music player on the other hand the cached browser can be overwritten with the music player without requiring any additional time, so no harm is done.
Modern systems don't have "free" and "in use" RAM, they have "free" (wasted space), "in use" and "cached". You shouldn't look at the amount of free RAM but rather the amount of actually used RAM is a better indicator.
The reason you only gain 50 MB when you kill all apps is because only 50 MB will be actually in use by apps and all remaining unused space is used for caching things. If your phone is slow, this is not the cause of it. You may just have a slow phone or the ROM might be slow for some (other) reason.
Click to expand...
Click to collapse
yeah only 50mb is used to keep the apps running, but it probably takes up a whole lot more when using the apps, and this is a problem for me that it is slow to change between apps, and when I do change between the for example if I wanna text some one back while using a browser, once i turn the browser back on it restarts the page, and that didn't happen in my zte blade, unless I had some more apps running.
I wanna know what is using those 250+mb of ram!

ltkipras said:
yeah only 50mb is used to keep the apps running, but it probably takes up a whole lot more when using the apps, and this is a problem for me that it is slow to change between apps, and when I do change between the for example if I wanna text some one back while using a browser, once i turn the browser back on it restarts the page, and that didn't happen in my zte blade, unless I had some more apps running.
I wanna know what is using those 250+mb of ram!
Click to expand...
Click to collapse
see exchange service,any svn services n keep track of system usage. normally 100mb+ will be taken for ui, framework...etc.
but. eventhough u keep track of it,then slaughter it, it will come back to life n running, so i wouldnt recommend slaughtering system usage.
switching between app normally slow for full or stock rom. try find some debloated rom. it will be suitable for u if u wanna more free ram rather than liquidity.
Sent from my GT-I9000 using xda app-developers app

I also observed some sluggishness after some time of usage. Sometimes the phone got totally unresponsive, not catching any push events (from buttons or screen), so that I couldn't even wake it after the screen timeout. I had to wait even few minutes before it was alive again.
Google Chrome was the most ram-eating app as far as I know.
Sometimes the best method is just restart your phone from time to time or even make a wipe - this is normal for all low-end android phones as they get sluggish after some time.
Long story short: I ended up buying a new phone with 2gb of RAM

pawci0 said:
I also observed some sluggishness after some time of usage. Sometimes the phone got totally unresponsive, not catching any push events (from buttons or screen), so that I couldn't even wake it after the screen timeout. I had to wait even few minutes before it was alive again.
Google Chrome was the most ram-eating app as far as I know.
Sometimes the best method is just restart your phone from time to time or even make a wipe - this is normal for all low-end android phones as they get sluggish after some time.
Long story short: I ended up buying a new phone with 2gb of RAM
Click to expand...
Click to collapse
well...good luck on ur new fone
wish i had extra money to buy one......
but, bigger ram doesnt solve anything as far as i know.stock gapps n app from firmware will be da 'pacman' here. unless ur obtain 'god mode' for ur fone.
Sent from my GT-I9000 using xda app-developers app

I have the same issue
I'm using CM10.1 RC5, kernel 3.0.76-gc0a8d45 [email protected] #1
I have same symptoms pawci0 and ltkipras mentioned.
But I don't want to buy a new phone...
The lack of memory is noticeable when I run Waze or maps . It just opens for a couple of minutes and closes by itself or rather hangs the entire device.
What should I do? Go for the CM10.1 stable, try a different ROM (i.e. Slim). Change kernels?

nope, waze doesnt use that much ram, try to fix permission first n clear cache in recovery
n try to use other kernel, mine ok with multitask, rather heavy with online games n hearing mp3 n receiving whatsapp, line n we chat at da same time
n try greenify app to control app thats always running.
Sent from my GT-I9000 using xda premium

Just try a other rom or kernel you would be amazed how lets say a change of kernel can speed things up. The point is everyone uses their phone differently different apps and things so you need to find the rom that suits you mostly.
Sent from my GT-I9000 using xda app-developers app

Related

[Q] Full RAM after using a some apps... with a little analysis

After fixing some lags with I/O system by using filesystem LagFix I still have a Lag problem in my system and I think it's not related to Samsung.
I think this could be an Android problem.
After a fresh reboot I get 124MB of free RAM.
BUT... every day I need to reboot the phone because after 3 hours it became laggy.
Now I analysed this and read a bit about the memory management on several forums and was able to reproduce the lag 2minutes after reboot.
I just need to use much applications one after another to raise the RAM usage for every application.
When the free RAM reaches 40MB I think the system clears some pieces for using it for the app I now want to use and there is the LAG.
Is there any fix for Android not caching every activity of an application in the RAM?
Now for me Android feels like: Usage -> Full RAM -> Lag
Sorry for the new thread but after 2 hours of research I didn't find anything useful over search function.
Yea, every program should have as much ram available as their size. 2gig for program storage on sgs, so there should be the same amount of ram ;D Anyway, theres still less memory for programs on the sgs than for example in the N1. I'd say there is about 384MB of ram total on the sgs and not the 512 claimed.
Sent from my GT-I9000 using XDA App
Not just the RAM for the apps... there's much more...all mails from internet, all google talk conversations, the wather I checked out from internet with any widget, feels like every interaction is cached into the RAM until it reaches the 40mb mark and after that every interaction on my system is laggy... for example: opening the notification bar needs 2-3 seconds.
I already talked to N1 users with the same problem
DasLeo said:
I already talked to N1 users with the same problem
Click to expand...
Click to collapse
Heading out the door in a minute so can't comment on the rest, but I strongly disagree with that part of your statement.
As an N1 owner I've NEVER seen lag like I suffer on the SGS. Never seen the absolute FREEZE in the GUI like the SGS gets.
I'm running FroYo on the N1 now, so can't compare side-by-side to the SGS things like memory usage, but I don't think that's the issue here if you're going to use the N1 as a comparison, despite other users complaining of lag.
You might try Autokiller or the free memory manager app from the Market and see if that improves thing, they'll keep more or less memory free depending on settings. You could test how soon lag comes with default, minimal, and aggressive settings.
I never testet Froyo because everyone said, it's unstable but for me it seems like froyo has other RAM management than Eclair when you said you can't reproduce this problem.
I'm already using a task killer... I have my main apps ignored or excluded and most time there are 2 or 3 apps which will be killed after lock or time or what else.
What's the problem here... if I would use a PC with 512MB RAM and use only 10 small applications, it won't cache everything in the ram until it's full.
Hi, didn't read all the posts, but u should look into the RFS file system, which is samsung proprietery file system. It has a very bad implementation on android (i could be wrong). As for ram, the phone has 512 mb, but 128 are reserved for Gsm/data connection. Just think if you had an incoming call and all your ram was in use, u had to wait for the system to clear up some memory before being able to receive the call physiclly. That would be a long wait.
I could be wrong and sorry for the bad english.
Sent from my GT-I9000 using XDA App
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
rkantos said:
. I'd say there is about 384MB of ram total on the sgs and not the 512 claimed.
Click to expand...
Click to collapse
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
tra33372 said:
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
Click to expand...
Click to collapse
DAMN!!! Nice app... it does exactly what I need cleans my RAM so I'll get 120MB and after that loading of apps is much faster than starting apps with Android included RAM cleaning.
It just cleans my RAM like a reboot but without the reboot
This should be a temporary solution until someone finds a better solution or until froyo is released.
I would like to have an application like this with an autoclean option on 2 hours
Guys please,
Getting off-topic here. Here is Android Development.
Not Q&A or General.
Please post in the right section.
Here is getting too many off-topics that pose no relation to Android Development.
Too cluttered.
Thanks
DasLeo said:
DAMN!!! Nice app... it does exactly what I need cleans my RAM so I'll get 120MB and after that loading of apps is much faster than starting apps with Android included RAM cleaning.
It just cleans my RAM like a reboot but without the reboot
This should be a temporary solution until someone finds a better solution or until froyo is released.
I would like to have an application like this with an autoclean option on 2 hours
Click to expand...
Click to collapse
Auto killer is better.Its exactly the same as minfreemanager but can be made to apply at boot.Minfree manager resets itself at boot.
I use Memory Booster Lite (free version) app to free up memory, must do that manually but it works very well, if you buy the app it free up memory automaticly.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
The phone does have 512mb of ram. It just isn't used properly.
MOJO783010 said:
Hi, didn't read all the posts, but u should look into the RFS file system, which is samsung proprietery file system. It has a very bad implementation on android (i could be wrong). As for ram, the phone has 512 mb, but 128 are reserved for Gsm/data connection. Just think if you had an incoming call and all your ram was in use, u had to wait for the system to clear up some memory before being able to receive the call physiclly. That would be a long wait.
I could be wrong and sorry for the bad english.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, wrong. The reserved ram is in the form of a ram disk, which seems to be a bit oversized. Not really sure why a ram disk is needed at all, personally.
sammy555 said:
Auto killer is better.Its exactly the same as minfreemanager but can be made to apply at boot.Minfree manager resets itself at boot.
Click to expand...
Click to collapse
This is the correct solution. the JF* series of firmwares have very bad default settings for killing unused apps. Use this app to set them a bit better and you shouldn't have any problems.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
It does have 512 of ram, but some is partitioned off for the phone, so that you can always receive phone calls. Just about every device does this, because users would be more upset if they couldn't pick up the phone until they had closed a bundle of running programs. Don't you think that people here would have noticed earlier if the SGS physically had less ram than claimed ?
As far as the OP is concerned, sounds like you are just running too many programs at once. Its not an android problem, its user error.
Any task manager, but particularly an auto-killer will set you right, although alternatively you could try not leaving every app open when you're finished with it. You think your PC would run ok if you left one game open while you opened another ?
DasLeo said:
I never testet Froyo because everyone said, it's unstable but for me it seems like froyo has other RAM management than Eclair when you said you can't reproduce this problem.
I'm already using a task killer... I have my main apps ignored or excluded and most time there are 2 or 3 apps which will be killed after lock or time or what else.
What's the problem here... if I would use a PC with 512MB RAM and use only 10 small applications, it won't cache everything in the ram until it's full.
Click to expand...
Click to collapse
I wasn't comparing a N1 on FroYo to the SGS on Eclair. My comments were in regard to when I was on Eclair, which was several months...FroYo's only been available for a couple of months. What I said was since I'm on FroYo now, I can't compare side-by-side, but my experience with an N1 on Eclair was never any lag problem or GUI freezes.
Anyways, I also suggested you try Autokiller, and you missed that or misunderstood it by saying you already run a Task Killer (which is generally considered a bad idea, but I see you picked up on Autokiller after someone else suggested it. Enjoy.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
Nah, all phones advertise the actual chip size in it, not the amount the system actually lets you use.
tra33372 said:
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
Click to expand...
Click to collapse
Thank you. This removes almost all lag I'm experiencing.

How to make your LG Optimus 2x run like a Rocket! (Requires Root)

You don’t need to change your ROM to get the best from your 2x, just a rooted stock ROM and a couple of apps that will change things dramatically. One thing I’ve noticed on the 2x is its memory management is too lenient and gets consumed quickly by background tasks etc. In no time I was down to 40-30Mb free memory and then my phone would run like a dog resulting in a reboot as the only solution.
Installing task and app killers are not the way, as they’ll only give you a short respite before the apps and background tasks you killed relaunch.
However, there is a solution.
1)Root your phone using SuperOneClick (piece of cake, instruction already on this forum)
2)Install “AutoKiller Memory Optimizer” by AndRS Studio free from the market
Optional
3) Install “Watchdog Task Manager” by Zolmut LLC (There’s a free or Paid version) I paid!
4) Install “Root App Remover” by Best of Best Android app
AutoKiller is not a task killer/manager it reconfigures Androids inbuilt memory manager to kill or suppress memory usage by applications and tasks. I now always have about 140-170MB free RAM at all times regardless of what I’m doing (but I do close my apps with the back button rather than click home)
AutoKiller Memory Optimizer Settings
I’ve used the ‘Extreme’ settings to ensure I have around 150MB free, and this makes a huge difference in everything I do with the phone.
----------Optional things you may want to consider-----------
Watchdog
Yeah, I know this is a task killer but Watchdog is different from other task mangers as it monitors CPU usage rather than free RAM, 3D Gallery for example is a CPU hog on my 2X, so I configured it to be killed if it consumes more than 30% CPU whilst running in the background, you’d be surprised what saps your battery!
Root App Remover
Uninstall the tosh supplied on the ROM, I removed the following, AndroidBackup (I use Titanium Backup), CarHome, F-Secure_Mobile_Security, SNS (If you’re not using the built in Facebook and Twitter app).
I also use LauncherPro with Beautiful Widgets to give my phone an almost HTC Sense look and feel and uninstalled LG Home using Root App Remover afterwards.
Hope it makes a difference for you, it did for me, vote if you like
What do you think having 140-170MB RAM free at all times actually does?
Guess what? Nothing.
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
We want to see some bench marks.
Thanks for sharing! My phone does become much more responsive
Sent from my LG-P990 using XDA App
I tried the app too and i can say that it works, I also did some of the advanced tweaks.
phone seems more responsive now.
Yes, me too. It's more responsive now. Also when I open app manager, the app list is a lot faster.I know it's more related to file read/write but still it's nice to finally able to browse with less waiting time.
Sent from my LG-P990 using XDA App
thx
good one and simple, thx
cann someone please post some benchmarks?
Here are some screenshots, tested with AnTuTu Benchmark
The first one is v10c stock, some apps like f-secure, carapp etc frozen, second one is with using autokiller memory with preset extreme, third one is to compare, this was while using cm7.1 rc
now we'll see if autokiller works stable ^^
edit: realized that with cm7 something seemed to be wrong with the sd-card, so don't forget to compare the single-scores
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'm sure Rusty knows what he is talking about. Thing is, this talk about "the more free ram the better" has been repeated so many times, and at the end of the day, it seems to be more about user preference.
The default LG ROM seems to allow tasks to run in the background until it reaches around 50MB free RAM, then it starts to close tasks one by one. For multi-taskers like me, this is fine, I love how I can switch between facebook, tweetdeck, miren browser, google+, gmail, and messaging without seeing the apps reload.
For some, they'd want to open a task, close it, and move on to another without looking back. I guess that is where the 100MB of RAM is good for.
If you guys will be looking at benchmarks, I can guarantee that you will have higher scores with RAM optimizers. As benchmarks do not test multitasking, they simply check the performance of your phone at that point in time. (Which is also why some modders pump up their CPU freq to insane values before doing their bench then posting it.)
I have nothing against AKMO, and I find it very effective for Froyo builds. But I would recommend that each user try it out themselves. It's not a "1 fix for all" thing.
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
kiljacken said:
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
Click to expand...
Click to collapse
Does O2X already support swap space in EXT? (Or are your referring to VM heap?)
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
akyp said:
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
Click to expand...
Click to collapse
Yeah, FR19 is one of the more stable ROMs out there. Try full wipe then reflash maybe.

Apps Performance issue

Hello evry one. I have problem in my captivate and other models of android. I installed almost every custom rom but problem of loading apps fast still exist. What i mean is.. that when i on my mobile, so first time apps like calender, messenging etc take a little time to load. than when i close the app and open again, it loads very quickly. When mobile goes to standby for more than 10 mins, and when i on it, it again take little time to load apps, and widget menu etc.
Why it is like that ??? and whats the solution to always load the apps quickly
majidshahab091 said:
Hello evry one. I have problem in my captivate and other models of android. I installed almost every custom rom but problem of loading apps fast still exist. What i mean is.. that when i on my mobile, so first time apps like calender, messenging etc take a little time to load. than when i close the app and open again, it loads very quickly. When mobile goes to standby for more than 10 mins, and when i on it, it again take little time to load apps, and widget menu etc.
Why it is like that ??? and whats the solution to always load the apps quickly
Click to expand...
Click to collapse
It's how Android manages memory. It keeps your apps in memory until it needs to free some, at which point it starts to close apps to free some up. If they're already in memory they open fast because they're already open. If they aren't, they open more slowly.
There's not a ton you can do, really. Some 3rd party sms apps let you lock the app in memory, but I honestly never checked to see if it really works or not.
Personally, I restart my phone every morning when I wake up. This frees up the most memory and allows your phone to leave more apps open before closing them.
make sure you arent running any ****ty task killers.
You could flash an I9000 ROM/kernel that let's you tweak the lmk. (low memory killer)
Talon and semaphore both offer that option.
The trick is to make it weak enough to not kill the apps you want, but aggressive enough to not allow to run out of ram completely.
both of those kernels also have a "bigmem" version that gives the user a bit more ram at the cost of being able to record video in 720p.
studacris said:
You could flash an I9000 ROM/kernel that let's you tweak the lmk. (low memory killer)
Talon and semaphore both offer that option.
The trick is to make it weak enough to not kill the apps you want, but aggressive enough to not allow to run out of ram completely.
both of those kernels also have a "bigmem" version that gives the user a bit more ram at the cost of being able to record video in 720p.
Click to expand...
Click to collapse
I like ur answrr. But can u pls guide me abt lmk. I like this idea but never use such tweaks. I m using talon kernel right now and rom is much fast. But have same prb of apps loading
In the app memory freak, that installed with the kernel, there is a slider for you to adjust,
lower number the more aggressive the lmk but the better the overall performance.
Higher number is less aggressive and is better for multitasking, but can be a bit slower.
studacris said:
In the app memory freak, that installed with the kernel, there is a slider for you to adjust,
lower number the more aggressive the lmk but the better the overall performance.
Higher number is less aggressive and is better for multitasking, but can be a bit slower.
Click to expand...
Click to collapse
Where to find app memory freak ? i haven't seen any option in CWM
Should have been installed when you flashed talon. If not, it should be linked in the talon op.

[Q] Extremely Low Ram & Camera Force Closes - CM7

I have a Droid A855 rooted, CM7 installed. I have the latest build. I have two issues, one is that the free RAM is ridiculously low with like 5 apps open it has about 20MB of RAM free. This is unacceptable because my Huawei Ascend has 90 free with many apps open, and the Droid has twice the ram of the Ascend. Is there any suggestions about this? Also the camera was working great and then it started freezing, and now the camera force closes when I press the button to take a picture. If I go to the camcorder it works fine, but otherwise I get force close. Any help would be greatly appreciated.
AtmosFEAR4701 said:
I have a Droid A855 rooted, CM7 installed. I have the latest build. I have two issues, one is that the free RAM is ridiculously low with like 5 apps open it has about 20MB of RAM free. This is unacceptable because my Huawei Ascend has 90 free with many apps open, and the Droid has twice the ram of the Ascend. Is there any suggestions about this? Also the camera was working great and then it started freezing, and now the camera force closes when I press the button to take a picture. If I go to the camcorder it works fine, but otherwise I get force close. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Personally CM7 has just never ran smooth. No matter what I have tried. Gingerbread was never really meant for the Droid so most roms have built in stuff to help with memory that I do not believe CM7 ever had added. and the camera is outright terrible lately, I have it force closing on all my roms. I really don't know how to help all I can really try suggesting is trying out other roms
durandgir said:
Personally CM7 has just never ran smooth. No matter what I have tried. Gingerbread was never really meant for the Droid so most roms have built in stuff to help with memory that I do not believe CM7 ever had added. and the camera is outright terrible lately, I have it force closing on all my roms. I really don't know how to help all I can really try suggesting is trying out other roms
Click to expand...
Click to collapse
Thanks for the quick reply, I beg to differ on the Gingerbread not being for the droid part, my old Ascend runs Gingerbread Cm7 with flying colors, and this droid has double the performance...
AtmosFEAR4701 said:
Thanks for the quick reply, I beg to differ on the Gingerbread not being for the droid part, my old Ascend runs Gingerbread Cm7 with flying colors, and this droid has double the performance...
Click to expand...
Click to collapse
Try Peter Alfonsos GB, I found that it gave me the most amount of free ram at any time
taptaptouch said:
Try Peter Alfonsos GB, I found that it gave me the most amount of free ram at any time
Click to expand...
Click to collapse
Hmm
Sent from my Droid using xda premium
I think you guys are missing a crucial part about how Android is built. Free RAM is wasted RAM.
Newer versions of Android, especially Gingerbread, are better at RAM management than older versions. Granted, there's an ever-growing need for more RAM for basic system functions, but Android is designed to free up RAM on-demand for the things that need it.
Just because RAM isn't free doesn't mean that the system is going to slow down. Android will put the stuff that's not being used anymore into a swap file so that the stuff you need to work with can do what it wants.
projektorboy said:
I think you guys are missing a crucial part about how Android is built. Free RAM is wasted RAM.
Newer versions of Android, especially Gingerbread, are better at RAM management than older versions. Granted, there's an ever-growing need for more RAM for basic system functions, but Android is designed to free up RAM on-demand for the things that need it.
Just because RAM isn't free doesn't mean that the system is going to slow down. Android will put the stuff that's not being used anymore into a swap file so that the stuff you need to work with can do what it wants.
Click to expand...
Click to collapse
Yes but the ram is going so low that it is closing my applications like music when I go to a different screen.. it's frustrating
information ++
sfahadzb said:
information ++
Click to expand...
Click to collapse
What? I dont understand
I agree with you and I will like to agree with you but it just won't work. This is like Windows Vista, they use all the memory, but it is very slow when you try to open application which you don't use a lot.. and it also causes a lot of slowness when you try to use more ram for soemthing else, like modify a huge image in photoshop and then switch to some other application.
Get back to the real story, my phone get memory lower than 50 free MB easily. and when I open Google current in this stage, it just hangs for 5 minutes. then I get a message "force closed". However, if I have 100 free MB, then I am safe, I don't see that popup message. Moreover, when I go to 40 free MB, I even have hard time to open skype and pick up the phone, it just rings, but the screen just hangs! when the screen refresh back, people get into mailbox already....
anyway, I found a software to temp solve this problem ZDbox. I set up when the screen hangs, "kill all apps in the memory" it is not best, but at least I can pick calls, I can run application without getting "force closed" message all the time.. because I need to reboot few times a day to solve ram issue.
perhaps, you can do a test yourself.
- install CM7
- install facebook app and run
- install google reader and run
- install google current and run
- install skype and run
- install gmail and run
- install google voice serach and run
- install google book and run
- install whatsapp and run
- install naver LINE and run
- install twitter and run
- install zdbox and run
- install lookout and run
- install go laucher
well after all this, your phone show be in less than free 50MB.. if so, try to run other application and you will see the problem.. screen hangs.....very slow response....not able to pick calls...
projektorboy said:
Just because RAM isn't free doesn't mean that the system is going to slow down. Android will put the stuff that's not being used anymore into a swap file so that the stuff you need to work with can do what it wants.
Click to expand...
Click to collapse
Yeah but even though "free ram is wasted ram" it still causes instability and force closes along with just pure out lag. My D1 lags when it has only 30mb of ram or less anything over 50 and it flies along. It lags to the point were even simple tasks are slow when they should not be.
AtmosFEAR4701 said:
I have a Droid A855 rooted, CM7 installed. I have the latest build. I have two issues, one is that the free RAM is ridiculously low with like 5 apps open it has about 20MB of RAM free. This is unacceptable because my Huawei Ascend has 90 free with many apps open, and the Droid has twice the ram of the Ascend. Is there any suggestions about this? Also the camera was working great and then it started freezing, and now the camera force closes when I press the button to take a picture. If I go to the camcorder it works fine, but otherwise I get force close. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Droid has 256MB RAM. (Actually, there's only 226MB RAM available to kernel.)
If the Droid has twice the RAM of your Huawei Ascend, then your Ascend has only 128MB RAM.
If it has 90MB RAM free with many apps open, then it means that all the system services and all the "many" open apps has to fit to 38MB of RAM.
That's hard to believe.
And btw., you can't compare RAM consumption on devices with different display resolution. Droid drives 854x480 pixels and uses hdpi bitmaps. I guess that the Ascend has lower resolution. The RAM demand is much higher on WVGA hdpi devices compared to low resolution HVGA/QVGA mdpi/ldpi devices.
When I my HTC Desire Z, I was in love, awe of the beautiful interface HTC Sense and the many adjustments I needed to make experience to a higher level, the Android. However, as I went about installing my wealth of applications, games and widgets (more than a hundred, are addictive), Sense started getting so instead of improving my experience. The initial screen would start every few hours re; each faucet took longer to record; Screen rotation when the keyboard sliding open continue for centuries; and each phone looked like he was struggling to get by.

[Q] memory usage

Good day!
Im new to xda-developers forum, just found a link in youtube while watching some stuff about galaxy note.
I have not discovered my galaxy note thoroughly yet coz its still new to me. Just wondering, the usage of memory without running any apps will go about 60%-70% percent. My temporary solution for this is to run task application and kill all exciting apps. Just wanna ask what kind of problem this may be?
No need to get alarmed by that. That's the way Android runs: it keeps apps in cache, so you can access them faster. When there's too much of them cached, the system kills off some apps.
chasmodo said:
No need to get alarmed by that. That's the way Android runs: it keeps apps in cache, so you can access them faster. When there's too much of them cached, the system kills off some apps.
Click to expand...
Click to collapse
thank you for your reply.
in this case, i cannot access on other apps that i'll run. just manually kill all the apps every-now-and-then.
Just remember: free memory is wasted memory. This is true for almost every piece of computing machinery out there.
inkanyamba said:
Just remember: free memory is wasted memory. This is true for almost every piece of computing machinery out there.
Click to expand...
Click to collapse
Thank you.
the only thing is, when i access on other apps like games. loading on the apps takes longer or even it crashes. maybe its because of the memory allocation of the apps or just there is no enough memory space to allocate the app.
JoshuaTumanda said:
Thank you.
the only thing is, when i access on other apps like games. loading on the apps takes longer or even it crashes. maybe its because of the memory allocation of the apps or just there is no enough memory space to allocate the app.
Click to expand...
Click to collapse
While what the other member said is true, unused memory is wasted memory, but the issue is exactly that. Android ends apps that you may be running to be able to open more apps, which I find bad.
While it is normal to find the amount of ram you have said already loaded and being used, I still don't like it.
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
But still, I hope ICS fixes this issue. I don't need 200 of the 1 gig of ram in use, what I would like is to have 300 or so free to be able to multitask normally.
zkyevolved said:
While what the other member said is true, unused memory is wasted memory, but the issue is exactly that. Android ends apps that you may be running to be able to open more apps, which I find bad.
While it is normal to find the amount of ram you have said already loaded and being used, I still don't like it.
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
But still, I hope ICS fixes this issue. I don't need 200 of the 1 gig of ram in use, what I would like is to have 300 or so free to be able to multitask normally.
Click to expand...
Click to collapse
Thats exactly my point. Thank you!
zkyevolved said:
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
Click to expand...
Click to collapse
can you please elaborate on the workarounds so that Android doesn't kill the background apps especially opera mobile

Categories

Resources