mtklog结构及分析

1.mtklog简介:mtklog是由log生成工具MTKLogger生成的一系列问题追踪文件,其主要作用就是对系统或者应用产生的异常进行快速定位,从而解决问题。

mtklog 的分类:MDLog、Mobile Log、Network Log,可能出现的aee_exp log

MD log:medom 相关底层的log

Mobile Log:主要是Android log 和kernel log

Network log:网络相关log

aee_exp log :crash ANR 重启相关的log输出

 

2.mtklog 的开启和关闭:

(1)在拨号盘界面输入*#9646633# :

(2)进入EngineerMode的第一个Telephony界面:

(3)向左滑动进入Log and Debugging界面:

(4)点击MTKLogger 菜单:

点击log设置图标可进入log设置界面,如果我只要打印MobileLog可将ModemLog,NetworkLog,GPSlog关闭,点击蓝底色1 即可:

(5)点击开始(红色播放按键)按键:

(6)log 开启:

(7)当我们已经发现异常时,当关闭log,并截图记录时间点,下拉进入下拉栏界面,点击MTKLogger is running:

(8)点击停止按键:

如图关闭成功:

 

3.mtklog的导出和分析:

(1)MTKLogger停止后,手机USB,下拉下拉栏,点击USB for charging,切换至MTP模式:

 Transfer files(MTP);

(2)双击:便携设备:

(3)在内部存储中找到mtklog文件夹复制粘贴到本地:

(4)打开mtklog文件夹:

(4)关于分析log,我们主要分析mobilelog 文件夹中的对应Android log 和 kernel log:

对应log文件名称为:

crash_log :崩溃日志,主要输出 程序崩溃造成的crash log

events_log:事件日志,主要输出记录各个activity周期及事件

kernel_log:底层驱动,按键,低内存相关log

sys_log:系统日志,Exception定位点

radio_log:输出通话,网络状态变化

main_log:详尽输出每一步的log

 

分析kernel log安装可查看对应kernal_log的时间点:

安装成功之后,如下操作打开kernal_log.localtime文件可查看带时间点的kernal log:

 

(5)常见异常分析:

1.编译报错

build.log 中搜索unfinished 关键字,查找上文能够很快定位报错原因,或者搜索 error: 关键字能够直接定位相关报错文件(注意是搜索error和冒号)

 

2.程序崩溃(系统提示***已停止运行):

1)启动崩溃:一般情况为第三方预置缺少库文件,或者兼容性问题

2)应用间交互崩溃:startActivity找不多对应包名或者类名,或者无对应启动Activity的权限

