| 365e4c38d58d38bb61d1fdd870346f2f594825fd |
|
18-Sep-2014 |
Christoph Studer <chstuder@google.com> |
Remove FLAG_FOREGROUND_SERVICE on Service.stopForeground()
When services call Service.stopForeground(), remove
FLAG_FOREGROUND_SERVICE from the notification that was supplied
to Service.startForeground().
This enables services to post notifications that become user
dismissable when they switch to being a background service.
Restrict this to targetSdk=L apps to reduce the risk of breaking
existing apps.
Bug: 17551106
Change-Id: Iff8541e5bb2a23ad1fbc9ad80df5fd6eb683148b
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| da4bd209cffad7e47a4bc6e9f02c4bfc333d3d8d |
|
04-Sep-2014 |
Chris Wren <cwren@android.com> |
Keep contact affinities separate across users.
Also ignore people extras on USER_ALL notifications.
Bug: 16213960
Change-Id: Ic0341c88d42d4a4f12cac35c0f41c2746aec02ac
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 3ad4e3a45bbe44129b14c4d391431e44f1e04f0c |
|
02-Sep-2014 |
Chris Wren <cwren@android.com> |
Honor per-app sensitivity setting.
Settings are stored by NotificationManagerService in the policy file,
and are communicated to NotificationListeners via a hidden API on the
RankingMap object.
Bug: 16324353
Change-Id: I2d5cf6782273744cbf9b309dec76780cc0a4c39e
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| cd4adf8b5ef9ac1f90fdddbb405404e173aedc87 |
|
19-Aug-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Fix inconsistent notification comparator
Switch second phase of notification sorting to lexicographic
string comparison in order to enforce a consistent comparison.
Note that this slightly changes the logic: Within groups we
previously fell back on authoritative rank comparison when
one of the notificiations didn't have a sort key. Now we
just replace missing sort keys with " ".
Bug: 16626175
Change-Id: I91f4f4afeeb2c8edda6cd2668011a7367795086c
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 6ac5f8df62a4b6d87cf32797d2886efab8e28226 |
|
18-Jul-2014 |
John Spurlock <jspurlock@google.com> |
Allow user-prioritized packages through in priority mode.
Bug:16396715
Change-Id: I115d717e5c25500407d4f7876f070a1497fb2887
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| bfa5dc4c6c486bdabadb5ea2e356a7d348e3b975 |
|
29-Jul-2014 |
John Spurlock <jspurlock@google.com> |
Zen: Classify notifications using the alarm stream.
Also:
- include audio attributes in dump
- workaround for recent AudioAttributes change.
Bug:16455021
Change-Id: Ib9b047a74cff3e0cc354a5aaa96bc92a400b3845
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 1031c974855ff4117a6d7866e664295786840319 |
|
23-Jul-2014 |
Chris Wren <cwren@android.com> |
Honor the sort and group keys for notification ranking.
Sort notifications naturally, then move group childen to be next their proxy.
The group proxy is the summary, or if no summary exists, the lowest-ranked
member of the group is chosen as the proxy.
Notifications with a sortKey but no group and placed into a synthetic
group that consists of all notifications from that package and user in
the same priority bucket that also have sortKeys.
Expose a new API for listeners to get the group key for the notificaiton.
Bug: 15190903
Change-Id: I324ba0c394affdabb3588ca2ebafa7cf0acad2af
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| cf7ed583080b6c958f5a02817110505bae2a17df |
|
23-Jul-2014 |
Chris Wren <cwren@android.com> |
Revert "Honor the sort and group keys for notification ranking."
This reverts commit df09d4c348f9f2aea10391b27d157d8b71a9e189.
Change-Id: Idbc9ed5c5c83cd0cad5a71872bcc203321a11e9e
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 4a24fd3c7bab53e4e9c127214e7168db0af8800a |
|
17-Jul-2014 |
Chris Wren <cwren@android.com> |
Honor the sort and group keys for notification ranking.
Sort notifications naturally, then move group childen to be next their proxy.
The group proxy is the summary, or if no summary exists, the lowest-ranked
member of the group is chosen as the proxy.
Notifications with a sortKey but no group and placed into a synthetic
group that consists of all notifications from that package and user in
the same priority bucket that also have sortKeys.
Bug: 15190903
Change-Id: I377ed65b9592079446da4a4189f5ab49d28630ec
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.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/NotificationRecord.java
|
| 312d1d01def474e39e4dabbf4aef0b8adaa7caed |
|
08-Jul-2014 |
John Spurlock <jspurlock@google.com> |
Zen: Use default phone app api in call filter.
Remove hardcoded list of packages (for calls).
Use the TelecommManager version until the PhoneManager version
is ready.
Change-Id: I4488f4ea3f0c03f009c84f519eb533e0ea1e07d5
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| d5092bcb11c28f656eb470bd9b74585287fd75b4 |
|
03-Jul-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Allow notifications to transition !ZEN -> ZEN
Bug: 15979100
Change-Id: Ifd620caf2e00f8cd3d9f1458b93585a454af4b74
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 52b7a5a5973c05fe59b751b82ee357fdfc1c5ef7 |
|
06-Jun-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Rank by 'when' instead of 'postTime'
Bug: 15461215
Change-Id: If17e2ff0a6e36ab45da07c2d883fcf8dc8025dc2
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| a344656a010dc3c88aef39109f1ac459792e7607 |
|
04-Jun-2014 |
Chris Wren <cwren@android.com> |
A notification that emerges from Zen Mode interception should beep.
If a notificaiton emerges from Zen Mode due to a ranking
reconsideration (possibly because a long-running query resolved an
important person) then it should get the oportunity buzz, beep, blink,
and send accessibility events.
Save what we need to know about the old notificaiton record on the new
record so we don't have to hold onto it.
Bug: 15383458
Change-Id: I15c7834fef03ff6a676e78e9d2caae24f00720ef
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.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/NotificationRecord.java
|