Android system does not start up for reasons to find

After we encountered the Android system boot Interface (bootanimation), the system was unable to run up the problem,

System has always appeared waiting for ... Log

Seems to be waiting for what service to start

Therefore, the system server is suspected to be block

The debugging methods are as follows:

1. ADB Shell mkdir/data/anr/

2. ADB Shell PS | grep system_server

System 1138 234 908376 39440 ffffffff 40061a54 S system_server

3. ADB Shell kill-3 1138

4. ADB Shell Pull/data/anr/trace.txt

-----PID 1138 at 2014-01-01 08:40:42-----
CMD Line:system_server


Jni:checkjni is off; Workarounds is off; Pins=1; globals=289


DALVIK THREADS:
(mutexes:tll=0 tsl=0 tscl=0 ghl=0)


"Main" prio=5 tid=1 MONITOR
| group= "main" scount=1 dscount=0 obj=0x4159ee58 self=0x414be920
| systid=1138 nice=-2 sched=0/0 Cgrp=apps handle=1073963348
| State=s schedstat= (6367457522 242583118 5270) utm=595 stm=41 core=0
At Com.android.server.am.ActivityManagerService.registerReceiver (activitymanagerservice.java:~13106)

-Waiting to lock <0x41965278> (a Com.android.server.am.ActivityManagerService) held by tid=27 (Inputdispatcher)

At Android.app.ContextImpl.registerReceiverInternal (contextimpl.java:1458)
At Android.app.ContextImpl.registerReceiverAsUser (contextimpl.java:1433)
At Android.content.pm.registeredservicescache.<init> (registeredservicescache.java:134)
At Android.content.syncadapterscache.<init> (syncadapterscache.java:43)
At Com.android.server.content.syncmanager.<init> (syncmanager.java:399)
At Com.android.server.content.ContentService.getSyncManager (contentservice.java:75)
At Com.android.server.content.ContentService.notifyChange (contentservice.java:283)
At Android.content.ContentResolver.notifyChange (contentresolver.java:1621)
At Com.android.providers.settings.SettingsProvider.sendNotify (settingsprovider.java:262)
At Com.android.providers.settings.SettingsProvider.insertForUser (settingsprovider.java:941)
At Com.android.providers.settings.SettingsProvider.call (settingsprovider.java:645)
At Android.content.contentprovider$transport.call (contentprovider.java:325)
At Android.provider.settings$namevaluecache.putstringforuser (settings.java:903)
At Android.provider.settings$system.putstringforuser (settings.java:1169)
At Android.provider.settings$system.putintforuser (settings.java:1274)
At Android.provider.settings$system.putint (settings.java:1268)

You can clearly see the call stack, who is blocking the operation of the System_server.

The Android system does not start the cause lookup