yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] tomtor:
Fsck after boot?

Depending on the journalling fs, in most cases only metadata like directory and file creation is

is journalled, not the file content writes.

Even if this was not an issue, the ext2 metadata writes

would still be pending, either in the ext2 or loopfs buffercaches.

An fsck on the loopback image file is needed imho

after a unclean shutdown of the phone.

Using ext3 or ext4 would not help due to the loopfs on rfs layering.
[Galaxy S I9000 Android Development] RyanZA:
Most people do actually want their contacts, calendar and email to be blazing fast! Me especially. ;)

There are still no known issues of data loss - but if it is a problem for you, consider syncing them with google, or some other provider. I don't really know what would happen if you lost only part of /data/data, I doubt it would be any different from losing all of it. So it doesn't change much.
[Galaxy S I9000 Android Development] jd-omnia:
Wow. I got quadrant score 2160 with this fix. Initially the ddjg4 score is juat 898.
[Galaxy S I9000 Android Development] THUDUK:
Blimey...spent near on most of the morning get this done, must admit, being three days an Android virgin, I was a bit scared to say the least, but I have now managed to root, install all these things and now add this update file and so the msc script install, before hand I was got 900 odd on the Quadrant check, now I have just run it and I got 2024...but more impressive, I thought my new device was pretty quick before doing all this, now its balistic, paper toss opens instantly now, where as before it took about 5-10 seconds to get started.

Everything is just so zippy, you people on here are just way to clever...:)
[Galaxy S I9000 Android Development] RyanZA:
We don't actually have any idea how RFS works! So maybe, maybe not.

Next version will have the fsck for sure. At any rate, these are phones which are always connected to battery. Plus, this is very fast flash memory. I understand the concerns at a theoretical level, but I'm not convinced they make a difference on the practical side of using your device. Could be wrong... :D

It would be super if you (or anyone) could do some tests and help work this stuff out!
[Galaxy S I9000 Android Development] udovoodoo:
Thanx

I haven't tried this yet, however if the phone explodes I'll know that you were only trying to help ;)

Thanx and keep up the great work.
[Galaxy S I9000 Android Development] kalpik:
Can we get the fsck version quickly? :D
[Galaxy S I9000 Android Development] atul.dharne:
Thank you! You the man... Hat's off!

Quadrant score 892 before and 2083 now :)
[Galaxy S I9000 Android Development] engineer14:
any replies?

also now that our phones quadrant score has gone through the roof with this fix (even beat nexus one on froyo), do we still expect to see tremendous improvements like the nexus one had when changing from 2.1 to 2.2? so would our quadrant score become something like 3500+?

if so do we need seatbelts when using our phone?:):D
[Galaxy S I9000 Android Development] lyno:
Any idea how to get my marketplace working after removing mimocan's fix (I did the market fix too)?

Just stays on "Starting download...."
[Galaxy S I9000 Android Development] Tayutama:
From what i have read so far from people that are running JP3 (Froyo) and this fix they only get around 1800 in quadrant but remember JP3 is what i would consider an alpha built since JIT isn't optimised in it yet.
[Galaxy S I9000 Android Development] RyanZA:
e2fsck / fsck.ext2 / fsck.auto is missing from busybox... Makes this hard to put into a fix. Anybody got any ideas or am I just missing something?
[Galaxy S I9000 Android Development] Kanjtozzft:
ohh ye!!

thanks for that "update.zip" man!

went from 900 to 2228!

just standing ovations.

cheers
[Galaxy S I9000 Android Development] atul.dharne:
Had the same issue...was going to clear the Market cache...and then the download started after around 2 minutes...just did a reboot..everything's fine

Suddenly the Quadrant score has gone up to 2134 from 2083 now!!! i.e. 892 (Stock) ~> 2083 (RyanZA's lagfix) ~> 2134 (rebooting after the lagfix)

Fastening my seatbelt :)

Thanks RyanZA...was regretting migration from my HTC Desire...until today :)
[Galaxy S I9000 Android Development] RyanZA:
JIT isn't just not optimised yet. It's totally broken. :D
[Galaxy S I9000 Android Development] Gooofy:
This fix really turns the galaxy S into the jesus phone it was meant to be. Works like a charm.
[Galaxy S I9000 Android Development] kalpik:
Try mailing him? Stericson.g1@gmail.com

He's the developer of the busybox installer on the market. Please also tell him about the missing stuff in 1.18?
[Galaxy S I9000 Android Development] RyanZA:
Will do. Looks like the only option is gonna be to include an ARM binary for e2fsck inside this fix. I don't really want to do that, since I think it opens up a lot of room for errors...

