Android之mtklog分析

【海外场测反馈】【xxx】动态测试时对比机xxxx拨打测试机xxxxx自动挂断电话

工作中遇到一个掉话的问题，需要分析log，log比较大，我也没法上传，就简答的讲讲吧

其实我也不太懂，随便说说吧：

1.   在mobilelog/APLog_2016_0902_134517/radio_log中：

56200:09-02 13:50:59.012418 1570 1570 D CallManager: handleMessage (EVENT_SERVICE_STATE_CHANGED)
mobilelog/APLog_2016_0902_134517/radio_log:56202:09-02 13:50:59.013388 1570 1570 D CallManager: handleMessage (EVENT_SERVICE_STATE_CHANGED)
mobilelog/APLog_2016_0902_134517/radio_log:56586:09-02 13:51:00.571278 1570 1570 D CallManager: handleMessage (EVENT_INCOMING_RING)
mobilelog/APLog_2016_0902_134517/radio_log:57025:09-02 13:51:02.361298 1570 1570 D CallManager: handleMessage (EVENT_IN_CALL_VOICE_PRIVACY_OFF)
mobilelog/APLog_2016_0902_134517/radio_log:57058:09-02 13:51:02.364957 1570 1570 D CallManager: handleMessage (EVENT_IN_CALL_VOICE_PRIVACY_OFF)
mobilelog/APLog_2016_0902_134517/radio_log:57101:09-02 13:51:02.373686 1570 1570 D CallManager: handleMessage (EVENT_PRECISE_CALL_STATE_CHANGED)
mobilelog/APLog_2016_0902_134517/radio_log:60984:09-02 13:52:25.815752 1570 1570 D CallManager: handleMessage (EVENT_DISCONNECT)
mobilelog/APLog_2016_0902_134517/radio_log:61056:09-02 13:52:25.827674 1570 1570 D CallManager: handleMessage (EVENT_PRECISE_CALL_STATE_CHANGED)
mobilelog/APLog_2016_0902_134517/radio_log:62892:09-02 13:52:27.080981 1570 1570 D CallManager: handleMessage (EVENT_SERVICE_STATE_CHANGED)
mobilelog/APLog_2016_0902_134517/radio_log:62894:09-02 13:52:27.082019 1570 1570 D CallManager: handleMessage (EVENT_SERVICE_STATE_CHANGED)

通过这可以看出从来电到断掉连接

2.在mobilelog/APLog_2016_0901_114539/sys_log:中

