History log of /frameworks/base/services/core/java/com/android/server/notification/RateEstimator.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
888b7a8faf7d6c2aa4272bebeb875eac9a2ff21c 17-Jun-2016 Chris Wren <cwren@android.com> assume a generous prior in the rate estimator

currently with one data point the estimator is biased high. If we don't
have any data we want to be biased low to allow the first interaction
to be an isolated burst.

Also add metrics for enqueue rate to make it easier to debug this
code in the future (currently we only have metrics after the
rate limiter).

Bug: 29379789
Change-Id: I7b1d379290a55f120d039fd29d1bc0abbc6d4932
/frameworks/base/services/core/java/com/android/server/notification/RateEstimator.java
fd303327083fdf309b9d8a15343f9eb70c014b11 24-May-2016 Tony Mak <tonymak@google.com> Fix first notification of each app is not shown

When app tries to post its first notification,
value of now is equal to that of mLastEventTime.
And hence getRate return a very large number.

Bug: 28902358

Change-Id: If5b5b3c46e2bb80a9b40988ba7f7d777e40cc8e7
/frameworks/base/services/core/java/com/android/server/notification/RateEstimator.java
c8673a88fed53715d2295a535535c7ce7acbe7b6 17-May-2016 Chris Wren <cwren@android.com> rate limit notification enqueues

This is distinct from and in addition to the limit on the number of
distinct notifications. This includes many updates to a single
notification.

Bug: 28693065
Change-Id: I5ec0911716cace91d3ad85435a5c6123b290b3a2
/frameworks/base/services/core/java/com/android/server/notification/RateEstimator.java