Database Info

getting swapfile working on /data partition

Im trying out a theory. I running JAC Hero 2.3 and wanna try running the swapfile on the /data partition. I moved app_s over to /system/sd and used swapper app to create the swapfile but android doesnt seem to use it. when i run free It says Total/used/free are all 0 but the swap file is 34 meg. I tried putting it in a sub folder and chown root.root on the folder before setting up and still no luck. Anyone have any ideas why it wont work on /data or how to get it to work on /data?

Once you run swapper go into the setting and change the location of your swap file from /sdcard/swapfile.swp to /system/sd/swap.swp ( see sxfx post[url]

you don't want to do that. Swapping involves a lot of writing and erasing, it'll wear out your internal chip and you'll start experiencing reduced capacity, write cycles for nand are even less than for flash memory!

jubeh said:
you don't want to do that. Swapping involves a lot of writing and erasing, it'll wear out your internal chip and you'll start experiencing reduced capacity, write cycles for nand are even less than for flash memory!
Click to expand...
Click to collapse
not to mention, swapon as implemented (on every build i've tried) doesn't work on a swapfile stored on a yaffs2 partition

jubeh said:
you don't want to do that. Swapping involves a lot of writing and erasing, it'll wear out your internal chip and you'll start experiencing reduced capacity, write cycles for nand are even less than for flash memory!
Click to expand...
Click to collapse
Actually /sdcard/ is your fat32 portion of your sd card, /system/sd/ is the ext2/3 of your sd card.
Also I have done a bunch of research on this write/read fiasco just because of android.
And even if you set a swap file to your SD sure it will shorten your life of the card but it will still last you at least 2 years.
I have been using USB devices on linux as swap locations forever now and I still have thumb drives that have been used and abused for months and months as a swap place and they are still pulling strong.
As for the internal chip, Im not sure what you mean by that?

Even if you could put swap on the internal flash, its not going to be faster.
Putting swap on the internal flash will make things slower as the internal flash is about 3 to 5 times slower than a class 6 sdcard.

you're comparing using a flash drive for swap in a full blown computer that probably has around 1-4gb of ram, the swap file is hardly ever touched, unless you're running a lot of applications at a time. Dream has only 90 mb available to dalvik, and rosie is a big fat... lady... plus linux/dalvik manage memory in a different way, so files are often dropped to swap and they dont stay there for long (maybe in a 256 swap, but not in a 32 mb one).
the OP also is talking about moving his swap to his internal storage (chip, nand, whatever), as he thinks it's having no effect working from the sd card. Personally, i think that both a2sd and swapper are flawed. They're overcompensating for an os that was not meant to run on that device, and the real work should be in porting (as in developing, not just file-swapping as most "devs" do here) a launcher app that we can feel comfortable with running on a stock android system with stock (or slightly improved) libraries and that we can call comparable to rosie. Just look at ahome or dxtop or openhome, they're good, solid, great looking home replacements that work as well or better than rosie, but they run out of the stock libraries. I wonder why nobody has made a free, open source home replacement app yet

jubeh said:
you're comparing using a flash drive for swap in a full blown computer that probably has around 1-4gb of ram, the swap file is hardly ever touched, unless you're running a lot of applications at a time. Dream has only 90 mb available to dalvik, and rosie is a big fat... lady... plus linux/dalvik manage memory in a different way, so files are often dropped to swap and they dont stay there for long (maybe in a 256 swap, but not in a 32 mb one).
the OP also is talking about moving his swap to his internal storage (chip, nand, whatever), as he thinks it's having no effect working from the sd card. Personally, i think that both a2sd and swapper are flawed. They're overcompensating for an os that was not meant to run on that device, and the real work should be in porting (as in developing, not just file-swapping as most "devs" do here) a launcher app that we can feel comfortable with running on a stock android system with stock (or slightly improved) libraries and that we can call comparable to rosie. Just look at ahome or dxtop or openhome, they're good, solid, great looking home replacements that work as well or better than rosie, but they run out of the stock libraries. I wonder why nobody has made a free, open source home replacement app yet
Click to expand...
Click to collapse
You make a very good point about computer having 1-4gigs of ram and not needing a swap file.
Honestly I almost never run a swap file on a computer that has more then 1gig of ram.
Plus90% of the time when I do run a swap file is when Im running a live distro of linux of a cd, but also 90% of the time I run the distro from the flash drive instead of cd cause its much faster.
So now imagine how many reads/writes I abuse that flash drive with by running a full OS on it.
Also I don't understand how a2sd or swapper is flawed? Just because they do their job? I mean it's not really our fault that they made the G1 with a little less memory spaces then we would like it to have.
But that's exactly why we have tools like swapper and a2sd. Plus no one is really forced to run these roms on the G1 phone and those of us that do realize that we have to take extra steps in creating tools to help it.
And that's not only true for the G1 but anywhere in the computer world these days.

dwang said:
Even if you could put swap on the internal flash, its not going to be faster.
Putting swap on the internal flash will make things slower as the internal flash is about 3 to 5 times slower than a class 6 sdcard.
Click to expand...
Click to collapse
I'd like to spread swap over the sd and internal storage if possible -- should make paging a lot less evident if priorities are set up properly.

dwang said:
Even if you could put swap on the internal flash, its not going to be faster.
Putting swap on the internal flash will make things slower as the internal flash is about 3 to 5 times slower than a class 6 sdcard.
Click to expand...
Click to collapse
internal memory is faster. class 6 guarantees 6mbs read/write times but doesnt mean the bus can support those times. if you run a test copying something to /system/sd and to /data you will see /data is faster. as for those saying it will degrade the internal memory, that is not the case being the flash memory inside is designed to have much much much more read/write cycles. Think about it in a stock G1, this is where dalvik-cache is writen to as well as email, sms, user settings, cache for browser and uTube. Do not confuse internal flash memory to sd card flash memory

Are you sure about that? This guy has some test results and it indicates that a class 6 sdcard is much faster than the internal flash.
http://forum.xda-developers.com/showpost.php?p=4059520&postcount=15
MonkySlap said:
internal memory is faster. class 6 guarantees 6mbs read/write times but doesnt mean the bus can support those times. if you run a test copying something to /system/sd and to /data you will see /data is faster. as for those saying it will degrade the internal memory, that is not the case being the flash memory inside is designed to have much much much more read/write cycles. Think about it in a stock G1, this is where dalvik-cache is writen to as well as email, sms, user settings, cache for browser and uTube. Do not confuse internal flash memory to sd card flash memory
Click to expand...
Click to collapse

dwang said:
Are you sure about that? This guy has some test results and it indicates that a class 6 sdcard is much faster than the internal flash.
http://forum.xda-developers.com/showpost.php?p=4059520&postcount=15
Click to expand...
Click to collapse
That's interesting. Going to have to try that test out. I just noticed when xfering stuff to /data it was faster then to /system/sd. If it is then touche my friend.....touche

Need some help/clarification CM 4.2.3.1 + linux swap

Still new at this and searching hasn't really helped me understand whats really going on as well...
I have MT3G, CM 4.2.3.1, 8GB SD (7437MB Fat32, 500MB EXT3, 32MB Linux swap)
So here are my questions:
1) Is CM 4.2.3.1 have linux swap automatically enabled, or will i need to enable it?
2) If not enabled automatically, how do i enable it?
3) Does the CM 4.2.3.1 run better with linux swap on the MT3G or the same?
Just trying to utilize my MT3G to its MAX potential with the CM firmware! Please enlighten me. I tried searching, but being a newb to linux, i am just getting more confused.
Thanks for helping!

