yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Chainfire:
Hmm, that is an unexpected format! Should be fixable, though. I'll try to fix this for the next update.

Well it had a lot of advantages against his v1, but his v2 matches my patch in various features.

Top of my head, my v1.20 vs RyanZA's v2 would be:

Chainfire v1.20 better:

- more checking is performed, there is a good chance the application will give you an error before any changes are made, instead of the procedure going wrong and you not being able to boot

- partition size is configurable (without modifying scripts)

- directories to "fix" is somewhat configurable (without modifying scripts)

- copying the data is done in a much safer way, much less chance of applications stopping to work correctly or settings being lost

- can also do /dbdata/databases, without breaking the ROM, which makes a large difference in "real world" performance, though not so much in "Quadrant"

- looks better (questionably ;))

RyanZA v2 better:

- can use all space from /data, instead of mine which only uses free space (I will also bring this feature in an update)

- can be uninstalled (Mine cannot yet do this automatically, will also be fixed in a an update)

- v2 is newer than my own patch, but if you include v1 RyanZA has been at this longer. Whether that means anything remains to be seen
[Galaxy S I9000 Android Development] phpcool:
Just tried it，Worked flawlessly on my Galaxy with I9000ZSJH1，

Thanks！
[Galaxy S I9000 Android Development] Aquario79:
Think the issue may be related to custom rom (SamSet). I tried again using your fix first before flashing SamSet and it worked!
[Galaxy S I9000 Android Development] stluciasound:
Problems?

Installed lagfix and everything went smooth as my device speed went up to 2183.

However, my internal memory was being swallowed by this lag fix (from 1.3gb to 400mb is kinda too much..)

And another one : My PC wont detect my I9000 driver after I intalled this lag fix. Can somebody tell me how to get it back?

Mine was : I9000DXJF4
[Galaxy S I9000 Android Development] Chainfire:
Re: size, seems you used a 900mb size for the ext2 image. What you need to understand is that apps will now be installed (and their data stored) _inside_ that 900mb, not in the 400mb you have left. There is still some space needed outside of that 900mb image for the system, though. This version of the lagfix does not reclaim the space yet that is used double, but a future version will.

All in all, after this lagfix (or any of the others, really), what your phone reports as the internal memory space it has left has no meaning. If you install or remove apps, the space it reports wont actually change.

Re: driver, no idea. I don't understand how the lagfix would cause such a thing either ...
[Galaxy S I9000 Android Development] stluciasound:
Thx, im re-installing it right now. Will get back to you soon...
[Galaxy S I9000 Android Development] lucasjohny:
anyone did a factory reset after apply this fix, will it the same after a factory restore, I try one click lag fix before but all will back to normal after a factory restore. hope this version will sustain after fac reset.
[Galaxy S I9000 Android Development] stluciasound:
I don't get it...can you explain it more details?
[Galaxy S I9000 Android Development] chasy:
he means that after a factory reset the lag-fix is not persistent.
[Galaxy S I9000 Android Development] RyanZA:
It don't think it means anything. ;)

Most of my goal with my lagfix was to get people who know more about this stuff than me a reason to chip in and make something great. :)

Regards to lag fixes being removed with a reflash: All lag fixes will be removed when you reflash, as a reflash overwrites everything on your device.
[Galaxy S I9000 Android Development] tomolewis:
Ok how many times should this reboot? Mine seems to be stuck in a boot loop?
[Galaxy S I9000 Android Development] zerocoolspain:
RyanZA, ChainFire ... Why do not you work together in a single fix?

It would be the perfect fix ... :D
[Galaxy S I9000 Android Development] dupel:
Hmm, works like a charm. Only complaint - some things lag like hell. FOr example installing apps from market.

I'd say it is because I included dbdata to ext2 too.
[Galaxy S I9000 Android Development] Chainfire:
I've seen it take 30 reboots before completion... Has it finished yet ? Which ROM are you using ?

My way is not compatible with RyanZA's, uses different methods to (somewhat) the same thing ...

I haven't noticed this all... but I'll check it out. I do know a lot of things are a _lot_ more snappy, if marketplace install is the only thing that gets slower, that's still a win, I'd say.
[Galaxy S I9000 Android Development] dupel:
Yeah, a lot of things are much-much faster =)

So big thanks for putting such fix for us :cool:

Will try now to install it without moving dbdata.

Btw, you described an uninstall fix here, wich I think worked for older version. Cos in 1.2 all files appear to be in data/cflf

