Dumpsys Alarm查看应用程序唤醒命令

Dumpsys alarm查看应用程序唤醒命令：

在安卓adb root进如命令行后（没有root或者root群组的权限执行不了该命令），

1.


<span style="font-size:18px;">Pending alarm batches: 48</span>

当应用设置ALARM的时候，系统不会将这些ALARM在设置的准确时间内触发，而将用一种批量触发（batches mode）的策略，这样可以最小化地使系统从休眠状态醒来，最低程度地减少电池的消耗，即将一批触发时间接近的闹钟，压缩到某一个时间段内一起触发，而不是一个个触发，这样系统会很难休眠。

上面的字段则表示，有48个ALARM将被触发，dumpsys alarm 输出后，就是现实每一个闹钟的触发详情，如：


<span style="font-size:18px;">4293d3a8： 批处理模式下的内部ID号

num = 1：表示在该batch中，只有一个闹钟

start和end后的时间，表示自系统启动后，流逝的时间，该段时间粗略的表示，该闹钟会在start和end之间的时间触发</span>

RTC #0: Alarm{4293d358 type 1 com.android.chrome}

type=1 whenElapsed=1369361 when=+19s304ms window=-1 repeatInterval=0 count=0

operation=PendingIntent{429e4500: PendingIntentRecord{429dbbc8 com.android.chrome broadcastIntent}}

对于每一个alrm，都会有如上所示的三行解说


RTC：表示ALARM的类型，一般有：RTC_WAKEUP, RTC, ELAPSED_WAKEUP, or ELAPSED每个类型代表的意思就不赘述了，有兴趣的 可以自己查阅资料

#0：表示在该批量模式中，该ALARM的标号，取值0~n-1，n为该batch中alarm个数

4293d358 ：闹钟的内部编号

com.android.chrome：设置该闹钟的应用包名

type=1：闹钟的类型，即第一条中提到的几个闹钟类型

whenElapsed=1369361：该闹钟会在系统开机后，大概1369361后触发，这是大概时间

when=+19s304ms：该闹钟会在执行完这条dumpsys alarm命令后，19秒304ms后触发

window=：根据该alarm被调度的不同方法，设置不同的值，如果该alarm是 setExact()或setAlarmClock()方法调用的，该值为 AlarmManager.WINDOW_EXACT（=0），如果是 setInexactRepeating()，则赋值为AlarmManager.WINDOW_HEURISTIC（=- 1），然而A PI的level不同该值也不同，API小于19（KITKAT）的是WINDOW_EXACT，大于19的是WINDOW_HEURISTIC

repeatInterval=900000：改闹钟的重复频率，900000ms后重复，0表示不重复

count=：表示该alarm因为某些原因而被忽略了的次数，0表示没有被忽略过

operation=PendingIntent{...}：与pendingIntent相关，该intent被实例化后，可以发送广播，启动服务，或者启动Activity， 说白了就是唤醒应用的操作。

Broadcast Ref Count: 0

为了使得系统在醒来后，发送必要的广播帧，并且保证在所有的广播帧没有发送出去之前，系统不要进入睡眠状态，内部定义了一个变量：mBroadcastRefCount ，它的初始值是0，并且当需要发送的广播在队列配对的时候，该变量的值就会递增，发送一个广播后则递减，当减到0的时候，就会释放它持有的wakelock，而让系统进入休眠状态。

所以，Broadcast Ref Count: 0 表示在运行dumpsys alarm的时刻，该时刻并没有广播要发送。


top alarms：

根据应用的唤醒系统的时间排行，取最长时间的前十名，然后按照降序列出，有助于找出第三方app因为编程不规范，而导致极度耗电

Alarm Stats

列出所有系统中应用设置alarm的情况，可以排查设置的闹钟是否起作用了

格式如下：

com.example.someapp +1s857ms running, 0 wakeups:

+1s817ms 0 wakes 83 alarms: cmp={com.example.someapp/com.example.someapp.someservice}

+40ms 0 wakes 1 alarms: cmp={com.example.someapp/com.example.someapp.someotherservice}

com.example.someap：设置alarm的应用包名

+1s857ms running：系统总体被该应用所有的alarm消耗的时间

0 wakeups：设备被闹钟唤醒的次数

接下来是每个alarm的情况：

+1s817ms：该alarm消耗的时间

0 wakes：设备被唤醒的次数

83 alarms：alarm被触发的次数，重复闹钟，该值大于1

