wakelock查看

count: wakelock被激活次数。如果该数值比较大，说明它处理了大量的事件，而该数值比较小则表示，花了很长的时间来处理这些事件，或wakelock没有正确释放。

expire_count：超时的wakelock的次数。

wake_count：

active_since：当前状态下，仍持有锁的wakelock，

total_time：wakelock 锁持有的总时间，该时间最重要。

sleep_time：wakelock 在系统休眠的时候锁持有的时间

max_time：wakelock单次花费最多的时间。

last_change:最后记录的时间。

count, tells you how many times the wakelock was activated. If a

wakelock prevented suspend for a long time a large count tells you it

handled a lot of events while a small count tells you it took a long

time to process the events, or the wakelock was not released properly.

expire_count, tells you how many times the timeout expired. For the

input event wakelock in the android kernel (which has a timeout) an

expire count that matches the count tells you that someone opened an

input device but is not reading from it (this has happened several

times).

wake_count, tells you that this is the first wakelock that was

acquired in the resume path. This is currently less useful than I

would like on the Nexus One since it is usually "SMD_RPCCALL" which

does not tell me a lot.

active_since, tells you how long a a still active wakelock has been

active. If someone activated a wakelock and never released it, it will

be obvious here.

total_time, total time the wake lock has been active. This one should

be obvious.

sleep_time, total time the wake lock has been active when the screen was off.

max_time, longest time the wakelock was active uninterrupted. This

used less often, but the battery on a device was draining fast, but

the problem went away before looking at the stats this will show if a

wakelock was active for a long time.