yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] novaIS350:
I was just about to post the same thing. The unlagfixme.bat should be all you need.
[Captivate Android Development] iamamp3pimp:
looking at going back to a clean slate, just going to mess with some things in the phone and see what happens.
[Captivate Android Development] IStern:
Ran the nand fix for a few weeks, just tried this one. *Noticeable* real life usage improvements. So far no stability issues...have nandroid backups just in case.
[Captivate Android Development] gr4v3r:
mmmmmmmm 2182 score, ty so much
[Captivate Android Development] gotfolk:
I guess no one else has ran into the weird phone hiccups that i had.

(not getting sms untill reboot) & (losing signal and having to reboot to get it back)

I will say that uninstall.bat worked flawlessly!! I really did enjoy this fix on my phone, but i am going to give the community more time to release a more stable fix, rather it be this way or one of the other ones people are working on.

I just want to thank everyone that has worked on this fix and Im on here all day looking for more updates. This is by far the best community i have ever been a part of.
[Captivate Android Development] gotfolk:
when i did have this fix running my quad score hit a best of 2255 :)

stock captivate rom, no OC hack
[Captivate Android Development] Zilch25:
Funny you should mention a more stable method:

RyanZA just posted a new thread in the I9000 about a 2.0 release

http://xdaforums.com/showthread.php?t=751864

Apparently this adds:

1.7GB of application data available, with no data loss.

e2fsck of the EXT2 partition on each boot.

Correct busybox version included! YES!

/app directory included in the fix for faster application installs.

Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).

e2fsck is the part that should be exciting, as it adds a disk check on startup to scan for corrupted data.

I'm flashing my phone back to stock, I'll report back whether or not this is functioning as advertised.
[Captivate Android Development] kennethpenn:
I know Quadrant is useless, but v2.0 + 1.2 GHz overclock + JH2 firmware = ~2800 quadrant?

Wow...
[Captivate Android Development] Zilch25:
OP Updated for 2.0 goodness!
[Captivate Android Development] kennethpenn:
I would take down v2.0. Severely messed up phone here. Wait till he irons out some bugs.
[Captivate Android Development] Zilch25:
I'm fighting with it myself ATM, just rewrote a few lines of his creatlagfix.sh to hopefully fix the low space issues, but it does seem like this has some severe crapups when you've had a previous lagfix installed.
[Captivate Android Development] kennethpenn:
Zilch - your modified createlagfix.txt did the trick.

Works on stock JH2 + Zilch-modified 2.0 lag fix. :)
[Captivate Android Development] Zilch25:
Very glad to hear it, but really I just modified some lines in RyanZA's code, he totally deserves the credit haha.

When the batch file ended for you did the window hang at the step for clearing the linux.ex2 file for you? It did for me, but I figured it was just due to all the times I've applied/removed the fix.

Also check your internal SD and see if theres a linux.ex2 file eating up 1.5 gigs... if so you can safely delete it :)
[Captivate Android Development] kennethpenn:
I don't see a linux.ex2 file. Is it in root directory?

No hangs on install for me...
[Captivate Android Development] Zilch25:
Okay good, the script completed for you then. The last time I ran it it hungup on the housecleaning step (removing linux.ex2) from the SDcard. Just wanted to make sure it was just me :)
[Captivate Android Development] sdimezq8:
Just incase anyone is curious; The 'unlagfixme' script works perfect. I had ZERO issues with this 'fix' installing, using the phone with the new filesystem and uninstalling it. (version 1.0) This is my opinion; there is an over all performance gain to this I am just unsure how great the gain is. I need to use it more both ways... This is my reason for uninstalling... I believe I will be reinstall shortly.
[Captivate Android Development] IStern:
Ran into the space issue after uninstalling 1.0 and installing 2.0. Attempting to uninstall 2.0 resulted in a series of cp failures due to lack of space and a near-brick, thank god for clockwork...
[Captivate Android Development] Zilch25:
Use the file that I attached to the OP instead of the createlagfix.txt file included in the original script, it'll fix the space issues with Captivate firmwares
[Captivate Android Development] joeybear23:
downloaded and renamed to createlagfix.sh

this is correct, right?

