[Epic 4G Android Development] wonderhunt:
I am not familiar with unix command, so I can only attempt to show you what I learned from my experience. Based on OP's instruction, I put some notes in between in red, hope that helps:

-------------------------------------------------------------------------------

1 - do a clean install as on the OP.

2 - when phone boots up, do not install or restore any apps/data, follow OP's lagfix instruction right away. This keeps your phone's internal memory as large as possible to install that 300MB "swap" file.

lagfix from OP:

Instructions...

1. Go to the market and download "busybox installer".note that there is no "busybox installer", only "busybox", what it does is after you install "busybox", there will be a "busybox installer" under apps in your phone

2. Install busybox. (Yes, i know the ROM comes with it, but the ROM doesn't have one of the files the fix needs.)

3. Type these commands into windows command prompt.you need to turn usb debug on under setting->applications->development, and then plug in your phone to the PC.

PART 1

adb shell - type this in DOS windows prompt

su (at this point you will have to allow superuser on your phone, so look at your phone lol)

mv /system/bin/userinit.sh /system/bin/used

reboot

Allow the phone to reboot, then type this...

PART 2 - note that if any adb command fails below, you must delete all the files (dataimg, loop0) and exit ADB and start over. I did the dumb way - reinstall ROM and start from scratch, that works for me. In a word, the whole PART 2 must be completed in one ADB session (all commands entered in one succession), or it won't work. The only error that can be ignored is the "mkdir /dev/data1", all other command errors will need a way to clean start the PART 2, or re-installation of the ROM from scratch.

adb shell

su

busybox dd if=/dev/zero of=/data/dataimg bs=1024 count=300000- it takes about 1 minute to do this, so wait for the # to comes back before continue typing. You will see some status lines , make sure the last line says something indicating a file was created around 294MB and transfer rate xxMB/Sec. Sorry I can't remember the exact wording. if you don't see this last line, the command was not successfully executed, you might not have enough memory, and need to start all over

busybox mknod /dev/loop0 b 7 0 - here it is creating a file, if you get a dll not found message, it means busybox was not installed correctly, unplug your phone, re-install busybox, delete the dataimg file from step before using root explorer or re-install the ROM and start from scratch

busybox losetup /dev/loop0 /data/dataimg - dll not found = busybox not installed correctly. file or directory not found = you didn't run the whole PART 2 in one ADB session (id. you got an error, but contined, or you exited ADB and come back and entered command not from the start)

busybox mkfs.ext2 /dev/loop0 - same error might show up like the previous command

mkdir /data/data1 - you might get an unspecified error, mostly because /dev/data1 already exists, and can be ignored.

mv /system/bin/used /system/bin/userinit.sh - i don't think you can get an error here.

reboot

Again, all credit to the OP, I am just following the lead and it works for me.:)