yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Zilch25:
Good to know I'm not the only one with unpredictable USB issues on this thing. My work computer kind of selectively decides the phone will work, if I'm in debug mode and I turn on drag n drop it causes Explorer on my work computer to seize up until I unplug the phone... then if I plug it in again they're friends again.

Also, I was attempting to do some command-line stuff with adb this morning and it was giving me the device not found BS as well, I just yanked the cable, plugged it into a different port and windows picked it up like a new device.

Thankfully my Win7x64 machine doesn't have these issues =P
[Captivate Android Development] Zilch25:
That's weird... 2.3gb shouldn't flag an error on ANY card. Do you have any external SD cards that are crammed with stuff? Also this reading you're getting for size, are you getting it from the last line of the "SD card and phone storage" section titled "Internal phone storage"?.

The reason I ask is it's completely impossible for your internal NAND to have 2.3GB as it's only 2 gigs to begin with O_o

Also clarification, the fix went through before the errors started popping up right?
[Captivate Android Development] A.VOID:
Sorry, I meant the 2.3 gbs is what shows on the computer as the SD card.

It showed full memory and then I couldn't even get Text messages. Tried to run uninstall and there is no space left on drive to move data.

Uninstall script failed

Phone crashed and I lost all apps on the reboot
[Captivate Android Development] Zilch25:
Are there things on your internal SD (the one your computer can see) you can delete? Or at least move temporarily?

The way this works is that a 1.5GB file is created on your internal NAND (2GB space), but in the process of installing and uninstalling it creates temporary gigantic files on your user storage area (the 14GB area you can see with your computer that has 2.3GB remaining). Theoretically if you free up space there the uninstall script should run smoothly. Make sure you turn off the copy files to computer option in the notification area before attempting to remove!

Edit: Bah, well that sucks =/ I'm not sure why you'd be getting the low memory error though, do you have a ton of apps/pay apps?
[Captivate Android Development] A.VOID:
I have/ had roughly 100 apps.

Running the uninstall lag script again to see if I have any luck on the reboot. If not, then I guess I'll reinstall the firmware and reset everything.
[Captivate Android Development] Zilch25:
Hmm 100 apps shouldn't be nearly enough to screw things up that badly. You should probably see if you can clear some space out of the internal SDcard though, it *should* only need 1.5GB to do the remove, but if it failed before maybe it needs more during the process.
[Captivate Android Development] A.VOID:
It was totally borked and I lost all ...

Reinstalling the firmware to get a fresh base
[Captivate Android Development] Zilch25:
Jeez, I'm sorry to hear that... I really hope we can figure out why these bugs crop up for some people and not others soon
[Captivate Android Development] A.VOID:
tried titanium to restore, but the file structure must be too hosed because it's not working well

using appbrain to hopefully get it now'
[Captivate Android Development] Some1PR:
ok... i debugged my issue.

For some reason the "mkdir /data/lagfixtemp" command in the createlagfix.txt is not getting execute or for some reason the directory is not beign created.

Any ideas what could it be?
[Captivate Android Development] Some1PR:
at last ... used the update_EliteSuperRooter.zip first. Aparently it repaired something. Then did the fix and worked flawlessly. 2213 on quadrant.
[Captivate Android Development] Crizthakidd:
ugh wtf. i finally did everything i want on my phone and it says memory full, and i cant receive texts. being that im a young teen i really need to text lol. so what can i do i have 3 gigs left on external, 6 on internal sd and um 178 mbs on the last one available memory. i know somewhere the 1.5gig thing was installed but what can i do now?. i did fix 2.3 and i never gotthe option to which size to chose o.o

the fone keeps surprising me how rediculously fast it runs now tho i dont even have a lag time after calls anymore its SO insane lol love this thing cant beleive i didint have an android til now
[Captivate Android Development] TheTodFather:
Well chris what i did was and would advise you would be to use 1click odin and start from a clean state. More then likely u had the previous lag fix and flashed over this so ask your follow up questions over at the odin. One click ghread
[Captivate Android Development] Crizthakidd:
hm you know what i did have the NAND fix, but when i flashed jh2 woudlnt that make me complete stock and have everything fine? before the lag fix on my available memory i had 1.6 gigs available. after i have 170 mb and thats when im getting the low space/ no texts cuz its full
[Captivate Android Development] mitchhh:
So I don't know if this fix has anything to do with it, but I am not able to mount my SD drives when I hook my captivate up to my PC.
[Captivate Android Development] A.VOID:
MIne did the same thing, and it crashed when i used the unlag since there wasn't any memory left to move the files.