I guess if I was gonna include that, I could also include binaries for EXT3 and other stuff... Still doesn't seem like a great idea though.
[Galaxy S I9000 Android Development] furstrated:
i'd say the average for jp3 is 1900, ive hit several 2k with highest at 2058. lowest is 1870, most o the time in the 1900 range
[Galaxy S I9000 Android Development] mikebeecham:
Really want to try this fix, but I'm so concerned about the future damage to my phone because of it.

Can I get any reassurances?
[Galaxy S I9000 Android Development] stianbert:
Hey. Have some problem installing this. have downloaded busybox from thread an activated usb debugging. Start lagfixme on my computer, but gets "error device not found" any help:)
[Galaxy S I9000 Android Development] Denizzje:
Unplug your phone's USB cable, go to 'device management' (I don't know the exact English title) on your computer, and delete the USB drivers already there. Then plug your phone back in and let the drivers reinstall. That fixed it for me :).
[Galaxy S I9000 Android Development] lafaya:
I did the n00b fix on the Girlfriend's Galaxy S for her and it worked perfectly. Thanks a lot man (that I didn't get shot!)
[Galaxy S I9000 Android Development] stianbert:
didnt work for me, but thanks:)
[Galaxy S I9000 Android Development] bogeyface:
Thanks to all the clever folk hereabouts. I'm about as noob as it gets when it comes to rooting, but following the steps on #417 and using the new beta of update.zip I'm getting a quadrant score of 2125

The phone is more responsive, slicker and show-offable than ever.
[Galaxy S I9000 Android Development] RyanZA:
Since this fix does less writes to the hardware than stock, it should in theory increase the lifetime of your device! :D

The only theoretical threat is to your data. No known issues in practice yet though.
[Galaxy S I9000 Android Development] magle:
Tried this on JF3, but i came across some issues.

I used this guide from post #417

Used the update.zip that's under "requirements" and followed everything and then came to installing the script. Did that and when it was done I was about to download quadrant but I couldn't open any aps, everyone was saying "force shutdown" (maybe not a direct translation because I don't use english in the phone). So i tried to restart it but nothing happened after the first white 2D samsung picture, so i did a factory restore from the menu from volume up+home etc. and now I'm back.

Anyone who knows what could've gone wrong? I have not flashed, rooted or installed any fixes before.
[Galaxy S I9000 Android Development] RyanZA:
Sorry, no idea. For an almost guaranteed fix, do this though (from a fully stock rom):

1. Install samsung kies / make sure you have drivers for SGS

2. Put the device into USB debug mode from Settings->Applications->Development

3. Plug your device in - do not select the option to mount the drives in the notification area on your phone.

4. Use this one click root - http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/

5. Mount the drives so you can copy the apk in the next step to your phone.

6. Download busybox from this link, copy the apk to your device, install it with My Files, Run the busybox installer app on your phone, select install and wait for it to say that you have the correct version - http://xdaforums.com/showpost.php?p=7574130&postcount=229 - You must have version 1.17.1 of busybox!

7. Unplug your phone, and then plug it back in. Do not mount the drives.

8. Run my one click lag fix

Reports show that following this exactly practically guarantees that the fix will work.
[Galaxy S I9000 Android Development] OlegZh:
Thank you, RyanZA, for your work. Did everything exactly how you described and it worked like it should. Score is 2154 or something. Even XDA App works much faster now. Running stock Eclair jm2.
[Galaxy S I9000 Android Development] Aafjes:
Incredible work!

Before the fix I had a score below 750. After the fix I had a score of 1975 :O.

More than doubled!!
[Galaxy S I9000 Android Development] sandyph:
hi Ryan

I follow all your step, the problem is when I run lagfixme from my PC, it finish really fast and dont seems to be creating any 1GB file (the available internal memory is still 1.85GB)

do you know what might go wrong ?

thanks
[Galaxy S I9000 Android Development] Tayutama:
You might wanna read this from the Vibrant forum: http://xdaforums.com/showpost.php?p=7589078&postcount=136

Looks like there is abit of corruption on the ext2 file we made.
[Galaxy S I9000 Android Development] Sledutah:
I was having the same problem.

After you connect and windows recognize the phone. Pull down the menu and click 'Turn off USB Storage'.

After that it worked great and now I'm getting results of ~2200 :D
[Galaxy S I9000 Android Development] beat.kitano:
I have a question. If i flash the phone with a new rom, i must reinstall the lag fix again? ;) Thanks.
[Galaxy S I9000 Android Development] RyanZA:
Yeah I'm working on making a nice easy fix with that included, and I'd like to use busybox for the e2fsck. I contacted Stephen from busybox, and he said he can have it by tonight. After that, I'll put up the busybox here (or try to include it directly in the fix) and then I can add e2fsck on boot. I'm trying to avoid putting binaries in this fix, and relying on others, so that everybody can see exactly what this fix is doing. :D