cmp={...}：alarm被触发，则启动该服务，服务实例位置在{}中声明

如果触发的是广播，则格式如：

android +4m51s566ms running, 281 wakeups:

+2m46s583ms 0 wakes 1224 alarms: act=android.intent.action.TIME_TICK

+1m25s624ms 89 wakes 89 alarms: act=android.content.syncmanager.SYNC_ALARM

+52s898ms 0 wakes 41 alarms: act=com.android.server.action.NETWORK_STATS_POLL

...

act=...：发送广播的名称

注意：-wakes 是指后面的alarm的次数中有多少次是将设备从休眠中唤醒的


Microsoft Windows [版本 6.1.7601]

版权所有 (c) 2009 Microsoft Corporation。保留所有权利。

C:\Users\wangbaoqun1>d:

D:\>cd adb

D:\ADB>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

HS8937QC:/ $ dumpsys alarm

dumpsys alarm

Current Alarm Manager state:

Settings:

min_futurity=+5s0ms

min_interval=+1m0s0ms

listener_timeout=+5s0ms

allow_while_idle_short_time=+5s0ms

allow_while_idle_long_time=+9m0s0ms

allow_while_idle_whitelist_duration=+10s0ms

nowRTC=1483279792773=2017-01-01 22:09:52 nowELAPSED=782053

mLastTimeChangeClockTime=1483279201060=2017-01-01 22:00:01

mLastTimeChangeRealtime=+3m10s339ms

Time since non-interactive: +19s736ms

Max wakeup delay: +2m0s0ms

Time since last dispatch: +33s262ms

Next non-wakeup delivery time: -21m55s934ms

Next non-wakeup alarm: +7s226ms = 2017-01-01 22:09:59

Next wakeup: +29s767ms = 2017-01-01 22:10:22

Last wakeup: -33s262ms set at -30s232ms

Num time change events: 1

mDeviceIdleUserWhitelist=[]

Next alarm clock information:

Pending alarm batches: 15

Batch{dbb22e2 num=1 start=789279 end=789279 flgs=0x1}:

ELAPSED #0: Alarm{a1ae673 type 3 when 789279 android}

tag=*alarm*:android.intent.action.TIME_TICK

type=3 whenElapsed=+7s226ms when=+7s226ms

window=0 repeatInterval=0 count=0 flags=0x1

operation=PendingIntent{f9d5930: PendingIntentRecord{24bc9a9 android broadcastIntent}}

Batch{36c8b2e num=1 start=811820 end=811820 flgs=0x1}:

ELAPSED_WAKEUP #0: Alarm{b3376cf type 2 when 811820 com.cleanmaster.mguard}

tag=*walarm*:com.cmcm.chargemaster.action.START_DETECTING_UNSTABLE_PLUG

type=2 whenElapsed=+29s767ms when=+29s767ms

window=0 repeatInterval=0 count=0 flags=0x1

operation=PendingIntent{636d85c: PendingIntentRecord{e6e5765 com.cleanmaster.mguard broadcastIntent}}

Batch{ba2c3a num=11 start=941210 end=1055391}:

ELAPSED_WAKEUP #10: Alarm{79ab0eb type 2 when 941210 android}

tag=*walarm*:*job.deadline*

type=2 whenElapsed=+2m39s157ms when=+2m39s157ms

window=+10m39s186ms repeatInterval=0 count=0 flags=0x0

operation=null

[email protected]

ELAPSED #9: Alarm{b7204e1 type 3 when 808579 com.cleanmaster.mguard}

tag=*alarm*:com.cleanmaster.screensave.intent.action.REPORT_INFOC_CMC_AVOID

type=3 whenElapsed=+26s526ms when=+26s526ms

window=+18h0m0s0ms repeatInterval=86400000 count=0 flags=0x0

operation=PendingIntent{40ed206: PendingIntentRecord{4f170c7 com.cleanmaster.mguard broadcastIntent}}

RTC #8: Alarm{c13d6f4 type 1 when 1483279779410 com.cleanmaster.mguard}

tag=*alarm*:com.ijinshan.common.kinfoc.ActivityTimer

type=1 whenElapsed=-13s363ms when=2017-01-01 22:09:39

window=+2h34m45s0ms repeatInterval=12380000 count=0 flags=0x0

operation=PendingIntent{4a90e1d: PendingIntentRecord{5b60892 com.cleanmaster.mguard broadcastIntent}}

