eViLrAcEr
Senior Member

Nope, just happened one day when I was testing kernel updates. Thought it was because of one of the patches to the kernel. So re-loaded kernels, format+restored system & data, re-applied ROMs, nothing fixed it. Finally did fix it though. Did tar backups of system & data, then re-flashed stock firmware, then flashed LK2.08 for root, then updated kernel, then restored system & data, and now no more pauses at database writes, and back to normal quadrant scores. Just wish I knew what the cause was ... maddening.

Hi, remember when you said you had problems with database writes in quadrant benchmark taking really long, 44 seconds? Well, it's happening to me now. Did you manage to fix it?

Try to use cache-cleaner, try again. Then clear dalvik-cache and try again.

Definitely not 44 seconds! Usually less than 5.

Yup. Use it daily. Cost of cars here in SG are frikkin ridiculous! And yes, entire line is visible on gmaps.

Makin' your own app? Cool! Been wanting to do an app that customizes performance settings, but just haven't found the time. Lemme know when your ready, be more than happy to test!

You don't need to modify the script, you only need to delete zImage and logo.png.

It wouldn't hurt, but in i5700 /cache is only used in recovery to hold images (for kernel, logos, etc). And it's usually re-formatted with major updates (e.g. from Alpha6.4 > Alpha6.5). So data corruption in /cache is a non-issue, and checking it in init.d script would just unnecessarily extend boot-up time.

Dude,

Need to send you updated an updated fsckdata. Just tested it on RFS, and it totally screwed up the filesystem! The e2fsck is tailored for EXT filesystems, so when run on RFS, all inodes get screwy, and unable to mount after that. Luckily I did a backup first.

Download the update zip from here --> http://www.mediafire.com/?ilc5eg56uyur48z and apply from recovery. It should over-write the existing "dangerous" script. But just to be safe, recommend that you delete /etc/init.d/03fsckdata b4 applying the zip.

... ch33rs

High scores in quadrant mostly helped by my use of ext2 for /data, since quadrant only checks this partition to derive I/O performance score. And since my /data is on ext2, there's no journalling, and I need to rely on regular file system checks to keep /data healthy. "fsckdataext" is actually just a simple /etc/init.d script which does that on every boot.

For 3D, I put in this line --> 0 0 android , into /system/lib/egl/egl.cfg which tells the kernel to use Android's default software engine for rendering 3D images, instead of Samsung's buggy FIMG driver for 3D engine. Will probably have to remove it when (if?) tom3q's driver is finally released.

Also running many experimental tweaks for battery, memory, cpu and i/o scheduling, so guess all of that helps too. But kinda makes my phone a little unstablE, and freezes up sometimes, and that leads me off on another quest to find out what caused it and on to further tweaks. Geeky? HELL YEAH!

Sequence does not matter, but recommended to rum CM update first, since it will automatically format system to RFS. Xmister's scripts should work well, so let me know exactly where you're facing problems ...