I had removed lag1 before I installed 2.3. Seeing your issues seems to suggest a big issue with 2.3
[Captivate Android Development] Crizthakidd:
can anyone help us. also there is somethign called CFlag fix that worked for me very well, i like it and isnt giving me problems after doing the unistal from ryuans 2.3.

but there are a lotof questions i still have. like can i move the huge lagfix file somewhere to external or what can i delete/ not need and is there an updated script i cant be running on low mem all the time -___-
[Captivate Android Development] Tayutama:
Did you read my last post to you on the i9000 board?

Zilch25:

Up for some being test subject again? :) This time it's ext4 you need to test.

We got ext4 working on stock kernels :D
[Captivate Android Development] Clienterror:
Yea, I'm doing fresh install, 1.2 oc kernal then the ex3 lagfix update.zip and do the fix I have 260 megs left. Then when I install my apps from titanium backup they all install on on the 260 megs causing low memory. Am I doing something wrong?
[Captivate Android Development] acandia007:
I got 1704!!!

aren't i suppose to get 2k+?????

im happy with the results, im just asking
[Captivate Android Development] :
Benchmarks results vary this is not rocket science...try closing all your background apps and rerunning the benchmark.
[Captivate Android Development] Zilch25:
Yeah you'll see some variance. You'll get higher numbers after a clean boot (After media scan zzzzzzzzzzzzz), than you will after loading up the market and other apps. But what should really make it for you is the real world improvement in phone performance, if you don't see that any "fix" is a waste :)
[Captivate Android Development] acandia007:
Well I had the i900 jm5 rom, but reverted back because of this fix.

