[EVO 4G Android Development] hx3:
Hey everyone, this is my first post here but I've been lurking throughout this thread since it started. The Evo is my first Android device and I've been loving it. I've learned quite a lot about Android, adb, etc over the past few weeks but I've ran into a minor issue recently. My apologies ahead of time if this post gets to be a bit long, but I want to be as specific as I can be. Also, I haven't seen anyone else post anything similar to what I'm experiencing so I've gotten stuck.

I originally used toast's method to root and unlock NAND, and I was using the various DC roms with perfect results. I later followed whitslack's guide to starting over. That worked perfectly. Then wiped data/cache/dalvik-cache and flashed the DC 3.2.3 rom. Finally, I started looking into the higher frame rate kernals for nova panels. I flashed the first kernal that TrevE posted in this thread, but it broke my WiFi. I then nandroid'd back to a previous state and installed the 7/7 undervolted kernal that ffolkes provided to fix the WiFi. Well, I did that a little too early as I read a few hours later to only use the kernals that TrevE provided. Anyways, I once again nandroid'd back and flashed the 7/7 FIXED kernal from TrevE and all was fine again. Averaging 45fps in fps2d, five finger input in Dotty and WiFi is working fine.

My current problem is that there is a specific area on the screen that will not respond to touches. I never noticed this until I flashed to 3.2.3. I thought it could have been something with the frame rate kernal(s) I flashed, but I nandroid'd to a backup that used the stock kernal (with the DC 3.2.3 rom) and I'm still experiencing the unresponsive spot on the screen. What happens is if I tap on that specific area, any option directly above or below that spot will activate.

- In Dotty, when I move one finger across the "dead" area, two circles will then appear. One above the dead spot and one below it. (See screenshot)

- One example with menus is the "Phone Options" menu. If I tap on the "Silent Mode" option, then either "Power Off" or "Vibration Mode" will activate. (See screenshot)

- In DCUpdater, the "Check Now" button is right in the area where this dead spot is, so if I tap on it, then nothing happens. And seeing that there are no selectable options directly above or below that button, no action will go.

Now I've been able to get around this for the most part, but it can be kind of annoying and worrisome. Hopefully it isn't a hardware issue on my device and maybe the 3.5 rom that may come out to tomorrow will magically fix the problem. But does anyone have any insight towards this issue? I have done nearly everything I can think of on the front-end. I always have JIT enabled, but the same problem occurs when it's disabled. Vanilla lock screen from DCUpdater is being used, but same problem happens with the HTC lock screen. I'm just lost on what the problem could be right now. I haven't tried another full wipe yet. Any help would be greatly appreciated.

I also want to say thanks to the developers for their great work. My phone has gotten so much better (besides that pesky dead spot issue, but that's probably something I screwed up) and I look forward to any new updates that are provided. Also, many thanks to those in this thread that provide help to myself and others.