As far as actual corruption goes... it has yet to actually affect anyone as far as I know. No reports of lost data... I can keep saying this, Im gonna stop. :D

e2fsck is coming! Feel free to make a fix with e2fsck that won't blow people's phones up and I'll put it in the first post. :D
[Galaxy S I9000 Android Development] RyanZA:
Yeah, lagfix is completely wiped when you flash. That is why it is safe. :D
[Galaxy S I9000 Android Development] kalpik:
AWESOME! Waiting for it! I did the steps manually, but I guess ill use your script once the fsck is ready :D
[Galaxy S I9000 Android Development] RyanZA:
The fsck is just one extra line in the boot animation replacement script, really simple to add yourself. The hard part of the actual fsck binary itself. ;) Currently you need to compile it into a custom firmware. Obviously useless for most people, I feel. However, once it is added to busybox, it will be very simple. :D

Note: Any linux/arm gurus around? I tried compiling a static arm version of e2fsck, and then copying it into a stock firmware. In a custom compiled firmware it seems to work fine. When I run it on a stock firmware, I get

[1] Illegal instruction e2fsck.static

Any ideas?! :D
[Galaxy S I9000 Android Development] Tayutama:
How about getting Stephen to add mkfs.ext3 and mkfs.ext4 to busybox?

Was more if people wanted to use those instead of ext2
[Galaxy S I9000 Android Development] magle:
Got it working now, showin 2195, thanks alot, great work! :)
[Galaxy S I9000 Android Development] tomtor:
sync

I'd suggest adding a sync option to the ext2 mount options for the loopback device. This will not impact read performance and eliminates one potential cause for fs inconsistency (dirty ext2 buffers). Without it writes will be delayed both in the ext2 cache and in the underlying (journaling) cache of the native filesystem. Would be interesting to compare the speed scores with and without this sync option.

I assume the main speedup is just caused by the introduction of a read buffer cache, it's strange that the standard filesystem has no such implementation, would be easy to add for Samsung.

A potential cause for fs inconsistencies could be people rebooting their phone by keeping the power button pressed till it reboots. I don't believe the device executes a proper unmount/sync sequence when rebooting that way. One should use the power button popup menu and choose "power off"
[Galaxy S I9000 Android Development] JuWa:
There is a one big minus in this fix. It sucks my battery very fast dry. Anyone else having same issue?
[Galaxy S I9000 Android Development] anthonyytw:
This "noob" method is really great!!!!!!!!!!

Really thank you all the buddies here for turning my Samsung Galaxy S into an even more powerful machine!
[Galaxy S I9000 Android Development] FadeFx:
didnt hear of this yet, and i cant eaven think of this ever. i guess there somthing went bad on install and now you get an app to hang in background and not leting the phone sleep. the fix itselves should actually extend your battery life slightly...
[Galaxy S I9000 Android Development] bigbuffalo:
When I applied Samset ROM1.9b after applying the lagfix to JM5, the lagfix was still applied. I didn't have to re-apply it. How can that be?
[Galaxy S I9000 Android Development] RyanZA:
Yeah one step ahead of you! I did ask him for those as well. ;) We'll see if he comes through for us! ^^

Yeah.. I'm trying! Adding that option to stock roms is harder than it sounds. (Probably since I'm a bit clueless about cross platform linux binaries on ARM! Healp?)
[Galaxy S I9000 Android Development] millerliteguy:
Is there going to be a version for the US Tmo Vibrant..This lag and freezing up is getting annoying..Ready to return this because it's driving me Nuts!!!
[Galaxy S I9000 Android Development] tomtor:
Does replacing:

mount -t ext2 -o noatime,nodiratime,errors=continue /dev/loop0 /data/ext2data;

with

mount -t ext2 -o sync,noatime,nodiratime,errors=continue /dev/loop0 /data/ext2data;

in userinit.sh and createlagifx.sh not do the job?

Do we need a busybox mount command instead?

I also found this:

http://www.samsung.com/global/busin...memory/downloads/rfs_v12_application_note.pdf

rfs is quite well documented.
[Galaxy S I9000 Android Development] Bynar010:
er, because you didnt flash...you applied a update.zip - its not the same thing
[Galaxy S I9000 Android Development] RyanZA:
The fix should work on any and all galaxy S phones, since it does nothing variant specific. People in the vibrant forum confirm.
[Galaxy S I9000 Android Development] Civil Disobedient:
Did Tayutama's .zip.

first time, accidentally exited, but the icon was in the status bar, did not see "complete" message so i re-ran it. Nothing would load, force close on everything. quadrant, market, etc. thought maybe i should reboot, so i did so.

Now i have a brick.

Used quick boot to get into recovery, as nothing else seemed to work for me.

anyone's advice is greatly appreciated.

Edit: Also tried an uninstall first, gave me:

Permission denied

$
[Galaxy S I9000 Android Development] fantacies:
Have you seen in this xda-developers forum particularly with SGS I9000 stock firmware scoring Quadrant over 2k building an ext2 on top of rfs without oc before your nice work? I did follow through ykk_five's thread and realize who have been inspired DIRECTLY by his finding, tests, and experience sharing. I am not suggesting offer a credit to Linus Torvalds or whom we all learn Linux from. It takes merely a line or two, and that's what my understanding of the meaning of community. :)
[Galaxy S I9000 Android Development] faizalr:
trying to use this and it seems my device is damaged, can't see anything but black only.... I use DXJF4...

Please anyone help me, try to flash and it pass, but still in black screen...

Please please let me know how to fix it....
[Galaxy S I9000 Android Development] mekwall:
Supreme Tools - Lag Fix v0.1 BETA

Hey guys!

I've been working my butt off to build a combo between RyanZA and Tayutama's fixes. I think I finally managed and will now release my first version to the public.

I will not dedicate this to it's own thread just yet. I want permission from RyanZA and Tayutama since I've used much of their work, and also need some people to test it out so I can squash some bugs.

This release don't support any other fixes, so you need to make sure that you remove any other fixes before applying this one.

First off, this fix should be tested on a newly flashed phone for the best. I recommend that you do the following:

Do a nandroid and/or titanium backup of your current setup

Flash the I9000XWJM5 firmware

Flash the OC 1.2 v2.0 kernel by rasdeep

Download and unpack the ST-LagFix zip into its own folder

Run install_root.bat and follow the instructions

Run install_lagfix.bat and follow the instructions

Install SetCpu 2.0.2

If you also go with SamSet 1.9b rom (which I strongly recommend) the userinit script will zipalign all your apps on boot.

For testing purposes (i.e. Quadrant and other benching), set cpu governor to performance in SetCpu - for daily usage, I recommend using max 1200, min 400 with conservative governor for best balance. Also enable profiles, screen off at min 400 and max 600.

You should be getting very great performance and 2500+ in Quadrant after applying this fix (and rebooting a couple of times)! :cool:

Big thanks and credits go to: RyanZA, Tayutama, rasdeep, setenza, ChainDD, mimocan and ykk_five

Download can be found here: https://www.dropbox.com/s/ni0r0bwjgxc77zw#view:list

Disclaimer: You use this on your own risk. I do not take responsibility from any damage this might do to your phone. If you brick it, YOU did something wrong and it's entirely your own fault. Also, this is considered BETA-ware.
[Galaxy S I9000 Android Development] stepinmyworld:
i trully don't see a problem with the current fix... going from 2200 which ive made to 2500 isn't that much. the only bug i can think of is a method to clear the ext cache... after a long use of the phone, it's like full from eating cache and wants to barf so it acts sick. Is there a program to just clean partitioned cache with this fix?
[Galaxy S I9000 Android Development] darksaber73:
All went the smoothest way possible,my Galaxy is fast to a redicous degree. got 2288 in quadrant but the best thing is that everything opens instantly, and i mean everything. A big thank you to everyone involved, this is the greatest fix i ever experienced.
[Galaxy S I9000 Android Development] mekwall:
Cleaning cache is very easy... Just run adb shell and do the following:

