Commit a87cd5da authored Jul 28, 2017 by Neil Fuller

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

parent b967f5e5

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

+1 −1

Original line number	Diff line number	Diff line
		@@ -1194,7 +1194,7 @@ public final class SystemServer {
		if (startRulesManagerService) {
		traceBeginAndSlog("StartTimeZoneRulesManagerService");
		mSystemServiceManager.startService(TIME_ZONE_RULES_MANAGER_SERVICE_CLASS);
		Trace.traceEnd(Trace.TRACE_TAG_SYSTEM_SERVER);
		traceEnd();
		}

		traceBeginAndSlog("StartAudioService");