I noticed my phone (running 0722 build, w/ kernel #53, ondemand CPU 245-600) had good drain after reboot & full battery charge and idling with everything off except 3G data on (Section 1 in graph). This was about 1%/hour drain.
Then I turned on GMaps w/ navigation and normal usage with light texting & a few phone calls (Section 2 in graph). This seemed normal for active use. But then after that is when it gets odd.
Section 3 was idling overnight while I was sleeping (everything off, except 3G/phone on). This doesn't seem right because the Awake & Screen on detected it was on all the time, but the phone was really off. And the battery drain was about 2%/hour. I did a logcat at the end of this section.
--------- beginning of /dev/log/system W/InputManagerService( 118): Window alr - Pastebin.com
Finally I rebooted the phone, which seemed to allow it to resume to 1%/drain, but the awake/screen on was still detected as on. Keep in mind this was still with ondemand governor and default 245/600 CPU. I did a second logcat at this point.
--------- beginning of /dev/log/main I//system/xbin/run-parts( 59): run-parts - Pastebin.com
Does anyone know what could explain the constant awake & screen on phenomenon and worse battery drain after using navigation & text/phone calls? Sections 3 & 4 should've been the same as section 1. I checked the services and no extraneous app services were running (wifi, BT, GPS, screen all off). I even killed the maps app before the overnight idling to make sure it was stopped.
I've just flashed the newer 0725 build and will report back if anything's different, but I don't think it would be much different since it was mostly USB tethering fixes right? Seems like something grabbed the CPU and constantly drained it while idling.
UPDATE: I'm beginning to suspect it's a problem with the Google Maps app (navigation is still in beta after all). I remember battery meter did read Maps was using about 40% of the juice, higher than the usual cell standby & phone idle. On 0725 build now and after 6 hrs unplugged, it's still at 97% left. I have 3G,wifi,GPS,BT all off except a couple of test calls, a quick web email check & a few random battery stat checks in this time. I'll try to enable things one at a time to see what triggers the massive drain.
UPDATE: It's the turning on and off of GPS that causes it to go into high-drain mode. The reporting of awake-lock seems like a bug because in a later fully charged rom, the drain was modest, but the stats still reported the screen being locked.