[HTC EVO 3D] mikeyxda:
Wow... some sleeping dogs woke up overnight. ;) Too much to quote so I'll just give my feedback on a few things:

Background

This all started with Lrod (thanks man!) playing with the mpdecision file. While I didn't see much of a performance boost in the ondemand/ondemand mpdecision file, I did notice that when it was missing, the system ran both CPU's and the phone flew and was more responsive. Having discovered that some parts of the OS expect the mpdecision file, I decided to try to find a way to get the "missing mpdecision performance" while still having it... by setting the CPU governor and other parameters optimally.

What I discovered when looking through the code is that there were conflicting values in the ROM. The post boot script sets CPU performance parameters to (someone's) recommended values. Then the sicktweaks init.d script overwrites some of those parameters with new values. Then the sysctltweaks overwrite them with a third set of values... all conflicting. So I decided to do several days of testing to find out which values were really best for this phone! What I found, some of which surprised me, has been fully documented in other threads. Since I've already been through the gory details, I won't repost those, but in a nutshell I found that running both CPU's continuously in conjunction with the proper ondemand governor settings, could drastically improve performance while at the same time improving battery life!

"Full on programmer"

I've never been one to toot my own horn, so I don't normally "announce" who I am but yeah, I'm a "full on programmer" who understands exactly how these CPU tweaks work. I'm relatively new (~6 months) to the Android scene but I do have plenty of Unix background and that's where a lot of this stuff comes from. While most of my work is Windows based, I'm enjoying the Android world more and more. If you want to see some of my work as proof of me being a "full on programmer" for 30 years, here it is.

sqlite tweak is the bomb

I hate disagreeing with Scott, but I couldn't disagree more. The sqlite files (ripped from the Adrenaline tweak), as far as I can tell, do nothing but "trick" Quadrant into giving a better score by making the one "I/O database read/write" test move faster. It has no other affect on performance that I've found, all other benchmarks give the same result with/without it, and it comes at the cost of busting auto-fill. If anyone has any evidence that it makes a performance boost outside of Quadrant, I'd like to see it. Besides, when most of us think of a fast, responsive phone, we're normally not concerned about fast SQL database operations.

my phone is so slow when I delete init.d and run the mikey tweaks

Well, that's not exactly surprising when you delete more than a half dozen tweaks and then just put one back. You've affected more than what the mikey3 tweaks do.

Make CleanROM clean with no tweaks

Actually, I don't think that's a bad idea at all! As I already found, there are multiple tweaks in DE 2.0 P1 that already conflict with one another. Having a solid base is a good thing, then we can put in what WE want.

Not optimal settings

Someone was arguing about settings not be "optimal for this device". Well, in the ROM itself we have three different people's opinions on what is optimal (init.post-boot.sh, sicktweaks, and sysctltweaks) and they all conflict with one another... the last at bat having the final say! Mikey3.zip takes care of that by having one set... a set that was tested with many hours of testing, observing the CPU and battery to find the right values so that the CPU would ramp UP when needed and DOWN when not. It also takes care of conflicts like the two phase governor not working as designed on this ROM, down_differential being set to a value that is (way) out of range, etc. I think mikey3.zip has this nailed because the phone screams and I'm getting the best battery life I've ever seen. If you have issues, try wiping (you can start with just cache/dalvik) and reflashing the ROM... then the mikey3 tweaks.

Testing

Even though I'm a "full on programmer", I don't claim to know more than ANYONE else. I'm just making a contribution. And not everything works the same on every phone. People have different tweaks, tweaks that when installed, might even overwrite my tweaks, etc. The best thing you can do is test it. If you want to try the "gabers" tweaks or any others, try them and then run System Tuner and watch the CPU frequency. Is it hopping all over the place when the phone isn't doing anything? Is your battery life better/worse? Is performance better/worse? Then decide for yourself. For me personally, what I saw with the as-installed DE 2.0 P1 ROM was that the CPU was spastic: hopping up to 1.5 continuously even when nothing (important) was going on. My tweaks take care of that by removing a number of conflicts and optimizing the up/down thresholds for the Evo 3D and this ROM. Also, having both processors idle at 384 leaves them both available to perform tasks and (with the other tweaks) allows them to run at 384 the vast majority of the time. Letting both processors stay online at idle, ready to jump at a task without being brought online first, is the biggest contributor to the speed increases we've seen in this discussion of the last few days, not the sqlite files! Both processors being online is what completely eliminates lag in the interface and allows the phone a lot more power especially when other tasks are running. And as I said, having both processors idle properly actually helps battery life.

Mike