[Galaxy S I9000 Android Development] Project1.exe:
Sure. What I do is mostly around the first thread link on OP. I would want to keep this thread about the releases only and no questions about why this and that isn't working so if you do have please direct them there. I hope you understand (you the one reading this ;) )

Anyway, I...

Make sure i'm rooted so i can access /system/framework, and I have the baksmali and smali jar files, and dexopt-wrapper ready.

Copy the framework folder to PC either thru SD card or whichever

Copy jar files and dexopt inside the folder

Open command prompt and navigate to the path of the folder

java -jar baksmali.jar -x android.policy.odex -o android.policy

Navigate to the newly created folder "android.policy" and go deeper up to "impl" folder where there are tons of .smali files

Edit LockPatternKeyguardView.smali thru notepad, looking for

.method private getLockScreenMode()Lcom/android/internal/policy/impl/LockPatternKeyguardView$LockScreenMode;

Read through the "logic" of the method implementation as it differs a little on every leaked rom. What usuallly happens here is that the phone retrieves and checks if there's a missed call or a text message (usually "if-eqz v0", meaning "if equal to zero"), and if it doesn't have one it jumps over to the next few lines to call the GlassLock method then jumps back to the line where the function returns to the OS. Otherwise it calls the PuzzleLock and just right after it is the same return call. What we need to do here is to copy the line of GlassLock and put it before the check condition, change that line's "GlassLock" text to "TapLock" (this is the key, the built-in lockscreen of android) and also copy the same return line just below it. This way the function returns right after calling TapLock and the remaining code below will be disregarded.

Save the file

Open "LockScreen.smali" and search for "return v4", and make sure you only find one instance. If there's only one, just rename "v4" to "v6". Save.

Go back to the command prompt and type

java -jar smali.jar android.policy -o classes.dex

This will create a classes.dex file

Open android.policy.jar in winrar (or some other that supports zip) and add classes.dex inside the jar as if it is a zip file. This file is now the de-odexed version which i again rar and upload.

We continue for the odexed/untouched roms. Rename the phone's android.policy.jar to something else (i used to just add a "u" suffix) and so goes for android.policy.odex.

Copy the newer bigger deodexed android.policy.jar and dexopt-wrapper to the phone /system/framework

Using terminal or ADB, get super user access and navigate to /system/framework and run

./dexopt-wrapper android.policy.jar patched.odex /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar

this will create a patched.odex file, which will be our new android.policy.odex but "unsigned"

Next, we still have our old android.policy.odex, we are going to copy the "signature" bits from it and write it in our patched.odex so android would think this is still a valid odex. Assuming that the name is android.policy.odexu(note the "u" suffix), run

dd if=android.policy.odexu of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc

if it doesn't work cause dd isn't found, use "busybox dd ..." instead. You'll know if it is successful cause there's a 20 in 20 out message. At this stage, we now have a new odex file. This is the odex file I rar and upload

Delete android.policy.jar(the deox one) and android.policy.odex (the original). Rename android.policy.jaru(the original) back to android.policy.jar, and patched.odex to android.policy.odex.

Reboot and cross your fingers you won't have to reflash

Of course, I test these files first on my phone before uploading, but still I'd like to raise DISCLAIMER if something wrong happens :D, this is a critical mission and you jump to this cause you know the risk :)