712886fd979f58b0de7cefc3bce885ad7f4493b6 |
|
28-Apr-2018 |
Makoto Onuki <omakoto@google.com> |
Log slow message delivery on Looper Sample log: 04-27 15:30:17.306 1000 942 942 W Looper : Dispatch took 222ms on main, h=Handler (com.android.server.job.JobSchedulerService$JobHandler) {42042fc} cb=null msg=7 start=48162 end=48384 04-27 15:30:17.306 1000 942 942 W Looper : Delivery took 235ms on main, h=Handler (com.android.server.job.JobSchedulerService$JobHandler) {42042fc} cb=null msg=4 start=48149 end=48384 04-27 15:30:17.773 1000 942 942 W Looper : Dispatch took 445ms on main, h=Handler (android.app.ActivityThread$H) {5df4c77} cb=android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA@badd538 msg=0 start=48406 end=48851 04-27 15:30:17.828 1000 942 942 W Looper : Drained 04-27 15:30:24.389 1000 942 942 W Looper : Dispatch took 718ms on main, h=Handler (android.hardware.soundtrigger.SoundTriggerModule$NativeEventHandlerDelegate$1) {d7e9947} cb=null msg=4 start=54749 end=55467 04-27 15:30:24.389 1000 942 942 W Looper : Delivery took 621ms on main, h=Handler (com.android.server.media.MediaSessionRecord$MessageHandler) {5851574} cb=null msg=7 start=54846 end=55467 04-27 15:30:24.499 1000 942 942 W Looper : Drained Bug: 78590632 Test: Boot and check log Test: setprop log.looper.1000.android.bg 1 and runtime-restart and check log Change-Id: Ief1fc65b40b8a3d583879f55a76288e3dba6be7d
/frameworks/base/services/core/java/com/android/server/UiThread.java
|
daf72b1bd190eb9df405347419c19a98b58bb89c |
|
01-Nov-2017 |
Michael Wright <michaelwr@google.com> |
Change shared looper tag from ACTIVITY_MANAGER to SYSTEM_SERVER Most of these are shared, so enabling all ActivityManager logging just to get looper traces seems wrong. Test: build, trace with system_server tag, see looper info Change-Id: I3741dbacab25f5c02f6f8d17f0c8377d8f842776
/frameworks/base/services/core/java/com/android/server/UiThread.java
|
479bb430d1554ff84cdf63fb4652cec88526ccab |
|
29-Mar-2017 |
Makoto Onuki <omakoto@google.com> |
Merge "Correctly set thread group to UiThread's thread." into oc-dev
|
9957151661b8ae65da45a1fb72df5b66176302cb |
|
28-Mar-2017 |
Makoto Onuki <omakoto@google.com> |
Log a warning if a dispatch on UiThread takes more than a certain amount of time. Bug: 34961340 Test: Boot and launch several apps. Change-Id: I38bd85a1dd9c572242d04f550df4a979f5f3bea5
/frameworks/base/services/core/java/com/android/server/UiThread.java
|
be7878db546e160906d34ca1cd7d518df166f80b |
|
28-Mar-2017 |
Makoto Onuki <omakoto@google.com> |
Correctly set thread group to UiThread's thread. Bug: 36683525 Test: Manual (booted and launched several apps.) Change-Id: Iff65b306e302aa2aaa2321d3faf254414f9ce1e7
/frameworks/base/services/core/java/com/android/server/UiThread.java
|
4074ad01e898605c64a80a8cb14c10bdbedf1bdb |
|
09-Jul-2016 |
Tim Murray <timmurray@google.com> |
Sets android.ui to be in the fg stune group. setThreadGroup(TOP_APP) will place a thread in the fg stune group but not the top_app cpuset. This allows android.ui to get more runtime to render transitions between activities without impacting its CPU placement. bug 29512132 Change-Id: I95e031975f83290f88ac6e538abf1062aea27ed4
/frameworks/base/services/core/java/com/android/server/UiThread.java
|
74cd3de6f4889d54a3da930de5e7ad00b97f03e9 |
|
07-Apr-2016 |
Jeff Sharkey <jsharkey@android.com> |
Automatically trace messages on shared loopers. There are a handful of looper threads in the system_process that are shared by dozens of different internal services. To help track down what these operations are, tag the processing of each message with a string that tries describing where it originated from: the class name of the Handler, and the message number or class name of the Runnable. Bug: 28046299 Change-Id: I409ec43fea8daaae4fd70df05d4fed929a7249ae
/frameworks/base/services/core/java/com/android/server/UiThread.java
|
4ccb823a9f62e57f9d221f83a97e82967e79a9e5 |
|
17-Jan-2014 |
Jeff Brown <jeffbrown@google.com> |
Refactor display manager service to new pattern. Transform DisplayManagerService into a SystemService and start cleaning up other local services that it uses from window manager and input manager. Clean up service thread initialization. Remove unnecessary static variables from ActivityManagerService. It's starting to become clear that we really need a better way to manage service dependencies. Boot phases don't quite cut it. Change-Id: If319dbd7cbfbd4812fe55ece969e818d4b20755b
/frameworks/base/services/core/java/com/android/server/UiThread.java
|
9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories Refactored the directory structure so that services can be optionally excluded. This is step 1. Will be followed by another change that makes it possible to remove services from the build. Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/core/java/com/android/server/UiThread.java
|