Does /sys/devices/platform/i2c_omap.2/i2c-0/0-0045/disable_kp (n810) exist and does it lock/unlock keys when writing 1 and 0 to it? Does writing 1 and 0 to /sys/devices/platform/omap2_mcspi.1/spi1.0/disable_ts lock (n800 and n810) and unlock the screen?
Let me know if this is still a problem after I release the new code, and if it is try to let me know what conditions cause it.
Kroll mentioned some abnormal battery drain a couple releases back and I optimized a few of the hardware polls but none of the changes shouldv'e made any noticable changes in battery life. The loop goes to sleep when screen is off or ASUI is unmapped and only dbus signals will wake it briefly. You can test this by installing the debug binary and watching its log while the screen is off or ASUI is unmapped.
For a couple months now I've had a 0.4%/minute drain, with no load and screen off, after turning off wifi or entering flight mode. Even happened after I reformated and hadn't yet installed ASUI. I had to reboot every time I used wifi. Recently found out that if I stop ssh and all wifi services the problem goes away. So your 0.8%/hour is nothing!