about to run it on my newly JH2'ed and UTB'ed phone.
[Captivate Android Development] Zilch25:
No, it has to be createlagfix.txt, the bat file renames it when it moves it, so you've got to keep it as a .txt when it's on your PC
[Captivate Android Development] joeybear23:
Interesting... I never used a bat file on the first one, I did the phone-only option...
[Captivate Android Development] Zilch25:
This one is A LOT more complicated haha
[Captivate Android Development] joeybear23:
Okay, got it done... but now I am getting that low storage message...
[Captivate Android Development] IStern:
There is a problem with version 2.X's undo script, especially if you're trying to undo after seeing the free space error. I think it's probably the rm failing on /data/linux.ex2.

Make sure you have a working backup and clockwork's update.zip is set up in /sdcard before you try to undo.
[Captivate Android Development] Zilch25:
Are you sure you used my .txt when you ran it? The one that comes in the zip file will 100% give you the out of space message. Also what version of the firmware are you running?
[Captivate Android Development] joeybear23:
Running JH2 and put the .txt file downloaded from post 1 into the bat file's directory. I can always do it again to make sure...

What size ext2 partition is the fix supposed to create?

The old phone-only one I did only used 1 GB, this one did 1.6 GB...
[Captivate Android Development] Zilch25:
Hmm well 1.6 is correct, try the one attached to the other post, it should create a 1.5 and give you a bigger margin.
[Captivate Android Development] IStern:
anything wrong with going with just the old 1.0GB? More than enough space it seems, and leave enough room for the remove script even if the rm fails on linux.ex2
[Captivate Android Development] Zilch25:
Nope, nothing wrong with that, the thing is that this script adds in some stuff to test the integrity, and hauls in the apps folder as well to speed things up a bit more.

I could edit the createlagfix for a 1gig if you were interested in that
[Captivate Android Development] joeybear23:
if you do it I would be happy to test it out for you and let you know how it does...

BTW, thanks for all the time you have spent on this.
[Captivate Android Development] Zilch25:
The last post had the 1.5gb, attached to this one is the 1gig!

I'm kinda puzzled why it works on mine but not on yours though... we're running the same device on the same firmware... really strange.

If you could, could you tell me how much free space you have on your phone after you remove the fix?
[Captivate Android Development] joeybear23:
I have about 50 apps installed... perhaps that's it.

Trying the 1GB option now.
[Captivate Android Development] Zilch25:
I wonder if this might have something to do with paid apps. Someone in the I9000 thread mentioned that RyanZA didn't migrate the apps-private folder into this fix (something I'm sure will be rectified once he reads the thread in the morning). Assuming you have paid apps in there, perhaps the fact that they're still occupying space on the NAND and not being moved to the virtual FS is enough to bloat things up to make the image file fill the NAND to the point where it gripes about low space.
[Captivate Android Development] joeybear23:
Okay, the 1GB option is installed and the system is showing me with 786 MB free on phone storage.

Cool, I will play around with it and see how it does.

THANKS!!!
[Captivate Android Development] joeybear23:
I only have a few Paid apps, like Battery Indicator Pro, Titanium Backup, and Robo Defense Full...

:think:

I don't know.
[Captivate Android Development] Zilch25:
Weird, well I'm sure RyanZA will come up with something tomorrow, he's been a fiend working on this. Now that you're sorted out I'm going to get some sleep! haha I'm sure I'll be poking around with this a bit first thing in the morning though as well.
[Captivate Android Development] IStern:
there we go, thanks zilch!
[Captivate Android Development] joeybear23:
Again, thank you so much!!
[Captivate Android Development] washow:
holy **** do not do this yet.

I was getting that "not enough space" error and none of my widgets would load up so I uninstalled it. It wouldn't power up so I resetted the phone by taking out the battery and now I'm back to ****ing factory setting
[Captivate Android Development] _Opiate_:
LOL after adding the added file it works perfectly fine.
[Captivate Android Development] washow:
Is there a market.apk? My phone doesn't have market anymore.. what the ****
[Captivate Android Development] acandia007:
nooby here, but im getting the low on space notification. im on a fresh JH2 Rom

i ran the 1.6gb one
[Captivate Android Development] darth_vato:
For some reason I'm now getting a wakeup lag of about two seconds.it just started doing it, too.know anything about this?
[Captivate Android Development] Clienterror:
I did 1.5 with no problems. Actually I'm 90% sure that apps that take a little longer to load (asphalt 5, home run battle .ect) are loading quite a bit faster. And I don't mean the click the icon and it starts to load, I mean the actual load screens are near instant for me. I've done the NAND and v1 lag fix and they both loaded obviously faster than stock, but for some reason v2.0 is making it noticably faster than the other 2 and I'm not sure why.
[Captivate Android Development] Zilch25:
Whoa, you're having some strange issues. I'm sorry this crap happened, but this is still super-alpha stuff =/ When it works it works, but when it doesn't it *REALLY* doesn't.

