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)
Loading
Please register or sign in to comment