Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit ab608e5d authored by Neil Fuller's avatar Neil Fuller
Browse files

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 a87cd5da)
parent 13b17b29

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

+1 −1
Original line number Original line Diff line number Diff line
@@ -1203,7 +1203,7 @@ public final class SystemServer { 
            if (startRulesManagerService) {

            if (startRulesManagerService) {

                traceBeginAndSlog("StartTimeZoneRulesManagerService");

                traceBeginAndSlog("StartTimeZoneRulesManagerService");

                mSystemServiceManager.startService(TIME_ZONE_RULES_MANAGER_SERVICE_CLASS);

                mSystemServiceManager.startService(TIME_ZONE_RULES_MANAGER_SERVICE_CLASS);

                Trace.traceEnd(Trace.TRACE_TAG_SYSTEM_SERVER);

                traceEnd();

            }

            }





            traceBeginAndSlog("StartAudioService");

            traceBeginAndSlog("StartAudioService");