Welcome to the forums
.
1) I don't think many people are using that ROM yet because it's fairly new. Give it some time for a new ROM to catch on
. Thanks for spreading the word, though. I hadn't seen this one yet. Looks pretty nice.
2) There really isn't any conclusive evidence that setcpu profiles conflict with HAVS. It's using the smartass governor that conflicts with HAVS. Let me go into a little more detail:
The smartass governor is designed to scale the CPU frequency based on a number of factors, such as screen on/off state, battery life, CPU load, etc. These are things you would make setcpu profiles to control. If you make profiles using smartass, they will fight each other when trying to set the min/max frequency for certain conditions. That's a bad thing. Almost every other governor will make decisions on load, only (albeit, with varying levels of battery savings), so they can be used with profiles.
HAVS, on the other hand, does something different. Normally, on a stock kernel, or a kernel with stock behavior, a constant voltage is supplied to the CPU. Using HAVS, the voltage supplied to the CPU is variable. As the frequency goes up, so does the voltage, and vice versa. It has no control over what to set the frequency at. It's more reactive than proactive in that sense. Also, if you think about it, using HAVS along with the smartass governor is a safe combination. If that's the case, then why couldn't you use HAVS with profiles? it's almost the same thing, just in a different manner. Basically the combination you want to avoid is smartass with profiles. HAVS is fine with profiles, but stick with the conservative governor for best battery life (use on-demand for best performance, but worse battery life). All that being said, a lot of setcpu profiles can sometimes cause worse battery life. The reason is that it has to constantly poll and decide if it needs to activate different profiles. You might be better off with just a screen off profile. Obviously, ymmv.
3) How old is your phone? If you got it recently, and it's a HW version 0004, you might have issues with the camera. Have you tried to use the camera since you flashed that kernel? If it works fine, then ignore the rest of this. If you find that it doesn't work, the reason is that you have a newer Evo, which as newer camera hardware. For reasons we can't be *exactly* sure about (probably shortages or something), HTC started using different camera hardware. That being said, different kernel drivers are required. NA 4.1.9.1 was released before the new camera drivers were released. If you have issues with the camera, you need to flash either NA 4.3.1 or 4.3.2, as they include the new camera drivers.