Your best course is probably to just do an odin reflash back to stock or JH2.
[Captivate Android Development] Zilch25:
Really bizarre, can you tell me what the phone shows your free space as? This really *shouldn't* happen since we're using the same firmware... though I told mine to repartition- I doubt that the partitioned space between a stock partition and a JH2 partition is different though. Maybe the script failed to clean up after itself.

I'm showing 194MB free
[Captivate Android Development] joeybear23:
FYI - mine was showing the low space warning at 187 MB free...

The 1 GB .txt you made for me fixed that right up. Now I have 786 free.

O, by the way, get some sleep.
[Captivate Android Development] Zilch25:
Was that with the 1.6 or 1.5 text file? (The 187 I mean)

Also, sadly, I got my 5 hours of sleep and I'm back to the boring office grind where between working I haunt XDA =P haha
[Captivate Android Development] joeybear23:
That was with the 1.6 GB.

I didn't try the 1.5, since you created the 1.0 before I got to that point.
[Captivate Android Development] Zilch25:
This is interesting, that means your available space on a clean install had a 7MB difference from mine and the only thing I did different was do a repartition when I flashed, maybe JH2 has a slightly larger NAND area partitioned... kinda scary that we're cutting it *that* close.

I suspect that this low memory issue is generated by the system when the NAND reaches a certain percentage rather than a finite number, my anecdotal evidence for this is that other phones (Such as the N1) that don't give a 2GB app space tend to start getting the warnings at about 20MB instead of ~185-200 we get on our phone.... seems like once it hits 10% of our app space it throws up errors. If we could find some way to modify THAT (which is unlikely) it should eliminate this issue... the more practical solution is probably to just use a smaller EXT2 file though haha
[Captivate Android Development] joeybear23:
Well you could always test yours by installing a 7-8 MB app and see if that makes yours give you the error. At least that should tell if the repartition you did allieviates the error...

I like the 1 GB :D