When i ran the benchmark with a clean stock rom i got 1700, but checkd apps open and all apps were open!! >=(

So i canceled all roms, ran another benchmark and got 2k+!!! =D

Pretty sweet fix!!

Btw i ran this without busybox?

is it a good thing or bad thing?
[Captivate Android Development] Zilch25:
If you feel like it you can go back to the JM5 rom and apply the fix, it should work just as well on that rom (Since it's just using userinit to mount the virtual ext file). But that's all personal preference- I doubt you'll see too much of a performance increase.
[Captivate Android Development] igm503:
im using the new north american rom uj something(forgot the exact name ;)) im getting 2100s consistently and i have no lag whatsoever in normal use! great fix
[Captivate Android Development] acandia007:
I think i am because the i9k rom is pretty sweet compared to the stock captivate rom
[Captivate Android Development] dougp.me:
So, I copied everything over to my internal sd card as above, and ran it through adb shell, this is the output I got.

C:\android-sdk-windows\tools>adb shell
$ su
su
# cd sdcard
cd sdcard
# sh createlagfix.sh
sh createlagfix.sh
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, 19.058301 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!
#

I still received a 961. As for busybox, I am running the recommended version:

------------------------------------------
This will try to upload a test file to your phone and test if it contains all th
e files needed for applying the dirty lag fix trick.
*** to CONTINUE, press any key
*** to QUIT, press control-C
------------------------------------------
Press any key to continue . . .
3 KB/s (1077 bytes in 0.339s)

Validating file requirements

Checking busybox
BusyBox v1.17.1 installed
Checking if busybox contains required function
losetup..... found
mknod..... found
mkfs.ext2..... found
mount..... found
chmod..... found
it seems that your busybox are capable to do the trick!!

Checking busybox
Found su: ../xbin/su
------------------------------------------
test finished
------------------------------------------
Press any key to continue . . .

Any other ideas?
[Captivate Android Development] Zilch25:
Hmmm this is kind of odd, were you by any chance running any other fixes like the NAND fix prior to this one? The only reason I ask is because your scores seem to be in line with the results I always got while using it. If you ARE using the NAND fix, you'll have to revert it first.
[Captivate Android Development] dougp.me:
I thought I had reverted it - I'll try reverting again though.
[Captivate Android Development] alphadog00:
Where did you find this? I haven't seen any mention of it anywhere. Is it for Captivate or Vibrant?
[Captivate Android Development] acandia007:
Is it a good thing or bad thing if this thing works without busybox installed?

because im getting 2K+ scores without busybox?

oh im running the I9k rom
[Captivate Android Development] mitchhh:
Works great for me, 2135 on the first boot up...problem though not sure if this may have anything to do with it, my alarm went off and it sounded all distorted, did not sound like that yesterday..maybe it's just me. I'll try another alarm now.

Edit:

Still have the distortion...can anyone else test out an alarm so I can make sure I'm not going crazy? lol
[Captivate Android Development] alphadog00:
If you have titanium backup, then you probably installed Busybox.

If you didn't have BusyBox at all, then the script would fail as Busybox installs the basic unix commands that let the script do its work.
[Captivate Android Development] acandia007:
But than why am i getting 2K+ scores?
[Captivate Android Development] dougp.me:
There's a few applications that automatically install BusyBox. Chances are, you have it installed, but don't know it.

Also, I got it to take on my phone - had to revert the NAND fix (again, not sure why ...) and then it finally went through. Got a score of 2165 this time.
[Captivate Android Development] naxir:
I asked this in the other thread, but as it has a ton of activity I'm going to guess it'll be missed:

Quick question. it creates a virtual ext2 on the existing partition. now, the gripe with ext2 is lack of journaling which means a crash/hard shut down can cause data corruption. that said, because this virtual ext2 partition is just a file sitting on top of a RFS partition (which I assume does have journaling) won't the RFS partition have a journal of modifications to that ext2 file and there for able to repair the ext2?
[Captivate Android Development] BplusB:
works great on my captivate!
[Captivate Android Development] max_warheads:
Simple answer: No. Not exactly as such.

RFS think's its a file. Until data is in the file, the virtual Ext2 still just ext2. Ext2 was chosen and configured for speed. No atime, etc on the files means less write need to happen with means less hits against the rfs but also by the same token, writing those atimes aren't going to block actual writes that need to take place!

Battery yanking = bad, with or without journaling. Don't do it unless absolutely necessary.
[Captivate Android Development] naxir:
stock quadrant: 895

nand fix quadrant: 967

RyanZA fix quadrant: 2240

blazing.
[Captivate Android Development] Tayutama:
Hmm shouldn't do that.

Let me run the ext3 here again after i remove ext4 from my phone
[Captivate Android Development] Clienterror:
Yea its weird, I've redone it 3 times now with the same result. Even more weird when I unlag fix it crashes the phone (it boots to a continuous force close) and when I load rom manager and it reboots to reflash the backup it says the md5 check sums dont match and it wont reflash so my only option is to do a fresh odin image and start over. Not really a big deal this is 1/2 the fun with an android phone :-) thanks for all your work btw it's amazing what's you guys have done.
[Captivate Android Development] praveer01:
LAG Fix version which runs directly from Ubuntu

Warning: You are responsible for your device if something goes wrong and I am not responsible for any outcome after running the script. (As mentioned in RyanZA's thread in the worst case you need to reflash your device with proper ROM)

This is a simplified script for those who want to fix lag issues using the ext2 fix on Ubuntu or any Linux system.

I have added lagfixme.sh which is a unix variant of lagfixme.bat.

Prerequisites: Same as the the ones mentioned in RyanZA's thread (showthread.php?t=749495) except a few specific for Linux desktop.

To sum it all:

1) Bash shell, grep and wc are needed

2) Android SDK must be installed

3) Linux kernel must be able to detect the Galaxy S variant

4) The device must be rooted to allow superuser priviledges

5) Busybox version with mkfs.ext2 (to find out, use command ./adb shell busybox and check the list of commands)

6) su or sudo and root permissions on the desktop or laptop on which this script is executed

To run the fix:

1) Extract the zip

2) Set the parameter ANDROID_TOOLS in the file lagfixme.sh to the path where android-sdk..../tools can be found

3) Open a terminal or terminal emulator(gnome-terminal/konsole/xterm anything will do) and cd to the directory where you extracted the zip

4) chmod +x lagfixme.sh

5) su or sudo and get root

6) Run the script -> ./lagfixme.sh

I have tested this on my laptop running Ubuntu 10.04 and I was able to get a Quadrant score of >2000 on Samsung Captivate.