ELAPSED #7: Alarm{80a5263 type 3 when 0 com.cleanmaster.mguard}

tag=*alarm*:android.scenemonitor.ap_hotspot_workeralarm

type=3 whenElapsed=-18s192ms when=--

window=+11m15s0ms repeatInterval=900000 count=0 flags=0x0

operation=PendingIntent{d116e60: PendingIntentRecord{e4d6f19 com.cleanmaster.mguard broadcastIntent}}

RTC_WAKEUP #6: Alarm{5281bde type 0 when 1483279764491 com.cleanmaster.mguard}

tag=*walarm*:com.cleanmaster.service.ACTION_UPDATE_CLOUD_CFG

type=0 whenElapsed=-28s282ms when=2017-01-01 22:09:24

window=+4h30m0s0ms repeatInterval=21600000 count=0 flags=0x0

operation=PendingIntent{645b1bf: PendingIntentRecord{8f108c com.cleanmaster.mguard startService}}

RTC #5: Alarm{c3ce3d5 type 1 when 1483279762461 com.cleanmaster.mguard}

tag=*alarm*:com.ijinshan.cleanmaster_check_apk_update

type=1 whenElapsed=-30s312ms when=2017-01-01 22:09:22

window=+18h0m0s0ms repeatInterval=86400000 count=0 flags=0x0

operation=PendingIntent{f1617ea: PendingIntentRecord{adaadb com.cleanmaster.mguard broadcastIntent}}

ELAPSED #4: Alarm{462a978 type 3 when 748928 com.cleanmaster.mguard}

tag=*alarm*:com.cleanmaster.NotificationDisturbAlarm

type=3 whenElapsed=-33s125ms when=-33s125ms

window=+4h30m0s0ms repeatInterval=21600000 count=0 flags=0x0

operation=PendingIntent{874e851: PendingIntentRecord{835c8b6 com.cleanmaster.mguard broadcastIntent}}

ELAPSED #3: Alarm{4d219b7 type 3 when 748850 com.cleanmaster.mguard}

tag=*alarm*:android.scenetrigger.workeralarm

type=3 whenElapsed=-33s203ms when=-33s203ms

window=+22m30s0ms repeatInterval=1800000 count=0 flags=0x0

operation=PendingIntent{bd4e524: PendingIntentRecord{54eb88d com.cleanmaster.mguard broadcastIntent}}

ELAPSED_WAKEUP #2: Alarm{8cdba42 type 2 when 641210 android}

tag=*walarm*:*job.delay*

type=2 whenElapsed=-2m20s843ms when=-2m20s843ms

window=+6m54s181ms repeatInterval=0 count=0 flags=0x0

operation=null

[email protected]

RTC #1: Alarm{40d2f90 type 1 when 1483279200000 com.emoji.keyboard.touchpal}

tag=*alarm*:com.cootek.usage.alarm_operation

type=1 whenElapsed=-9m52s773ms when=2017-01-01 22:00:00

window=+45m0s0ms repeatInterval=3600000 count=0 flags=0x0

operation=PendingIntent{77b5089: PendingIntentRecord{501388e com.emoji.keyboard.touchpal broadcastIntent}}

RTC #0: Alarm{c9488af type 1 when 1483279200000 com.emoji.keyboard.touchpal}

tag=*alarm*:com.cootek.presentation.action.CONFIG_UPDATE

type=1 whenElapsed=-9m52s774ms when=2017-01-01 22:00:00

window=+45m0s0ms repeatInterval=3600000 count=0 flags=0x0

operation=PendingIntent{33db4bc: PendingIntentRecord{3bf6c45 com.emoji.keyboard.touchpal broadcastIntent}}

Batch{ddc4f9a num=1 start=1090280 end=1090280 flgs=0x1}:

RTC #0: Alarm{22b00cb type 1 when 1483280101000 com.android.deskclock}

tag=*alarm*:com.android.deskclock.ON_QUARTER_HOUR

type=1 whenElapsed=+5m8s227ms when=2017-01-01 22:15:01

window=0 repeatInterval=0 count=0 flags=0x1

operation=PendingIntent{e8f60a8: PendingIntentRecord{c6f87c1 com.android.deskclock broadcastIntent}}

Batch{71fcb66 num=1 start=1090280 end=1090280 flgs=0x1}:

RTC #0: Alarm{f66dea7 type 1 when 1483280101000 com.android.deskclock}