EDIT: Yes, uninstaled the fix and installed without dbdata/dabases. Market works much faster.
[Galaxy S I9000 Android Development] dupel:
By the way. Has anyone thought about combining the mimocan's fix and this fix together?

I'm sure if we run some things from memory card and some from internal memory it could lead to speed improvement (probably not very significant, but still).
[Galaxy S I9000 Android Development] stluciasound:
O yeah, I just did it. All the problems solved, and I also lost the lag fix. Gonna tested it again. Hope this time wont affect the windows driver. Thx :)
[Galaxy S I9000 Android Development] paulthesinner:
the tool is forced closed whenever I choose size lower than 1 GB:(
[Galaxy S I9000 Android Development] Tayutama:
ok either i'm blind or something since i can't find the link to the 1.20 version...
[Galaxy S I9000 Android Development] jodeltje:
I can't either so it's probably taken down... Chainfire are you uploading 1.30 or something?

BTW thanks for jumping on the 'lag fixing bandwagon'! greatly appreciated :D
[Galaxy S I9000 Android Development] Tayutama:
Looks like 1.50 is up ^^

Chainfire: are you using tune2fs to make the ext3? aka making an ext2 and then turning it into ext with tune2fs?
[Galaxy S I9000 Android Development] Chainfire:
CFLagFix v1.50 released !

Now also supporting ext3, resizing, uninstallation, and "full auto" mode!

Enjoy!
[Galaxy S I9000 Android Development] jodeltje:
HA! nicely done, thanks
[Galaxy S I9000 Android Development] sandyph:
hi Chainfire

I got this error message :

Temporary Location is not writeable

any idea what its mean ?

I already have Root and BusyBox
[Galaxy S I9000 Android Development] Tayutama:
Hmm ran into a problem running this.

Running JP3

Image attached:

EDIT: Just tried with an ext2 partition instead of ext3 and no problems at all with that one.
[Galaxy S I9000 Android Development] Chainfire:
Indeed I was uploading 1.50 at the time.

Journal is set directly through mke2fs

It means the program can't find a location it can write to for some reason. Which ROM are you using ?

Not sure why that is, using ext3 works fine for me.
[Galaxy S I9000 Android Development] dupel:
So, whay are the advantages of ext3? Safer but slower?

What about ext4?
[Galaxy S I9000 Android Development] zerocoolspain:
Very Very Good Job :)
[Galaxy S I9000 Android Development] sandyph:
this is my phone data, its still Singapore Singtel stock rom

firmware version

2.1-update 1

baseband version

I9000DXJF4

kernel version

2.6.29

root@SE-S604 #2 (rooted using the one click root)

oh, and I tried your 1.50 version

any help would be appreciated :D
[Galaxy S I9000 Android Development] Chainfire:
There is some debate as to ext3 being better or not. Some claim it is better because of journaling, some claim it is slower exactly due to that journalling, some claim it may kill the flash chip quicker as the journals are always (and repeatedly) written to the same spot, some claim the latter is not true due to RFS/controller implementing wear-levelling, etc.

In other words, your guess is as good as mine, all of the above may be valid points, but we don't know which are actually true in this case.

Personally, I just use ext2 - which people generally advise over ext3 for flash storage. So many people have asked me for ext3 support through PM and IRC though, that I decided to add it.

As for ext4, no support in kernel, nor in the supplied tools. Not really sure what the benefits of ext4 would be anyways. It still doesn't allow a larger blocksize, and personally I have the intuition that a 16kb block size would be optimal (not supported by any extX filesystem).
[Galaxy S I9000 Android Development] pauernet:
same problem with JP2

the cannot write to temporary location thing?
[Galaxy S I9000 Android Development] Chainfire:
Open a commend line, go to the folder you dumped CFLagFix in, type:

adb shell

su
ls -l -d /data
ls -l /data/
ls -l /data/local/
echo "test" > /data/local/test
cat /data/local/test
toolbox df
toolbox mount
exit
exit

Copy/paste the command to make sure no L's have becomes ones, etc.

Paste everything that rolls out here.
[Galaxy S I9000 Android Development] Chainfire:
Which exact problem ?
[Galaxy S I9000 Android Development] CazeW:
As much as I like seeing this problem tackled by this many persons and with such intensity; wouldn't it be more efficient to concentrate all the knowledge, ideas and skills you guys have into one single complete fix instead of everyone releasing their own tools? I'm new to the XDA community so this might be how things work here but to me it seems a little unefficient and confusing for us "normal" users to have this many tools and not know which one you should use.

