[Android Apps and Games] nobnut:
Excellent.

That being the case, what is the best way to test I wonder? I have something causing momentary wake every minute or so. I was going to root it out last week but then I saw this thread and thought that whatever I had would be a good test for this facility. Anyway here is the outcome of the latest test:

deepsleepdetective.txt

07:31:07 up 20 min, load average: 2.98, 2.09, 1.41
07:31:49 up 21 min, load average: 2.54, 2.10, 1.44
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:32:31 up 22 min, load average: 1.33, 1.84, 1.38
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:32:52 up 22 min, load average: 1.53, 1.85, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService radio-interface
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock
07:33:13 up 22 min, load average: 1.18, 1.74, 1.37
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:33:35 up 23 min, load average: 0.91, 1.65, 1.34
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:33:36 up 23 min, load average: 1.48, 1.75, 1.38
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:33:56 up 23 min, load average: 1.55, 1.76, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:33:57 up 23 min, load average: 1.55, 1.76, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:33:58 up 23 min, load average: 1.55, 1.76, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:33:58 up 23 min, load average: 1.55, 1.76, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:33:59 up 23 min, load average: 1.55, 1.76, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:33:59 up 23 min, load average: 1.55, 1.76, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:34:00 up 23 min, load average: 1.55, 1.76, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:34:00 up 23 min, load average: 1.43, 1.73, 1.38
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:34:23 up 24 min, load average: 1.46, 1.72, 1.38
name expire_count wake_count
"sec-battery-monitor" 0 22

ApmCommandThread AudioOutLock KeyEvents PowerManagerService client-interface efsd-interface gps-lock radio-interface
07:34:44 up 24 min, load average: 1.46, 1.70, 1.39
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:35:01 up 24 min, load average: 1.26, 1.64, 1.37
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:35:30 up 25 min, load average: 1.56, 1.67, 1.38
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents PowerManagerService client-interface efsd-interface gps-lock radio-interface
07:36:04 up 25 min, load average: 1.23, 1.58, 1.36
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:36:17 up 25 min, load average: 1.03, 1.51, 1.35
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents PowerManagerService client-interface efsd-interface gps-lock radio-interface
07:36:29 up 26 min, load average: 1.18, 1.53, 1.35
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:36:38 up 26 min, load average: 0.99, 1.48, 1.34
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:37:08 up 26 min, load average: 1.49, 1.54, 1.36
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface
07:37:20 up 27 min, load average: 1.26, 1.49, 1.35
name expire_count wake_count
"sec-battery-monitor" 0 22
PowerManagerService
ApmCommandThread AudioOutLock KeyEvents client-interface efsd-interface gps-lock radio-interface

DSD-BootReport.txt

---------------------
---------------------
Date | 5004 |
Time | 4968 |
DS against total uptime | 100% |
DS against total DSP time | 100% |
Total Display off time | 83 minutes |
---------------------
---------------------

DSD-Shutdown.txt

08.40
136
%DISPOFFT
6-29-11
2376
09.01
1254
%DISPOFFT
6-29-11
13932

DSD_Uptime.txt

4860
27average:1.45

Even though you can see that something is causing wake from screenshot, nothing at all has been written to the deepsleepdetective.txt. I have attached a screenshot I took of the txt file I took before the last test. The times still refer to 07.37 etc (this test was run between approximately 09.15 and 09.30).

Perhaps this falls within your parameters above, but maybe there is a loophole where some valid 'awake' data is not being stored?

EDIT: Another point. I do not have AdHoc contained as a task within v3.0.