tag=*alarm*:com.android.deskclock.ON_QUARTER_HOUR

type=1 whenElapsed=+5m8s227ms when=2017-01-01 22:15:01

window=0 repeatInterval=0 count=0 flags=0x1

operation=PendingIntent{2cddf54: PendingIntentRecord{aabdefd com.android.deskclock broadcastIntent}}

Batch{dcd37f2 num=1 start=1362315 end=1362315 flgs=0x5}:

RTC_WAKEUP #0: Alarm{e98be43 type 0 when 1483280373035 com.android.systemui}

tag=*walarm*:screen_off_app_clear

type=0 whenElapsed=+9m40s262ms when=2017-01-01 22:19:33

window=0 repeatInterval=0 count=0 flags=0x5

operation=PendingIntent{bd39cc0: PendingIntentRecord{f5c6df9 com.android.systemui startService}}

Batch{b72e13e num=1 start=1368880 end=1818880}:

ELAPSED #0: Alarm{47efb9f type 3 when 1368880 com.cleanmaster.mguard}

tag=*alarm*:android.scenemonitor.badchargingworkeralarm

type=3 whenElapsed=+9m46s827ms when=+9m46s827ms

window=+7m30s0ms repeatInterval=0 count=0 flags=0x0

operation=PendingIntent{6b5c4ec: PendingIntentRecord{7ecf0b5 com.cleanmaster.mguard broadcastIntent}}

Batch{237d34a num=4 start=2562461 end=3169687 flgs=0x8}:

RTC #3: Alarm{961b2bb type 1 when 1483281573181 com.cleanmaster.mguard}

tag=*alarm*:com.cleanmaster.service.ALARM_START_BG_SCAN_MEDIASTORE

type=1 whenElapsed=+29m40s408ms when=2017-01-01 22:39:33

window=+22m29s999ms repeatInterval=0 count=0 flags=0x0

operation=PendingIntent{ab043d8: PendingIntentRecord{2c8e331 com.cleanmaster.mguard broadcastIntent}}

RTC #2: Alarm{da7da16 type 1 when 1483280850358 com.emoji.keyboard.touchpal}

tag=*alarm*:com.cootek.abtest.ACTION_UPDATE_CONFIG

type=1 whenElapsed=+17m37s585ms when=2017-01-01 22:27:30

window=+22m30s0ms repeatInterval=1800000 count=0 flags=0x0

operation=PendingIntent{7eebf97: PendingIntentRecord{4d1c584 com.emoji.keyboard.touchpal startService}}

RTC #1: Alarm{f97816d type 1 when 1483280831598 com.emoji.keyboard.touchpal}

tag=*alarm*:com.emoji.keyboard.touchpal.INTERNAL_ACTION.noah_invest_temp

type=1 whenElapsed=+17m18s825ms when=2017-01-01 22:27:11

window=+22m30s0ms repeatInterval=1800000 count=0 flags=0x0

operation=PendingIntent{43f81a2: PendingIntentRecord{dd5be33 com.emoji.keyboard.touchpal broadcastIntent}}

ELAPSED #0: Alarm{267b5f0 type 3 when 1819687 android}

tag=*alarm*:com.android.server.action.NETWORK_STATS_POLL

type=3 whenElapsed=+17m17s634ms when=+17m17s634ms

window=+22m30s0ms repeatInterval=1800000 count=0 flags=0x8

operation=PendingIntent{737c769: PendingIntentRecord{5b815ee android broadcastIntent}}

Batch{a240a8f num=2 start=5022340 end=5322340 flgs=0x8}:

ELAPSED_WAKEUP #1: Alarm{62a411c type 2 when 5022340 android}

tag=*walarm*:com.android.server.ACTION_TRIGGER_IDLE

type=2 whenElapsed=+1h10m40s287ms when=+1h10m40s287ms

window=+5m0s0ms repeatInterval=0 count=0 flags=0x8

operation=PendingIntent{77c7125: PendingIntentRecord{213a2fa android broadcastIntent}}

RTC #0: Alarm{560c0ab type 1 when 1483282631596 com.emoji.keyboard.touchpal}

tag=*alarm*:com.emoji.keyboard.touchpal.INTERNAL_ACTION.auto_update

type=1 whenElapsed=+47m18s823ms when=2017-01-01 22:57:11

window=+45m0s0ms repeatInterval=3600000 count=0 flags=0x0

operation=PendingIntent{4285308: PendingIntentRecord{ea7faa1 com.emoji.keyboard.touchpal broadcastIntent}}