By no means is this meant to be a negative rant and I want you guys to keep up the great work of cleaning up after Samsungs lazyness. :)
[Galaxy S I9000 Android Development] Chainfire:
Welcome and congrats on your first post :)

As stated before my method is not directly compatible with the other methods. Each different methods has it's own benefits and drawbacks, for example:

- Mimocan, external SD

- CFLagFix, internal storage, more features, Windows only, through ADB, safer than OCLF, currently limited to 50% usage when installing/uninstalling

- OneClickLagFix, internal storage, Windows only but easily adapted to Linux, through ADB, uses SD during transfer so no 50% limit

- Update.zip, internal storage, no computer required

So which to use depends on what you want... though there is a lot of overlap, the goal for these methods is the same (fix the lag) but the methods are not. Some methods will work for some but not others. It would take a lot of work to combine all features into a single package.
[Galaxy S I9000 Android Development] dupel:
Ok, thanks for clarifying! I'll probably stick with ext2 than.

Btw, I tested the "move databes vs do not move" and have to say that without moving phone is more responsive.

Installing apps from market is still slower than with mimocan's fix. With it I could install (with appbrain web installation) some 10 apps simultaneously, with your fix and without moving dbdata/databases I can install some 2-4, and with moving - 1, and while it installs phone is pretty much unresponsive to anything.

But in real life this seems like the fastest fix yet =)
[Galaxy S I9000 Android Development] sandyph:
ok, I think something is wrong with my phone :-/

(using adb application on your cflagfix 1.50)

adb shell

$su

su

#ls -l -d /data

ls -l -d /data

#ls -l /data/

ls -l /data/

#ls -l /data/local/

ls -l /data/local/

# echo "test" > /data/local/test

echo "test" > /data/local/test

# cat /data/local/test

cat /data/local/test

# toolbox df

toolbox df

/dev: 166708K total, 0K used, 166708K available (block size 4096)

/mnt/.lfs: Function not implemented

/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)

/system: 302336K total, 276064K used, 26272K available (block size 4096)

/data: 1963904K total, 179584K used, 1784320K available (block size 16384)

/dbdata: 109760K total, 22488K used, 87272K available (block size 4096)

/cache: 30784K total, 6792K used, 23992K available (block size 4096)

/efs: 6064K total, 4103K used, 1961K available (block size 1024)

/sdcard: 14086752K total, 12951712K used, 1135040K available (block size 32768)

/sdcard/sd: 15549952K total, 15015648K used, 534304K available (block size 32768)

# toolbox mount

toolbox mount

rootfs / rootfs ro 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

/dev/block/stl6 /mnt/.lfs j4fs rw 0 0

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

none /dev/cpuctl cgroup rw,cpu 0 0

/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s

hortname=mixed,utf8,errors=remount-ro 0 0

/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-

1,shortname=mixed,utf8,errors=remount-ro 0 0
[Galaxy S I9000 Android Development] Chainfire:
After some more testing on different ROMs, I _may_ have found your problem. Update to 1.60 coming soon.
[Galaxy S I9000 Android Development] sandyph:
great, can not wait :D

thanks :D
[Galaxy S I9000 Android Development] Chainfire:
Well as I said I think we could get even faster speeds if we could get 16kb block size.

But I will try a different method for dbdata/databases, experiment, see if I can make that even faster.
[Galaxy S I9000 Android Development] Chainfire:
1.60 released !

Should fix issues with some versions of root+busybox.

Also tested on JM2, JP2 and JP3. Seems ext3 is not supported on the Froyo ROMs.

Please try the 1.60 that is posted and let me know if it fixes the issue for you.
[Galaxy S I9000 Android Development] daijirok:
hey Chainfire, I am going to test this new version of the tool, but I'm wondering if it's better to select ext3 instead of ext2, what's your advice?
[Galaxy S I9000 Android Development] Chainfire:
My advice == the default settings, i.e., leave everything as it is and just hit "Install !" :)

That's why those are the default settings!
[Galaxy S I9000 Android Development] Chainfire:
Well, that experiment seems to have worked, and highest score yet. However, it will take quite some reworking to put in the lagfix... I'd look to see you test it manually first, @dupel, if you don't mind backup/restoring your ROMs to test. I am in a real hurry though, I'm going on vacation in 20 hours, so :P

EDIT: 2287 @ JM2
[Galaxy S I9000 Android Development] emelie:
@Chainfire: Thx for all your work!