Not that I will ever install 700 MB of apps, but I "could"...
[Captivate Android Development] Zilch25:
I just pushed two 8MB files into there (one wasn't quite enough, put me at 185 haha), after the second one the system started griping about low storage, so we really are right on the razors edge.

This would definetly explain why paid apps still living in the app-private folder would put this over the limit, especially if you're using the 1.6GB file
[Captivate Android Development] magikspl:
Ah, good times, in the middle of the script my terminal emulator FC'd. Phone boots, have contacts and messages, that's all. No apps, not even market. This should be fun.
[Captivate Android Development] Zilch25:
Yikes... it probably isn't a good idea to use a phone based terminal emulator for the 2.0 fix since this fix actually messes with the app space on the phone (where the terminal emulator app would live)- RyanZA says RFS doesn't seem to pay attention to files in use being goofed with while the FS is mounted, but that apparently doesn't mean it can't cause application glitches =/
[Captivate Android Development] magikspl:
Ya, the reason I went with an emulator is because my ADB stopped working, but now that the phone is pretty much stock now, ADB miraculously picked up the phone just fine now. I'm gonna try to run the remove script and start all over through ADB
[Captivate Android Development] tbae2:
So I can't just do the unlagfix.bat for version 1 and apply this version 2 ?
[Captivate Android Development] joeybear23:
That leads me to believe it wants like 10% free of the original 1.8 GB (and change) phone storage...

Is there any downside to using 1.0 GB instead of 1.6?
[Captivate Android Development] Zilch25:
Just less storage space, that's it. It gives you a little bit of fault tolerance too for paid apps until Ryan works out that issue too.
[Captivate Android Development] Zilch25:
You *SHOULD* be able to, and many people have done so with success, but make sure you have a Titanium backup or a good nandroid just in case. Also if you use paid apps you should consider using the 1.5GB file if you're brave, and the 1GB file if you're cautious!
[Captivate Android Development] tbae2:
I'll be a wimp and use the 1GB File :p , I also have a good nandroid backup but it's almost a week old now. Oh well worst i'll lose is text messages, I'll report back with what I find.
[Captivate Android Development] Zilch25:
Hold off if you haven't done this! There's a fix in the works for app-private, i'll try to toss it into the zip in the op!
[Captivate Android Development] masterhaides:
I am using RyanZAEXT2LagFix ALPHA 1.zip with Busy Box 1.18.1 and had no difficulties with installing the fix. My Captivate runs great!! THANKS!
[Captivate Android Development] joeybear23:
Yes, 1.18.1 was supposed to include what was dropped out of 1.18.0

I didn't know it was out yet, though.

Cool beans.
[Captivate Android Development] tbae2:
You caught me just in time, I'm glad I checked back!
[Captivate Android Development] Zilch25:
Oh that's awesome, I didn't know it was out yet, wonder if he added ext3 support into it like he was supposed to =o
[Captivate Android Development] Zilch25:
Awesome, I actually just grabbed the update.zip (which has the app-private fix) method and I'm modifying it for the captivate. In the process of reverting my phone to no lagfix so that I can be the guinea pig, wish me luck!
[Captivate Android Development] tbae2:
Good luck, let us know :D my once again laggy phone is bugging me already :p
[Captivate Android Development] Zilch25:
The script is running now (Modified to default to 1.5GB instead of 1.6)... soon we will see if it works :o
[Captivate Android Development] Zilch25:
Had a SU force close during the fix installation process which fudged things up a bit (User data lost, but the fix worked). The update.zip throws the new version of Superuser on the phone which may be the issue, looking into this now. I'll toss it up there once I can install it without hosing my market installs haha

Edit: Had SU FC on me just poking around in the App, looking into rolling back SU.
[Captivate Android Development] tbae2:
Why did the update.zip include a new SU?
[Captivate Android Development] Zilch25:
Eh Tayutama wanted to make the update.zip work from an unrooted phone without any end user interaction, so he included it all in the update.zip. Though it's looking like this problem might be exclusive to me, and possibly due to me using the bugless pre-root, because even reverting back to the old SU I started to get FCs. I just restored to stock, going to install a few apps and try this again with all the included stuff.

After that I'll look into just modifying the createlagfix.txt files for people who dont want to mess with update.zips
[Captivate Android Development] tbae2:
Ah that makes sense, good idea I think a lot of people don't mind plugging it up and running the .bat. I find it easier then the update.zip :)
[Captivate Android Development] joeybear23:
Zilch,

Can you mount USB in Mass Storage mode?

I can't seem to, and I think I have it narrowed down to the lagfix... but I am not 100% sure.

I wiped my device. Checked that USB Mass Storage worked: Check.

Put on JH2. Checked that USB Mass Storage worked: Check.

Ran UTB update. Checked that USB Mass Storage worked: Check.

Ran Lagfix. Checked that USB Mass Storage worked: no-go.

No big deal at this point. I can attach with USB Debugging just fine...
[Captivate Android Development] tbae2:
If you're talking about the version of lag fix posted here, USB storage works fine for me. (can't say for the one he's trying to setup).
[Captivate Android Development] Zilch25:
Hmmm, thats strange, let me give it a whirl, I'm in between testing lagfixes, so let me use the original 2.0 and get back to ya (I'll even use the 1.0)
[Captivate Android Development] Zilch25:
Here's the update on that so far... it *works*... unless you want to transfer apps over. It seems to conveniently forget to migrate your existing settings over to the new EXT2 file... now I haven't confirmed whether it's just not mounting the right stuff, or if it just doesn't copy it though.
[Captivate Android Development] Zilch25:
Oh in case anyone wants to be a guinea pig on this one- I just want to confirm that the issue isn't just me. I'm going to attach the update.zip version to this post.

DO NOT USE THIS UNLESS YOU'RE PREPARED FOR YOUR INSTALLED STUFF TO NOT TRANSFER!

That said, to install it just dump it on your internal SD, rename to update.zip and reboot into recovery mode to launch it (or use clockwork).

PLEAAAAAAAASE DONT USE THIS IF YOU DONT WANT TO RISK LOSING YOUR INSTALLED APPS
[Captivate Android Development] max_warheads:
Did the output read clean? (did not have a mkfs.ext2 error)

Have you rebooted?
[Captivate Android Development] Zilch25:
Do you have busybox 1.71.1 installed? If you don't this WILL NOT work.

