So, it turns out the /preload partition is 500 megs of almost unused space, just to show us a video of Asphalt. So, how about turning it into swap space to almost double the effective amount of memory you have? To use this mod, you must be rooted, and have busybox installed. I recommend the stericson busybox installer https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I would like feedback on whether or not it actually speeds up the device, especially when running graphics-intensive games, and also effects on battery life.
How to install:
1.Be rooted.
2. Get busybox. If you don't already have it, you can get it here https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
3. You must have init.d support. This is built into my NardROM but you can also flash the file attached to this post.
4. Flash the script installer, attached below. NOTE: This will wipe your /preload partition. You can make a nandroid before you perform this step but CWMR doesn't back up /preload. Back up anyway
5. If it's successful, you will see something like the following screenshot when you open a terminal window and execute "free". Notice the swap being used. If you don't have swap enabled it will read 0 available.
To disable the mod:
1. Delete the script from /system/etc/init.d
2. Reflash your Asphalt video from a backup
To disable init.d:
1. Delete /system/etc/install-recovery.sh, /system/etc/init.d (entire folder), /system/bin/sysinit, and /system/xbin/run-parts
Disclaimers:
Using nand memory as a swap can significantly reduce its life. Your phone's internal memory will wear out in years rather than decades
A lot of people argue using Android swap works against the built in memory management of the Dalvik machine
http://forum.xda-developers.com/showthread.php?t=1504774
This is awesome, glad to see people spending time on this device
Tappin' Typin'
'' /vendor '' also has 590,56 Mbyte of space..
what kind of data is there? there are some folders called ''multi_pose_face_landmark_detectors.3'' and ''yaw_roll_face_detectors.3'' ? is this the carrierIQ stuff?
After deleting everything on that partition it says 395,95 mb used, 194,61 mb free.
ludacris1 said:
'' /vendor '' also has 590,56 Mbyte of space..
what kind of data is there? there are some folders called ''multi_pose_face_landmark_detectors.3'' and ''yaw_roll_face_detectors.3'' ? is this the carrierIQ stuff?
After deleting everything on that partition it says 395,95 mb used, 194,61 mb free.
Click to expand...
Click to collapse
I think it's device-specific info for face unlock to compensate for various things like the angle you're holding the phone at and the distance away from your face. And if you'll look a little more closely, you'll find /vendor is symlinked from /system/vendor, it's not actually a separate partition. You should probably put those files back if you want face unlock to work.
Technically I just downloaded some ram
Sent from my SGH-I927 using xda app-developers app On Ics
FYI, this could be a potential source of serious slowness. Swap isn't anywhere near as fast as real RAM.
I wouldn't do this unless you're legitimately having issues you can directly attribute to running out of RAM. It may be useful as Android marches on and demands more and more RAM but for ICS we're already a good clip above the recommended specs.
Same thing I was thinking. I have more than enough RAM but if by some miracle we get something past JB that uses a lot of RAM I'll do this. Nice work on it though!
sent from my captivate glide running ICS (NardROM 0.4 Rooted)
roothorick said:
FYI, this could be a potential source of serious slowness. Swap isn't anywhere near as fast as real RAM.
I wouldn't do this unless you're legitimately having issues you can directly attribute to running out of RAM. It may be useful as Android marches on and demands more and more RAM but for ICS we're already a good clip above the recommended specs.
Click to expand...
Click to collapse
Waiting for the comparison,then
mewatashiakumoi said:
Waiting for the comparison,then
Click to expand...
Click to collapse
So with this hack having been out a couple months now, how are the reviews? Performance increase? Fewer slow downs?
pm2gonzales said:
So with this hack having been out a couple months now, how are the reviews? Performance increase? Fewer slow downs?
Click to expand...
Click to collapse
1) this is not a hack, this is a simple tweak
2) swap file is ALWAYS has a performance decrease effect, no matter what (desktop PC, android phone). The only reason of use is when the device has no enough RAM, and the background processes shall be kept elsewhere
3) android has it's own RAM managing system and methods, simply stick to that as only that will gives you the best performance and user experience
4) "slowdown" occurs when the device runs out of free RAM and starts closing background applications to give everything to the foreground app. When you close the heavy resource use foreground app witch caused android to close every possible background apps, the phone reloads them (launcher, live wallpaper, app drawer, widgets, user apps, etc...) and this is what causes a temporary slowdown, and this is unavoidable, no matter if you use swap or not.
Related
This thread is for the discussion about the bounty and how to fix the poor IO performance
--> Bounty thread <--
A shellscript that do
-mount partition
-make a tarball of all data from this partion
-copy this tarball to /sdcard
-umount partion und format to new fs
-mount partion with new fs
-untar the tarball from /sdcard
for all relevant partion should be simple to write. After this the init.rc must modified to mount the new fs and not the old rfs. If the file is the same for all eclair firmwares, only this one has to change. The shellscript move the init.rc to init.rc.bak and copy the modified version.
This script can be started from an update.zip(I dont know if this possible). Or modify a recovery image, to start the script by a menu selection(this is possible).
I think this can be provide a simple solution for endusers. Unclear for me is why samsung use the rfs. This filesystem is optimized for flashdisks. It sounds like the internal nand has no wearleveling and a not flash optimized filesystem can damage the internal nand by rapid use to quickly.
I plan to test out how an external sdcard can provide the full os, not only partial like the speedhack. The init.rc file must modified to switch directly after start to the init.rc file on external sdcard. The init.rc from external sdcard start the the system from external sdcard. This variant reduce the modification on the phone and if the flashdisk is dead, the SGS is not a brick.
gr, Steffen from Germany
What types of file systems does the stock kernel support? Can it boot from ext2 as it can from this rfs?
Also: apparently the Nexus One uses the YAFFS2 file system for its root file system, which is made for use on NAND memory. Although it's probably easier to get kernel, tools and scripts to work for an ext2 based solution, we should probably look at getting a YAFFS2 fix eventually for best reliability.
I put up a quick guide over here which uses the playlogo hack. It's working perfectly for me and my phone is as smooth as butter!
http://forum.xda-developers.com/showpost.php?p=7571976&postcount=161
bub181 said:
I put up a quick guide over here which uses the playlogo hack. It's working perfectly for me and my phone is as smooth as butter!
http://forum.xda-developers.com/showpost.php?p=7571976&postcount=161
Click to expand...
Click to collapse
What firmware are you on?
As far as i remember, it is possible to ajust the times to which the filesystem (ext2,3,4?) syncs... If you increase that time, i would mean less writings to the nand - which again makes it last longer..
EDIT: spell correction.
andrewluecke said:
I'm concerned about this. People who are contributing to this bounty should consider:
1) Who decides if the fix is done? How exactly are you going to test? You can cause lag on every phone if you open enough crap, so how you going to test this? Or will you use a synthetic benchmark such as Quadrant?
2) Who verifies that the fix is safe. It's all good that you might end up with a solution where all lag is gone. But you might end up with a solution with no wear levelling which sucks up battery power because whenever the phone is idle it's performing online defragmentation.
3) Is battery life a consideration?
4) Remember, erasing flash memory also has a cost, which is why early SSD drives without trim slowed down a lot after a while, because they wouldn't erase it when the system was idle. So the fastest solution might be fast initially, but might write a lot of excess crap, which could affect long term results. Hence (1).
Before anyone explores a solution for this bounty, these questions must be answered, because disturbingly, I haven't heard 1 mention of SLC, Movinand or write cycle yet. I've only heard "RFS".
Furthermore, I've only heard "EXT", not "profiling tool" (has anyone actually profiled applications yet to isolate where the slowdown is). So, I think this bounty needs a bit more discussion.
It might also just be something simple, such as implementing something similar to Trim potentially (I myself aren't familiar with the architecture). Yes I want a solution too, but I want to ensure it's done properly.
Click to expand...
Click to collapse
We need to decide on how to test it!
My experience with lag
Hi Guys
The lag can be observed in two places:
1- While moving between windows in system apps (e.g. settings) or 3rd party apps (games, utilities). This lag keeps fluctuating, so sometime you would get it and sometimes you would not, and I DONT KNOW WHY
The above is definitely due to inefficient coding by Samsung
2- Second type of lag is when you try to start an App and you need to wait for a couple of seconds between the time you click on the App icon till the time you actually get a response (the App loads)
The above is inefficient coding by either Samsung or 3rd party App programmers. I DONT KNOW WHO
I believe that the first one could be solved, but there is no way in solving the second one as apparently the Android market does not enforce rules on 3rd pary programmers to make sure their apps are up to standard
On the other hand, i noticed that the second type of lagging was non-existant in Apple Store even for large applications/games because they enforce certain coding standards (as compared to Asphalt5 which is a big game and lags like hell when you want to load it)
Does what i am saying make sense, or is it that improving or patching the Samsung OS itself will solve all lagging problems for both the firmware and 3rd party Apps ????????????????
Apple has codingstandards that eliminates loading time? Thats impressive...
Sent from my GT-I9000 using XDA App
may I suggest contacting XDA user TKirton over on the Hero CDMA portal. He's written a fantastic implementation of Apps2sd which works across many platforms. He has great insight and knowledge of Android and linux filesystems and may be a good person to get on board with this.
What are the possibilities of using our 2gb of ddr program storage and re allocating it as system ram?
Even if it isn't pure flash (slow speed) I imagine it would be better then nothing, we could always store programs on the sdcard.
Sent from my GT-I9000 using XDA App
android53 said:
What are the possibilities of using our 2gb of ddr program storage and re allocating it as system ram?
Click to expand...
Click to collapse
very good, this post actually explains how to make a swap file (on /cache which is fast nand!).
if you want a swap partition you could a) use part of the 2gb /data partition for a new swap partition which you create in a project-voodoo like manner -> not very easy to do as you would have to repartition /data before boot OR b) just make a 2nd partition on your external sd card to swap on. a lot of people (me included) actually did this with their htc magic.
but to be honest i don't think that you will gain any speed improvements with this, on the contrary your system will be slower an more laggy... i found swap even worse on the magic with ~90mb of user-available-ram. if you want to try it nevertheless, it think the swap file on /cache would be a good start!
jodue said:
very good, this post actually explains how to make a swap file (on /cache which is fast nand!).
if you want a swap partition you could a) use part of the 2gb /data partition for a new swap partition which you create in a project-voodoo like manner -> not very easy to do as you would have to repartition /data before boot OR b) just make a 2nd partition on your external sd card to swap on. a lot of people (me included) actually did this with their htc magic.
but to be honest i don't think that you will gain any speed improvements with this, on the contrary your system will be slower an more laggy... i found swap even worse on the magic with ~90mb of user-available-ram. if you want to try it nevertheless, it think the swap file on /cache would be a good start!
Click to expand...
Click to collapse
If we go for b, will the sgs detect and use the swap partition or do we need to do something else.. I still use my htc magic along side my sgs
Sent from my GT-I9000 using XDA App
i have tried using a swap file, but i didnt c any improvements, and the usage was about 500kb only
I recall that on liquid we managed to use a ramzswap module, which fakes a zipped swap partition in ram. It causes cpu to work a bit more, but it was still efficient.
Elvoski said:
If we go for b, will the sgs detect and use the swap partition or do we need to do something else.. I still use my htc magic along side my sgs
Click to expand...
Click to collapse
you would have to repartition our external sd to have a second (linux swap) partition.
then use mkswap to set the partition up and after that call swapon. swapon has to be redone every time you restart but you could place it in a playlogos1 script to automate that.
captive said:
I recall that on liquid we managed to use a ramzswap module, which fakes a zipped swap partition in ram. It causes cpu to work a bit more, but it was still efficient.
Click to expand...
Click to collapse
compcache?! ... i guess this would also be a good trade off for our galaxy s because the cpu is definitely not the bottleneck here...
btw. a good read about swap & compcache from the cyanogenmod wiki: swap & compcache
android53 said:
What are the possibilities of using our 2gb of ddr program storage and re allocating it as system ram?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Bad, bery bad idea, MoviNand is not in any way releated to DDR. It's waaaay slower.
Also, RAM is designed for virtually unlimited data read/write counts.
NAND memory is not.
What would be the benefit of using swap space? Nothing. Data is being read/written in filesystem in the end. No improvement in performance. (It could be seriously degraded).
This behavior is totally against Android core design principles. Android doesnt use swap because it doesnt need to. Programs not fitting into "RAM" are being closed with their state remembered. When program is re-launched it is loaded from filesystem and its state is being restored.
If we had "swap" space, it would become really messy. Just imagine:
System wants to close program X, resident in swap, it needs to:
- restore program from swap to RAM (talk about additional ram needed)
- close program, resulting writing state to FS.
i was talking about this sort of thing with Ryza and Voodoo guy they said it was too much work
i'm forward with the idea of using a Swap drive in RAM or external SD
to prevent over usage on the internal SD
This means external SD would need to be powered up at all times -> battery drain (it is present with APPS2SD - or whatever this name was)
Wuld this mean that we would have extra ram available for running apps...like SGS task manager will show more than 311Mb RAM ?
If this is the case then I am very interestied, since I don't care about speed so much. I just need to run an app that currently can not run due to out-off-memmory (needs 130Mb of RAM) for pure presentation purposes
There is a app in market called swapper2 which can make use of the swap partition or creates a swap file for use. I had been using this app since my HTC MAGIC and now on SGS.
I'm currently using swap partition that had been created earlier in my class 6 SDCard. Works on both eclair or froyo kernels on SGS. So far I am not complaining, with swappiness 20, there is not much of memory hog or lag due to opening too many apps or single memory hogging apps (like flash on browser) on my XXJPK, the swap memory gets allocated and deallocated as you can tell from the swapper info feature.
But the battery effects is something to think about though, sdcards are cheap so I don't mind sacrificing it. The other way is to create a swap file on the rfs and use it if you value your sdcard. The screenshot provided is a normal usage of my device with a few apps running at background (Still gonna be 300+ RAM, nothing magical about it though) and I had also used minfree tweak on the kernel.
You can try and see if it helps in terms of performance for a few days. I cant vouch for the swapper a lot as I'm using it myself - I am more uncomfortable without it though. What Xan said does makes sense but there are rare times when the things that doesn't makes sense gives us surprises.
A good read up and comments from people who had tried and used it in different scenarios...
http://zerocredibility.wordpress.com/2009/08/24/why-android-swap-doesnt-make-sense/
Sent from my GT-I9000 using Tapatalk
I installed a single widget from Beautiful Widget yesterday and today I've had the launcher redraw itself multiple times and this is aomethig I've never seen before. How much free RAM should be available? I'm hovering around 120. Stock Nex HSPA running 4.0.1 on T-Mobile.
Sent from my Xoom using Tapatalk
I usually hover around 350mb free... 120 is seeming a little low. Are you exiting apps with the home button or the back button?
Sent from my GSM Galaxy Nexus
Either or, no preference either way.
Sent from my Xoom using Tapatalk
Are you stock?
Sent from my Xoom using Tapatalk
Often i stay around 120mb free ram so i think you are functioning normally.
Free ram is unused ram.
You only need as much free ram as the next, uncached task will require. On Android this is unlikely to ever be more than 80MB.
On this basis, if you have 120 free you should be fine.
djmcnz said:
Free ram is unused ram.
You only need as much free ram as the next, uncached task will require. On Android this is unlikely to ever be more than 80MB.
On this basis, if you have 120 free you should be fine.
Click to expand...
Click to collapse
Uh no. Free RAM consists of cached but not currently running apps and cached kernel resources. It is by no means "unused".
You also need a lot more free RAM than what the next app you are going to run requires, due to kernel caches and paging policy problems. If you are actually interested in learning how memory management works I suggest you read up on virtual memory first before giving others advice.
Chirality said:
Uh no. Free RAM consists of cached but not currently running apps. It is by no means "unused".
You also need a lot more free RAM than what the next app you are going to run requires, due to kernel caches and paging policy problems. If you are actually interested in learning how memory management works I suggest you read up on virtual memory first before giving others advice.
Click to expand...
Click to collapse
Don't be snide, it's unbecoming.
"Free" in the context that the OP used it is exactly that, free and unused - as in not used by anything at all, empty. Perhaps you might want to look that one up.
I responded to him in context and accurately. From an end user perspective it's a more helpful answer than a technical one about paging, caches and kernels...
I suggest downloading Cache Cleaner NG (yes, the "NG" one) from the Market if you're having lag or other problems. This will help no matter which definition of "free RAM" you choose to adopt I can say, though, that in my experience a lot of lag and force close issues have had more to do with cache and app data than with "free RAM." For example, on my Fascinate I'd have 120 MB or so of "free RAM" according to my system settings, but I'd still have major lag and more force closes than a chain of Circuit City stores until I cleared app cache using Cache Cleaner NG. This is different from wiping the cache partition in recovery.
Terminators run on Android
djmcnz said:
Don't be snide, it's unbecoming.
"Free" in the context that the OP used it is exactly that, free and unused - as in not used by anything at all, empty. Perhaps you might want to look that one up.
I responded to him in context and accurately. From an end user perspective it's a more helpful answer than a technical one about paging, caches and kernels...
Click to expand...
Click to collapse
Free in the context? There is no context needed here, as there is no ambiguity. Free here refers to exactly one thing: the amount of free memory reported by the Android system. The Android system uses a Linux kernel and reports free memory the way all Linux systems report free memory: all kernel and userland caches are reported as free memory. Free memory is not unused memory. Free memory is physical memory pages that are not currently marked in use by any virtual page entries. Free memory is used as cache by the virtual memory system. If you understand the virtual memory system at all you'd realize that truly "free and unused" memory doesn't even make sense in a virtual memory system. Truly unused memory is just cold cache, once the cache has been warmed up, the idea of unused memory becomes irrelevant.
Basically OP, you should never have to worry about it. This phone has more than enough RAM to handle anything you throw at it. If it ever feels "sluggish" just give it a reboot. No need chasing your tail to free up 15MB of RAM that won't make a difference anyways.
Thank you. This is what I figured as I've had quite a bit of experience with Android dating back to the G1 (it's why I don't have a task killer installed). Yeah, the lag is annoying although it's way better than my Xoom's. I was just wondering what you guys were hovering at.
I do have an app that turns itself on in my running apps list (it's ESPN's Fantasy Football app) I want to keep the app but it's sort of annoying seeing it pop up there all the time. Is there a way I can force it to stay off?
BlazinGTI said:
Thank you. This is what I figured as I've had quite a bit of experience with Android dating back to the G1 (it's why I don't have a task killer installed). Yeah, the lag is annoying although it's way better than my Xoom's. I was just wondering what you guys were hovering at.
I do have an app that turns itself on in my running apps list (it's ESPN's Fantasy Football app) I want to keep the app but it's sort of annoying seeing it pop up there all the time. Is there a way I can force it to stay off?
Click to expand...
Click to collapse
Do you have a widget running for this app? Any app that has a widget on the main screen will automatically run because of said widget.
I personally think thats REALLY low. I'm typically sitting over 400MB free with a couple widgets running and battery monitor in the background as well.
As of this moment I'm showing 367 free. Apps running: Angry birds RIO, Phone, Google Music (with music streaming currently), battery monitor, settings page.
4.0.1 is not memory efficient at all compared to 4.0.2&4.0.3. Not only are the newer builds more efficient with RAM but the size of the ROM on disk is much leaner.
After a reboot and once the dust was settled seems like I have 346 MB of free RAM, something you should try just to see how much you are starting with.
So I'm assuming you're on a build other than 4.0.1? I just tried a reboot and am sitting at 290MB free, I'll monitor it to see how long it takes to get back to the low 100's.
As for the Fantasy Football app, it does NOT have a widget. And apps that HAVE widgets, like Pandora, Evernote, Music, Docs, Soundhound, none of those show up in running OR cached apps.
Hello,
So I just recently got my Nexus, and I'm really really loving it. I had a question about the RAM. I'm on stock un-rooted and I noticed I had a little less that 700 MB ram. I know that's for system or gpu or whatever so I'm ok with that.
What I'm confused about is, I'm currently using 400 MB of it. If I combine the totals from the "Running Apps" section plus what is in the "Cached" section, it doesn't come close to the total 400MB being used.
So where is the extra Ram being used from? How can I free some of it up?
I've been reading that task managers are a no-no for ICS, so I'm more curious about which apps are killing my ram.
Thanks in advance
ellimistx99 said:
How can I free some of it up?
Click to expand...
Click to collapse
Why would you want to?
killing my ram.
Click to expand...
Click to collapse
Killing it how? Using it to make you phone react faster?
beren28 said:
Why would you want to?
Killing it how? Using it to make you phone react faster?
Click to expand...
Click to collapse
Well sure in theory make the phone run faster. I imagine having more free ram available to be used in the cached application section and not the "running application section" will help make apps load quicker too. My friend had a desire and the amount of ram she had did drastically effect her phone performance.
But also because I'm curious about where is that extra 200 or so MB of ram is being used from?
Linux shares ram within apps/processes in a very complex way where even the experts have difficulty explaining exact tallies on ram levels. This is why different apps report different free ram values like os monitor vs system panel vs stock settings etc. So i wouldnt wprry about how android OS shows your ram value in settings, its not gonna add up and its a tricky question to ask.
RogerPodacter said:
Linux shares ram within apps/processes in a very complex way where even the experts have difficulty explaining exact tallies on ram levels. This is why different apps report different free ram values like os monitor vs system panel vs stock settings etc. So i wouldnt wprry about how android OS shows your ram value in settings, its not gonna add up and its a tricky question to ask.
Click to expand...
Click to collapse
Hmm alright. So basically it's not something I should worry about? It's quite a large discrepancy. I guess I'll worry about it once I have errors that are "low ram" or something to that effect.
Thanks anyway
It's the discussion like there was in the galaxy s forum. The not displayed ram is used by the kernel it self and by the GPU. And besides it's a good thing to have a full ram in Android, because then many apps are pre loaded in the ram and can start faster this way.
Sent from my Galaxy Nexus using XDA
ellimistx99 said:
Hmm alright. So basically it's not something I should worry about? It's quite a large discrepancy. I guess I'll worry about it once I have errors that are "low ram" or something to that effect.
Thanks anyway
Click to expand...
Click to collapse
Its always been like this on my android phones, i wouldnt worry. For example if you kill all current apps, you wont see free ram increase at the exact level of the total of all closed apps. Too much overlap and ram page sharing i think.
Don't worry about it. Some ROMs e. the stock ROM, don't have a seperate RAMDisk.
So, basicly, the ROM dumps some cached processes on to the RAM directly "clogging" it. If you however, have a custom ROM, eg. CynagonMod, the system uses half of the RAM it would use as a stock ROM, because cm uses a RAMDisk, which uses a minimal amount of space, on the device's memory.
But, there's absolutley nothing to worry about
Enjoy the phone and leave the RAM, as it is
Can anyone here tell me how to partition my sd card to create 1 ext4 partition to increase internal memry, 1 simple fat partition for daily use, and most importantly gto create 1 swap partition to increase my RAM and how to use it as RAM in galaxy fit ... Plz provide me a tutorial
Sent from my GT-S5670 using XDA
abhinav2196 said:
Can anyone here tell me how to partition my sd card to create 1 ext4 partition to increase internal memry, 1 simple fat partition for daily use, and most importantly gto create 1 swap partition to increase my RAM and how to use it as RAM in galaxy fit ... Plz provide me a tutorial
Sent from my GT-S5670 using XDA
Click to expand...
Click to collapse
The Galaxy Nexus doesn't have an SDcard. You can't partition it up like that.
Also, think you're in the wrong forum.
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.