Android Event Log

北境王

于 2023-10-13 11:06:47 发布

阅读量988

点赞数

文章标签： android java

本文链接：https://blog.csdn.net/fenghanfenghan/article/details/133806609

版权

Android Event Log
日志是极好的，可以及时记录程序的运行状态信息，和出现异常的时候的异常状态信息，是程序运行的后知后觉的晴雨表。它可以给我们查找问题指明方向，带来查找问题的便利。因此，可以读懂Android Event Log显得很重要。为了让您可以懂它，使用它，我来做一个小小总结。

event log:
09-06 16:18:46.197 1632 2405 I am_proc_start: [0,4394,1000,com.android.usbsecurity,broadcast,com.android.usbsecurity/.UsbSecurityReceiver]

log-tag tag-values部分是下面这部分：
am_proc_start: [0,4394,1000,com.android.usbsecurity,broadcast,com.android.usbsecurity/.UsbSecurityReceiver]
根据am_proc_start这个关键字，在/system/etc/event-log-tags文件或在…/server/am/EventLogTags.logtags中找到它的定义：
30014 am_proc_start (User|1|5),(PID|1|5),(UID|1|5),(Process Name|3),(Type|3),(Component|3)

根据上面这个定义我们就知道event log的tag-values这个值的含义了，放在一起对比下：
am_proc_start
(User|1|5),(PID|1|5),(UID|1|5),(Process Name|3),(Type|3),(Component|3)
am_proc_start: [0,4394,1000,com.android.usbsecurity,broadcast,com.android.usbsecurity/.UsbSecurityReceiver]

含义：
进程启动: pid=4394,uid=1000, 进程名=com.android.usbsecurity, 类型broadcast,相应组件=com.android.usbsecurity/.UsbSecurityReceiver

1 Android Ecent log 常用tag说明
adb logcat -b events > eventlog
1.1 查看前台的activity
adb logcat -b events -s am_on_resume_called
Android R 11
screen_toggled：屏幕电源状态信息
其中 0 表示屏幕关闭，1 表示屏幕打开，2 表示已锁屏。
10-18 15:05:04.383 992 992 I screen_toggled: 1
10-18 15:05:07.010 992 992 I screen_toggled: 0
10-18 15:23:15.063 992 992 I screen_toggled: 1
10-18 15:23:25.684 992 992 I screen_toggled: 0
10-18 15:36:31.623 992 992 I screen_toggled: 1
10-18 15:36:37.660 3283 3283 I screen_toggled: 2
状态栏没有下拉：
04-27 15:20:57.639 1098 6137 I notification_panel_hidden:
下拉状态栏完全展开：
04-27 15:21:45.970 1098 11208 I notification_panel_revealed: 5
Back按键：
KEYCODE_BACK = 4
04-27 15:28:23.540 1393 1393 I sysui_multi_action: [757,931,758,4,759,4,932,0,933,0] // 最后的0是按下
04-27 15:28:23.542 1098 5988 I sysui_multi_action: [757,803,799,key_back_down,802,1] // 按下
04-27 15:28:23.600 1393 1393 I sysui_multi_action: [757,931,758,4,759,4,932,0,933,1] // 最后的1是抬起
04-27 15:28:23.605 1098 5988 I sysui_multi_action: [757,803,799,key_back_up,802,1] // 抬起
HOME按键：
KEYCODE_BACK = 3
04-27 15:24:04.764 1393 1393 I sysui_multi_action: [757,931,758,4,759,3,932,0,933,0] // 按下
04-27 15:24:04.853 1393 1393 I sysui_multi_action: [757,931,758,4,759,3,932,0,933,1] // 抬起
Power按键：
04-27 21:27:05.063 1098 1315 I intercept_power: [ACTION_DOWN,1,0] // 按下
04-27 21:27:05.081 1098 1098 I screen_toggled: 1 // 屏幕打开
04-27 21:27:05.164 1098 1315 I intercept_power: [ACTION_UP,1,0] // 抬起
2 Notification Event Log解析

notification_enqueue
notification_cancel
notification_canceled
notification_cancel_all
notification_panel_revealed
notification_panel_hidden
notification_visibility_changed
notification_expansion
notification_clicked
notification_action_clicked
notification_visibility
notification_alert
notification_autogrouped
notification_unautogrouped
- Notification cancellation reasons
- Notification_Importance
  链接如下：Notification EventLog解析常用如下
  Notification Event Log介绍
  1.1 最常用Notification Event Log介绍
  notification_enqueue
  /** 2750 notification_enqueue (uid|1|5),(pid|1|5),(pkg|3),(id|1|5),(tag|3),(userid|1|5),(notification|3),(status|1) */
  public static final int NOTIFICATION_ENQUEUE = 2750;
  e.g.12-02 19:29:24.709 1000 24263 24263 I notification_enqueue: [10179,26715,com.tencent.mm,2141405575,NULL,0,Notification(channel=null pri=2 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x101 color=0x00000000 category=msg actions=2 vis=PRIVATE),0]

