Android GMS Crash 优化方案

其他 2019-08-09 14:54:45 阅读次数: 0

极力推荐Android 开发大总结文章：欢迎收藏
程序员Android 力荐 ，Android 开发者需要的必备技能

GMS(GoogleMobile Service)包是出口国外手机中 Google 必须要预制，过 CTS 认证必须的。

本篇文章主要介绍 Android 开发中的部分知识点，通过阅读本篇文章，您将收获以下内容:

  1. 多次刷机 开机向导过程中com.google.android.gms.ui Crash 解决方案
  2. 恢复出厂设置，com.google.android.gms.ui Crash 解决方案
  3. 恢复出厂，开机向导 com.google.android.setupwizard报错解决方案
  4. 恢复出厂设置或者第一次开机，先闪壁纸再显示开机向导
  5. 多次刷机com.google.android.setupwizard报错
  6. 开机向导点击 On-body com.google.android.setupwizard报错

1.多次刷机 开机向导过程中com.google.android.gms.ui Crash 解决方案

Crash Log如下：

--------- beginning of crash
01-01 00:00:16.892  2210  2473 E AndroidRuntime: FATAL EXCEPTION: IPreferenceServiceThread
01-01 00:00:16.892  2210  2473 E AndroidRuntime: Process: com.google.android.gms.ui, PID: 2210
01-01 00:00:16.892  2210  2473 E AndroidRuntime: java.lang.IllegalArgumentException: Service not registered: wfg@202e22a
01-01 00:00:16.892  2210  2473 E AndroidRuntime:    at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1329)
01-01 00:00:16.892  2210  2473 E AndroidRuntime:    at android.app.ContextImpl.unbindService(ContextImpl.java:1495)
01-01 00:00:16.892  2210  2473 E AndroidRuntime:    at android.content.ContextWrapper.unbindService(ContextWrapper.java:648)
01-01 00:00:16.892  2210  2473 E AndroidRuntime:    at android.content.ContextWrapper.unbindService(ContextWrapper.java:648)
01-01 00:00:16.892  2210  2473 E AndroidRuntime:    at android.content.ContextWrapper.unbindService(ContextWrapper.java:648)
01-01 00:00:16.892  2210  2473 E AndroidRuntime:    at android.content.ContextWrapper.unbindService(ContextWrapper.java:648)
01-01 00:00:16.892  2210  2473 E AndroidRuntime:    at msl.a(:com.google.android.gms@11951440:39)
01-01 00:00:16.892  2210  2473 E AndroidRuntime:    at wfh.run(:com.google.android.gms@11951440:5)
--------- beginning of system

当绑定服务已经解除绑定，再次解除绑定，会出现此异常

解决方案：

修改1：
在ContextWrapper的 unbindService 方法中try-catch IllegalArgumentException 。
frameworks/base/core/java/android/content/ContextWrapper.java
在ContextWrapper的 unbindService 方法中try-catch IllegalArgumentException

修改点2：
在ContextImpl的unbindService 方法中try-catch IllegalArgumentException 。
frameworks/base/core/java/android/app/ContextImpl.java

在ContextImpl的unbindService 方法中try-catch IllegalArgumentException

2.恢复出厂设置，com.google.android.gms.ui crash 解决方案

Crash Log如下：

12-31 21:01:26.711  3776  3776 E AndroidRuntime: FATAL EXCEPTION: main
12-31 21:01:26.711  3776  3776 E AndroidRuntime: Process: com.google.android.gms.ui, PID: 3776
12-31 21:01:26.711  3776  3776 E AndroidRuntime: android.view.WindowManager$BadTokenException:
                                                  Unable to add window -- token android.os.BinderProxy@f176911 is not valid; is your activity running?
12-31 21:01:26.711  3776  3776 E AndroidRuntime:    at android.view.ViewRootImpl.setView(ViewRootImpl.java:567)
12-31 21:01:26.711  3776  3776 E AndroidRuntime:    at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:310)
12-31 21:01:26.711  3776  3776 E AndroidRuntime:    at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:85)
12-31 21:01:26.711  3776  3776 E AndroidRuntime:    at android.app.Dialog.show(Dialog.java:319)
12-31 21:01:26.711  3776  3776 E AndroidRuntime:    at com.google.android.location.network.ConfirmAlertChimeraActivity.a(:com.google.android.gms:164)
12-31 21:01:26.711  3776  3776 E AndroidRuntime:    at rzo.onServiceConnected(:com.google.android.gms:71)
12-31 21:01:26.711  3776  3776 E AndroidRuntime:    at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1223)