mautai916 said:
Still new at this and searching hasn't really helped me understand whats really going on as well...
I have MT3G, CM 4.2.3.1, 8GB SD (7437MB Fat32, 500MB EXT3, 32MB Linux swap)
So here are my questions:
1) Is CM 4.2.3.1 have linux swap automatically enabled, or will i need to enable it?
2) If not enabled automatically, how do i enable it?
3) Does the CM 4.2.3.1 run better with linux swap on the MT3G or the same?
Just trying to utilize my MT3G to its MAX potential with the CM firmware! Please enlighten me. I tried searching, but being a newb to linux, i am just getting more confused.
Thanks for helping!
Click to expand...
Click to collapse
It doesn't have linux swap enabled, but I recommend that you just leave it alone. Cyanogen's is the fastest ROM out there compared to other stock roms and he absolutely murders Hero in terms of speed. Though he does not have linux swap, or compcache anymore, he still has the CPU overclocked to 528. The phone will probably run the same with or without linux swap. That is really only needed if you are running a Hero ROM.
Oh, and you should probably post this in the general forums, or in the Q&A of the Dream. I'm sure you would get more answers there anyways.

outside of hero, the main use for Linux-swap was to keep your homescreen from having to constantly be refreshed. It was a huge annoyance in earlier CM builds when you didnt have CC enabled.
With the "keep homescreen in memory" spare parts toggle, I havent seen a refresh since 4.2.3.1 came out... well thats not true, but its rare enough that it never ruins the user experience for me.