Edit: Also added unlagfixme.sh
[Captivate Android Development] Tayutama:
Right just for ext3 version up and running on my phone again and noted down space left before doing titanium backup.

/dev/block/mmcblk0p2 1.9G 1.5G 417.3M 78% /data

dev/loop0 1.4G 57.0M 1.3G 6% /data/data-ext3

And this is after titanium backup is done:

/dev/block/mmcblk0p2 1.9G 1.5G 417.3M 78% /data

dev/loop0 1.4G 95.6M 1.3G 6% /data/data-ext3

So can't really redo what you had :(

Can't remember if i have changed some of the script in the version i'm using compared to the version i have released.

But new version will be up soon with Check_Space.sh script that will print out the space you got for installing applications and with ext4 support.
[Captivate Android Development] Clienterror:
Yea it's no biggie, I'm having a blast flashing this phone. I can't leave stuff unmodified, my GF says it's a curse but I love it :-)
[Captivate Android Development] Zilch25:
Whoaaaaaaaa ok how'd you get EXT4 on stock kernel? But more importantly: Gimme whatever I need to guinea pig it up!
[Captivate Android Development] Tayutama:
This is from my post about it to RyanZA:

Right got ext4 working.

Quadrant before Titanium backup: 1760

Quadrant after Titanium backup: 1819

Overall system feels pretty nice and fast.

Test zip attached.

Please note other people if you download it that it isn't the final version but pretty close.

Note: I need to fix up my test versions... go v2.2, v2.3 and v.24 as test versions...

All 3 with different changes in them ^^ and got enough for a v2.5 also if i don't get it into one of the others.
[Captivate Android Development] Zilch25:
Already nandroided back to JH2, so I'm blasting this over now!

How'd you manage to get EXT4 to work without a custom kernel?
[Captivate Android Development] Tayutama:
We are using insmod to insert 3 .ko files into the running system (modules) which enables ext4 support.

Sadly we don't have any for ext3 yet so the ext3 versions is still kernel dependent.

Also this won't work on froyo as they are specific to the 2.6.29 kernel version that eclair is running.

Btw you might note a new script called Check_Space.sh

IT does just what you think it does :D
[Captivate Android Development] Zilch25:
Ahhh okay, that's pretty creative. I was under the impression this was impossible without the custom kernel- so this is probably good news for people who want to mess with ext4 anyway, though ext3 is supported by the kernel so is there any reason why you'd need the .ko files for ext3? Hell... if you can run EXT4 why even bother with 3, they both have the same journaling wear.

Haha I noticed the checkspace script when i went in there, didn't bother running it though. Seems like titanium backup might be causing some of the issues people are having though from the posts I've been reading
[Captivate Android Development] Zilch25:
Getting a mke2fs error saying invalid option - - t
[Captivate Android Development] Tayutama:
the .ko for EXT3 was mostly thinking ahead on froyo when we can get those running since the froyo builds we got atm only supports ext2 :(

the check space script doesn't show any numbers though if the fix isn't done :)
[Captivate Android Development] Zilch25:
Ahhhh so it checks how much space is inside of the EXT2/3/4 file so people don't have to mess with adb, nice thought :)
[Captivate Android Development] Tayutama:
hmm weird since these mke2fs and those are static compiled binaries... -t is used to specify which filesystem to use :(

The ext3 script will fail also then i think since it's another version of mke2fs then i used before
[Captivate Android Development] Tayutama:
Yeah it prints out Used Space, Free Space and Total Space
[Captivate Android Development] Zilch25:
Amazingly enough the phone boots up just fine, though theres only 243MB of internal storage left- which makes sense since mke2fs failed, so it succeeded in creating the monster ext4 space but not mounting it... good thing I only have a handful of apps :)

I'll nandroid back again- strange though that the EXT3 I tried yesterday worked though which I'd assume means that mke2fs was working properly then
[Captivate Android Development] Zilch25:
Hmmm looking into the script, for EXT3 you're using the -j switch for mke2fs but with no reference to mounting EXT3, whereas in the EXT4 it's -t and specifying ext4

EXT3 script:

mke2fs -j -m 0 $LOOPBACK_2;

EXT4 script:

mke2fs -t ext4 -m 0 $LOOPBACK_2;

