History log of /frameworks/base/core/proto/android/server/statlogger.proto
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
21b8d26084d32b94c8f71cfd4e3f47f31a654e6d 30-Mar-2018 Kweku Adams <kwekua@google.com> Cleaning up frameworks protos.

Note: It is currently only safe to renumber the fields because we have
not started using them yet.

* animationadapter: added in http://ag/3709688, but was not following
the indentation policy or the unit naming policy. The durations that
have documentation in
frameworks/base/services/core/java/com/android/server/wm/ state that
they're in milliseconds. These durations didn't have documentation, but
I'm assuming they're in the same units.
* batterystats: was not following the indentation policy
* jobscheduler: AppIdleController was removed in http://ag/3699210 and
the proto was only partially updated
* powermanagerservice: BatterySaverStateMachineProto added in
http://ag/3763026 but was not privacy tagged and the indentation was off
* surfaceanimator: was not following the indentation policy
* remote_animation_target: was not following the indentation policy
* others: weren't following the indentation policy

Bug: 74975371
Test: flash device and run 'test CtsIncidentHostTestCases'
Change-Id: Id012f4690b1d58816fef096523e1a0ea2bccadb0
/frameworks/base/core/proto/android/server/statlogger.proto
ecf4bdb4477d5fcc469c1c4ea7418e16e71037b8 23-Feb-2018 Kweku Adams <kwekua@google.com> Modifying proto csv output to include privacy levels.

Bug: 73775471
Test: use new output in go/irpf
Change-Id: Ib9e836e350f8d664ef66ecfe2539d15d164953be
/frameworks/base/core/proto/android/server/statlogger.proto
5dd532315ed80d4dcdbbe4d0f2b265f7a869157c 27-Jan-2018 Kweku Adams <kwekua@google.com> Adding privacy tags to last few protos.

I left out the protos that aren't officially used in incident.proto in any way.
The notification captions are set in NotificationManagerService and
ConditionProviders. They're not set by the app at all.

Bug: 72393215
Test: flash device and check incident.proto output
Change-Id: I4b36e066740fa1e6755eb946e2bcfa4959d9f9db
/frameworks/base/core/proto/android/server/statlogger.proto
eb898f1b8a3a1c5ce32ec9780c6a3a302347a0b9 24-Jan-2018 Makoto Onuki <omakoto@google.com> Do not throttle EXEMPT apps on battery saver

- Also keep track of # of callback calls and their duration and print them in
dumpsys. Example:

Stats:
UID_STATE_CHANGED: count=141, total=31.9ms, avg=0.226ms
RUN_ANY_CHANGED: count=0, total=0.0ms, avg=0.000ms
ALL_UNWHITELISTED: count=0, total=0.0ms, avg=0.000ms
ALL_WHITELIST_CHANGED: count=0, total=0.0ms, avg=0.000ms
TEMP_WHITELIST_CHANGED: count=28, total=14.9ms, avg=0.532ms
EXEMPT_CHANGED: count=2, total=4.7ms, avg=2.370ms
FORCE_ALL_CHANGED: count=6, total=1.1ms, avg=0.178ms
FORCE_APP_STANDBY_FEATURE_FLAG_CHANGED: count=0, total=0.0ms, avg=0.000ms

Bug: 70565111
Test: atest $ANDROID_BUILD_TOP/frameworks/base/services/tests/servicestests/src/com/android/server/ForceAppStandbyTrackerTest.java
Test: atest CtsBatterySavingTestCases
Test: atest CtsJobSchedulerTestCases
Test: atest CtsAlarmManagerTestCases

Change-Id: Ie4983456dd60f7115a15ee25a8d1bf5c078dac74
/frameworks/base/core/proto/android/server/statlogger.proto