Is it safe to use the current version (1.6) to uninstall an older one (1.2) and after a reboot use the same current version (1.6) to install again?

thx

EDIT

answering myself because i was too lazy to do my homework: shoulda checked the first post again, it's all there ;)

"You can only uninstall installations of CFLagFix 1.20 and newer !!"

thanks again for this fantastic tool & service that comes along with it! best of all lagfixes IMHO!
[Galaxy S I9000 Android Development] dupel:
Sure, I can test =)

EDIT: Btw, any idea how this fix works with nanodroid? SHould I make a back up of fixed system and than restore to system without the fix. I see two outcomes - nandroid back ups all god, and nandroid backs ups img file as well, making the back up some 1.5 gigs.
[Galaxy S I9000 Android Development] Chainfire:
Sending you a PM :) (+- 5 mins)
[Galaxy S I9000 Android Development] Chainfire:
Yes, 1.60 should be able to uninstall earlier installs from version 1.20, 1.50, and 1.60. I haven't tried it with 1.20, but it _should_ work.
[Galaxy S I9000 Android Development] kenkiller:
Will this have any complications with mods like samset?

when they update superuser or busybox apps. And will future mods be any problems?
[Galaxy S I9000 Android Development] emelie:
I'm testing this:

- using version 1.60 to uninstall 1.20

- shutdown, battery out, Boot, Reboot - for extra safety ;)

- using version 1.60 to install 1.60

EDIT: wrote a new post
[Galaxy S I9000 Android Development] Chainfire:
CFLagFix has it's own busybox version stored and called seperately. SuperUser update should not matter.

Before v1.60, it seems CFLagFix sometimes used the installed busybox instead of the busybox it comes with, but that should be fixed in 1.60 and no longer an issue.
[Galaxy S I9000 Android Development] kenkiller:
thanks for the explanation. Alas 1.6 came too late for me. Went back to stock JM5, did CFLagfix 1.5, then applied Samset 1.9d.

Now restoring with Titanium....hope everything goes well.

But I did notice after doing CFlagfix 1.5 that Quadrant scores are around 200+ pts less than Ryanza's lagfix. That's not really a concern for me, I just hope the performance after restoring is comparable.

Even after reading the intro, I'm still not sure how different this is from Ryanza's V1 of the lagfix. I know there's certain problems with his V2, but u seem to be comparing urs to his V2. Can u give a short explanation? :D
[Galaxy S I9000 Android Development] WhatZitTooya:
maaaaannnn :/!

its great work but the same problem as the "One Click Lag Fix 2.0".

Many private apps not working.

Astro Player Key or Tower Raiders Gold for ex.
[Galaxy S I9000 Android Development] Chainfire:
I'll try getting some of these apps and test them specifically. Are any of them free?
[Galaxy S I9000 Android Development] emelie:
just used 1.60 to uninstall 1.20.

after the reboot initiated by the app i lost a couple of apps (or they were not visible).

after an additional reboot (and removal of the battery for a couple of minutes) it took a while to boot to homescreen - didn't touch the screen while it was doing that.

after i unlocked the sim i got a ****load of force close messages from every kind of app - android.process.core, .gapps, user installed apps, etc.

afer confirming them they popped up again -> force close loop.

i'm going to flash JM5 again and then have another go.

shouldn't the uninstall process work? or did i miss something?
[Galaxy S I9000 Android Development] Chainfire:
Yeah it should have worked ... un/reinstalling 1.60 works, I thought it would have worked with 1.20 too... but maybe I was wrong ?

Or perhaps the uninstall has something that doesn't work with JM5, that is also possible (running JM2 myself)
[Galaxy S I9000 Android Development] WhatZitTooya:
no problem with free apps.

only payed apps have this issue, but it seems not all of them.

many payed apps work like radiant, buka, gentle alarm, phonemypc, list master pro (as far as i remember) and some more are working.

very strange...
[Galaxy S I9000 Android Development] dupel:
same here (uninstall 1.2) and also JM5.

Just reflashed + samset1.9d and now Im installing the 1.6 lagfix. Will tell you how it works.
[Galaxy S I9000 Android Development] Chainfire:
Well, I don't seem to be able to buy apps through the market.

Here is something you can do to help:

Connect your phone in USB debug mode, open a command line, go to the CFLagFix folder.

Type:

adb logcat > logcat.txt

It will keep running if you don't touch it (or it should).

On your phone, launch one of these applications, wait until the force close message pops up, and press force close. In the command line window, press ctrl+c.

There should now be a logcat.txt file in that folder, zip it, and attach it to your reply.

