[EVO 4G Android Development] DaKlown:
First I would like the thank the OP for bringing some attention to the issue. This thread seems to have started going in the wrong direction so I will make an attempt to clear some things up and shed some light on the situation with my findings. In my tests so far I cannot really find a combination of radios and pri to solve any of the problems mentioned in this thread. All my findings are using and testing aosp roms. Cm7 really but most aosp roms are based off of cm so this post should be helpful if you use an aosp rom and are having a unreleased pokelock caused by the dialer and/or high android system in the battery usage after phone calls. If you use a sense rom I do not recommend any of these fixes for you. If you use these on a sense rom you will probably mess something up and/or experience boot loops and lots of other problems. That being said lets get started:

Problem 1: The pokelock not being released after a phone call is made or received. This problem comes from the phone app and not the radios as far as I can tell from my tests.

Solution: http://www.mediafire.com/?xzw0zhonmnjw1xs

This file is a flashable zip of a new phone app that releases the wakelock after making a phone call the way its supposed to. I take no credit for this new phone app. It was made by Scott Brady (The same dev that fixed the mms problems on the evo in the cm nightlies about a month ago). I just got this from him. We haven't thoroughly tested it yet so please FLASH AT YOUR OWN RISK. Make a nandroid. I will say this though. In my current tests I have made about 40 calls with no pokelock and it seems to work wonderfully. The only reason I'm posting it early is because if you're like me and you know something is wrong then you want an immediate fix. Also using the killall command in terminal emulator or adb after every call can get tiresome... I have also tested with multiple radios In case anyone was wondering.

Problem 2: Android system spikes in the battery use in settings after a phone call is made or received.

Solution: I'm close but not finished yet...

Please read what I am about to say all the way through. What I have found is that the current proximity drivers for the evo are causing the android system in the battery use to go bonkers. I'm not really sure how much it affects your battery because it seems that it causes all your apps to not even show up in your battery stats. Proof? I have supplied two files in a zip:

http://www.mediafire.com/?mxks9k60shlckk5

THIS IS NOT A FLASHABLE ZIP. USE AT YOUR OWN RISK. One file is "sensors.supersonic.so" where I edited it so that android cannot find the drivers for your proximity sensor so it never comes on. The second file is "sensors.supersonic.so.bak" which is a backup of the original .so file that you can use if you want to turn your proximity back on. When I edited my sensors.supersonic.so file so the proximity wouldn't come on android system no longer spiked in my battery stats after a phone call!!! Also I tried to add a command to the build.prop first to disable the proximity sensor which would have been better practice but the command didn't work. Not sure if that's because cm overrides it or what. I can pretty much guarantee that this is an aosp problem and not a sense problem so if you use a sense rom you don't even need to worry about this. I doubt HTC has faulty proximity drivers on a stock rom... I could be wrong but I doubt it, they have screwed up in the past...

So what now? Well if you're on an aosp rom and the current proximity drivers work for you then you know what they say, "If it ain't broke don't try to fix it." For the rest of us I am in the process of trying to find some proximity drivers that don't make battery stats go haywire. Lets try to keep the thread relevant to findings so that we as a community can come closer to a fix instead of all the repetitive questions and things that don't help us get closer to a true fix... Don't forget the thanks button if you found this useful =P

Thanks for your time.

Edit: I would also like to add that I am on the most current radios, nv, and pri with no wakelock or spike in my android stats. And If you flashed the combo from the Calkulin thread you are probably missing the newest NV file because its not in there.