diff options
| author | Bookatz <bookatz@google.com> | 2017-09-27 14:09:55 -0700 |
|---|---|---|
| committer | Bookatz <bookatz@google.com> | 2017-09-29 15:10:47 -0700 |
| commit | c68a9d21b47f4c2fb65139c10d646145a9ab9a73 (patch) | |
| tree | bbcbc14ff9cb2c8a159eae59e1b29d692eb2e1b2 /tests/DynamicCodeLoggerIntegrationTests/src | |
| parent | 0121af618995f93dc0fff92e8b0e1b98c5106a9e (diff) | |
Statsd can pull kernel wakelock data
When statsd is told that it is time to poll data, it asks
StatsCompanionService to pull kernel wakelock data, receives the result
(as a string), and outputs it to screen.
Still to do:
1. don't use a string; use a parcel instead
2. don't output it to screen; do something useful instead
3. do more than just kernel wakelocks
4. pull data on demand, in addition to just on periodic pulling
Test: added setPollingAlarms to statsd.main and confirmed that kernel
wakelock information was written to screen
Change-Id: I35f5164420699dea1a00c9e530b938904f1d3055
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src')
0 files changed, 0 insertions, 0 deletions