it lowers the cpu speed with the screen off
I wouldn't argue with that. Especially since I can't prove you wrong
Doesn't explain the overclocking that occured for me though. It didn't start until I toggled the cpu button twice. Any ideas?
honestly i do not know... but i looked all over the chinese site for the answers to the CPU button after i did a whole night of testing, not being able to REALLY figure out what it does.
the chinese devs said plain and simple that it lowers cpu activity when your screen is off, so that background apps have less power draw.
i think it may UNINTENTIONALLY cause other things to happen, 100-200mhz difference either higher or lower with setCPU running or not running. But it was only designed to lower cpu draw @ screen off.