Batch{568f4c6 num=1 start=7389280 end=7389280 flgs=0x1}:

RTC #0: Alarm{f68bc87 type 1 when 1483286400000 android}

tag=*alarm*:android.intent.action.DATE_CHANGED

type=1 whenElapsed=+1h50m7s227ms when=2017-01-02 00:00:00

window=0 repeatInterval=0 count=0 flags=0x1

operation=PendingIntent{7397b4: PendingIntentRecord{2a89fdd android broadcastIntent}}

Batch{46f9752 num=2 start=11808753 end=13348973}:

RTC #1: Alarm{f0a9a23 type 1 when 1483290819473 com.cleanmaster.mguard}

tag=*alarm*:com.ijinshan.cleanmaster_get_versions

type=1 whenElapsed=+3h3m46s700ms when=2017-01-02 01:13:39

window=+4h36m30s0ms repeatInterval=22120000 count=0 flags=0x0

operation=PendingIntent{c8c7b20: PendingIntentRecord{145cd9 com.cleanmaster.mguard broadcastIntent}}

RTC #0: Alarm{5cbd69e type 1 when 1483286959693 com.cleanmaster.mguard}

tag=*alarm*:com.cleanmaster.mguard.SERVICE_PROCESS_CHECKER

type=1 whenElapsed=+1h59m26s920ms when=2017-01-02 00:09:19

window=+1h30m0s0ms repeatInterval=7200000 count=0 flags=0x0

operation=PendingIntent{f62b57f: PendingIntentRecord{f8e294c com.cleanmaster.mguard broadcastIntent}}

Batch{ce4ed95 num=2 start=14610726 end=25005724}:

RTC #1: Alarm{41abeaa type 1 when 1483293621446 com.cleanmaster.mguard}

tag=*alarm*:weather_alert_notification_manager_action

type=1 whenElapsed=+3h50m28s673ms when=2017-01-02 02:00:21

window=+2h53m14s998ms repeatInterval=0 count=0 flags=0x0

operation=PendingIntent{6f72a9b: PendingIntentRecord{51a8e38 com.cleanmaster.mguard broadcastIntent}}

RTC #0: Alarm{af3ce11 type 1 when 1483293600000 com.cleanmaster.mguard}

tag=*alarm*:com.cleanmaster.service.ACTION_LOCATION_UPDATE

type=1 whenElapsed=+3h50m7s227ms when=2017-01-02 02:00:00

window=+4h30m0s0ms repeatInterval=21600000 count=0 flags=0x0

operation=PendingIntent{4be1b76: PendingIntentRecord{493d577 com.cleanmaster.mguard startService}}

Batch{f0655e4 num=1 start=32589280 end=32589280 flgs=0x9}:

RTC_WAKEUP #0: Alarm{6363a4d type 0 when 1483311600000 android}

tag=*walarm*:ScheduleConditionProvider.EVALUATE

type=0 whenElapsed=+8h50m7s227ms when=2017-01-02 07:00:00

window=0 repeatInterval=0 count=0 flags=0x9

operation=PendingIntent{f687902: PendingIntentRecord{de65213 android broadcastIntent}}

Batch{5c4ec50 num=4 start=43284665 end=44848593}:

RTC #3: Alarm{ab92e49 type 1 when 1483322295385 com.cleanmaster.mguard}

tag=*alarm*:com.cleanmaster.service.ACTION_WEATHER_UPDATE

type=1 whenElapsed=+11h48m22s612ms when=2017-01-02 09:58:15

window=+9h0m0s0ms repeatInterval=43200000 count=0 flags=0x0

operation=PendingIntent{269234e: PendingIntentRecord{bd9fc6f com.cleanmaster.mguard startService}}

RTC_WAKEUP #2: Alarm{3947d7c type 0 when 1483321497763 com.mobisystems.office}

tag=*walarm*:com.mobisystems.office.notifications_chain

type=0 whenElapsed=+11h35m4s990ms when=2017-01-02 09:44:57

window=+18h0m0s0ms repeatInterval=86400000 count=0 flags=0x0

operation=PendingIntent{e5d6605: PendingIntentRecord{fb8265a com.mobisystems.office startService}}

RTC_WAKEUP #1: Alarm{b3f08b type 0 when 1483311585697 com.mobisystems.office}

tag=*walarm*:com.mobisystems.office.dailycacheprune

