**UPDATE 20/10**  This has been superceded by a new, better fix.  See here - http://hemorrdroids.net/galaxy-s-voodoo-now-on-froyo/

I decided last night to take the plunge and give FroYo a try on my Galaxy S.  I’d left it a couple weeks because the initial ROM’s seemed very buggy (like no working WiFI!).  We’re now on to the 3rd leak of FroYo on the SGS but what really tempted me to flash was a new speed fix.  I’d applied the one I posted about previously which did a good job, but this one is even better and even easier!

As before, this isn’t my own work, but Paul over at MoDaCo and a guy from XDA Developers.  They’re homing in on the cause of lag on what is technically a superior device.  My understand is the problem boils down to Samsungs poor implementation and use of the in built RFS file system. Here’s what the speed fix does, explained by it’s creater RyanZA -

Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc. It allows only 1GB for application data at this stage, down from the 2GB of application data when running stock.

You can see from the image of the benchmark done using Quadrant, this puts the Galaxy S into a different league of performance, even against the Nexus One running FroYo.

So, read on to find out how we move our SGS to FroYo and then apply this with no partitioning of your SD Card, in around 10 minutes!