Related
hi everyone, i'm no expert on phone, so don't kill me if i sound stupid
been using my galaxy S for about 4 months now. and yes it does lag compare to the iphone, or other HTC phones. so i been trying to find out, what's going on? why is my top end phone lagging? here's what i found:
1) when does it start to lag badly?
i installed system panel which gives me a nice list of active and inactive apps, and how much free ram i have left. the phone ALWAYS starts to lag like crazy when ram gets below 60mb. this is a problem - samsung is not giving us enough free ram to play with as once we run a few apps (market, internet especially), we're reaching the 60mb point already. when the phone gets to the 60mb mark it tries to manage the apps by closing some less important ones. but it lags BADLY while doing so.
what's gonna happen is the phone gonna get into this never ending cycle of closing apps and laggin as it's stuck in around the 50mb-60mb mark.
i can solve this by going to system panel and closing all inactive apps. then the ram is gonna go back to around 140mb. however after opening a few apps, once again it goes back to below 60mb and the lag starts again.
2) autokiller
guys been saying autokiller is great and they go with the aggressive settings. i tried it and it made the phone worse. why? because instead of killing apps at the 60mb mark it starts killing apps even sooner! that's wasting battery, wasting free ram, and making the phone even slower. we don't have enough free ram to begin with, so we should make max use of it. here's how i do it:
1) root the phone. install autokiller from the market.
2) instead of using high aggressive settings, use the LOWEST settings. i use advanced mode and then enter all values to 8mb only.
now it is awesome!! the phone never lags until you get it down to around the 20mb mark. you now have around 40mb of extra ram to use (of course autokiller does use some ram but no big deal). the lag starts much latter. u may not think 40mb is a lot but it is in practice!
if you dont believe me, you can try it. it may or may not work for u, but it's definitely working for me. of course, once the ram falls below 20mb, it may be a good idea to close some inactive apps yourself, LOL
but really, samsung should give us at least 100mb more free ram, i can't believe i even have to do this!
Well you point one issue that lag happens, but almost every custom kernel/Rom use memory tweak that Make you around 40MB more to start with.
And yes autokiller don't work good.
The program in the phone is the best to use.
The main lag issue is the filesystem.
Even these can be fixed with many different kernel/Rom.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram
i don't disagree with what you're saying. but a few things to add:
1) i have not applied lag fix myself but i have a friend who has. i dont feel his phone is much quicker than mine in reality. also, his phone crashed after a few weeks and he had to do a hard reset. what we REALLY need is more ram. if we have lots of ram, who cares about the file system? we don't even need any swap from the file system. just let everything stays in ram where it is the quickest.
2) i'm not using any custom roms. if custom roms give me extra 40mb, and then i adjust the auto killer setting to low, that gives me 80mb extra to play with. great.
autokiller DOES work good i feel if you're doing what i'm saying. maybe u have already tried what i'm doing, i don't know, but if you have not, then i highly recommend you to try it.
like i said i'm no expert on this, but autokiller is so easy to install and adjust, and that i feel anyone here can use it
maybe flashing custom firmware is easy to do, i haven't tried it, but it sounds complicated to do for me, and i don't want really big changes on my phone, i want it to be extremely stable and safe as i use it a lot for business. i don't really want to risk any data or risk reinstalling stuff.
so maybe i sound uneducated but like i said i suggest everyone to try this method if they're newbies and don't wanna do too much
I can confirm that setting autokiller to low settings makes the phone feel faster than on high settings, I tried that some time ago.
But lag will still be present.
As mentioned by the poster this is a low risk, low skill method of improving the phone and is easy to do for all.
For all others I recommend the JFS lagfix. It is by far the lagfreest experience out there!
i have a buddy with a moto milestone and his phone lags just the same as ours. his phone has even less free ram than ours and so his is constantly lagging. sometimes he can't even take a phone call while listening to music becoz his phone only has like 50mb of free ram after starting up. so, just a point of reference - our galaxy is crippled with just not enough free ram, i heard stories of nexus one having 200+ free ram after startup and that's why they dont lag like us, so at the end of the day we're fighting a losing batter becoz samsung didn't give us a good enough phone
Mycorrhiza said:
I can confirm that setting autokiller to low settings makes the phone feel faster than on high settings, I tried that some time ago.
But lag will still be present.
As mentioned by the poster this is a low risk, low skill method of improving the phone and is easy to do for all.
For all others I recommend the JFS lagfix. It is by far the lagfreest experience out there!
Click to expand...
Click to collapse
thank u and i may try the jfs fix, but i'm just worried about something happening to the phone becoz of what happened to my buddy who lost all his data (i can't remember which lag fix he used though), i always have this thinking that if the lag fix are 100% safe, then why aren't samsung doing it? samsung are paying tons of money to the programmers i'm sure and you would think they know how to do it too? but they choose not to, and there must be a good reason why.
You have a very good point supraman123! I realized it was the memory management that made the phone go crazy around the 60MB mark (you'll see the kswapd0 process go crazy), but never realized Autokiller could help us lower that mark. I hope this works, would be one of the best and easiest fixes for the SGS.
supraman123 said:
thank u and i may try the jfs fix, but i'm just worried about something happening to the phone becoz of what happened to my buddy who lost all his data (i can't remember which lag fix he used though), i always have this thinking that if the lag fix are 100% safe, then why aren't samsung doing it? samsung are paying tons of money to the programmers i'm sure and you would think they know how to do it too? but they choose not to, and there must be a good reason why.
Click to expand...
Click to collapse
If we know the amount of time and money Samsung spend on developing RFS...
So wait, the phone is faster if the minfree is set higher than default, and the phone is faster if the minfree is set lower than default... holy ****!
I applaud Samsung for figuring out the one setting that makes the phone suck and use that as default. Way to go, Sammy, way to go.
I know what u are talking about. I think it was an ext4 fix. All other lag fixes I know of don't share that problem.
Also with root there are many ways to secure your data prior to installing a lag fix.
Sent from my GT-I9000 using XDA App
Mycorrhiza said:
I know what u are talking about. I think it was an ext4 fix. All other lag fixes I know of don't share that problem.
Also with root there are many ways to secure your data prior to installing a lag fix.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
hi, thank u, can u tell me how to secure the data? or u have any good links to show me? thanks
jjwa said:
You have a very good point supraman123! I realized it was the memory management that made the phone go crazy around the 60MB mark (you'll see the kswapd0 process go crazy), but never realized Autokiller could help us lower that mark. I hope this works, would be one of the best and easiest fixes for the SGS.
Click to expand...
Click to collapse
i hope it will work good for u also
xmonkee said:
So wait, the phone is faster if the minfree is set higher than default, and the phone is faster if the minfree is set lower than default... holy ****!
I applaud Samsung for figuring out the one setting that makes the phone suck and use that as default. Way to go, Sammy, way to go.
Click to expand...
Click to collapse
i'm quite disappointed at the ram issue also. coming from a n97 mini which seriously lacks ram, i was hoping by going for a high end phone like the galaxy, i aint gonna have to worry about ram and closing apps manually all day, however in reality the Galaxy aint much better than the n97 at multi tasking. of course, it's far better than the n97 at everything else.
I totally agree with OP on this one!
But Autokiller is not the only app that can fix the lag.
One Click Lag Fix 2.0 can root your SGS (Eclair only), lagfix it (with EXT2) and it can even do some additional tweaks like minfree (same as the Autokiller app) and fix the Scheduler.
With minfree Samsung put these values in "/sys/module/lowmemorykiller/parameters/minfree":
"2048,4096,5120,5632,6144,7172"
But best is:
Aggressive: "1536,2048,4096,21000,23000,25000"
or
Strict: "1536,2048,4096,15360,17920,20480" - I prefer this one
btw when you've a lot of ram free the ram is mostly used to cache file system reads ^.^
this explains that a little
Im using the 341MB of free ram so that gives me an instant 40MB ontop of the stock kernel, never seen the phone had less than 60mb free with this kernel, with my usage it doesnt even go under 95mb free.
I am also running one of those kernels that gives extra RAM. And I have all my partitions Ext4 lagfixed. But my phone still seems quite slow at times. My RAM was above 80MB free at that time though, so probably not related to any minfree/Autokiller thing at all. Which means there are way more causes to get rid of I guess.
I don`t know how you guys have problems with the lag, I use the stock samsung JPO, not even deodexed with zankinz 23 kernel and NO-RFS all ext4 lagfix and the phone is running perfectly, no lag whatsoever, the RAM is somewhere near 220 mb free after reboot. After deodexing and optimizing the apk`s the phone should run even better. I was determined to change my SGS with a Desire HD, but now I`m really thinking of keeping it.
Just wondering if anyone else has lags in there roms the more apps and games etc they add/install.
I have tried loads of roms and they all seem to slow down and get laggier and laggier the more stuff you install.
Im currently using Superrom HD Data2Ext v2.0 and thought it was ok at first then when it starts to fill up it gets worse.
Anyone know a good rom that doesn't lagg up on app and game instalation.
I currently have 18 app/games and it runs fine now and again but some times it can just lagg like mad, this morning I had to remove the battery it was that bad and unresponsive.
AOSP roms are very good with not becoming laggy and also the stock rom as well. HD rom tend to lag as I found out last week with InsertCoinHD Data++. Even using my internal memory, it still lagged massively.
Meaple said:
AOSP roms are very good with not becoming laggy and also the stock rom as well. HD rom tend to lag as I found out last week with InsertCoinHD Data++. Even using my internal memory, it still lagged massively.
Click to expand...
Click to collapse
Storing stuff on SD card will slow down your ROM, especially data.
I used to have data on SD card and tried a lot of combinations of kernels and IO schedulers but all of these showing various lags. Strangely enough, some of them gave very high quadrant scores (because of various caches) but almost as a constant I observed that the higher the quadrant score the more laggier the ROM.
If you need more space, store your apps on SD card. From there, the VM will generate .dex files in /data/dalvik-cache.
The key point is to keep your phone running as much as possible from the internal memory. This will reduce lags.
HD ROMs have more lagging than the non-HD ones. That is what I have experienced and I have tried almost all of them. So I am back to (modified) stock ROM.
But there can be many other reasons ... kernel ... settings that are done at boot time through /etc/init.d, very difficult to say in general.
I have got about 75 apps on my phone. No lags. Also no degrading performance over time.
I am running the stock Froyo (and removed unneeded bloatware), with custom compiled kernel, OC at 1113Mhz. Only apps are installed on SD (because otherwise not enough space) but all the rest is running from internal memory.
Check how many (background) services are running on your phone. I have 11. They may compete for some resources.
One other point ... check your kernel. Dalvik VM on HD ROMS requires cgroups enabled kernel. If your kernel does not have cgroups the VM will stall (causing lags).
Check the logcat ... you will see error messages saying "Unable to find CPU subsystem" ... in that case your kernel does not have cgroups.
would this free up space I am using VR Kingdom and is it advisable
Yes, it can, however, if your device is performing sufficiently as-is, I wouldn't move the dalvik. Do a little bit more research. I haven't heard of anyone claiming huge performance increases by moving the dalvik to SD.
dougjamal said:
Yes, it can, however, if your device is performing sufficiently as-is, I wouldn't move the dalvik. Do a little bit more research. I haven't heard of anyone claiming huge performance increases by moving the dalvik to SD.
Click to expand...
Click to collapse
Thanks will do
Only IF
I am trying to move my dalvik or upsize the folder (which is limited to 160MB on mu EVO 4G) because once the dalvik threshold has been acheived you will receive the dreaded "There is insufficient room on the device" error message when trying to install applications
dougjamal said:
Yes, it can, however, if your device is performing sufficiently as-is, I wouldn't move the dalvik. Do a little bit more research. I haven't heard of anyone claiming huge performance increases by moving the dalvik to SD.
Click to expand...
Click to collapse
You don't move dalvik to the SD card for performance increases. If anything, it slows it down (particularly on boot). The only reason to move it is for extra space.
Mine has shown zero performance loss on MIUI and better performance when I was on Blazing Roms Fusion. MUCH better performance. Moving Dalvik on Fusion freed up 200MB of internal space, which would ONLY result in better performance.
It's like Windows after a temp/cache file cleanup and defrag.
Can anyone chime in on wether my used/free memory amounts look normal? I have 181 apps in total and a2sd running, an 8gb card. I do have navigon installed which the maps suck up 1.5gb of my SD card. I am not having any issues, just want to make sure I didn't screw anything up.. Thanks for any input/advice.
ROM
367MB (total)
147 MB (free)
Internal
446 MB (total)
309 MB (free)
SD
7 GB (total)
3.9 GB (free)
SD(a2sd)
959 MB (total)
672 MB (free)
**Edit**
Disregard, looks like I'm in good shape. Thanks.
Hi,
working daily with linux-OS and beeing actively using custom roms since Android 2.1 I have a bit of knowledge on RAM usage on Linux and Android. As many know and like to post "free RAM is wasted RAM" - we all know that. But why? Because all not actively used RAM (lets call it "free") can be used as a cache for applications you likely will need in future. But what if your GNEX runs out of free RAM an is not able to cache any more? What if you start a new huge application like your browser and free RAM has to be obtained to give it to your starting application? Yes - bad things can happen!
But lets start from the beginning:
1. If you go to Settings->Applications->Running you get the RAM-bar at the bottom of the screen. This is splitted in two parts: used and free (like defined above). Used RAM seems to be actively allocated RAM which cannot be used for other things like starting applications and free is the RAM which can be obtained because it only containes caches apps which are not running.
2. Directly above that bar you se a kind of brace which seems not to be just eye-candy but has some meaning: The lower and thiner part of that brace seems to show the part of that RAM (used or free) that is used by the applications/service in the list above. Example: if you switch to cached applications the brace will jump to that part of the bar and by killing some of the cached apps you will change the width of the brace.
Lets put things together:
viewing the used RAM you will notice that the brace does not cover the whole used-ram-bar but, in my case, about the half. I also noticed that the width of the brace does not change greatly with uptime of the device as all listed services will stay at their size more or less so their sum is not going to change greatly. In my case all services sum up to about 250MB meaning the braces width is about 1/3 of the screen assuming that GNEX has 700MB total RAM (the rest of 1GB total physical RAM is allocated to other parts of the SOC-chip like Baseband and GPU and not available to linux-kernel or android).
But one thing does change greatly!!! The part of the used-ram-bar which is not covered by the brace will be very small after rebooting and will grow with uptime. As the part covered by the brace is a fixed factor this means that the free ram is the trade-off for the growing uncovered part of the used-ram. In my case I get after rebooting the device: 250MB free, 450MB used of which 250 are covered by the brace, leaving 200MB used RAM for whatever (kernel, non-android stuff like filesystem caches, ideas?) After some days of usage this changes to 50MB free, 650MB used of which still about 250MB are covered by the brace, leaving 400MB used for other things (NOT app-cache).
Consequences:
From the assumptions above this means that android is not able to cache apps anymore (because they live in the free RAM) and my device beginns to lag while opening new apps. To obtain enough RAM for starting apps like browers (stock or firefox tested) it will even need to kill services!!! And in extreme low-memory situations it even kills the foreground app you are using (to me it happened while I used firefox). Also when you go to settings->applications->running again you will notice that android will be restarting your services over and over again to obtain more RAM without much success. In the situations my actively used firefox got killed something different happened: the launcher also had been killed because it was starting over but more importently settings->applications->running showed that much of the used RAM not covered by the brace was gone! Free RAM jumped from 50MB to about 200MB which is nearly what I get after a fresh reboot. I assume that in this extreme low memory situation also the kernel did clean up things.
From my observations you will get the following if your free RAM accoring to settings->applications->running is very low:
1. no cached apps if you swich to settings->applications->running->cached
2. laggy phone
3. your launcher gets killed more oftern when returning from e.g. browser
4. more apps get killed when returning to launcher meaning that they will get restarted if you return to that app
5. in low memory situations (app does not fit into free-RAM-part) services will get restarted frequently
6. in extreme low-memory situations kernel cleans up everything (i guess)
The question now is: what is using so much RAM and growing over uptime until our GNEX has no more free RAM? I alread checked different ROMs including stock 4.1.2, stock 4.2.2 slimbean 4.2.2 cm10-stable cm10.1-nightly and all of them show this behavior. The only thing I noticed: all 4.1 ROMS perform better in this area: their RAM does not fill up that quickly but it does. On 4.2 ROMs it takes just few days to run out of free RAM for me. I already wiped my device and installed only realy needed apps (20 out of 140!!!) but it still happens.
I think this happen in any OS
A daily reboot is always a must in my opinion, to free ram, to stop some services, to stop wake locks, to stop battery drain without sense..
Inviato dal mio Galaxy Nexus con Tapatalk 2
That's what always makes me ask : Is Gnex really have 1gb of memory?
Other phones with same spec. uses same OS have more than 693mb that in gnex , why the hell our phone has the lowest read ram in 1GB category phones
I'm sure this is the only weak-point in gnex
300MB is GPU reserved for camera.
madd0g said:
300MB is GPU reserved for camera.
Click to expand...
Click to collapse
Why?
Sent from my Galaxy Nexus using Tapatalk 2
I didn't engineer the device. But I presume it's a requirement by the GPU PowerVR chip, since it uses alot of RAM on the Nexus S, which had the same chip only downclocked. It was 330MB usable out of 512MB advertised there. The amount reserved is bigger on GN obviously because of HD video capture option.
madd0g said:
I didn't engineer the device. But I presume it's a requirement by the GPU PowerVR chip, since it uses alot of RAM on the Nexus S, which had the same chip only downclocked. It was 330MB usable out of 512MB advertised there. The amount reserved is bigger on GN obviously because of HD video capture option.
Click to expand...
Click to collapse
I agree GPU shared system RAM, but 300MB is wayy too much bro. I checked my N4 it has 1.82GB of 2GB total considering N4 Adreno and camera chip is more powerful than i9250
It's (again probably) not because of the speed/power etc. but that it's like that by design. Adreno ain't the same as the one used on GN, so there's no comparison.
I'm sure Google didn't allocate that much memory just to screw us up, but instead there's a legit need for it. For instance, the amount of RAM available on a Galaxy S2 is much bigger, around 830-850MB out of 1 GB and it has a completely different camera/GPU combo, spite full HD video and 8 mpix instead of GNs 5. That's why I presume it's just PowerVRs "fault".
Perhaps, i just checked galaxy tab 2 ics available ram, it less than 700, but after flashed stock JB, it shows more RAM, about 770MB. Tab 2 uses OMAP and PowerVR right? Imho. i just curious why it reserves so much ram. Searched google and can't found the reason :S
Sent from my Galaxy Nexus using Tapatalk 2
*Update*
An galaxy S2 with all stock (Android 4.1.2) shows the same amount of used RAM after 10 days of uptime (380MB free and 380MB used - a nearly perfect 50/50 ratio). No sign of degradation so far. Honestly this phone is not used much but still it feels very different from what I see on my Gnex.
Has someone shorlty fully wiped and reflashed his phone to stock 4.2.2 (JDQ39). How does the RAM usage look like after fresh reboot?
RAM problem
This is what i get today. Using liquidsmooth 2.4 fraco kernel. But i know its not abut apps i use. I dont know where are all that RAM. After reboot with same apps runing in background i have 230-260MB free RAM. But if i using phone day or so it look like this.
Phone get laggy, slow with high latency. Im not sure if its 4.2.2 bug for Gnex or just some mess with ROM but its same on any custom ROM. ill try flash stock and see what i get.
castaway1 said:
This is what i get today. Using liquidsmooth 2.4 fraco kernel. But i know its not abut apps i use. I dont know where are all that RAM. After reboot with same apps runing in background i have 230-260MB free RAM. But if i using phone day or so it look like this.
Phone get laggy, slow with high latency. Im not sure if its 4.2.2 bug for Gnex or just some mess with ROM but its same on any custom ROM. ill try flash stock and see what i get.
Click to expand...
Click to collapse
I'm experiencing the same problem with AXI0M and AK kernel.
castaway1 said:
This is what i get today. Using liquidsmooth 2.4 fraco kernel...
Click to expand...
Click to collapse
Hi, this is exaclty what i was talking about... very frequent service restarts and laggy phone and even basic things like keyboard and music-playback can quit while in use. While I tried to compose an email to send a screenshot to my desktop to post it here my stock-mail-app died and the phone rebooted. At least I have now both an after reboot and an after two days of using PARANOID ROM screenshot
I recently switches to PARANOID 3.55 and now have even more issues as the phone boots with just 200MB free RAM. This ROM seems to demand very much RAM.
BTW. I installed Stock for more than a week before switching to PARANOID and had around 260MB free after booting and around 150MB free after some days of usage. Increase was ways lower than on any custom rom. Can anyone comment on this? Same or contrary stock-experience?
Stock JDQ39 rooted. (running one week)
kernel stock or lean both are perfect and have no affect RAM or smoothness. Screenshot is after some days of full usage. Battery life i getting is about 1day with 2h screen on.
now someone tell me that its not custom ROM problem. 4.2.2 stock is just awesome. Im sad that custom ROMs not..
castaway1 said:
Stock JDQ39 rooted. (running one week)
kernel stock or lean both are perfect and have no affect RAM or smoothness. Screenshot is after some days of full usage. Battery life i getting is about 1day with 2h screen on.
now someone tell me that its not custom ROM problem. 4.2.2 stock is just awesome. Im sad that custom ROMs not..
Click to expand...
Click to collapse
2h screen time is really bad..
But nice to know that stock works well for you..
Mach3.2 said:
2h screen time is really bad..
But nice to know that stock works well for you..
Click to expand...
Click to collapse
its average +/- 30min and for me its not so bad for 24h
castaway1 said:
its average +/- 30min and for me its not so bad for 24h
Click to expand...
Click to collapse
As long as it makes your boat float, why not?
Beamed from my Grouper
castaway1 said:
Stock JDQ39 rooted. (running one week)...
Click to expand...
Click to collapse
Next step would be to deodex this ROM and to try again because Stock is odexed in contrast to any custom rom. I realy would like to figure out the reason for this bad RAM usage on custom roms.
fajabird said:
Next step would be to deodex this ROM and to try again because Stock is odexed in contrast to any custom rom. I realy would like to figure out the reason for this bad RAM usage on custom roms.
Click to expand...
Click to collapse
yes im on odexed rom. and im curious if deodexing some custom ROM will help with this. I think about slighty modified vanilla rascarlo ROM with kernel that work perfect lean 6.4 is smooth like stock and dont broke anything. Its deodexed rom so i can propably try THIS to odex it.
http://fitsnugly.euroskank.com/?rom=rasbeanjelly&device=maguro-vanilla
castaway1 said:
... im curious if deodexing some custom ROM will help with this...
Click to expand...
Click to collapse
I thing you ment odexing some custom ROM, right? I'm thinking about to try the odex-me apk you can find on XDA which will odex all apks from /system/app but leave the framework.jar stuff untouched. But its far more easy to deodex the stock ROM and to try again
I'm asking because I'm frequently out of RAM, causing extreme lags and launcher reboots. I know the CPU reserves 300MB, leaving 700MB, but how much do ROMs typically occupy? Any recommendation for leaner ROMs? Or perhaps there are modifications to enable more aggressive task killing (non-background tasks)?
843 said:
I'm asking because I'm frequently out of RAM, causing extreme lags and launcher reboots. I know the CPU reserves 300MB, leaving 700MB, but how much do ROMs typically occupy? Any recommendation for leaner ROMs? Or perhaps there are modifications to enable more aggressive task killing (non-background tasks)?
Click to expand...
Click to collapse
Run out of RAM? never again with this Mod
Gnex Supported! :good::good::good:
http://forum.xda-developers.com/showthread.php?t=2145133
How would that work since my GNex doesn't have an SD card? Isn't everything on the same internal memory?
843 said:
How would that work since my GNex doesn't have an SD card? Isn't everything on the same internal memory?
Click to expand...
Click to collapse
First of all, that mod puts it in /system, /data and/or /cache. So it doesn't even try to use the sd card regardless.
Second, I just thought i would try it out and it throws out an error "incompatible with your device Galaxy Nexus (toro).
I figured maybe i would give swapper 2 a go again. It hasn't been updated in ages, but it seems to work. You can leave it on sdcard (which is just internal memory anyway) or change the directory to any you want. I changed mine to /cache since my sdcard is kind of full. Can even change the swapiness within the app. Only downside is the limit for it is 256mb. So far it seems to be working properly on Verizon Galaxy Nexus stock, rooted, 4.1.1 with lean kernel.
Sent from my Galaxy Nexus using Tapatalk 2
I have done some tinkering. What seems to work for me is limiting background processes to 4 or less. These turn out to be cached processes which keep opened apps open. They eat up your remaining RAM and should ideally be removed if an app you're trying to run demands it. However, the removal process causes significant lag, possibly due to the slow internal memory the GNex has.
I'm running CM10 (4.1.2), and I have 245MB free right now. It has gone down to as low as 150MB, but rarely below. When using 4.2.2 based roms, I get as low as 40-50MB, which causes problems. I don't have high hopes for 4.3 right now.