| 5eab2b72afe5b20dc66c237b1cceedfc09de2d52 |
|
16-Jun-2015 |
Chris Wren <cwren@android.com> |
high-frequency notification stats.
Aggregate and then periodically report stats that are high-frequency
because they are driven by app behavior, not user behavior.
Reuse the NotificationUsageStats facility.
Remove redundant stats.
Lessen memory foot print.
Enable in-memeory aggregates with small, bounded memory footprint.
Bug: 20258744
Change-Id: I87e391419c53917fa13c68a56f8cdb40a7c8e548
/frameworks/base/services/core/java/com/android/server/notification/NotificationSignalExtractor.java
|
| 54bbef435ed857fc68941672799fc8001c101119 |
|
10-Jul-2014 |
Chris Wren <cwren@android.com> |
Implement application-level high priority bit.
Enable checkbox in settings and wire it to NotificationManagerSerivce.
Add RankingHelper to collect ranking configs and logic.
Bug: 15080024
Change-Id: Ib1d3b0b5ca4fcfdc52c2cb6838a009b9addf1094
/frameworks/base/services/core/java/com/android/server/notification/NotificationSignalExtractor.java
|
| 333a61c3a5a83fe9c50ebeb5c947317f61385b7b |
|
28-May-2014 |
Chris Wren <cwren@android.com> |
Track Zen Mode status in the NotificationRecord
This requires the record to be present in makeRankingUpdateForListener,
however, if the ranking object is created before the post to the handler,
then no cloning is necessary.
Depends-On: I907a1ff28123219db1c08889d723ad1b70b191ab
Change-Id: I51fcf689ddbee7715e3387b865f18a715887c943
/frameworks/base/services/core/java/com/android/server/notification/NotificationSignalExtractor.java
|
| 470c1accf5a54f9844a779eafab74e63c09342b5 |
|
21-May-2014 |
Chris Wren <cwren@android.com> |
Fix a concurrency bug in the ranking reconsideration.
If we rely on mNotificationList to be sorted, then we cannot allow
records to change without a corresponding call to sort. Currently
RankingFuture may modify records in a separate thread, while the sort
doesn't happen until later. This creates a window for race conditions.
Instead, RankingFuture should record operations to be performed on the
record that will replayed later, in a transaction along with a sort.
We can't simply overwrite the old record completely because another
future may be concurrently modifying a different aspect of the record.
Two futures that attempt to modify the same aspect will be serialized
and the second will overwrite eventually the first.
Change-Id: I9223cabdc60f72d8e37e6d8119bea1e0127185c0
(cherry picked from commit 77d3e0d0297caca5358879d36e8ba77710eb8e82)
/frameworks/base/services/core/java/com/android/server/notification/NotificationSignalExtractor.java
|
| f953664dc17dca23bd724bd64f89189c16c83263 |
|
17-Apr-2014 |
Chris Wren <cwren@android.com> |
notification ranking infrastructure
Added an ordered list of notifications (n.b. a complete ordering).
Added a mechanism for ranking to be updated asynchronously
Added onNotificationRankingUpdate to NotificationListeners
Added an opaque order update object and a convenience comparator that
uses it to sort notifications for listeners
Repurpose scorers to be ranking preprocessors. The preprocessors will
perform heavy-weight validation of the notification object and memoize
the results to improve efficiency of the ranking comparator.
Current internal comparator implements status quo ordering, except
that notes with a valid contact sort to the top of their priority
bucket.
Change-Id: I7244c65944a9657df41fb313b3cb5a52e149709d
/frameworks/base/services/core/java/com/android/server/notification/NotificationSignalExtractor.java
|