rm -rf /data/dalvik-cache/*
[Galaxy S I9000 Android Development] RyanZA:
I really hate leaving out people in credits.. but I guess you're right. I'll credit mimocan and ykk_five in the first post, as I think they're the ones most directly involved in this fix. :)
[Galaxy S I9000 Android Development] RyanZA:
You (and everyone else) are granted full permission to use anything I have done with or without credit for anything at all. Go wild! :D
[Galaxy S I9000 Android Development] engineer14:
RyanZA, thanks for the fix, havent got a chance to test it out, waiting to get off work (why am i here on the job?)

quick question, since our phones will be so fast now, can i drive my phone to work instead of my car?
[Galaxy S I9000 Android Development] RyanZA:
Your phone will be so fast, that you won't even need to drive to work - your phone will have all your work done for you before you can even get there! ;)
[Galaxy S I9000 Android Development] mekwall:
Cool mate ;) same goes for my stuff! Btw. good work with the fix! I do however recommend using mount instead of symlink. Should be better performance, but a bit slower startup since it has to mount on every boot.
[Galaxy S I9000 Android Development] stepinmyworld:
when you say adb shell, can i use Android Terminal Emulator from the Market?

and do I type su first then

rm -rf /data/dalvik-cache/* ?
[Galaxy S I9000 Android Development] mekwall:
Yup. But remember that it will remove all the cached dalvik files so rebooting and starting apps will take longer because it has to generate the cache again.
[Galaxy S I9000 Android Development] SkulleD_PT:
PC 1 click method Lag fix used. Quadrant: 2000 :D

Major freaking win! Thanks! The guy that did this fix has the same value as samsung for putting such an awesome hardware piece :)
[Galaxy S I9000 Android Development] stepinmyworld:
it says rm failed for -rf, No such file or directory

.....
[Galaxy S I9000 Android Development] RyanZA:
Is there really a performance difference? I guess the OS has to look up the symlink each time? Good point, didn't really think about it!
[Galaxy S I9000 Android Development] RyanZA:
put a 'busybox' in front -- busybox rm -rf whatever
[Galaxy S I9000 Android Development] FadeFx:
there is a space between -rf and /data...
[Galaxy S I9000 Android Development] mekwall:
You get the same if you do: su -c "rm -rf /data/dalvik-cache/*" ?
[Galaxy S I9000 Android Development] mekwall:
Well... I guess it does since I got 2813 with my fix. I think that's the highest anyone have got so far ;)

I'm also thinking about doing a hybrid-fix with having some of the stuff on the external SD as well. Perhaps have system, app and app-private there? This would probably boost performance even more since you will be using two separate storage devices which would give you more bandwidth to work with... Also better for multitasking.

I'm also looking into that kernel with yaffs2 support that rasdeep released. Using yaffs2 instead of ext2 should boost it even more!
[Galaxy S I9000 Android Development] mekwall:
Woops! I guess that's my bad lol
[Galaxy S I9000 Android Development] RyanZA:
Hey guys

I have been playing around with using /sdcard (The internal SD card you see always, where all your data goes) as the data store.

This TECHTEST lag fix is identical to the regular lag fix, but instead of using 1GB in /data, it uses 3GB in /sdcard.

Performance scores are nearly identical between the regular lag fix and this one. This indicates to me that the RFS partition is very very similar to the VFAT32 partition for /sdcard. This fix has some annoying issues that I haven't been able to solve well enough to make this a real release of any kind, so I'm just throwing it out in it's most basic form for anybody who wants to play with.

Problems with this fix:

VFAT32 has no journaling - could be bad for data loss. I haven't seen any data loss yet in tests, but data loss is a lot more likely in this fix than in the regular one.

The data file is on /sdcard - this means it can be up to 18GB big!

This also means that when you mount your internal SD card onto your PC, your device will crash. ;)

Anyway, this fix is interesting for technical purposes (regarding speeds of VFAT32 and RFS), so here it is. (16GB of application data?! Woohoo.. uhh.. I don't think there are even enough applications available to use all of this. :( )
[Galaxy S I9000 Android Development] AllGamer:
i like this idea, to have the private stuff on the External microSD, makes it easier for manual backup, safety, wipe on deman, etc
[Galaxy S I9000 Android Development] Tayutama:
Ill take a look though your scripts :)

Btw you don't really need to ask me for permissions as all i did was make an update.zip out of RyanZA's stuff (And ofc added root + right version of busybox)

If you want ill supply you with an update.zip that only includes su, superuser.apk and the right busybox version as the one you included atm also include ase and the scripts which i'm working on cleaning abit up atm.
[Galaxy S I9000 Android Development] stepinmyworld:
i think this worked

busybox rm -rf /data/dalvik-cache/*

i typed this and it went to the next line but didn't say or do anything. i guess it worked lol... *shrugs* thanks you guys