现象：
本地升级update升级后，提示信息停止运行

堆栈：

04-14 06:42:17.747 2854 3279 E AndroidRuntime: FATAL EXCEPTION: TransactionService
04-14 06:42:17.747 2854 3279 E AndroidRuntime: Process: com.android.mms, PID: 2854
04-14 06:42:17.747 2854 3279 E AndroidRuntime: java.lang.IllegalArgumentException: Unknown URL content://mms/9223372036854775807/part
04-14 06:42:17.747 2854 3279 E AndroidRuntime: at android.content.ContentResolver.delete(ContentResolver.java:1326)
04-14 06:42:17.747 2854 3279 E AndroidRuntime: at com.google.android.mms.util.SqliteWrapper.delete(SqliteWrapper.java:102)
04-14 06:42:17.747 2854 3279 E AndroidRuntime: at com.google.android.mms.pdu.PduPersister.release(PduPersister.java:1652)
04-14 06:42:17.747 2854 3279 E AndroidRuntime: at com.google.android.mms.pdu.PduPersister.getPduPersister(PduPersister.java:301)
04-14 06:42:17.747 2854 3279 E AndroidRuntime: at com.android.mms.transaction.TransactionService.onNewIntent(TransactionService.java:288)
04-14 06:42:17.747 2854 3279 E AndroidRuntime: at com.android.mms.transaction.TransactionService$ServiceHandler.handleMessage(TransactionService.java:696)
04-14 06:42:17.747 2854 3279 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
04-14 06:42:17.747 2854 3279 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)

从堆栈上看是因为，系统没有加载或公布mms 数据库，为什么？
发生异常的 mms 与正常mms 的区别
异常进程：
04-14 06:41:40.832 1431 1476 I am_proc_start: [0,2854,10022,com.android.mms,added application,com.android.mms]
crash后启动的进程：
04-14 06:42:34.957 1431 2936 I am_proc_start: [0,3723,10022,com.android.mms,restart,com.android.mms]
mms因为在AndroidManifest.xml 添加了persistent 属性，所以在系统启动ActivityManagerService 的systemReady() 方法结尾时去启动apk进程。
android:persistent=”true”
梳理了一下他的代码没有问题。

mms 数据库是谁，是不是他的进程发生了问题?
mms: 4b8e997/com.android.providers.telephony/.MmsProvider
* ContentProviderRecord{4b8e997 u0 com.android.providers.telephony/.MmsProvider}
package=com.android.providers.telephony process=com.android.phone

由此可以看到mms 数据库依据的是com.android.phone

查看com.android.phone当时进程堆栈：

----- pid 2996 at 2017-04-14 06:42:24 -----
 Cmd line: com.android.phone