notification_canceled
/** 2751 notification_cancel (uid|1|5),(pid|1|5),(pkg|3),(id|1|5),(tag|3),(userid|1|5),(required_flags|1),(forbidden_flags|1),(reason|1|5),(listener|3) */
public static final int NOTIFICATION_CANCEL = 2751;

56186:11-13 22:11:50.769 1000 2030 2030 I notification_cancel: [10103,12098,com.google.android.gm,-539083030,gig:2140555145:^sq_ig_i_personal,0,0,0,12,NULL]

notification_visibility
/** 27531 notification_visibility (key|3),(visibile|1),(lifespan|1),(freshness|1),(exposure|1),(rank|1) */
public static final int NOTIFICATION_VISIBILITY = 27531;

e.g.11-20 20:49:31.607 1000 1891 2452 I notification_visibility: [0|com.facebook.orca|20001|null|10169,1,221395,220539,0,2]
visibile : 当前notification是否可见 1 可见 0 不可见 lifespan : System.currentTimeMillis() - mCreationTimeMs freshness : System.currentTimeMillis() - mUpdateTimeMs exposure : 曝光时间 rank : 排序 0位于顶部第一，不同notification 相同rank则为折叠/更新了

notification_alert
/** 27532 notification_alert (key|3),(buzz|1),(beep|1),(blink|1) */
public static final int NOTIFICATION_ALERT = 27532;

01-03 11:43:09.552 1355 1398 I notification_alert: [0|com.tencent.tim|121|null|10159,1,0,1]

notification_panel_revealed
/** 27500 notification_panel_revealed (items|1) */
public static final int NOTIFICATION_PANEL_REVEALED = 27500;

11-20 20:49:31.105 1000 1891 3313 I notification_panel_revealed: 3
当前通知面板/浮动通知面板显示有几个Notification 更新/折叠算一个浮动通知面板通常==1
notification_panel_hidden
/** 27501 notification_panel_hidden */
public static final int NOTIFICATION_PANEL_HIDDEN = 27501;

01-03 11:26:11.262 1355 4180 I notification_panel_hidden:
通知面板/浮动通知面板收起
wm_create_activity
wm_pause_activity
wm_on_restart_called
3 Android EventLog
带你看看Android手机对应的日志
3.1 Acrivity Manager
2719 configuration_changed (config mask|1|5)
2721 cpu (total|1|6),(user|1|6),(system|1|6),(iowait|1|6),(irq|1|6),(softirq|1|6)

ActivityManagerService.systemReady() starts:

3040 boot_progress_ams_ready (time|2|3)

ActivityManagerService calls enableScreenAfterBoot():

3050 boot_progress_enable_screen (time|2|3)

Do not change these names without updating the checkin_events setting in

google3/googledata/wireless/android/provisioning/gservices.config !!

An activity is being finished:

30001 am_finish_activity (User|1|5),(Token|1|5),(Task ID|1|5),(Component Name|3),(Reason|3)

A task is being brought to the front of the screen:

30002 am_task_to_front (User|1|5),(Task|1|5)

An existing activity is being given a new intent:

30003 am_new_intent (User|1|5),(Token|1|5),(Task ID|1|5),(Component Name|3),(Action|3),(MIME Type|3),(URI|3),(Flags|1|5)

A new task is being created:

30004 am_create_task (User|1|5),(Task ID|1|5)

A new activity is being created in an existing task:

30005 am_create_activity (User|1|5),(Token|1|5),(Task ID|1|5),(Component Name|3),(Action|3),(MIME Type|3),(URI|3),(Flags|1|5)

An activity has been resumed into the foreground but was not already running:

30006 am_restart_activity (User|1|5),(Token|1|5),(Task ID|1|5),(Component Name|3)

An activity has been resumed and is now in the foreground:

30007 am_resume_activity (User|1|5),(Token|1|5),(Task ID|1|5),(Component Name|3)

Application Not Responding

30008 am_anr (User|1|5),(pid|1|5),(Package Name|3),(Flags|1|5),(reason|3)

