commit ab608e5dbc35c7201592419c4a1081665a249ae5
author Neil Fuller <nfuller@google.com> Fri Jul 28 17:16:11 2017 +0100
committer Neil Fuller <nfuller@google.com> Mon Jul 31 15:20:16 2017 +0100
tree 6c1369cdff742ca9598d26e65122d1e64d0a1cb1
parent 13b17b29905c33a370989a80722b2f920aaa4ae5

Fix tracing call for RulesManagerService startup

The tracing call was correct for aosp/master, but the tracing
code had been changed internally. The incorrect call meant it
wasn't actually tracking the points we're interested in and
it was reporting incorrectly (by ~1000 millis).

Bug: 64141572
Test: boot device / adb logcat
Change-Id: If11354d1d73cf90973ed4f43e885ae28ca1346ea
(cherry picked from commit a87cd5daa0bee1ed045e726194fca2deab6d88c5)

services/java/com/android/server/SystemServer.java

diff --git a/services/java/com/android/server/SystemServer.java b/services/java/com/android/server/SystemServer.java
index 61267ef..7b027bb 100644
--- a/services/java/com/android/server/SystemServer.java
+++ b/services/java/com/android/server/SystemServer.java
@@ -1203,7 +1203,7 @@
             if (startRulesManagerService) {
                 traceBeginAndSlog("StartTimeZoneRulesManagerService");
                 mSystemServiceManager.startService(TIME_ZONE_RULES_MANAGER_SERVICE_CLASS);
-                Trace.traceEnd(Trace.TRACE_TAG_SYSTEM_SERVER);
+                traceEnd();
             }
 
             traceBeginAndSlog("StartAudioService");