3APP内部逻辑空指针异常导致程序崩溃(NullPointerException

以上三种情况都可在mtklog\mobilelog\APLog_2016_0505_115433\events_log 文件中搜索 crash 关键字快速定位问题点,crash_log中可查看对应问题产生原因:

Line 4201: 03-29 11:25:32.894092 939 949 I am_crash:[9337,0,com.bbm,954744388,java.lang.UnsatisfiedLinkError,dalvik.system.PathClassLoader[DexPathList[[zip file"/system/framework/com.google.android.maps.jar", zip file"/data/app/com.bbm-1/base.apk"],nativeLibraryDirectories=[/data/app-lib/com.bbm-1,/data/app/com.bbm-1/base.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]]couldn't find "libgnustl_shared.so",Runtime.java,367]
Line 4202: 03-29 11:25:32.910190 939 949 Iam_finish_activity: [0,198242511,14,com.bbm/.ui.activities.StartupActivity,force-crash]

 

3.程序闪退:

1)外部原因:物理内存不足,被killevents_log中搜索 low_memory 关键字,以确定低内存杀死程序,kernal_log 中有存在对应时间点被 low memory kill如下:

05-10 11:36:22.588540 923 1439 Iam_low_memory: 19
05-10 11:36:22.594222 923 938 I am_destroy_activity:
[0,205784777,125,com.mediatek.filemanager/.MainFilemanagerActivity,finish-idle]
05-10 11:36:22.599262 923 923 I notification_cancel_all:
[1000,923,com.mediatek.filemanager,0,0,0,5,NULL]
05-10 11:36:22.601661 923 923 I notification_cancel_all:
[1000,923,com.android.providers.downloads,0,0,0,5,NULL]
05-10 11:36:22.650000 2036 2036 I auditd : type=1400 audit(0.0:347): avc:denied

{ read } for comm="GpuAppSpectator" name="cmdline"dev="proc" ino=10905 scontext=u:r:gas_srv:s0tcontext=u:r:system_app:s0 tclass=file permissive=0
05-10 11:36:22.869048 923 1910 Iam_proc_bound:
 [0,3769,com.cyin.himgr]
05-10 11:36:23.403472 1532 1532 Iam_on_resume_called:
[0,com.android.hios.launcher3.Launcher]
05-10 11:36:23.650000 2036 2036 I auditd :type=1400 audit(0.0:348): avc: denied { read }

forcomm="GpuAppSpectator" name="cmdline" dev="proc"ino=10905 scontext=u:r:gas_srv:s0 tcontext=u:r:system_app:s0 tclass=filepermissive=0
05-10 11:36:23.965602 923 938 I am_destroy_activity:
[0,102727749,125,com.android.packageinstaller/.InstallAppProgress,finish-imm]
05-10 11:36:23.972491 241 241 I sf_frame_dur:
[com.android.packageinstaller/com.android.packageinstaller.InstallAppProgress,2375,9,1,0,1,0,0]
05-10 11:36:24.126262 923 1520 I netstats_mobile_sample:
 [0,0,0,0,0,0,0,0,0,0,0,0,-1]
05-10 11:36:24.126560 923 1520 I netstats_wifi_sample:
[64660,844,36398,408,33328,147,33388,197,32228,126,33388,197,-1]
05-10 11:36:24.244910 923 934 I am_proc_died:
 [0,3665,com.android.packageinstaller]
05-10 11:36:24.245968 923 934 I wm_task_removed:
 [125,removeAppToken: last token]
05-10 11:36:24.246168 923 934 I wm_task_removed:
 [125,removeTask]

05-10 11:36:24.248168 923 934 I am_low_memory: 19
05-10 11:36:24.255912 923 923 I notification_cancel_all:[1000,923,com.android.packageinstaller,0,0,0,5,NULL]

05-10 11:36:24.318915 923 933 Inetstats_mobile_sample: [0,0,0,0,0,0,0,0,0,0,0,0,-1]

2)内部原因:main_log/sys_log 搜索Exception 或者 died关键字定位对应包名,进而定位问题

 

4.ANR问题:

出现ANR应当提供traces.txt文件,直接在文件中搜索 cmd 关键字,定位问题点。锁定三个方向:memoryleak(是否为低内存),CPU blockCPU使用率过高)、iowaitIO流使用过于频繁)

1memoryleak:首先根据Android log搜索低内存相关 low_memory 关键字,以确定是否存在低内存现象

2CPU block:搜索对应包出现ANR前后 TOTAL 关键字前的百分比,若百分比接近100% 说明CPU饥饿导致了ANR

3iowait:搜索iowait 关键字查看出现ANR前的百分比,若百分比过高,说明I/O流使用过于频繁导致ANR,此项需修改相关数据库的加载流程,如下:

4-0113:12:15.872 E/ActivityManager(  220):  5.5%21404/com.android.email: 1.3% user + 4.1% kernel / faults: 10 minor

04-0113:12:15.872 E/ActivityManager(  220):  4.3%220/system_server: 2.7% user + 1.5% kernel / faults: 11 minor 2 major

04-0113:12:15.872 E/ActivityManager(  220):  0.9%52/spi_qsd.0: 0% user + 0.9% kernel

04-0113:12:15.872 E/ActivityManager(  220):  0.5%65/irq/170-cyttsp-: 0% user + 0.5% kernel

04-0113:12:15.872 E/ActivityManager(  220):   0.5%296/com.android.systemui:0.5% user + 0% kernel

04-0113:12:15.872 E/ActivityManager(  220): 100%TOTAL:4.8% user + 7.6% kernel + 87% iowait

04-0113:12:15.872 E/ActivityManager(  220):CPUusagefrom 3697ms to 4223ms later:-- ANR后CPU的使用量

04-0113:12:15.872 E/ActivityManager(  220):  25%21404/com.android.email: 25% user + 0% kernel / faults: 191 minor

04-0113:12:15.872 E/ActivityManager( 220):    16% 21603/__eas(par.hakan: 16% user + 0% kernel

04-0113:12:15.872 E/ActivityManager( 220):    7.2% 21406/GC: 7.2% user + 0% kernel

04-0113:12:15.872 E/ActivityManager( 220):    1.8% 21409/Compiler: 1.8% user + 0% kernel

04-0113:12:15.872 E/ActivityManager(  220):  5.5%220/system_server: 0% user + 5.5% kernel / faults: 1 minor

04-0113:12:15.872 E/ActivityManager( 220):    5.5% 263/InputDispatcher: 0% user + 5.5% kernel

04-0113:12:15.872 E/ActivityManager(  220): 32%TOTAL:28% user + 3.7% kernel


转载:https://blog.csdn.net/u011714701/article/details/53398447

你可能感兴趣的:(Android应用)