[Galaxy S I9000 Android Development] zenkinz:
FREQUENTLY ASKED QUESTIONS

Does it have a recovery of some sort built in then. Maybe CWR..

Universal Lagfix Kernel (ULK) comes with Clockworkmod so yes it has the recovery function!

Does this works on my XXX ROM?

This kernel is compiled based on the available Froyo JPM source, so it'll definitely work on JPM-based ROM (custom or stock). For the rest of Froyo ROM, it has been reported that YA-OK is compatible with the following Froyo-based firmwares; JP6, JPO, JPP, JPD, JPA (all the above are based off Android 2.2 kernel) JPU ROM is however not supported at this moment. (See next FAQ point for more information)

Does this work on JPU-based ROM? When will you support it and/or Why does XXX kernel support JPU and not yours?

JPU-based ROM is apparently based on Android 2.2.1 firmware. Since the YA-OK kernel is based on version 2.2.0 kernel, there is a high chance YA-OK will not work well with JPU-based ROM. I have not tried personally myself but from what has been reported by other users, this does not work. Only when Samsung release the source code for JPU will YA-OK be able to support JPU (and later) ROM. As to why other kernel developers has already started releasing kernel to supporting JPU-based ROM, they are merely injecting lagfix and tweaks into the kernel through initramfs, instead of the tweaks that require source code modification (e.g. Overclocking, Undervolt, Display Fix, Kernel optimization through compiler optimization).

Please refer to supercurio post for more information

I installed this kernel on a JPO-based ROM. But it seems that there are no changes, reported RAM is 341 mb but Quadrant is about 1000.

You need to enable lagfix yourself by going to recovery mode, and select ULK option for all the possible choices of lagfix.

If I install this kernel on my rom, is it still necessary for me to install "voodoo"?

All the tweak and optimisation features mentioned in this thread are implemented within the kernel, so flashing or updating another kernel will lose whatever features found in YAOK kernel unless the said feature is also implemented in the other kernel. In the case of lagfix, it is important that if you flash another kernel over YAOK (for whatever reason), you need to be sure that kernel supports the relevant lagfix feature otherwise your phone

may

not boot.

I face alot of FC (Force close) with your kernel, what's wrong?

One of the common cause for the "FC" problem, particularly with custom kernel, is that you has chosen to enable the BIND option in the Lagfix setting. You should turn that off, and observe further if the FC issue stil persists.

How do I install this kernel?

First of all, make sure you have a compatible Froyo firmware (refer to above for a list of compatible firmware)

To install this kernel, download and unzip the zip file. Flash the .tar file using Odin, without selecting re-partition and you can omit the PIT setting.

After updating v1.31 (build 31), my Galaxy gets stuck at the bootscreen. What happens?

This is a sign of corrupted file system on the /system partition. Try this one time fix procedure

flash back v1.30 build 30

boot to recovery, do a backup

flash v1.31 build 31

boot to recovery, do a advance restore on /system

still at recovery, go to CWM and wipe davik cache

reboot your device (you may have to wait a few minutes for the system to rebuild the davik cache)

I was playing/running XXX game/application, the screen freezes halfway, what gives?

From experience, some applications (game or graphic intensive application such as video playback application) may not handle overclock feature very well, especially if the application rely solely on CPU (the main processor for computing process needs other than graphics), instead of GPU (the processor dedicated for graphic processing needs), to render graphics. In particular, Rock player seems to have problem handling video playback via software mode (instead of hardware), for HD video. This is understandable given that constant overclocking is usually undesirable. Remember our device can do dynamic CPU frequency scaling, which means it will never always run at overclocked frequency unless you manually set it to be.

Some games such as Asphalt were reported to freeze the device but from my observation, it is very rare it happens and I would usually would not bother about that. If it really bothers you, just set the CPU scaling threshold to 1GHz (instead of 1.12GHz or 1.2Ghz) via SetCPU app. Personally I won't bother and I think you should do the same. Afterall, it is probably a bad app out of many apps installed that is causing the problem, so why cripped your phone permanently for that? :)