tazz9690 said:
Oh, and you should probably post this in the general forums, or in the Q&A of the Dream. I'm sure you would get more answers there anyways.
Click to expand...
Click to collapse
You say that, but hardly anything gets answered in the general forum!

The_Chrome_Coyote said:
outside of hero, the main use for Linux-swap was to keep your homescreen from having to constantly be refreshed. It was a huge annoyance in earlier CM builds when you didnt have CC enabled.
With the "keep homescreen in memory" spare parts toggle, I havent seen a refresh since 4.2.3.1 came out... well thats not true, but its rare enough that it never ruins the user experience for me.
Click to expand...
Click to collapse
If i used "keep homescreen in memory" spare sparts toggle, am i utilizing the linux swap just because i have the partition or should and HOW do i enable it on CM 4.2.3.1?
Boonyard said:
You say that, but hardly anything gets answered in the general forum!
Click to expand...
Click to collapse
haha ya thats very true
So any insight guys?
Does CM 4.2.3.1 run better WITH linux swap or no? Just trying to figure out if it will help the firmware run better. If so, is it automatically enabled just because i have a 32mb linux swap partition or should and HOW do i enable it manually?
I guess my point is that i dun wanna go thru the hassle of linux swap when CM doesn't need it

mautai916 said:
If i used "keep homescreen in memory" spare sparts toggle, am i utilizing the linux swap just because i have the partition or should and HOW do i enable it on CM 4.2.3.1?
haha ya thats very true
So any insight guys?
Does CM 4.2.3.1 run better WITH linux swap or no? Just trying to figure out if it will help the firmware run better. If so, is it automatically enabled just because i have a 32mb linux swap partition or should and HOW do i enable it manually?
I guess my point is that i dun wanna go thru the hassle of linux swap when CM doesn't need it
Click to expand...
Click to collapse
just download swapper for root users and you will have linux swap. tada. No hassle there and it takes only seconds to do. From there you can make the decision for yourself.
You could go the hard way and pull the user.conf and edit it, then repush it to the phone and reboot. That just seems like a lot of work to me. Swapper is a much faster alternative.

Help setting up userinit.sh & user.conf for "Backing Swap" on CyanogenMod