If you know the java package name (bla.bla.bla.bla) of the app you just run, post that as well!
[Galaxy S I9000 Android Development] galaxyowner:
Quadrant says with the ext3 partition 1479 points...why it's slower as the ext2?
[Galaxy S I9000 Android Development] dan77net:
WORKS VERY FINE on my SGS with M2 Rom.

THANKS A LOT MAN !!!!

Good Work.
[Galaxy S I9000 Android Development] WhatZitTooya:
puh, maybe on weekend. tryed every lagfix that moves also /data/app dozens of time, thats not funny anymore.

but, u think logcat can reveal something?

dont know if this helps but the apk's, of the payed apps that dont work, are not copied anywhere, they just disappear. only there folders will be createt in /data/data or /ext2data/data, i didnt checked out where u mount the ext2 file.

it has something to do with the copying of /data/app folder, because by unchecking this, everything works fine.

even titanium cant restore them if this was checked...
[Galaxy S I9000 Android Development] pauernet:
1. Flashed JP2 (because of full flash support)

2. Rooted with OneClickRoot

3. Add the LagFix 1.6

4. Quadrant ~1700
[Galaxy S I9000 Android Development] qwas00:
Why not install JP3 instead. Its much more stable. You can install flash by installing /system/app/install_flash_player.apk
[Galaxy S I9000 Android Development] darckreign1984:
....

with jp3 i cant play asphalt 5, i dont have 1 mb free ....:)).

this patch 1.6 take a long long time to complete.
[Galaxy S I9000 Android Development] hcarrega:
and how many points in quadrant??
[Galaxy S I9000 Android Development] darckreign1984:
not much

1562 quadrant 1.02 advanced edition and ext3 partition
[Galaxy S I9000 Android Development] DocRambone:
I get around 1600 with I9000XWJG5 on ext 3

And 2300 on same rom with ext2.

All with lagfix 1.6
[Galaxy S I9000 Android Development] Chainfire:
Tower Raiders Gold seems to be working in my 1.70 (not yet released)... not sure what would have fixed it, though.
[Galaxy S I9000 Android Development] tkalli:
PDA: I9000XXJF3

Phone: I9000XXJF3

CSC: I9000OXAJF3

Had flashed some other ROM's, but had problems with Marketplace.

So flashed back to XXJF3. Been using that with no problems.

Clean ROM, Rooted.

Flashed CFLagFix 1.60. Seemed to go fine.

Just left it alone as advised. Phone rebooted

Waiting an hour and twenty minutes.

Not sure what happen, but phone just had Black screen.

Using Odin I Re-Flashed I9000XXJF3, several times without any luck.

Gets to Galaxy Logo and seems to stop.

Any suggestions?

UPDATE: Got it working. Reset and wipe all data.

Have to start over again.

Lot to learn about Android coming from WM..:confused:
[Galaxy S I9000 Android Development] Chainfire:
That is unfortunate. I'm not sure what happened (new version might actually have progress counter in it so you can see if it has stalled)

A reflash should completely get rid of CFLagFix. Perhaps try flashing another ROM ?
[Galaxy S I9000 Android Development] tkalli:
I always seem to have a problem with Marketplace with other ROM's.

I am in the U.S., so maybe it has something to do with the modem.

XXJF3 installs multiple CSC's.
[Galaxy S I9000 Android Development] insty:
Thanks a lot for the Lagfix, definitely great to see the community getting behind it and providing updates regulary.

Do have a quick question though... I am currently using Samset's rom and he puts updates out quite a fair bit. If I do this: SamSet 1.9d > LagFix > New update comes out then I re-apply the rom, will this make the lagfix fall over?

Cheers.
[Galaxy S I9000 Android Development] tkalli:
OK, ROM reinstalled and rooted.

Apps installed.

Will try again and see what happens this time.

:D

UPDATE:

Everything went fine this time.

Took 13 minutes till phone rebooted.

Ran Quadrant: 2070

Marketplace works fine. No problems, yet.

:D
​
[Galaxy S I9000 Android Development] insty:
OK, just finished applying the lagfix.

JM5+Samset 1.9d+Lagfix(ext2)=2225 in Quad. Nice.
[Galaxy S I9000 Android Development] sandyph:
hm, installed 1.60

run for a couple of minutes and then it rebooted the phone

been 2+ hours and the phone is stuck in boot-loop, never get pass the Samsung Galaxy logo

try removed the battery and sd card still some problem

guess I'll wipe and try again with the never version