Unable to add window -- token android.os.BinderProxy@f176911 is not valid; is your activity running

解决方案如下

在 ViewRootImpl类中，解决恢复出厂设置后的问题
frameworks/base/core/java/android/view/ViewRootImpl.java

Unable to add window -- token android.os.BinderProxy@f176911 is not valid; is your activity running?

3.恢复出厂，开机向导 com.google.android.setupwizard报错解决方案

Crash Log如下：

--------- beginning of crash
01-01 12:00:00.918  1583  1583 E AndroidRuntime: FATAL EXCEPTION: main
01-01 12:00:00.918  1583  1583 E AndroidRuntime: Process: com.google.android.setupwizard, PID: 1583
01-01 12:00:00.918  1583  1583 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.TIME_SET flg=0x25200010 } in com.google.android.setupwizard.time.DateTimeMonitor$1@7465601
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$-android_app_LoadedApk$ReceiverDispatcher$Args_52497(LoadedApk.java:1323)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at android.app.-$Lambda$aS31cHIhRx41653CMnd4gZqshIQ.$m$7(Unknown Source:4)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at android.app.-$Lambda$aS31cHIhRx41653CMnd4gZqshIQ.run(Unknown Source:39)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at android.os.Handler.handleCallback(Handler.java:790)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:99)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:164)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at android.app.ActivityThread.main(ActivityThread.java:6523)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:857)
01-01 12:00:00.918  1583  1583 E AndroidRuntime: Caused by: java.util.ConcurrentModificationException
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at java.util.ArrayList$Itr.next(ArrayList.java:860)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at com.google.android.setupwizard.time.DateTimeMonitor.updateStatus(DateTimeMonitor.java:134)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at com.google.android.setupwizard.time.DateTimeMonitor.-wrap0(Unknown Source:0)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at com.google.android.setupwizard.time.DateTimeMonitor$1.onReceive(DateTimeMonitor.java:73)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$-android_app_LoadedApk$ReceiverDispatcher$Args_52497(LoadedApk.java:1313)
01-01 12:00:00.918  1583  1583 E AndroidRuntime:    ... 9 more
--------- beginning of system

ConcurrentModificationException

解决方案如下：

此问题关键在于解决ConcurrentModificationException，但是没有源码，此问题还未完全解决，尝试规避方案如下：
/frameworks/base/core/java/android/app/LoadedApk.java

throw new RuntimeException 异常没有被try-catch 导致crash

4.恢复出厂设置或者第一次开机，先闪壁纸再显示开机向导

解决方案如下：

主要修改KeyguardServiceDelegate这个类。
frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java

  • 修改点1：

在此类中添加判断方法，获取手机DEVICE_PROVISIONED状态信息。

在此类中添加判断方法

  • 修改点2：

此类的构造方法中，如果获取到的为true,先隐藏

此类的构造方法中，如果获取到的为true,先隐藏

  • 修改点3：

在onScreenTurningOn 中判断显示

onScreenTurningOn 中判断显示

系统原生显示与隐藏方法

5. 多次刷机com.google.android.setupwizard报错

Crash Log如下：

--------- beginning of crash
12-12 15:19:11.984  1471  1471 E AndroidRuntime: FATAL EXCEPTION: main
12-12 15:19:11.984  1471  1471 E AndroidRuntime: Process: com.google.android.setupwizard, PID: 1471
12-12 15:19:11.984  1471  1471 E AndroidRuntime: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=com.android.wizard.NEXT (has extras) }
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1843)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at android.app.Instrumentation.execStartActivity(Instrumentation.java:1557)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at android.app.Activity.startActivityForResult(Activity.java:4228)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at android.app.Activity.startActivityForResult(Activity.java:4187)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at com.google.android.setupwizard.BaseActivity.startActivityForResult(BaseActivity.java:665)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at com.google.android.setupwizard.BaseActivity.nextAction(BaseActivity.java:651)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at com.google.android.setupwizard.BaseActivity.nextAction(BaseActivity.java:637)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at com.google.android.setupwizard.user.SuggestedActionsActivity.onItemSelected(SuggestedActionsActivity.java:226)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at com.android.setupwizardlib.items.RecyclerItemAdapter$1.onClick(RecyclerItemAdapter.java:106)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at android.view.View.performClick(View.java:5624)
12-12 15:19:11.984  1471  1471 E AndroidRuntime:    at android.view.View$PerformClick.run(View.java:22285)