Help setting up userinit.sh & user.conf for "Backing Swap" on CyanogenMod
I am trying to set up Backing swap, which combines Compcache and traditional swap, on the phone/rom in my sig. I have been unable to do so for two main reasons.
1. I used Amon RAs recovery to make the partitions so I'm not sure what order they are in (need to know so I can put the right partition # in the useritit.sh file).
2. I am unsure how to create these files once I have all the proper info to plug into them, or where to acquire a base-line version of these files to edit.
I have been looking for hours but only seem to find posts of people suggesting I use these files. Even the Q&A wiki doesn't contain anything on the subject either (unless I was entering the wrong search critiria). I only have the terminal on my phone to work with or my pc which is win XP 64bit, so if I need any 3rd software please provide the windows flavor.
TIA everyone,
~psguardian

You can have one or the other one not both.
Swap always slows down the phone after a couple of hours and compache is compressed into the ram.If you want a fast rom use Super-D or Wesgarner.

Ace42 said:
You can have one or the other one not both.
Swap always slows down the phone after a couple of hours and compache is compressed into the ram.If you want a fast rom use Super-D or Wesgarner.
Click to expand...
Click to collapse
According to the Cyanogenmod wiki it does work with both (atleast you can back a shrunk compcache with the swap partition), I just don't want to try putting the file together until I can cipher out which part. # my swap partition is, as this may turn my ext3 partition into a 512mb swap partition & I don't want that.
~psguardian

Think i was thinking about backswap..thats not important though.
Swap partition is Block3
EXT is block 2

Ace42 said:
Think i was thinking about backswap..thats not important though.
Swap partition is Block3
EXT is block 2
Click to expand...
Click to collapse
I can see how backswap & standard swap wouldn't work together because they will try to use the same space. Is the linuxswap partition always mounted as Block3 ? when going through the format process in Amon RA recovery fat 32 is the last partition defined, which is why I hesitated to use the example given on the wiki (since back when that was put together partitioning was all manually handled).
~psguardian

still not smooth
I managed to get user.conf maker app on the market but it doesn't work properly in 4.2.13 (it sets the files up with its own defaults, but never accepts user input for value changes).
Had to
cp /system/sd/userinit.sh /sdcard/userinitsh.txt &
cp /system/sd/user.conf /sdcard/userconf.txt
so that I could use a 'notepad' type app to edit them propperly & then push them back to /system/sd now my phone is lagging worse then before so I'm not sure what I've done wrong... for backingswap am I suppose to enable compcache AND backingswap or just backingswap? I think its option A because that is the only time my swap partition shows active under 'free' command.
So now a new set of questions.
How much RAM is good to allocate to compcache
How large a swap partition should be used
What swappiness level is good for my setup
I know these answer are subject to the situation on my phone so let me give some stats, I am running a theme w/advanced launcher (5 screens) 10 widgets & 3 background apps that update every 15-30min (1 of them is a craigslist scanner that pulls search data from 10-15 regions so it probly should count as 3 by itself) so lets say 15ish self-updating apps.
Please any constructive input is very very welcome
Thanks In Advance Q&A guys-n-gals
~psguardian

Swap on Cyanogen 5.0.7 test1 - Thoughts!

Hey,
So Ive been playing with CM-5.0.7-DS test1, like everyone im sure , however I am noticing some major slowdown in the Launcher, many apps, and especially in 3g gallery without some memory assistance such as Swap\CC for the "low-memory" devices like the G1\Dream.
I enabled a 96mb swap partition, swappiness 60 using a userinit.sh script (see attached), and it really helped speed things along.
Wanted to know everyone else's experience using swap on this crazy new upgrade to our 2-yr old device

Good call. You can also just install "Swapper" from market, and go to advanced preferences, enable partition, good to go.
I am using a 96mb swap partition, and am overclocked to 596 mhz with the replacement kernel. Everything is working brilliantly for me, very stable.
Android 2.1, 600mhz Android device, ample RAM via swap, 16gb card, new slim extended battery - I am once again a happy G1 owner!

kristoff123 said:
Good call. You can also just install "Swapper" from market, and go to advanced preferences, enable partition, good to go.
I am using a 96mb swap partition, and am overclocked to 596 mhz with the replacement kernel. Everything is working brilliantly for me, very stable.
Android 2.1, 600mhz Android device, ample RAM via swap, 16gb card, new slim extended battery - I am once again a happy G1 owner!
Click to expand...
Click to collapse
:O howd u overclock to 596mhz?!