You might want to try this:

http://xdaforums.com/showpost.php?p=7578514&postcount=373

It checks out your phone to make sure all of the prereqs are met
[Captivate Android Development] Zilch25:
I currently have 7 windows open, some mobile, some full, some running flash lite, and I'm not seeing any noteable delays. Pinch zoom works seemlessly, and scrolling has no issues- I just closed all the windows and they closed instantly.
[Captivate Android Development] acandia007:
Would it be faster on the I900 Rom or the same performance on the stock captivate rom?
[Captivate Android Development] mykenyc:
And not for nothing doesn't this leave almost 800mb on app data? mines say 737 free space.
[Captivate Android Development] Zilch25:
Most of the guys in the original thread are reporting 2100-2200 scores with JM5/Samset, though you would gain some of the other i9000 improvements (Freaking media scanner BS). Other than that, benchmark-wise at least we're equal with the i9ks.
[Captivate Android Development] Zilch25:
Yup, this works pretty much like the NAND fix, except you get 1GB of storage rather than 130MB
[Captivate Android Development] acandia007:
Ah okay because im running the i900 rom and dont know if i should go back to the origial stock rom.

Thanks
[Captivate Android Development] dougp.me:
Ran the unlagfixme.bat, then deleted ext2data folder. Reran the lagfixme.bat and had this log:

===============================================================
===============================================================
One Click Lag Fix for Galaxy S I9000
===============================================================
===============================================================
__________________________________________________________
Pushing required files to /sdcard This is internal SD Card Please wait.
* daemon not running. starting it now *
* daemon started successfully *
4 KB/s (1741 bytes in 0.344s)
0 KB/s (56 bytes in 0.176s)
10 KB/s (177 bytes in 0.017s)
Now running lag fix. On your device, select allow root privledges!"
Creating 1GB file to store data inside. This could take a long time...
0+0 records in
0+0 records out
0 bytes (0B) copied, 28.285099 seconds, 0B/s
Creating loopback, you may see an error that it already exists. Ignore that erro
r.
Linking loopback to the 1GB file store
Creating the EXT2 filesystem
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
64000 inodes, 256000 blocks
12800 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
8 block groups
32768 blocks per group, 32768 fragments per group
8000 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Creating a mountpoint for files, you may see an error that it already exists. Ig
nore that error.
Mounting device
Copying data across
Clearing out any old backups, ignore any errors
Backing up old data
Linking to fast ext2
Now setting up reboot support
Moving boot animation
Copying over init scripts
Setting up permissions
All Complete!
Script complete!
* server not running *
Press any key to continue . . .

Still sitting in the 9xx results of Quadrant.
[Captivate Android Development] iLoki:
For those having issues:

If it won't copy files (or won't ask for root)

rename createlagfix.txt to createlagfix.sh.

Copy it to the root of your internal sd card.

Copy playlogos1 to the root of your internal sdcard as well.

Copy userinit.sh to the root of your internal sdcard as well.

use an adb shell (open up a command prompt, navigate to your sdk install, then type in adb shell) or use the terminal emulator on your device.

Type in su and press enter, to enable root access.

Type in sh createlagfix.sh and press enter.

It should run the script without any issues at that point. Now, reboot your device and enjoy :D

--- Now for my personal take on it :D

It certainly feels a lot snappier, facebook and skyfire all load REALLY fast.

Quadrant score was boosted from high 800s to 2222.
[Captivate Android Development] max_warheads:
0 records copied in.... Theres the problem. Somethings keeping your data out of the vext2.
[Captivate Android Development] Zilch25:
Hmm, looks like everything worked properly, but it seems like the userinit scripts aren't running properly on startup. Which version of busybox are you running? This script is VERY picky and will only run with version 1.71.1.
[Captivate Android Development] Zilch25:
Crap, totally missed that... kind of odd. Again though, verify busybox, if you're running 1.18 it won't work, and anything before 1.17 also seems to fail.

Edit: Actually, that might be okay, that's the stage where the 1GB empty file is being created, and it took place before the formatting, the copy stage happens later.... so this might still be related to incorrect busybox screwing up userinit script launch.
[Captivate Android Development] alphadog00:
Off topic, but how do you scroll with volume buttons? Is this in the default browser? I keep getting the volume pop up.
[Captivate Android Development] Zilch25:
Nah it's a DolphinHD thing