Activity launch time

30009 am_activity_launch_time (User|1|5),(Token|1|5),(Component Name|3),(time|2|3)

Application process bound to work

30010 am_proc_bound (User|1|5),(PID|1|5),(Process Name|3)

Application process died

30011 am_proc_died (User|1|5),(PID|1|5),(Process Name|3),(OomAdj|1|5),(ProcState|1|5)

The Activity Manager failed to pause the given activity.

30012 am_failed_to_pause (User|1|5),(Token|1|5),(Wanting to pause|3),(Currently pausing|3)

Attempting to pause the current activity

30013 am_pause_activity (User|1|5),(Token|1|5),(Component Name|3),(User Leaving|3)

Application process has been started

30014 am_proc_start (User|1|5),(PID|1|5),(UID|1|5),(Process Name|3),(Type|3),(Component|3)

An application process has been marked as bad

30015 am_proc_bad (User|1|5),(UID|1|5),(Process Name|3)

An application process that was bad is now marked as good

30016 am_proc_good (User|1|5),(UID|1|5),(Process Name|3)

Reporting to applications that memory is low

30017 am_low_memory (Num Processes|1|1)

An activity is being destroyed:

30018 am_destroy_activity (User|1|5),(Token|1|5),(Task ID|1|5),(Component Name|3),(Reason|3)

An activity has been relaunched, resumed, and is now in the foreground:

30019 am_relaunch_resume_activity (User|1|5),(Token|1|5),(Task ID|1|5),(Component Name|3)

An activity has been relaunched:

30020 am_relaunch_activity (User|1|5),(Token|1|5),(Task ID|1|5),(Component Name|3)

The activity’s onPause has been called.

30021 am_on_paused_called (User|1|5),(Component Name|3),(Reason|3)

The activity’s onResume has been called.

30022 am_on_resume_called (User|1|5),(Component Name|3),(Reason|3)

Kill a process to reclaim memory.

30023 am_kill (User|1|5),(PID|1|5),(Process Name|3),(OomAdj|1|5),(Reason|3)

Discard an undelivered serialized broadcast (timeout/ANR/crash)

30024 am_broadcast_discard_filter (User|1|5),(Broadcast|1|5),(Action|3),(Receiver Number|1|1),(BroadcastFilter|1|5)
30025 am_broadcast_discard_app (User|1|5),(Broadcast|1|5),(Action|3),(Receiver Number|1|1),(App|3)

A service is being created

30030 am_create_service (User|1|5),(Service Record|1|5),(Name|3),(UID|1|5),(PID|1|5)

A service is being destroyed

30031 am_destroy_service (User|1|5),(Service Record|1|5),(PID|1|5)

A process has crashed too many times, it is being cleared

30032 am_process_crashed_too_much (User|1|5),(Name|3),(PID|1|5)

An unknown process is trying to attach to the activity manager

30033 am_drop_process (PID|1|5)

A service has crashed too many times, it is being stopped

30034 am_service_crashed_too_much (User|1|5),(Crash Count|1|1),(Component Name|3),(PID|1|5)

A service is going to be restarted after its process went away

30035 am_schedule_service_restart (User|1|5),(Component Name|3),(Time|2|3)

A client was waiting for a content provider, but its process was lost

30036 am_provider_lost_process (User|1|5),(Package Name|3),(UID|1|5),(Name|3)

The activity manager gave up on a new process taking too long to start

30037 am_process_start_timeout (User|1|5),(PID|1|5),(UID|1|5),(Process Name|3)

Unhandled exception

30039 am_crash (User|1|5),(PID|1|5),(Process Name|3),(Flags|1|5),(Exception|3),(Message|3),(File|3),(Line|1|5)

Log.wtf() called

30040 am_wtf (User|1|5),(PID|1|5),(Process Name|3),(Flags|1|5),(Tag|3),(Message|3)

User switched

30041 am_switch_user (id|1|5)

Activity set to resumed

30043 am_set_resumed_activity (User|1|5),(Component Name|3),(Reason|3)

Stack focus

30044 am_focused_stack (User|1|5),(Display Id|1|5),(Focused Stack Id|1|5),(Last Focused Stack Id|1|5),(Reason|3)

Running pre boot receiver

30045 am_pre_boot (User|1|5),(Package|3)

Report collection of global memory state

30046 am_meminfo (Cached|2|2),(Free|2|2),(Zram|2|2),(Kernel|2|2),(Native|2|2)

Report collection of memory used by a process