chim4ira312 said:
:O howd u overclock to 596mhz?!
Click to expand...
Click to collapse
The overclock thread that's been sitting on the top of this forum for the last week :0
the kernel I used is on page 38 or 39...anything over 600 eventually crashes for me, but 596 works very well. Flash video even plays fine with Skyfire - so many new goodies for my beloved G1!
-Although I am sure cyanogen will include that kernel or a better one with the next release, but leave it to the user to overclock using setcpu or whatever. Just leave it at 528 default via userinit.sh, so people can choose to what degree they want to melt their G1's, lol.

kristoff123 said:
Good call. You can also just install "Swapper" from market, and go to advanced preferences, enable partition, good to go.
I am using a 96mb swap partition, and am overclocked to 596 mhz with the replacement kernel. Everything is working brilliantly for me, very stable.
Android 2.1, 600mhz Android device, ample RAM via swap, 16gb card, new slim extended battery - I am once again a happy G1 owner!
Click to expand...
Click to collapse
hello
link please

lefeudedieu said:
hello
link please
Click to expand...
Click to collapse
Here, searched my ass off to find it...your welcome
http://forum.xda-developers.com/showpost.php?p=6352322&postcount=402

ok, thank
but i put the image boot by fastboot and G1 reboot and reboot ?

In my personal experiences with swap..... I'm not exactly sure what it was supposed to do after I applied it.
I do know what it does though...
As stated in previous forums,
The longevity og my card is very important to me
And finally, Cyanogen advises against swap.
if you would like to learn his thoughts, read his wiki.
And op, you crack me up. +10!
Sent from my HTC Dream using the XDA mobile application powered by Tapatalk

lefeudedieu said:
ok, thank
but i put the image boot by fastboot and G1 reboot and reboot ?
Click to expand...
Click to collapse
i think its not a image that can be flashed. it should be paste to /sd-ext document.

u need to extract the userinit.sh script and put it in /sd-ext

zimphishmonger said:
u need to extract the userinit.sh script and put it in /sd-ext
Click to expand...
Click to collapse
and thats it??

zimphishmonger said:
u need to extract the userinit.sh script and put it in /sd-ext
Click to expand...
Click to collapse
This conversation is confusing. 2 people talking about swap and 2 trying to overclock. Use the zip file from this thread, unzip it, open it with gedit or notepad++, add the stuff in the link from @zimphishmonger talking about overclocking. Follow the stepsw in that post. If you fastbooted the boot.img and it just boot loops, you may have trouble. You may need to reflash cm5.0.7. Or reinstall the Nandroid backup you made before you flashed it.
Also if history tells us anything, Cy will never include any over clock hack. He is pretty conservitive along those lines.

dangambino said:
and thats it??
Click to expand...
Click to collapse
Not exactly
do
adb shell chmod 755 /sd-ext/userinit.sh
to give it permissions.
My userinit.sh looks a little different so I can't say for sure it is correct.
...You mileage may vary.

thanks. running command now
seems to of took!

Swap is not a good feature to use, and I'll explain why:
When you enable swap, your end result is that you have a lot more "memory" available for programs to run in. Because of the memory management scheme used by android (kill background processes on low memory), it ends up that you will be RUNNING MORE PROCESSES. And this is a bad thing because (1) it means that your CPU will be more loaded (multitasking/background processes), and (2) it means that it will end up doing a lot of swapping (sdcard is SLOW) in order to continue providing all the "memory" allocated to each of those running programs.
The end result is that your phone will become VERY SLOW.
The ONLY legitimate use for swap is when you are running a process that is SO LARGE that it can't physically fit in the RAM available on the device *even when* all killable processes are already dead. And on Android, I have yet to encounter such a program.
DON'T USE SWAP! It will accomplish precisely TWO things;
(1) it will make your phone SLOW.
(2) it will kill your SDCARD.