Is this due to the new method of enabling ext4?
[Captivate Android Development] Zilch25:
Haha looks like you answered my question while I was typing it =P

Which begs the question... why does the captivate not like it?

Hmmm I wonder, it SHOULD be overwriting old versions of mke2fs... but what if it isn't? My nandroid image has the regular EXT3 update.zip preinstalled (but not applied) so all of the tools are already in xbin... let me try this from a totally virgin install
[Captivate Android Development] Tayutama:
hmm right had forgot that it was -j instead of -t ext3 for that one.

-j is basicly a ext2 with journally = ext3 :)

Still weird that the -t comes up as invalid argument... since it works fine here. Don't think the kernel would mean anything at this point.
[Captivate Android Development] Zilch25:
Just in case you didn't see my edit I'm bumping =P
[Captivate Android Development] Tayutama:
Ok else ill ask the person who compiled it.

Also can you check and see what version the stock kernel is on the captivate?
[Captivate Android Development] Zilch25:
JH2 is:

2.6.29

jetaek.lee@sep-11 #2
[Captivate Android Development] Tayutama:
hmm JG8 that i'm testing on atm (Africa version) shows this:

2.6.29

mobilus@SE-S606 #2
[Captivate Android Development] Zilch25:
Success!

(Well it isnt complaining about mke2fs anymore)

It's still in progress but I can't imagine why it wouldnt work... looks like you just need to find a way for it to clear out the old files in xbin and drop the new ones in
[Captivate Android Development] Tayutama:
That is pretty easy... I just need to adjust the updater-script to delete the old files i have new versions of.
[Captivate Android Development] Zilch25:
Confirmed working, 297 free on internal, and 1671 quadrant with all the AT&T garbage running... def faster than EXT3

Update the old script to clean xbin out, and I'll nandroid back to my "dirty" install and test again!
[Captivate Android Development] Tayutama:
nah ill only set it to delete those 3 new files: tune2fs, mke2fs and e2fsck. no need to remove the rest yet.

Attached.

Btw i have put the interactive script on hold for the moment :)

And next version will properly have a build in function to check for this:

Max size on /data

Space used on /data

Then it will make the file like this: Space used + 100mb or so

Then later resize it to Max size - 200-300mb or so.

So it will be dynamic which size the file gets :) aka no more low on memory warnings
[Captivate Android Development] Zilch25:
Yeah no point yanking out the stuff that's working (and that hasn't been updated). My nandroid is rolling back as we speak, so as soon as you get a chance to make the modifications I'll give em a whirl
[Captivate Android Development] Tayutama:
Dunno if you saw it but file is added in my other post :)
[Captivate Android Development] Zilch25:
Yikes how'd you sneak that in there without me noticing! Downloading now :o
[Captivate Android Development] Zilch25:
Hmm apparently the change didn't take, it's yelling at me about mke2fs again =/
[Captivate Android Development] Tayutama:
hmm right...

strange. Just did a test on my own with making the update.zip without those 3 files in it but with the updater-script that deletes them. (Ofc had the files on the phone already)

and it did delete those 3 files

go adb shell :)

and type: ls -l /system/xbin/mke2fs

the output should be like this: -rwxr-xr-x 1 0 2000 253468 Aug 1 2008 mke2fs
[Captivate Android Development] Zilch25:
Fresh nandroided back to my "dirty" install, it's reading -rwxr-xr-x 1 0 2000 30680 Aug 15 2010
[Captivate Android Development] Tayutama:
before or after using update.zip?
[Captivate Android Development] Zilch25:
Thats before... running the update.zip now to see what happens
[Captivate Android Development] Zilch25:
After:

-rwxr-xr-x 1 0 2000 253468 Aug 1 2008
[Captivate Android Development] Zilch25:
You think maybe it's trying to run my existing mke2fs file from the system/bin folder? When i run the list on that it shows the date of the old busted one.

Actually there's no think about it, that MUST be what it's doing
[Captivate Android Development] Tayutama:
Right so it does the job with deleting the old and putting the new in...

No idea why mke2fs fails sometimes then...
[Captivate Android Development] Zilch25:
Bump in case you missed this... that's got to be what's going on. Is there a way of telling it to ONLY use the one in xbin instead of the symlinked one in bin?