type=0 whenElapsed=+8h49m52s924ms when=2017-01-02 06:59:45

window=+18h0m0s0ms repeatInterval=86400000 count=0 flags=0x0

operation=PendingIntent{669f568: PendingIntentRecord{a535d81 com.mobisystems.office startService}}

RTC #0: Alarm{ec24e26 type 1 when 1483304959314 com.cleanmaster.mguard}

tag=*alarm*:ss_delay_task_action

type=1 whenElapsed=+6h59m26s541ms when=2017-01-02 05:09:19

window=+5h14m59s999ms repeatInterval=0 count=0 flags=0x0

operation=PendingIntent{3ef0a67: PendingIntentRecord{49d0014 com.cleanmaster.mguard broadcastIntent}}

Batch{5750bd num=3 start=87151578 end=123623675}:

RTC #2: Alarm{ef526b2 type 1 when 1483366162298 com.cleanmaster.mguard}

tag=*alarm*:com.cmcm.adsdk.ConfigMonitor_Action

type=1 whenElapsed=+23h59m29s525ms when=2017-01-02 22:09:22

window=+18h0m0s0ms repeatInterval=86400000 count=0 flags=0x0

operation=PendingIntent{fd7e603: PendingIntentRecord{540980 com.cleanmaster.mguard broadcastIntent}}

RTC_WAKEUP #1: Alarm{7ad3bb9 type 0 when 1483350207514 com.mobisystems.office}

tag=*walarm*:com.mobisystems.office.dormant_user_notification

type=0 whenElapsed=+19h33m34s741ms when=2017-01-02 17:43:27

window=+18h0m0s0ms repeatInterval=86400000 count=0 flags=0x0

operation=PendingIntent{70afbfe: PendingIntentRecord{ce8df5f com.mobisystems.office startService}}

RTC #0: Alarm{5b03dac type 1 when 1483349973730 com.cleanmaster.mguard}

tag=*alarm*:com.cleanmaster.service.ALARM_SHOW_FREQUENCE_ACTION

type=1 whenElapsed=+19h29m40s957ms when=2017-01-02 17:39:33

window=+14h37m40s665ms repeatInterval=0 count=0 flags=0x0

operation=PendingIntent{ddcda75: PendingIntentRecord{d16da0a com.cleanmaster.mguard broadcastIntent}}

Past-due non-wakeup alarms: (none)

Number of delayed alarms: 6, total delay time: +6m8s777ms

Max delay time: +5m25s575ms, max non-interactive time: +11m50s25ms

Broadcast ref count: 0

mAllowWhileIdleMinTime=+5s0ms

Last allow while idle dispatch times:

UID u0a51: -2m22s958ms

Top Alarms:

+17s621ms running, 0 wakeups, 2 alarms: u0a54:com.emoji.keyboard.touchpal

*alarm*:com.cootek.presentation.action.CONFIG_UPDATE

+16s145ms running, 0 wakeups, 1 alarms: u0a47:com.cleanmaster.mguard

*alarm*:com.cleanmaster.NotificationDisturbAlarm

+16s140ms running, 0 wakeups, 1 alarms: u0a47:com.cleanmaster.mguard

*alarm*:android.scenetrigger.workeralarm

+16s139ms running, 0 wakeups, 1 alarms: u0a54:com.emoji.keyboard.touchpal

*alarm*:com.emoji.keyboard.touchpal.INTERNAL_ACTION.noah_invest_temp

+16s127ms running, 0 wakeups, 1 alarms: u0a54:com.emoji.keyboard.touchpal

*alarm*:com.emoji.keyboard.touchpal.INTERNAL_ACTION.auto_update

+16s120ms running, 0 wakeups, 1 alarms: 1000:android

*alarm*:com.android.server.action.NETWORK_STATS_POLL

+2s616ms running, 0 wakeups, 2 alarms: u0a54:com.emoji.keyboard.touchpal

*alarm*:com.cootek.usage.alarm_operation

+930ms running, 0 wakeups, 4 alarms: 1000:android

*alarm*:android.intent.action.TIME_TICK

+354ms running, 0 wakeups, 1 alarms: u0a40:com.android.deskclock

*alarm*:com.android.deskclock.ON_QUARTER_HOUR

+175ms running, 1 wakeups, 1 alarms: u0a49:com.android.mms

*walarm*:com.android.mms.register.alarm

Alarm Stats:

1000:android +17s96ms running, 4 wakeups:

+16s120ms 0 wakes 1 alarms, last -12m35s386ms:

*alarm*:com.android.server.action.NETWORK_STATS_POLL

+930ms 0 wakes 4 alarms, last -33s981ms:

*alarm*:android.intent.action.TIME_TICK

+48ms 2 wakes 2 alarms, last -11m33s123ms:

*walarm*:*job.delay*

+46ms 1 wakes 1 alarms, last -9m51s714ms:

*walarm*:ScheduleConditionProvider.EVALUATE

+37ms 1 wakes 1 alarms, last -11m33s123ms:

*walarm*:*job.deadline*

u0a40:com.android.deskclock +354ms running, 0 wakeups:

+354ms 0 wakes 1 alarms, last -9m51s714ms:

*alarm*:com.android.deskclock.ON_QUARTER_HOUR

u0a47:com.cleanmaster.mguard +16s219ms running, 1 wakeups:

+16s145ms 0 wakes 1 alarms, last -12m35s386ms:

*alarm*:com.cleanmaster.NotificationDisturbAlarm

+16s140ms 0 wakes 1 alarms, last -12m35s386ms:

*alarm*:android.scenetrigger.workeralarm

+66ms 0 wakes 1 alarms, last -11m33s123ms:

*alarm*:com.cleanmaster.screensave.intent.action.REPORT_INFOC_CMC_AVOID

+46ms 0 wakes 1 alarms, last -11m33s123ms:

*alarm*:com.ijinshan.common.kinfoc.ActivityTimer

+40ms 1 wakes 1 alarms, last -11m33s123ms:

*walarm*:com.cleanmaster.service.ACTION_UPDATE_CLOUD_CFG

+40ms 0 wakes 1 alarms, last -11m33s123ms:

*alarm*:com.ijinshan.cleanmaster_check_apk_update

+40ms 0 wakes 1 alarms, last -11m33s123ms:

*alarm*:android.scenemonitor.ap_hotspot_workeralarm

+8ms 0 wakes 2 alarms, last -33s262ms:

*alarm*:com.cleanmaster.service.ACTION_LOCATION_UPDATE

u0a49:com.android.mms +175ms running, 1 wakeups:

+175ms 1 wakes 1 alarms, last -11m33s123ms:

*walarm*:com.android.mms.register.alarm

u0a51:com.android.systemui +6ms running, 1 wakeups:

+6ms 1 wakes 1 alarms, last -2m22s958ms:

*walarm*:screen_off_app_clear

u0a54:com.emoji.keyboard.touchpal +19s837ms running, 0 wakeups:

+17s621ms 0 wakes 2 alarms, last -12m16s422ms:

*alarm*:com.cootek.presentation.action.CONFIG_UPDATE

+16s139ms 0 wakes 1 alarms, last -12m35s386ms:

*alarm*:com.emoji.keyboard.touchpal.INTERNAL_ACTION.noah_invest_temp

+16s127ms 0 wakes 1 alarms, last -12m35s386ms:

*alarm*:com.emoji.keyboard.touchpal.INTERNAL_ACTION.auto_update

+2s616ms 0 wakes 2 alarms, last -12m16s422ms:

*alarm*:com.cootek.usage.alarm_operation

+48ms 0 wakes 2 alarms, last -11m33s123ms:

*alarm*:com.cootek.abtest.ACTION_UPDATE_CONFIG

u0a76:com.android.providers.calendar +55ms running, 3 wakeups:

+55ms 3 wakes 3 alarms, last -9m45s775ms:

*walarm*:com.android.providers.calendar.intent.CalendarProvider2

HS8937QC:/ $

原文地址：https://www.cnblogs.com/yejintianming00/p/9339701.html

时间： 2024-08-30 02:54:44

Dumpsys Alarm查看应用程序唤醒命令的相关文章

linux下查看进程（ps命令）

转自:http://www.jb51.net/LINUXjishu/151851.html Linux中的ps命令是Process Status的缩写.ps命令用来列出系统中当前运行的那些进程.ps命令列出的是当前那些进程的快照,就是执行ps命令的那个时刻的那些进程,如果想要动态的显示进程信息,就可以使用top命令.要对进程进行监测和控制,首先必须要了解当前进程的情况,也就是需要查看当前进程,而 ps 命令就是最基本同时也是非常强大的进程查看命令.使用该命令可以确定有哪些进程正在运行和运行的状态

linux下的进程管理（进程的基本了解及查看pstree,ps,pgrep命令）