com.google.android.setupwizard 报错log

解决方案如下：

在Instrumentation 类中对Google 开机向导进行特殊处理。
/frameworks/base/core/java/android/app/Instrumentation.java

Instrumentation 类中对Google 开机向导进行特殊处理下

6. 开机向导点击 On-body com.google.android.setupwizard报错

Crash Log如下：

--------- beginning of crash
12-31 19:00:26.668  2010  2010 E AndroidRuntime: FATAL EXCEPTION: main
12-31 19:00:26.668  2010  2010 E AndroidRuntime: Process: com.google.android.setupwizard, PID: 2010
12-31 19:00:26.668  2010  2010 E AndroidRuntime: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.google.android.gms/com.google.android.gms.trustagent.discovery.OnbodyPromotionActivity}; have you declared this activity in your AndroidManifest.xml?
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1805)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.app.Instrumentation.execStartActivity(Instrumentation.java:1523)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.app.Activity.startActivityForResult(Activity.java:4229)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.app.Activity.startActivityForResult(Activity.java:4188)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at com.google.android.setupwizard.BaseActivity.startActivityForResult(BaseActivity.java:665)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at com.google.android.setupwizard.BaseActivity.startFirstRunActivityForResult(BaseActivity.java:719)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at com.google.android.setupwizard.user.SuggestedActionsActivity.onItemSelected(SuggestedActionsActivity.java:217)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at com.android.setupwizardlib.items.RecyclerItemAdapter$1.onClick(RecyclerItemAdapter.java:106)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.view.View.performClick(View.java:5675)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.view.View$PerformClick.run(View.java:22641)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.os.Handler.handleCallback(Handler.java:836)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:103)
12-31 19:00:26.668  2010  2010 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:203)

Unable to find explicit activity class Log

解决方案如下：

com.google.android.setupwizard 解决方案

至此，本篇已结束，如有不对的地方，欢迎您的建议与指正。同时期待您的关注，感谢您的阅读，谢谢！

微信关注公众号： 程序员Android，领福利

猜你喜欢

转载自www.cnblogs.com/wangjie1990/p/11327080.html
今日推荐
开放签电子签章：停止新增，优化体验，前进更进（五一假期前工作）
开源日报 | 中学生开源前端动画引擎；全球首个Llama3 8B中文版开源模型；联想电脑恐出局；Linus讽刺AI炒作
“百模大战”必有一战 | 2024中国“百模大战”竞争格局分析
最强开源大模型 Llama 3 上架 Gitee AI
虽然老乡鸡开源的不是代码，但背后的原因却让人很暖心
富文本编辑器 Quill 2.0 重磅发布，特性、可靠性与开发者体验大幅提升
周排行
SVN同步出现问题
解决 nginx 出现 413 Request Entity Too Large 的问题
第一节 区块链服务BaaS的总体架构以及基本模块设计的一种方案
ITeye 2013年度盘点——社区赠书书单
IDEA / git 和github 的新手使用教程 史上最简单的 IntelliJ IDEA 教程 史上最简单的 GitHub 教程
测试工程方法：测试用例设计综合策略
Spark优化(三)：对多次使用的RDD进行持久化
使用STM32 ST-LINK Utility 设置读保护后不能运行
exgcd 解同余方程ax=b(%n)
Android使用脚本进行多渠道打包
每日归档
更多
2024-04-22(39)
2024-04-21(0)
2024-04-20(6)
2024-04-19(5)
2024-04-18(0)
2024-04-17(5)
2024-04-16(70)
2024-04-15(42)
2024-04-14(0)
2024-04-13(119)

代码天地 © 2018 codetd.com

境外服务器   最新电视剧2022