30047 am_pss (Pid|1|5),(UID|1|5),(Process Name|3),(Pss|2|2),(Uss|2|2),(SwapPss|2|2),(Rss|2|2),(StatType|1|5),(ProcState|1|5),(TimeToCollect|2|2)

Attempting to stop an activity

30048 am_stop_activity (User|1|5),(Token|1|5),(Component Name|3)

The activity’s onStop has been called.

30049 am_on_stop_called (User|1|5),(Component Name|3),(Reason|3)

Report changing memory conditions (Values are ProcessStats.ADJ_MEM_FACTOR* constants)

30050 am_mem_factor (Current|1|5),(Previous|1|5)

UserState has changed

30051 am_user_state_changed (id|1|5),(state|1|5)

Note when any processes of a uid have started running

30052 am_uid_running (UID|1|5)

Note when all processes of a uid have stopped.

30053 am_uid_stopped (UID|1|5)

Note when the state of a uid has become active.

30054 am_uid_active (UID|1|5)

Note when the state of a uid has become idle (background check enforced).

30055 am_uid_idle (UID|1|5)

Note when a service is being forcibly stopped because its app went idle.

30056 am_stop_idle_service (UID|1|5),(Component Name|3)

The activity’s onCreate has been called.

30057 am_on_create_called (User|1|5),(Component Name|3),(Reason|3)

The activity’s onRestart has been called.

30058 am_on_restart_called (User|1|5),(Component Name|3),(Reason|3)

The activity’s onStart has been called.

30059 am_on_start_called (User|1|5),(Component Name|3),(Reason|3)

The activity’s onDestroy has been called.

30060 am_on_destroy_called (User|1|5),(Component Name|3),(Reason|3)

The activity’s onActivityResult has been called.

30062 am_on_activity_result_called (User|1|5),(Component Name|3),(Reason|3)

The task is being removed from its parent stack

30061 am_remove_task (Task ID|1|5), (Stack ID|1|5)

The task is being compacted

30063 am_compact (Pid|1|5),(Process Name|3),(Action|3),(BeforeRssTotal|2|2),(BeforeRssFile|2|2),(BeforeRssAnon|2|2),(BeforeRssSwap|2|2),(DeltaRssTotal|2|2),(DeltaRssFile|2|2),(DeltaRssAnon|2|2),(DeltaRssSwap|2|2),(Time|2|3),(LastAction|1|2),(LastActionTimestamp|2|3),(setAdj|1|2),(procState|1|2),(BeforeZRAMFree|2|2),(DeltaZRAMFree|2|2)

The activity’s onTopResumedActivityChanged(true) has been called.

30064 am_on_top_resumed_gained_called (User|1|5),(Component Name|3),(Reason|3)

The activity’s onTopResumedActivityChanged(false) has been called.

30065 am_on_top_resumed_lost_called (User|1|5),(Component Name|3),(Reason|3)

An activity been add into stopping list

30066 am_add_to_stopping (User|1|5),(Token|1|5),(Component Name|3),(Reason|3)

下面列举tag可能使用的部分场景：