mobilelog/APLog_2016_0901_114539/sys_log:4911:09-01 11:46:14.887454 980 4368 D ConnectivityService: sending notification RELEASED for NetworkRequest [ id=21, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:22568:09-01 11:53:32.409970 980 4368 D ConnectivityService: sending notification RELEASED for NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED

释放掉网络请求

3.通过mobilelog/APLog_2016_0902_134517/radio_log:中

mobilelog/APLog_2016_0902_134517/radio_log:4924:09-02 13:45:27.939767 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> DISCONNECTED,DIALING
mobilelog/APLog_2016_0902_134517/radio_log:4925:09-02 13:45:27.939788 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:4936:09-02 13:45:27.940933 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> DIALING,DIALING
mobilelog/APLog_2016_0902_134517/radio_log:4937:09-02 13:45:27.940954 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:5225:09-02 13:45:27.981695 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> DIALING,DIALING
mobilelog/APLog_2016_0902_134517/radio_log:5226:09-02 13:45:27.981716 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:6545:09-02 13:45:33.160355 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> DIALING,ALERTING
mobilelog/APLog_2016_0902_134517/radio_log:6546:09-02 13:45:33.160392 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:6821:09-02 13:45:39.782391 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> ALERTING,ACTIVE
mobilelog/APLog_2016_0902_134517/radio_log:6828:09-02 13:45:39.783823 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:37785:09-02 13:49:35.813219 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> ACTIVE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:37786:09-02 13:49:35.813238 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:43971:09-02 13:50:03.843490 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:43972:09-02 13:50:03.843513 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:47324:09-02 13:50:08.799303 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> IDLE,ACTIVE
mobilelog/APLog_2016_0902_134517/radio_log:47327:09-02 13:50:08.799428 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:51570:09-02 13:50:39.936903 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> ACTIVE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:51571:09-02 13:50:39.936940 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:54314:09-02 13:50:56.714155 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:54315:09-02 13:50:56.714175 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:57104:09-02 13:51:02.373813 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> IDLE,ACTIVE
mobilelog/APLog_2016_0902_134517/radio_log:57107:09-02 13:51:02.373938 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE
mobilelog/APLog_2016_0902_134517/radio_log:61059:09-02 13:52:25.827773 1570 1570 D CAT : StkAppService: processPhoneStateChanged fg state -> ACTIVE,DISCONNECTED
mobilelog/APLog_2016_0902_134517/radio_log:61061:09-02 13:52:25.827804 1570 1570 D CAT : StkAppService: processPhoneStateChanged bg state -> IDLE,IDLE

4.通过mobilelog/APLog_2016_0901_114539/sys_log:中

mobilelog/APLog_2016_0901_114539/sys_log:2402:09-01 11:45:51.276954 980 4368 D ConnectivityService: sending notification AVAILABLE for NetworkRequest [ id=3, legacyType=-1, [] ]
mobilelog/APLog_2016_0901_114539/sys_log:2403:09-01 11:45:51.277411 980 4368 D ConnectivityService: sending notification AVAILABLE for NetworkRequest [ id=7, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:2412:09-01 11:45:51.282107 980 4368 D ConnectivityService: sending notification PRECHECK for NetworkRequest [ id=3, legacyType=-1, [] ]
mobilelog/APLog_2016_0901_114539/sys_log:2416:09-01 11:45:51.282791 980 4368 D ConnectivityService: sending notification PRECHECK for NetworkRequest [ id=7, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:2439:09-01 11:45:51.286045 980 4368 D ConnectivityService: sending notification CAP_CHANGED for NetworkRequest [ id=3, legacyType=-1, [] ]
mobilelog/APLog_2016_0901_114539/sys_log:2441:09-01 11:45:51.289230 980 4368 D ConnectivityService: sending notification CAP_CHANGED for NetworkRequest [ id=7, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:4158:09-01 11:46:02.761551 980 4368 D ConnectivityService: sending notification AVAILABLE for NetworkRequest [ id=21, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:4911:09-01 11:46:14.887454 980 4368 D ConnectivityService: sending notification RELEASED for NetworkRequest [ id=21, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:5878:09-01 11:46:21.066040 980 4368 D ConnectivityService: sending notification AVAILABLE for NetworkRequest [ id=3, legacyType=-1, [] ]
mobilelog/APLog_2016_0901_114539/sys_log:5880:09-01 11:46:21.066447 980 4368 D ConnectivityService: sending notification AVAILABLE for NetworkRequest [ id=7, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:5883:09-01 11:46:21.066860 980 4368 D ConnectivityService: sending notification PRECHECK for NetworkRequest [ id=3, legacyType=-1, [] ]
mobilelog/APLog_2016_0901_114539/sys_log:5885:09-01 11:46:21.067237 980 4368 D ConnectivityService: sending notification PRECHECK for NetworkRequest [ id=7, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:5937:09-01 11:46:21.137362 980 4368 D ConnectivityService: sending notification CAP_CHANGED for NetworkRequest [ id=3, legacyType=-1, [] ]
mobilelog/APLog_2016_0901_114539/sys_log:5939:09-01 11:46:21.141809 980 4368 D ConnectivityService: sending notification CAP_CHANGED for NetworkRequest [ id=7, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:6087:09-01 11:46:23.736490 980 4368 D ConnectivityService: sending notification CAP_CHANGED for NetworkRequest [ id=3, legacyType=-1, [] ]
mobilelog/APLog_2016_0901_114539/sys_log:6089:09-01 11:46:23.738329 980 4368 D ConnectivityService: sending notification CAP_CHANGED for NetworkRequest [ id=7, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:6570:09-01 11:46:38.463540 980 4368 D ConnectivityService: sending notification AVAILABLE for NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:6578:09-01 11:46:38.464370 980 4368 D ConnectivityService: sending notification AVAILABLE for NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:21200:09-01 11:53:30.654409 980 4368 D ConnectivityService: sending notification LOST for NetworkRequest [ id=3, legacyType=-1, [] ]
mobilelog/APLog_2016_0901_114539/sys_log:21202:09-01 11:53:30.654846 980 4368 D ConnectivityService: sending notification LOST for NetworkRequest [ id=7, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:21204:09-01 11:53:30.655223 980 4368 D ConnectivityService: sending notification LOST for NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
mobilelog/APLog_2016_0901_114539/sys_log:22568:09-01 11:53:32.409970 980 4368 D ConnectivityService: sending notification RELEASED for NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED

可以看出网络连接断开

下面是mtk给的分析结果，因为log中有一些文件只有mtk才有工具能打开查看，我们是看不到里面的内容的，

这次是网络挂断的call，应该是主叫异常导致的。手机处理正常。

1460091, 278588, 251943, 13:50:55:040 2016/09/02, MOD_CC_2, , TRACE_PEER, [NW->MS] CC__SETUP
1460173, 278591, 251946, 13:50:55:040 2016/09/02, MOD_CC_2, , TRACE_PEER, [MS->NW] CC__CALL_CONFIRMED
1460455, 278830, 252166, 13:50:56:240 2016/09/02, MOD_CC_2, , TRACE_PEER, [MS->NW] CC__ALERTING
1464486, 280013, 253258, 13:51:01:640 2016/09/02, MOD_CC_2, , TRACE_PEER, [MS->NW] CC__CONNECT
1464573, 280082, 253322, 13:51:02:040 2016/09/02, MOD_CC_2, , TRACE_PEER, [NW->MS] CC__CONNECT_ACKNOWLEDGE
1498308, 298067, 269923, 13:52:25:040 2016/09/02, MOD_CC_2, , TRACE_PEER, [NW->MS] CC__DISCONNECT
1498598, 298148, 269998, 13:52:25:440 2016/09/02, MOD_NIL, , TRACE_INFO, [AT_U p23, s14]+ECPI:
1,1,0,1,,,"",,"",126
1498324, 298067, 269923, 13:52:25:040 2016/09/02, MOD_CC_2, , TRACE_PEER, [MS->NW] CC__RELEASE
1498569, 298148, 269998, 13:52:25:440 2016/09/02, MOD_CC_2, , TRACE_PEER, [NW->MS] CC__RELEASE_COMPLETE

时间： 2024-08-01 10:20:31

Android之mtklog分析的相关文章

Cordova Android源码分析系列一（项目总览和CordovaActivity分析）

PhoneGap/Cordova是一个专业的移动应用开发框架,是一个全面的WEB APP开发的框架,提供了以WEB形式来访问终端设备的API的功能.这对于采用WEB APP进行开发者来说是个福音,这可以避免了原生开发的某些功能.Cordova 只是个原生外壳,app的内核是一个完整的webapp,需要调用的原生功能将以原生插件的形式实现,以暴露js接口的方式调用. Cordova Android项目是Cordova Android原生部分的Java代码实现,提供了Android原生代码和上层We

Android的Framework分析---5 ActivityManager分析

ActivityManager是android框架的一个重要部分,它负责一新ActivityThread进程创建,Activity生命周期的维护,管理系统中的Acitvity的状态切换. 这边内容还有更多内容,详细请参看ActivityManager.java ,ActivityMangaerNative.java 和SystemServcer.java 文件. 这几个的类的关系如下: 上图很清楚地描述了ActivityManager框架的几个主要类之间的关系,我们做应用开发接触很多的其实就是A

android 内存泄漏分析技巧

java虚拟机运行一般都有一个内存界限,超过这个界限,就会报outofmemory.这个时候一般都是存在内存泄漏.解决内存泄漏问题,窃以为分为两个步骤:分析应用程序是否真的有内存泄漏,找到内存泄漏的地方.这两个步骤都不是一般意义上的调试,直接打log,断点调试都不是太给力.动脑筋想一想,内存问题应该在很多地方上都会出现,这么常见的问题应该是有工具的.android现在更可以说是一个生态系统,当然也有很多开发辅助工具.在前面的两个步骤中都有很强大的武器,熟练的掌握这些利器,分析问题就会事半功倍.

Android dumpsys 内存分析

研究了Mat和Heap的分析方法之后,尝试用其他的方式来分析下,Androiddumpsys 的方式来看下结果. 如何得出数据的操作就不说了,网上太多了,只看数据来进行分析. 如图1,启动的时候的情况 执行三次怀疑有泄露的功能之后的数据 再执行三次 再执行三次 数据分析: Native 数据代表的是JNI层的数据,从mallinfo usmblks 获得 DalviK 数据代表的是Java层的数据,从Runtime Totalmemory获得 Size 代表是能获得的最大的数据 Alloc代表的

Android系统启动流程分析

随着Android版本的升级,aosp项目中的代码也有了些变化,本文基于Android 7.0分析Android系统启动流程. 简单来说Android系统启动大体如下: init进程 和所有Linux系统一样,Android系统的启动同样是从init进程启动.init进程会解析init.rc文件(关于init.rc中的语法,可以参见我之前写的深入分析AIL语言及init.rc文件),加载相关目录,并启动相关服务 init进程在/system/core/init/init.c init.rc文件在

Android init源代码分析（2）init.rc解析

本文描述init.rc脚本解析以及执行过程,读完本章后,读者应能 (1) 了解init.rc解析过程 (2) 定制init.rc init.rc介绍 init.rc是一个文本文件,可认为它是Android系统启动脚本.init.rc文件中定义了环境变量配置.系统进程启动,分区挂载,属性配置等诸多内容.init.rc具有特殊的语法.init源码目录下的readme.txt中详细的描述了init启动脚本的语法规则,是试图定制init.rc的开发者的必读资料. Android启动脚本包括一组文件,包括

android原生browser分析(二)--界面篇

我们先看一张浏览器的主界面,上面标示浏览器界面各部分对应的类,这里是以平板上的界面为例.给张图是为了给大家一个直观的感觉. BrowserActivity是整个应用的主界面,在onCreate中创建了Controller对象,Controller对象是整个应用最重要的管理类,这个后面再说. @Override public void onCreate(Bundle icicle) { mController = createController(); } Controller的创建中新建了UI类

Android 源码分析工具

标 题: [原创]Android源码分析工具及方法作 者: MindMac时 间: 2014-01-02,09:32:35链 接: http://bbs.pediy.com/showthread.php?t=183278 在对 Android 源码进行分析时,如果有得力的工具辅助,会达到事半功倍的效果.本文介绍了一些在分析 Android 源码时使用的一些工具和方法,希望能够帮助到有需要的同学. Eclipse 在 Android 应用程序开发过程中,一般会使用 Eclipse,当然 Googl

Android源码分析：Telephony部分–GSMPhone

Android源码分析:Telephony部分–GSMPhone红狼博客 PhoneProxy/GSMPhone/CDMAPhone 如果说RILJ提供了工具或管道,那么Phone接口的子类及PhoneFactory则为packages/app/Phone这个应用程序进程使用RILJ这个工具或管道提供了极大的方便,它们一个管理整个整个手机的Telephony功能. GSMPhone和CDMAPhone实现了Phone中定义的接口.接口类Phone定义了一套API,这套API用于使用RILJ(见后