[HTC EVO 3D] mikeyxda:
OK fellow flashers. Here's mikey3.zip. As usual, just flash from recovery. I found some odd idiosyncrasies in the CPU settings and corrected them. The result is the smoothest CPU tweaks yet, better battery life, and now NO jumping of the CPU clock (see below).

Changes:

- Reduced sampling_down_factor from 4 to 2: with sampling already slowed to 20 cycles/sec, we don't want to reduce that too much further when running at high clock speeds. This change will ensure that the CPU is still sampled 10 times/sec when at the high clock speed.

- Reduced down_differential from 50 to 30: down differential should never be set higher than up_threshold! down_differential is how the system decides when to ramp the clock back DOWN. The decision to cut back clock speed is made when CPU usage drops below (up_threshold - down_differential). Now the up_threshold is 40 and the down_differential is 30, meaning the CPU will increase clock speed at 40% CPU usage and decrease when CPU usage drops below 10%. The "stock" ROM had these values set to 15% upthreshold and 50 down_differential. Since 15-50 = -35%, the system defaulted to some other value to decide when to reduce speed. I believe this is one cause for the clock being so jumpy and never picking intermediate speeds. With the new settings in mikey3.zip, all settings should now mesh well.

- Turned off two phase clock cycling: I don't believe the two phase setup is working properly with this ROM. If you've ever watched the CPU speeds in System Tuner, you may have seen the CPU speed jumping up to 1.13Ghz... a lot! That's because for whatever reason, the OS was picking the two phase speed seemingly randomly when in fact, that's the speed that is supposed to be used only when the screen is off. I changed the two phase speed from 1.13Ghz to 384Mhz, effectively turning two phase cycling off. Now go into System Tuner and watch your CPU speeds quietly hover at 384Mhz when nothing else is going on! This has completely solved the erratic up-clock spasms and now the clock speed finally behaves as you'd expect. It's possible that our changes to the mpdecision file and/or forcing the second CPU online is what made the two phase operation not work properly. In any case, this change should resolve the issue.

- Removed the Adrenaline tweaks: given the problems reported here (auto-fill in HTC email not working for example), I decided to have mikey3.zip put back the original files from DE 2.0.P1, thus getting rid of the Adrenaline tweaks. That will solve any problems you guys have been having but it'll also reduce your Quadrant scores. Note, however, that your Quadrant scores are only reduced because the "database" section of the test doesn't run as fast. Apparently the "tricks" that the Adrenaline tweaks used to make Quadrant fly through that database test break other things. Not worth it anyway because as far as I can tell, the Adrenaline tweaks only made that one Quadrant test run faster. They had no effect on any of the other benchmarks (like AnTuTu: my fave). The others will run just as fast as before.

Anyway, the above is giving me much better battery life and if you tap below the CPU speeds in System Tuner to check how long your CPU has been spending at each clock speed, you'll see that your CPU spends a lot more time now at the lowest clock speed. In addition, some of the intermediate speeds are now being used instead of being skipped and the clock speed is no longer jumpy, only ramping up when something is truly demanding the CPU.

Mike