标签:function 13 recovery 04 Auto 08 18431 32 android
一、last_log中确认recovery模式的原因
参考日志如下: [ 0.264872] stage is [] [ 0.264891] reason is [ RescueParty] [ 0.268536] installing_text: en_US (304 x 38 @ 1446) [ 0.277906] Command : "/system/bin/recovery" "--prompt_and_wipe_data" " --reason=RescueParty" " --locale=en_US" [ 0.277925] 如上日志,可以基本判断是由于系统异常出发了救援程序,救援程序与Android8.0后引入默认开启;二、RescueParty 简单介绍:
在 Android 8.0 中,救援程序默认处于启用状态,其实现位于 /services/core/java/com/android/server/RescueParty.java 中。在出现以下情况时,救援程序会收到有关启动和崩溃事件的信息,然后即会启动:- system_server 在 5 分钟内重启 5 次以上。
- 永久性系统应用在 30 秒内崩溃 5 次以上。
三、android 常规日志确认救援程序触发重启进入recovery模式
由于是自动化测试,测试工程师无法准确记录问题发生的时间点,这个找log的过程比较通过,那么改善方式则是在recoverysystem重启进入recovery时写misc分区添加一个--date的参数,传递一个年月日时分秒的值,方便定位时间点。接着说,logcat的main buffer log中确认uncrypt接收到了相关指令,如下: 04-13 08:32:44.075 18774 18774 I /system/bin/uncrypt: received command: [--prompt_and_wipe_data 04-13 08:32:44.075 18774 18774 I /system/bin/uncrypt: --reason=RescueParty 04-13 08:32:44.075 18774 18774 I /system/bin/uncrypt: --locale=en_US 04-13 08:32:44.075 18774 18774 I /system/bin/uncrypt: ] (59) 04-13 08:32:44.075 18774 18774 I /system/bin/uncrypt: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor 结合system buffer的日志分析,参考日志: 行 342: 04-13 08:32:40.717 1539 3552 I ActivityTaskManager: START u0 {act=android.intent.action.SEND_MULTIPLE typ=application/zip flg=0x10000001 clip={text/plain U: content://com.android.systemui.fileprovider/leak/hprof-1618273957401.zip} (has extras)} from uid 10033 行 356: 04-13 08:32:40.835 1539 1615 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=15, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10033] ], android.os.BinderProxy@f13cf33) 行 360: 04-13 08:32:40.836 1539 2111 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=15, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10033] ] (release request) 行 493: 04-13 08:32:41.051 1539 2569 W RescueParty: Noticed 2 events for UID 10033 in last 0 sec 行 508: 04-13 08:32:41.180 1539 4649 W RescueParty: Noticed 3 events for UID 10033 in last 0 sec 行 519: 04-13 08:32:41.311 1539 5186 W RescueParty: Noticed 4 events for UID 10033 in last 0 sec 行 529: 04-13 08:32:41.463 1539 5186 W RescueParty: Noticed 5 events for UID 10033 in last 0 sec 行 532: 04-13 08:32:41.473 1539 5186 W RescueParty: Attempting rescue level RESET_SETTINGS_UNTRUSTED_DEFAULTS 行 552: 04-13 08:32:41.745 1539 4482 W RescueParty: Noticed 2 events for UID 10033 in last 0 sec 行 564: 04-13 08:32:41.851 1539 4482 W RescueParty: Noticed 3 events for UID 10033 in last 0 sec 行 573: 04-13 08:32:41.950 1539 5186 W RescueParty: Noticed 4 events for UID 10033 in last 0 sec 行 582: 04-13 08:32:42.050 1539 4649 W RescueParty: Noticed 5 events for UID 10033 in last 0 sec 行 584: 04-13 08:32:42.052 1539 4649 W RescueParty: Attempting rescue level RESET_SETTINGS_UNTRUSTED_CHANGES 行 607: 04-13 08:32:42.259 1539 5186 W RescueParty: Noticed 2 events for UID 10033 in last 0 sec 行 616: 04-13 08:32:42.355 1539 17630 W RescueParty: Noticed 3 events for UID 10033 in last 0 sec 行 625: 04-13 08:32:42.454 1539 1615 W RescueParty: Noticed 4 events for UID 10033 in last 0 sec 行 634: 04-13 08:32:42.551 1539 2083 W RescueParty: Noticed 5 events for UID 10033 in last 0 sec 行 636: 04-13 08:32:42.553 1539 2083 W RescueParty: Attempting rescue level RESET_SETTINGS_TRUSTED_DEFAULTS 行 659: 04-13 08:32:42.764 1539 5550 W RescueParty: Noticed 2 events for UID 10033 in last 0 sec 行 668: 04-13 08:32:42.867 1539 2798 W RescueParty: Noticed 3 events for UID 10033 in last 0 sec 行 677: 04-13 08:32:42.967 1539 4848 W RescueParty: Noticed 4 events for UID 10033 in last 0 sec 行 686: 04-13 08:32:43.065 1539 4848 W RescueParty: Noticed 5 events for UID 10033 in last 0 sec 行 688: 04-13 08:32:43.066 1539 4848 W RescueParty: Attempting rescue level FACTORY_RESET 触发了救援程序的最高级别的任务,即 提示用户将设备恢复出厂设置。 行 691: 04-13 08:32:44.087 1539 4848 I RecoverySystemService: uncrypt setup bcb successfully finished. 紧接着,rss触发重启。四、系统异常原因分析
如上log确认为systemui crash导致异常的发生,那么从crash log中再次确认异常原因: 04-13 08:32:41.459 18431 18431 E AndroidRuntime: FATAL EXCEPTION: main 04-13 08:32:41.459 18431 18431 E AndroidRuntime: Process: com.android.systemui, PID: 18431 04-13 08:32:41.459 18431 18431 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider com.android.systemui.keyguard.KeyguardSliceProvider: java.lang.NullPointerException: Attempt to invoke virtual method 'int android.telephony.UiccSlotInfo.getLogicalSlotIdx()' on a null object reference 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.app.ActivityThread.installProvider(ActivityThread.java:7207) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.app.ActivityThread.installContentProviders(ActivityThread.java:6747) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6658) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.app.ActivityThread.access$1400(ActivityThread.java:233) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1995) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.os.Looper.loop(Looper.java:241) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7582) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:941) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int android.telephony.UiccSlotInfo.getLogicalSlotIdx()' on a null object reference 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.isEsim(KeyguardUpdateMonitor.java:3053) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.<init>(KeyguardUpdateMonitor.java:2129) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.getInstance(KeyguardUpdateMonitor.java:1915) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardSliceProvider.getKeyguardUpdateMonitor(KeyguardSliceProvider.java:461) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardSliceProvider.registerClockUpdate(KeyguardSliceProvider.java:406) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardSliceProvider.onCreateSliceProvider(KeyguardSliceProvider.java:327) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at androidx.slice.SliceProvider.onCreate(SliceProvider.java:208) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.content.ContentProvider.attachInfo(ContentProvider.java:2092) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.content.ContentProvider.attachInfo(ContentProvider.java:2066) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at androidx.slice.compat.SliceProviderWrapperContainer$SliceProviderWrapper.attachInfo(SliceProviderWrapperContainer.java:77) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: at android.app.ActivityThread.installProvider(ActivityThread.java:7202) 04-13 08:32:41.459 18431 18431 E AndroidRuntime: ... 10 more 最终解决掉systemui空指针问题即可。标签:function,13,recovery,04,Auto,08,18431,32,android 来源: https://blog.csdn.net/huangyabin001/article/details/116046023
本站声明: 1. iCode9 技术分享网(下文简称本站)提供的所有内容,仅供技术学习、探讨和分享; 2. 关于本站的所有留言、评论、转载及引用,纯属内容发起人的个人观点,与本站观点和立场无关; 3. 关于本站的所有言论和文字,纯属内容发起人的个人观点,与本站观点和立场无关; 4. 本站文章均是网友提供,不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属;如您发现该文章侵犯了您的权益,可联系我们第一时间进行删除; 5. 本站为非盈利性的个人网站,所有内容不会用来进行牟利,也不会利用任何形式的广告来间接获益,纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。