It seemed with the OMAP architecture, the kernel needs to be matched to the userspace side, that's why 4.0.1 kernels won't work with 4.0.2/3 system images and 4.0.3 kernels won't work with older 4.0.1/2 system images. In the download section I have specified to only 4.0.3 images. I will update my thread info/title.
Sorry to break the news to you, as cool as coolbho3k is, his patches for CPU OC and UV both have problems, I originally used his patches in my older releases I have since reverted them both.
Coolbho3k's CPU OC has issues with 1.4 GHz... I have implemented my own @ 1.35 using different settings. My teammates have tested my version and it does not have any of the slow down lag issues at the highest speed.
Coolbho3k's CPU UV has issues as well. When you undervolt below min core vdd, the Dynamic Voltage Frequency Scaler (DVFS) will report error and stall thus not scaling down to lowest possible OPP state (this can be verified by all the errors in dmesg log). Once you stalled DVFS, all the benefits from Undervolt is immediately wiped out because you are stuck at a higher frequency. For now I have implemented my own undervolt which pre-UV @ -100mv across the board and again this has been tested under various conditions and it's been rock solid (no DVFS stalls).
I will address BOTH issues further with my subsequent releases.
As for as 4.0.2 compatibility, Google has skipped over 4.0.2 kernel source and released the absolute latest 4.0.3 (which includes 4.0.2 updates), so unless someone point out to me the exact patches needed for 4.0.2, there's nothing I can do for it. Either update to 4.0.3 using some unofficial AOSP builds by all these wonderful ROM developers or wait for Google to update to 4.0.3 officially.
Edited by faux123, 19 December 2011 - 02:31 PM.