Quote:
Originally Posted by teradog
Very important!!
"running 29007 reference"
Last I knew that ROM has NO COOKIE at all!!!!!!!!
I'm not running any Cookie, and pl0323 is on 1.8.5 & says 2.0 WAS his problem...
This isn't rocket science folks... TONS of people report issues with 2.0, so TRY A DIFFERENT ROM!! 1.8.5 & see if your problems go away.
|
I have not had CHT2000 freeze my test devices, except for that task widget issue which is pretty documented now. My main issues with CHT2000 were usability glitches. Enough that I only run CHT185 on all my primary users devices for now.
Quote:
Originally Posted by teradog
My 2 cents on WiMoSpeed:
I see absolutely NO improvement over Msm7kcpuspeed & SetCPUspeed01d. In fact, @ 806 mhz the TP2 locks up faster with wimospeed than with msm&setcpu. I can run very stable @ 786 with msm7kcpuspeed/setcpu, but tp2 eventually locks up with wimospeed.
Those that know me know I test thoroughly & push my TP2 to the limits... I rebooted at least 60 times testing this stuff. However, another may have different results based on their ROM/Radio/carrier/cabs/usage/etc..
The few I've seen reporting increases in speed have come from OCT... not msm7kcpuspeed/setcpu.
My opinion only...
|
For me using WiMoSpeed on these Energy ROMs is mainly out of convenience and quick stability. I no longer have to do registry imports/exports with OCT or mess around with funky mscr scripts with MSM7. I run a simple command line call with the value I want and I'm done. It's entirely possible that MSM7 can engage slightly higher OCs since it an active app vs the passive nature of WiMoSpeed.
I must admit it is cool that you took the time to see which of the current 3 OC apps works best for your setup and report it... might help others to consider the time investment vs gains.