am_low_memory：位于AMS.killAllBackgroundProcesses或者AMS.appDiedLocked，记录当前Lru进程队列长度。
am_pss：位于AMS.recordPssSampleLocked(
am_meminfo：位于AMS.dumpApplicationMemoryUsage
am_proc_start:位于AMS.startProcessLocked，启动进程
am_proc_bound:位于AMS.attachApplicationLocked
am_kill: 位于ProcessRecord.kill，杀掉进程
am_anr: 位于AMS.appNotResponding
am_crash:位于AMS.handleApplicationCrashInner
am_wtf:位于AMS.handleApplicationWtf
am_activity_launch_time：位于ActivityRecord.reportLaunchTimeLocked()，后面两个参数分别是thisTime和 totalTime.
am_activity_fully_drawn_time:位于ActivityRecord.reportFullyDrawnLocked, 后面两个参数分别是thisTime和 totalTime
am_broadcast_discard_filter:位于BroadcastQueue.logBroadcastReceiverDiscardLocked
am_broadcast_discard_app:位于BroadcastQueue.logBroadcastReceiverDiscardLocked
Activity生命周期相关的方法:
am_on_resume_called: 位于AT.performResumeActivity
am_on_paused_called: 位于AT.performPauseActivity, performDestroyActivity
am_resume_activity: 位于AS.resumeTopActivityInnerLocked
am_pause_activity: 位于AS.startPausingLocked
am_finish_activity: 位于AS.finishActivityLocked, removeHistoryRecordsForAppLocked
am_destroy_activity: 位于AS.destroyActivityLocked
am_focused_activity: 位于AMS.setFocusedActivityLocked, clearFocusedActivity
am_restart_activity: 位于ASS.realStartActivityLocked
am_create_activity: 位于ASS.startActivityUncheckedLocked
am_new_intent: 位于ASS.startActivityUncheckedLocked
am_task_to_front: 位于AS.moveTaskToFrontLocked
3.2 Power & Battery

---------------------------

6# BatteryService.java
7# ---------------------------
82722 battery_level (level|1|6),(voltage|1|1),(temperature|1|1)
92723 battery_status (status|1|5),(health|1|5),(present|1|5),(plugged|1|5),(technology|3)
10# This is logged when battery goes from discharging to charging.
11# It lets us count the total amount of time between charges and the discharge level
122730 battery_discharge (duration|2|3),(minLevel|1|6),(maxLevel|1|6)
13
14
15# ---------------------------
16# PowerManagerService.java
17# ---------------------------
18# This is logged when the device is being forced to sleep (typically by
19# the user pressing the power button).
202724 power_sleep_requested (wakeLocksCleared|1|1)
21# This is logged when the screen on broadcast has completed
222725 power_screen_broadcast_send (wakelockCount|1|1)
23# This is logged when the screen broadcast has completed
242726 power_screen_broadcast_done (on|1|5),(broadcastDuration|2|3),(wakelockCount|1|1)
25# This is logged when the screen on broadcast has completed
262727 power_screen_broadcast_stop (which|1|5),(wakelockCount|1|1)
27# This is logged when the screen is turned on or off.
282728 power_screen_state (offOrOn|1|5),(becauseOfUser|1|5),(totalTouchDownTime|2|3),(touchCycles|1|1),(latency|1|3)
29# This is logged when the partial wake lock (keeping the device awake
30# regardless of whether the screen is off) is acquired or released.
312729 power_partial_wake_state (releasedorAcquired|1|5),(tag|3)
32# The device is being asked to go into a soft sleep (typically by the ungaze gesture).
33# It logs the time remaining before the device would’ve normally gone to sleep without the request.
342731 power_soft_sleep_requested (savedwaketimems|2)
35
36#
37# Leave IDs through 2739 for more power logs (2730 used by battery_discharge above)

部分含义：

battery_level: [19,3660,352] //剩余电量19%, 电池电压3.66v, 电池温度35.2℃
power_screen_state: [0,3,0,0] // 灭屏状态(0), 屏幕超时(3). 当然还有其他设备管理策略(1),其他理由都为用户行为(2)
power_screen_state: [1,0,0,0] // 亮屏状态(1)
下面列举tag可能使用的部分场景：
power_sleep_requested: 位于PMS.goToSleepNoUpdateLocked
power_screen_state:位于Notifer.handleEarlyInteractiveChange, handleLateInteractiveChange
3.3 更多含义

---------------------------

3.4. EventLog完整语义分析
以am_proc_start分析log中的信息
30014 am_proc_start (User|1|5),(PID|1|5),(UID|1|5),(Process Name|3),
(Type|3),(Component|3)

am_proc_start之后紧跟着的几个括号，其中括号里的内容如下：
|data type[|data unit])
(<名字>|数据类型[|数据单位])

那么(User|1|5) ==> 名字为User, 数据类型为1，数据单位为5，下面再来看看数据类型和数据单位：
数据类型

1: int
2: long
3: string
4: list
数据单位
1: Number of objects(对象个数)
2: Number of bytes(字节数)
3: Number of milliseconds(毫秒)
4: Number of allocations(分配个数)
5: Id
6: Percent(百分比)
am_proc_start: [0,2703,10011,com.google.android.onetimeinitializer,
broadcast,com.google.android.onetimeinitializer/.OneTimeInitializerReceiver]

进程启动: UserId=0, pid=2703, uid=10011, ProcessName=com.google.android.onetimeinitializer, 数据类型=broadcast, 组件=com.google.android.onetimeinitializer/.OneTimeInitializerReceiver

北境王

关注

0
点赞
踩
2

收藏

觉得还不错? 一键收藏
打赏
0
评论
Android Event Log

日志是极好的，可以及时记录程序的运行状态信息，和出现异常的时候的异常状态信息，是程序运行的后知后觉的晴雨表。它可以给我们查找问题指明方向，带来查找问题的便利。因此，可以读懂Android Event Log显得很重要。为了让您可以懂它，使用它，我来做一个小小总结。
复制链接

扫一扫