Why cannot be found when the Android system is started

Why cannot be found when the Android system is started

We have encountered a problem that the system cannot run after the Android boot interface (bootanimation,

The system keeps waiting for... logs

What services seem to be waiting for to start?

Therefore, it is suspected that the system server is blocked.

The debugging method is as follows:

1. adb shell mkdir/data/anr/

2. adb shell ps | grep system_server

System1138234 908376 39440 ffffffff 40061a54 S system_server

3. adb shell kill-3 1138

4. adb shell pull/data/anr/trace.txt

----- Pid 1138 at 08:40:42 -----
Cmd line: system_server


JNI: CheckJNI is off; workarounds are 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 = 0x00009ee58 self = 0x414be920
| Shard id = 1138 nice =-2 sched = 0/0 MRM = 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. (RegisteredServicesCache. java: 134)
At android. content. SyncAdaptersCache. (SyncAdaptersCache. java: 43)
At com. android. server. content. SyncManager. (SyncManager. java: 399)
At com. android. server. content. ContentService. getSyncManager (ContentService. java: 75)
At com. android. server. content. ContentService. policychange (ContentService. java: 283)
At android. content. ContentResolver. policychange (ContentResolver. java: 1621)
At com. android. providers. settings. SettingsProvider. sendpolicy (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)

We can clearly see who blocked the running of system_server in the call stack.