Admin Edit: Links removed at OP request. I believe they will be available elsewhere.
I have always ben very anti-setcpu, but profiles with this kernel really are a must if you want a smooth experience without constant freezing.
This is pershoots source code as of 04/25/2011 with added overclocking patches, all governors available, swap (requested) with a max scaling frequency of 1.708ghz (1708800) YOU SHOULD NOT HAVE THE USB MOUNT ISSUES present in flippy's kernel.
YMMV - Overclocking seems pretty unstable above 1.708 with the current state of the kernel (trust me i tried MANY different voltage variables, different schedulers etc..) that's why 1.8 and 1.9 are not supported, and will not be until they are stable for me again.
DO NOT SCALE ABOVE 1.516 without setting scaling governor to performance, or raising the min cpu frequency as you will experience lockups, setcpu profiles are useful in this situation. screen off profiles should have a MAX frequency of above 768 (this way when the screen goes back on it will ramp to the higher freqency THEN ramp back to the oc'd 1.708 without the jump from 245 causing a freeze) if you want to go with ondemand scaling and want the max at 1.708, you will have the most luck with min at 806 (even then it can and likely will freeze)
Edit: testing screen off profiles, it looks like you can pick whatever you want, currently mine us set to 245 min 368 max. No issues yet.
I have my device set for 368 min 1.708 max performance governor on boot and it hasnt frozen in the last two days. scaling through frequencies, or if the delta between min and max is too high, you may get a kernel panic and a battery pull will be required.
My particular setup (recommended):
on boot - 368 min, 1.708 max performance
screen off - 245 min 806 max ondemand (allows idle speed at 245)
battery < 50% 245 min 806 max ondemand
The same rules basically apply with this OC kernel that applied to flippy's. I'm not responsible for any damage that may result from your use of this kernel. yada yada yada.
you should retain wifi, gps, etc.. if not, flash it again, you did something wrong.
freezes? lockups? lower your clock speed, they shouldnt happen with any more frequency than with pershoots kernel if you stay at 1.516 and below. above that, if you experience a freeze, a last_kmsg wont help, the kernel failed to sync and panicked, there is nothing i can do about that. sorry.
wake-lag? i've gone over that, but here we go again:
generally with oc kernels:
oc+screen on/off animations+brightness > 50% = no wake lag
oc+screen on/off animations+brightness < 50% = wake lag
it isnt ideal, but get a program called screen filter from the market to apply a lesser brightness when above 50% so you dont experience the wake lag.
There is weirdness with benchmarks, if you've oc'd and you know it should be higher, reset the scaling options in cm settings and try again. It's very weird and i havent put together a full list of what causes the behavior, more as it develops i guess.
sometimes we go outside to get inside
My G2 Files