"main" prio=5 tid=1 Native
  | group="main" sCount=1 dsCount=0 obj=0x754ecf70 self=0x7f8a246a00
  | sysTid=2996 nice=0 cgrp=default sched=0/0 handle=0x7f8ee03fe8
  | state=S schedstat=( 1540944525 3943247345 3555 ) utm=129 stm=25 core=1 HZ=100
  | stack=0x7fd36e6000-0x7fd36e8000 stackSize=8MB
  | held mutexes=
  kernel: (couldn't read /proc/self/task/2996/stack)
  native: #00 pc 00000000000683d0  /system/lib64/libc.so (__ioctl+4)
  native: #01 pc 00000000000723f8  /system/lib64/libc.so (ioctl+100)
  native: #02 pc 000000000002d584  /system/lib64/libbinder.so (_ZN7android14IPCThreadState14talkWithDriverEb+164)
  native: #03 pc 000000000002e050  /system/lib64/libbinder.so (_ZN7android14IPCThreadState15waitForResponseEPNS_6ParcelEPi+104)
  native: #04 pc 000000000002e2c4  /system/lib64/libbinder.so (_ZN7android14IPCThreadState8transactEijRKNS_6ParcelEPS1_j+176)
  native: #05 pc 0000000000025654  /system/lib64/libbinder.so (_ZN7android8BpBinder8transactEjRKNS_6ParcelEPS1_j+64)
  native: #06 pc 00000000000e0988  /system/lib64/libandroid_runtime.so (???)
  native: #07 pc 00000000013ad934  /system/framework/arm64/boot.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+200)
  at android.os.BinderProxy.transactNative(Native method)
  at android.os.BinderProxy.transact(Binder.java:503)
  at android.content.ContentProviderProxy.call(ContentProviderNative.java:644)
  at android.provider.Settings$NameValueCache.getStringForUser(Settings.java:1415)
  at android.provider.Settings$Global.getStringForUser(Settings.java:8267)
  at android.provider.Settings$Global.getString(Settings.java:8256)
  at android.provider.Settings$Global.getInt(Settings.java:8323)
  at com.android.internal.telephony.cdma.CdmaSubscriptionSourceManager.getDefault(CdmaSubscriptionSourceManager.java:167)
  at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:130)
  - locked <0x0f659217> (a java.lang.Object)
  at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:88)
  at com.android.internal.telephony.TelephonyPluginBase.makeDefaultPhones(TelephonyPluginBase.java:46)
  at com.qti.internal.telephony.QtiTelephonyPlugin.makeDefaultPhones(QtiTelephonyPlugin.java:44)
  at com.android.internal.telephony.TelephonyPluginDelegate.makeDefaultPhones(TelephonyPluginDelegate.java:105)
  at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:363)
  at com.android.phone.PhoneApp.onCreate(PhoneApp.java:43)
  at android.app.Instrumentation.0
  (Instrumentation.java:1014)
  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4885)

系统启动进程加载数据库的流程为：
系统正常启动流程发布provider 的流程为：

ActivityThread.main
ActivityThread.attach
ActivityManagerService.attachApplication
ActivityManagerService.attachApplicationLocked
ActivityManagerService.generateApplicationProvidersLocked   //将已经加载的 ContentProviderRecord，与当前的 ProcessRecord关联起来。
ActivityThread.bindApplication 
ActivityThread.handleBindApplication 
ActivityThread.installContentProviders 
ActivityManagerNative.getDefault().publishContentProviders
apk.Application.onCreate 

ActivityManager: getContentProviderImpl: from caller=null (pid=1075, userId=0) to get content provider com.android.contacts cpr=null

phone 进程启动时间为：
04-14 06:41:41.107 1431 1476 I am_proc_start: [0,2996,1001,com.android.phone,added application,com.android.phone]
异常发生的时间为：
04-14 06:42:17.747 2854 3279 E AndroidRuntime: Process: com.android.mms, PID: 2854
而phone 进程在 06:42:24 的时候，还在走PhoneApp.onCreate 方法
—– pid 2996 at 2017-04-14 06:42:24 —–

系统进行数据库操作，会首先，通过mProviderMap 获取指定的provider，如果没有获取到，那么通过pms获取要加载Providerinfo, 之后会加载对应的apk，
cpi = AppGlobals.getPackageManager(). resolveContentProvider(name, STOCK_PM_FLAGS | PackageManager.GET_URI_PERMISSION_PATTERNS, userId);

而本进程会wait，
等到对应的apk，加载完provider，调用publishContentProviders，去 notifyAll 等待的进程。

所以发生问题，只有
1、mProviderMap 没有对应的 provider
2、pms 中没有获取对应apk信息，需要加载的providerInfo。
由此发生的问题，并且会打印出对应的log：
ActivityManager: getContentProviderImpl: can’t get cpi from packagemanager
那为啥从pms 中获取不到呢？
pms 是比ams 先执行的systemReady啊
缺少当时的log啊，

规避修改，
将sms 改为非常驻进程，确保 sms 使用phone 数据库时，数据库可以准备ok，以此来规避此问题。