So I've been experiencing a strange problem that I've never had before... I've tried several kernels, and the same thing happens for each... I am on CM 6.1.2 currently, with SetCPU installed as well, with no profiles setup. I really prefer the OC settings nested in the ROM settings or in the Spare Parts app, but CM doesn't have it that I could see, so I installed SetCPU pretty much only to be able to track my CPU. I have tried toggling "set on boot" and intermittently using the "auto-detect" settings, and it hasn't worked. If I move the MAX slider down a little, then move it back to max, it works for a while before it reverts back to 600. I've used ChevyNo1's ULV latest kernels (2nd gen bootlooped for me), Slayher's 1.6 and 1.7 SLV kernels, cvpcs 1.1GHz LV (ran HOT)...each was either 1000 MHz or 1100 MHz, but after a little while (less than an hour) my SetCPU widget shows that the MAX is set to 600. I open up SetCPU, click on "autodetect" and then move the slider to the max like I've always done. 30-45 minutes later, right back where I was @ 600. I'm also on the ondemand governor by default, since chevyno1's latest kernels don't have interactive (unless somewhere knows where I can grab them!...?) Very frustrating, but I don't want to ditch CM over it, because it has some fun features. And the only ROM comparable in terms of features is UD which is bug hell imo (or heaven...depending on if you're the bug or a user...lol). Any help would be greatly appreciated. Does anyone else experience this problem? Know of any potential fixes? (I wiped 3x with install and am running the GB theme, but it has done it all along, not just with the theme. No other heavy-duty mods. Running LP instead of ADW.) Thanks in advance!!