Linux下的进程管理 1.什么是进程?程序是静态的文件进程是运行中的程序的一个副本进程存在生命周期(准备期,运行期,终止期)2.进程状态 状态 定义 R(TASK_RUNNING) . 可执行状态(RUNNING,READY)running:正在被处理 ready: 在排队, cpu处理进程个数有限 S(TASK_INTERRUPTIBLE) 可唤醒状态 :在cpu上使用的时间超时,此时被打入休眠状态,随着程序的调用会被唤醒 D(TASK_UNINTERRUPTIBLE) 不可唤醒状态 T(T

常用程序管理命令[转]

ps ps参数 [[email protected] ~]# ps aux <==观察系统所有的程序数据 [[email protected] ~]# ps -lA <==也是能够观察所有系统的数据 [[email protected] ~]# ps axjf <==连同部分程序树状态 选项与参数: -A :所有的 process 均显示出来,与 -e 具有同样的效用: -a :不与 terminal 有关的所有 process : -u :有效使用者 (effective user)

打开word时，出现“向程序发送命令时出现问题”的解决方法

本人用的是Windows 7的系统,这几天开word的时候,出现无法打开的问题,最后的提示框是"向程序发送命令时出现问题".上网查看之后,发现是模板文件Normal.dot出错,在关闭word时,在word中的插件都要往Normal.dot中写东西,如果产生冲突,Normal.dot就会出错,导致下一次启动word时,只能以安全模式启动. 下面是解决方法: 关闭所有打开的Word文档,将这条命令:%appdata%\microsoft\templates 复制到 开始 → 运行 的命令

查看进程之ps命令

引言 一般熟悉计算机的人员都知道,程序是保存在外部存储介质(如硬盘)中的可执行机器代码和数据的静态集合,而进程是在CPU及内存中处于动态执行状态的计算机程序.在Linux系统上,每个程序启动后可以创建一个或多个进程.例如,提供web服务的httpd程序,当有大量客户端访问web页面时,httpd程序可能会创建多个进程来提供服务.为了给用户更好的访问体验,需要随时关注后台进程的运行状态,以确保服务的正常运行. 而要对进程进行监测和控制,首先必须要了解当前进程的情况,也就是需要查看当前进程运行状态.

linux常用查看硬件设备信息命令

linux常用查看硬件设备信息命令  系统  # uname -a # 查看内核/操作系统/CPU信息  # head -n 1 /etc/issue # 查看操作系统版本  # cat /proc/cpuinfo # 查看CPU信息  # hostname # 查看计算机名  # lspci -tv # 列出所有PCI设备  # lsusb -tv # 列出所有USB设备  # lsmod # 列出加载的内核模块  # env # 查看环境变量  资源  # free -m # 查看内存使用量

linux查看网络链接状况命令netstat

linux查看网络链接状况命令 netstat 参数如下: -a 显示所有socket,包括正在监听的. -c 每隔1秒就重新显示一遍,直到用户中断它. -i 显示所有网络接口的信息,格式同“ifconfig -e”. -n 以网络IP地址代替名称,显示出网络连接情形. -r 显示核心路由表,格式同“route -e”. -t 显示TCP协议的连接情况. -u 显示UDP协议的连接情况. -v 显示正在进行的工作. 1. netstat -an | grep LISTEN 0.0.0.0的就是每

LInux 程序管理命令篇

工作管理 & 放在命令最后,可以把该命令加入后台执行 [Ctrl]-Z 将目前的工作丢到后台中 “暂停” jobs 查看目前后台的工作状况 jobs [参数] 参数: -l  : 除了列出 jobs number 与命令串之外,同时列出 PID 的号码 -r  : 仅列出正在后台 run 的工作 -s  : 仅列出正在后台当中暂停的工作 fg 后台工作拿到前台来处理 例  : fg %number bg 让后台的工作变成运行 例  : bg %number kill 管理后台当中的工作 参数 -

程序调试命令gdb

锁定线程 set scheduler-locking 1.要使用此命令,先用gcc -g编译程序,如:  $gcc -g test.c -o test  编译test.c源程序,输入此程序的调试版本test 2.调试程序  $gdb test //调试可执行程序test  $(gdb)start //使用程序test开始运行    列出指定函数的源代码,或列出指定行号开始的源程序  $(gdb)list 函数名  $(gdb)list 行号    backtrace(或bt) 查看各级函数调用及