It only bulks on the drag with the processor.
I'm not going to let all this talk go on without saying something.
While it is true that SetCPU runs as a background service
when profiles are enabled, it is very passive in its current state (as long as you keep the refresh interval on the CPU temperature profile down, but that was only introduced in the
last two versions) and should not affect performance at all.
The application runs
no code in the background when profiles are not enabled and the widget is not on the screen. When you use it, it sets the CPU speed and
leaves it alone. You may see it in your task manager, but it will be killed by Dalvik as soon as the Android system needs the memory. That's right, just having SetCPU installed cannot possibly cause any problems, as many people seem to assert. If profiles are disabled, it is certainly your ROM or setup, if profiles are enabled, it is almost certainly your ROM or setup. SetCPU is a very small part of the equation. Correlation does not imply causation.
I am planning to move parts of the code to the NDK to get additional performance benefits, but for now, the profiles service will not "bulk on the drag with the processor," whatever the hell that means.
As for the other concerns about 1.5.2x, the active widget was a huge mistake (I really regret pushing it out, though I can't pull it back now), and perhaps the Droid temperature sensor support was a mistake too. People just don't get that checking/updating something at a relatively fast interval will have detrimental costs to battery life. And the people who are asserting that their Droid is running hotter (oh noes!) don't get that
a different sensor will have different readings. There is a reason why I didn't push the active widget for so long. Someone else (who defaults the update interval to something like 30 or 60 seconds, effectively rendering it useless - cpufreq polls in the range of the thousands of
microseconds) gave people the idea that an active widget was such a good idea, though. The funny thing is that all of these detrimental effects can be reversed by removing a widget and changing a drop down list.
There's a common sense factor too, and many users just don't seem to get it. Yes, I am continuing to work on updates. Yes, SetCPU will get better. It's a complex beast that I admit is difficult for end users to grasp at first.
coolbho3k