lbcoder said:
DON'T USE SWAP! It will accomplish precisely TWO things;
(1) it will make your phone SLOW.
(2) it will kill your SDCARD.
Click to expand...
Click to collapse
(1) I disagree, it's the opposite ;-)
(2) agreed, but it probably will last enough till my next phone...

Most class 6 cards feature wear levelling from which from what I understand means I'll have upgraded my phone way before it ever dies.
For me using CM without swap has been impossible for quite a while now, gmail sync just doesn't work properly without the extra memory to fall back on. As for it slowing the phone down I've never noticed anything ever being slower with swap although I do have a class 6 card.

deimdos said:
(1) I disagree, it's the opposite ;-)
(2) agreed, but it probably will last enough till my next phone...
Click to expand...
Click to collapse
+1 I disagree as well.
If anything it helps the phone operate normally. Especially with the G1 it has a tendency to push GTalk out of the memory. That means it stops pushing email notifications to your phone, which is really annoying. Even eBuddy has a hard time staying in the memory if you minimize it. The G1 one really benefits from having the swap. And really, are SD cards that expensive? I've had swap on for 8 months and my SD card is fine. I personally use 64MB on my G1 and 30 swappiness, anymore is excessive.
Really you only want enough memory that it holds all the essential apps in place. Autokiller helps too if set at Moderate. So far CM5 though, the battery life is phenomenal compared to the old 4.2.15 (especially after the battery wipe stats fix, if you're having battery drain issues).
If you're using this on the Magic, then I have an issue with that, since it isn't even needed. Unless you have like over 300MB worth of apps and cache. Then maybe you'll need an ext partition. But that's a separate issue.

lbcoder said:
Swap is not a good feature to use, and I'll explain why:
When you enable swap, your end result is that you have a lot more "memory" available for programs to run in. Because of the memory management scheme used by android (kill background processes on low memory), it ends up that you will be RUNNING MORE PROCESSES. And this is a bad thing because (1) it means that your CPU will be more loaded (multitasking/background processes), and (2) it means that it will end up doing a lot of swapping (sdcard is SLOW) in order to continue providing all the "memory" allocated to each of those running programs.
The end result is that your phone will become VERY SLOW.
The ONLY legitimate use for swap is when you are running a process that is SO LARGE that it can't physically fit in the RAM available on the device *even when* all killable processes are already dead. And on Android, I have yet to encounter such a program.
DON'T USE SWAP! It will accomplish precisely TWO things;
(1) it will make your phone SLOW.
(2) it will kill your SDCARD.
Click to expand...
Click to collapse
Check out autokiller in the market. It limits the running processes so that swap actually works.

For those uncomfortable with making a userinit script, as I said before, Swapper does the same thing, it's free, and it's not a program that runs in memory. With the benefit being that you can experiment with swappiness and other settings on the fly. Just go to "Advanced" and select your partition - it's the right location by default.

RyanZa's one click lag fix

Hi,
I was browsing the dev forum for the lag fix and I was wondering if anyone had any first hand experience using it on the Epic? I searched and didn't find anything substantial in this forum.
Thanks,

Tonythetigger said:
Hi,
I was browsing the dev forum for the lag fix and I was wondering if anyone had any first hand experience using it on the Epic? I searched and didn't find anything substantial in this forum.
Thanks,
Click to expand...
Click to collapse
It's not needed. Have you seen your Epic lag? If so, return it.

Well, it lags a little when I try to open barcode reader or the camera? I thought there was discussion on how the Epic would still receive a benefit from the lagfix..

Actually you can pretty easily make it lag. Take two pictures at full res and then go through gallery and attah them to gmail. Send. If you are not on wifi the phone litterally is paralyzed until its finished.
Those chose pooly on the formating

So has anyone used the lagfix?

I believe or partitions are different. That would most likely brick your device if used. I'm fqairly certain we could do the same for our devices but that's going to take time. Working recovery > that atm.

Aridon said:
Actually you can pretty easily make it lag. Take two pictures at full res and then go through gallery and attah them to gmail. Send. If you are not on wifi the phone litterally is paralyzed until its finished.
Those chose pooly on the formating
Click to expand...
Click to collapse
Well thats not fix with a LagFix. Thats a bug. It happens attaching it to anything. MMS, Gmail, Email, Facebook. Its a known bug.

Well my quadrant benchmark is 1k, shouldn't it be capable of going up to 2k?

I believe the lagfix will actually work, and may even help. I don't have an epic, so I can't test it at all.
Anyway, the I9000 has 8gb or 16gb internal memory. 2gb of that is dedicated to /data (data is where all your apps and their data go).
The epic has 2gb? 1gb? -- some amount of fast internal memory dedicated to /data.
Both the I9000 and your epic use the RFS filesystem, which appears to be very poor.
What the OCLF apk does is make a loopback EXT2 partition in your RFS filesystem, and then uses symlinks to make android put the apps/data inside the EXT2 partition. This should work fine on your epic, especially if you have 2gb of program memory! If you have less than 1gb it may be a problem though.
Feel free to try it out if you have rooted your device! (The I9000 root won't work on the Epic)

RyanZA said:
I believe the lagfix will actually work, and may even help. I don't have an epic, so I can't test it at all.
Anyway, the I9000 has 8gb or 16gb internal memory. 2gb of that is dedicated to /data (data is where all your apps and their data go).
The epic has 2gb? 1gb? -- some amount of fast internal memory dedicated to /data.
Both the I9000 and your epic use the RFS filesystem, which appears to be very poor.
What the OCLF apk does is make a loopback EXT2 partition in your RFS filesystem, and then uses symlinks to make android put the apps/data inside the EXT2 partition. This should work fine on your epic, especially if you have 2gb of program memory! If you have less than 1gb it may be a problem though.
Feel free to try it out if you have rooted your device! (The I9000 root won't work on the Epic)
Click to expand...
Click to collapse
Its 1Gb. But its not completely empty.
Also, I'm willing to test it. Do you have a link for the download?

Well the Epic has 512 ram and 512 rom, Froyo is supposed to allow the phone to use the SD card as install room for apps.
Would the lagfix run there?
Here is the link to the app: http://forum.xda-developers.com/showthread.php?t=760571

Fixter said:
Its 1Gb. But its not completely empty.
Also, I'm willing to test it. Do you have a link for the download?
Click to expand...
Click to collapse
It's on the market.
http://www.appbrain.com/app/com.rc.QuickFixLagFix
1GB... and yeah its obviously not empty, it has all your stuff in it!
Anyway with 1GB is might be a bit tight, as that would leave only 500mb or so for apps.
Make a backup before you test it though, since I think you're the first person to test it on the Epic. It should refuse to run if there is anything wrong though.

So if the phone can use the SD card for /data would the fix have more space there? Or would we just get more space to install and run apps

RyanZA said:
It's on the market.
http://www.appbrain.com/app/com.rc.QuickFixLagFix
1GB... and yeah its obviously not empty, it has all your stuff in it!
Anyway with 1GB is might be a bit tight, as that would leave only 500mb or so for apps.
Make a backup before you test it though, since I think you're the first person to test it on the Epic. It should refuse to run if there is anything wrong though.
Click to expand...
Click to collapse
It says Unavailable.

Tonythetigger said:
Well the Epic has 512 ram and 512 rom, Froyo is supposed to allow the phone to use the SD card as install room for apps.
Would the lagfix run there?
Here is the link to the app: http://forum.xda-developers.com/showthread.php?t=760571
Click to expand...
Click to collapse
512MB is going to be too little.
You can actually get around this with a fast SD card though! If you know how to use gparted, you can make a 2GB or so EXT2/3 partition on your SD card, and then copy your data across to that, and use symlinks to point Android there. With the Epics fast NAND though, this shouldn't be necessary for speed - but it might be really nice for you guys if you want to install a lot of apps!
EDIT: You can follow mimocan's tutorial here: http://forum.xda-developers.com/showthread.php?t=724251
Just don't use EXT4 since your kernel won't support it. There is a way to dynamically load the EXT4 kernel module though, if anybody is interested.

RyanZA said:
512MB is going to be too little.
You can actually get around this with a fast SD card though! If you know how to use gparted, you can make a 2GB or so EXT2/3 partition on your SD card, and then copy your data across to that, and use symlinks to point Android there. With the Epics fast NAND though, this shouldn't be necessary for speed - but it might be really nice for you guys if you want to install a lot of apps!
Click to expand...
Click to collapse
Thats weird.. On the Samsung Specsheet is says 1Gb. I saw it not 30 minutes ago.
EDIT: User Memory 1GB (not all is usable for customer use/downloads)

DAMN IT! I'm sure Touchwiz is using the other 500Mb.

Here's a link to the dev page, you can download the app directly from there: http://forum.xda-developers.com/showthread.php?t=760571

lag fix?
SDcard-using lag fix is obviously unnecessary for Epic 4G.
The reason why Epic has a small NAND chip is that it uses a different type of NAND, called "OneNAND." OneNAND is much much faster than normal NAND or moviNAND (which other Galaxy S's use).
This is why Epic users don't experience "lag" which exists in Vibrant or Captivate.
But we can still make Epic faster, by getting rid of Samsung's rfs file system (which obviously makes Vibrant/Captivate slower) and mounting ext3/4 or other faster file system.
Then we need:
1) patching kernel or adding module to support ext3/4/nilfs2/yaffs2/ubifs/btrfs/etc/whatever we want.
(ext2 is supported by the stock kernel I think. However, unlike SD card and moviNAND which have own hardware wear-leveling algorithms in their controllers, OneNAND does not has it, so I'm not sure if ext2 (which does not support journaling/log) is okay to use.)
2) backing up the partitions which we want to change the file system from rfs
(such as: /data/data, /data/app, /data/dalvik-cache, etc, whatever)
and finally formatting it to what we want, and mount it.
3) kernel or script that automatically mounts as the file system we want.
4) a genius who can do this. (It is obviously not me.)
This is done for Captivate in XDA forum, and also for Galaxy S M110S in a Korean forum.

chocoberry said:
SDcard-using lag fix is obviously unnecessary for Epic 4G.
The reason why Epic has a small NAND chip is that it uses a different type of NAND, called "OneNAND." OneNAND is much much faster than normal NAND or moviNAND (which other Galaxy S's use).
This is why Epic users don't experience "lag" which exists in Vibrant or Captivate.
But we can still make Epic faster, by getting rid of Samsung's rfs file system (which obviously makes Vibrant/Captivate slower) and mounting ext3/4 or other faster file system.
Then we need:
1) patching kernel or adding module to support ext3/4/nilfs2/yaffs2/ubifs/btrfs/etc/whatever we want.
(ext2 is supported by the stock kernel I think. However, unlike SD card and moviNAND which have own hardware wear-leveling algorithms in their controllers, OneNAND does not has it, so I'm not sure if ext2 (which does not support journaling/log) is okay to use.)
2) backing up the partitions which we want to change the file system from rfs
(such as: /data/data, /data/app, /data/dalvik-cache, etc, whatever)
and finally formatting it to what we want, and mount it.
3) kernel or script that automatically mounts as the file system we want.
4) a genius who can do this. (It is obviously not me.)
This is done for Captivate in XDA forum, and also for Galaxy S M110S in a Korean forum.
Click to expand...
Click to collapse
Thank you for the explanation. Now lets wait for the genius.