Well... Can't use ext2 on stock DX kernel, won't mount partitions as ext2 either through loopback or from physical media. Soooo, I tried with ext3 through a loopback (basically the same as the Galaxy S lagfix with ext3 instead). Surprisingly, there was improvement, though not much:
Apparently the loopback interface itself does some write caching... But still stuck with ext3, and that damn journal...
I then went back and tweaked the fs parameters, and put the journal on a ramdisk (rebooting is tricky...), and got some even more surprising results...
Just as a note, apparently, the loopback is caching so much (or at least long enough) for this benchmark to effectively only be writing/reading ram with the tweaked fs. I get only slightly higher scores (~300) if I mount quadrant's data dir to tmpfs. More evidence the test is broken, without even outright cheating with tmpfs...
I also patched in a working version of stagefright (yes, quadrant tests it, and it plays h.264 just fine without sync issues... even records video and plays it back). It has many other problems, but so does opencore... Lagfix/Tweaked Lagfix:
Does it "feel" any faster? Actually yea, yea it does. Most of the standard android "hiccups" are gone, unlock is super fast, and there's no real lag on the home screen. Is it worth the trouble for the DX? No, not really. The DX doesn't suffer from nearly the same level of lag that the Galaxy S phones do, and this hack is a _lot_ more work on a DX. (and I bricked mine 3 times getting the ramdisk to initialize a journal properly on boot... that was a bit of a *****)
I just rooted and voodoo lagfixed and did 3 runs with Quadrant, an hour in between. I also closed all apps (except for the 2 auto-starting apps) before doing the test and this is what I got...
Hee is a lil explanation about it taken from the project voodoo site
On a side note between me my wife and friends I have access to most of the heavy hitter android phones and none of them out perrform my fascinate not the DX DI D2 Evo4G or Nexus1. Wait till the color fix comes out too.
Lagfix, Galaxy S Lagfix that work
Galaxy S hardware is different from previous generation’s Android phones.
To extend /data partition, the place where all your apps are installed and personal data are stored, Samsung use 2GB from the internal SD card.
There’s nothing wrong with this approach, but they use the proprietary RFS filesystem they build as a legacy FAT, adding journalisation and POSIX permission. Both are required to run safely Android.
Unfortunately, this filesystem tries too hard and don’t provide a consistent experience with many applications installed or a few days uptime.
And here comes Voodoo lagfix to the rescue
By replacing the faulty RFS filesystem with the Linux-standard Ext4 filesystem, Voodoo lagfix simply restores I/O performance and global user experience of the Galaxy S to what it should have been to begin with.
And the performance level is awesome
Last edited by khaf; 10-12-2010 at 03:44 AM.