| c977f81dad9e07a0f3f5f12fd3dfc1a42675740c |
|
13-Jun-2016 |
Chris Wren <cwren@android.com> |
Revert "boost starred people to at least high importance"
This reverts commit 7e431621c41af719354cb7100c2c9195179cdbe6.
Change-Id: I69e06505f79ecb9e2983cec0d0dcddb7979a3f94
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 7e431621c41af719354cb7100c2c9195179cdbe6 |
|
25-May-2016 |
Chris Wren <cwren@android.com> |
boost starred people to at least high importance
Bug: 28949659
Change-Id: If604062a282db5db463642315a8fa5f7cd6e597c
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 5b03ce95c77e16b46a177af32e640d71b7ff4e12 |
|
19-May-2016 |
Selim Cinek <cinek@google.com> |
Fixed a bug where autobundling could lead to bugs
Notifications could appear twice if a notification with an app
group became bundled and one could not be swiped away anymore.
This is because we were unconditionally copying over the override
key even if the notification just became a group.
This also fixes a nullpointer that could happen with a racecondition
when a notification was cancelled and it tried to be used for autobundling.
This also fixes an issue that the autobundling wasn't working correctly
when a notification didn't have a group set but was set to be a
group summary.
Change-Id: Icd971f16ae0804ce162fd3171fcdd99bd04f3885
Fixes: 28706404
Fixes: 28628237
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 8a1638f66a79dbf471e7e53294ba853b862434e6 |
|
02-May-2016 |
Chris Wren <cwren@android.com> |
copy auto-group decisions to updates
The rocket runs too late to affect auto-grouping for updates before
the UI reacts to the group change, so make sure it stays the same
until the rocket has an opportunity to reconsider.
Bug: 28517296
Change-Id: I16a0509cac06912c8b3139f06474f312207f9f8c
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 248a2e0364ecda36fa91704d5ed4902df3ea6e68 |
|
11-Apr-2016 |
Chris Wren <cwren@android.com> |
Merge "don't copy importance forward" into nyc-dev
|
| 1f602dc3264c2aaf3d9f1552077de1c8a0bbf56e |
|
11-Apr-2016 |
Chris Wren <cwren@android.com> |
don't copy importance forward
copyRankingInformation should only copy side notes to be used by rankers.
Bug: 26919636
Change-Id: I6d0d87d4dc93ced65180ce58a4dcde2cac60e8b6
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| e46bb37acf6d3cfb9974672ace93f5381f70ad99 |
|
17-Mar-2016 |
Julia Reynolds <juliacr@google.com> |
Allow the ranker to autobundle notifications.
Bug: 26709317
Change-Id: I5017a471604e513a7b582cdc2f3472441e108fae
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| f0f629ffe44716b8d900929135142f0ebb9325f4 |
|
25-Feb-2016 |
Julia Reynolds <juliacr@google.com> |
Introduce IMPORTANCE_MIN.
Allow HUNs for >= IMPORTANCE_HIGH.
Allow full screen intents for IMPORTANCE_MAX.
Bug: 22960980
Bug: 26918284
Change-Id: Id4d2b90ea2e21563dbc716db411060d826e73699
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 1ac52a91dc48f29785b34594ab29453a39bd67f5 |
|
24-Feb-2016 |
Chris Wren <cwren@android.com> |
remove some logspam and fix an NPE
notificaiton manager is logspamming, and also dump can fail
while collecting a bugreport if an actionIntent is null.
Bug: 27338511
Bug: 27338098
Change-Id: I8648541469887d62ee64b28d96e0cb7e4fab0f7b
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 73d96fb4bbe1e3796e655314619bf9897d07c929 |
|
19-Feb-2016 |
Julia Reynolds <juliacr@google.com> |
Merge "Remove Notification Topics." into nyc-dev
|
| f5df55302911d6122f742a44d6685ebb5ec5b78c |
|
18-Feb-2016 |
Julia Reynolds <juliacr@google.com> |
Get applicationinfo as user.
Bug: 27237907
Change-Id: I84a07f035904c42f535ef30f2950788f5ac50aba
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| ef37f284364cc45c2ed91bfe04c489d2cedd32d2 |
|
12-Feb-2016 |
Julia Reynolds <juliacr@google.com> |
Remove Notification Topics.
Bug: 23220370
Change-Id: Ifbcdbab1cf6974c192483091512f75762784a98e
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 83fa1073f577333e7f25ca8bc5ce1c13d4c6d9e5 |
|
17-Feb-2016 |
Julia Reynolds <juliacr@google.com> |
Increase the importance of noisy notifications.
For apps with a targetSdkVersion < N.
Bug: 27213267
Change-Id: I4c589d149a28357dbbd26344e7fadb59d8b50672
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| cdee8cd16ac3419d1975919e5d72ce173adc2e7f |
|
25-Jan-2016 |
Chris Wren <cwren@android.com> |
change the default notification rules
should make devices less noisy by default
more metrics so we can tell exactly what we're doing.
Change-Id: I2504df91083074de8fe08c896e017335bc0bc1c7
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 47633425339245a7b126c3e3310994e1a87d5399 |
|
22-Jan-2016 |
Chris Wren <cwren@android.com> |
implement onNotificationEnqueued callback
Bug: 22455414
Change-Id: I9dafc7b8cbf0268b28d9e9fb0cae9c3b451be52c
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 0421e6d58635f347f785ae4c78e8b2a5da327138 |
|
08-Jan-2016 |
Julia Reynolds <juliacr@google.com> |
Sort notifications by importance.
- Importance trumps 'package priority'
- Only notifications with a high enough importance can be intrusive
- default and lower importance notifications don't appear on the lock
screen and appear below the speed bump in the shade
Also, stop downgrading MAX importance noisy notifications.
Bug: 26425560
Change-Id: Ibb952eb6f8d0d336a1060332f58c8ba622f29867
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| de4b2645d929882d3b270accf32031608f150b38 |
|
11-Dec-2015 |
Chris Wren <cwren@android.com> |
unbreak the build,
plus some followon patches from Id3b0a074
Change-Id: I9f667a8d68a68d90c0d7f2fed3f28efcc6720533
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| bdf3376616c276ed18a51185351b44fd16eeae29 |
|
04-Dec-2015 |
Chris Wren <cwren@android.com> |
use importance instead of score
Change-Id: Id3b0a074671943b4fcabb63fe990cbfd1e46bdfd
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 5d25ee7a006fda7150ba251cff92c27130611f88 |
|
20-Nov-2015 |
Julia Reynolds <juliacr@google.com> |
Topics can now have an Importance.
Bug: 22451710
Change-Id: I627121da6c4b85492715a8e8a099656dca52b734
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| f612869ae1190e0885b58a3c33b23d36d7732f06 |
|
05-Nov-2015 |
Julia Reynolds <juliacr@google.com> |
Allow DND mode to suppress visual interruptions.
Bug: 25423508
Change-Id: Idd8242e4bc00a749dbe0b5503c458375fc017072
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| a17703138b0c51226c0e73dd8d34ea037d260aeb |
|
10-Jul-2015 |
Dan Sandler <dsandler@android.com> |
Allow notification strings to be unredacted in dump output.
This won't happen automatically and unredacted strings will
still not appear in bugreports, but if you are attached via
adb you can now do `dumpsys notification --unredact` to get
the contents of String/CharSequence fields and extras
emitted along with the rest of the dump.
The arg handling is also improved so that multiple filters
can be specified at once, e.g. --package (was "p") to
restrict to a single package, and --stats to get JSON
output.
Bug: 20451514
Change-Id: I37fc5ce86c7e28e8f8286917f6764d64bc081108
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| d1dbc92d67af4cb72bb2faff9011d36b6833bbfd |
|
19-Jun-2015 |
Chris Wren <cwren@android.com> |
add rank to notification visibility log
Only sysui knows the true rank, since it can (and does) reorder things.
The visibility logs are down in the service because it has other bits of data.
Bug: 21395744
Change-Id: Ibf9479dc2306fb27fb5df3bf21e161478d36d587
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| e6ddb8a1348d2ea53bc3033be43c4dae922b653a |
|
27-May-2015 |
Chris Wren <cwren@android.com> |
add event timers to all notification logs.
previously, some logs had only some times, and not others.
Bug: 21394955
Change-Id: I0d7af163be23f5a989c35aba6e6f6879672543fc
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 6650e5767b3d69268af7238cfa65dde6a9f2e0a3 |
|
15-May-2015 |
Chris Wren <cwren@android.com> |
log notification longevity and freshness
Split out monolithic visibility notifications into individual logs for
each visibility change with longevity and freshness.
Add exposure time to cancelation logs.
Bug: 20122735
Change-Id: I56c112cdb54fb65b41cfbef4c36ce8706729c5cb
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| d63f9321e62064660d426efd5abbd885c4a24652 |
|
06-May-2015 |
Dan Sandler <dsandler@android.com> |
Icon support comes to Notification.
And you may ask yourself: what is that beautiful icon?
And you may ask yourself: where does that API go to?
And you may ask yourself: is it a resource? is it a Bitmap?
And you may say to yourself: my god, what have I done
(This patch fixes a number of bugs in the initial
implementation, but other than that, it's the same as it
ever was.)
Bug: 18568715
Bug: 21141842
Change-Id: I1d3f9427abd7f0bb57e533fcfac708851ff644b6
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 24bd0be558838db4ff975e97fa986eb317773fc5 |
|
28-Apr-2015 |
Amith Yamasani <yamasani@google.com> |
Mark actually seen notifications as seen
This was missing from a previous CL that was meant to have it.
Change-Id: I856cee8708d988630778ba88b70deaad8730fc1f
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| f47e51ec605fccf7fed9e50d1adc98fbd4e8b340 |
|
17-Apr-2015 |
Amith Yamasani <yamasani@google.com> |
More usage tracking
Notification listeners can now report that a notification
has been seen by the user and that package is then marked
as active.
Bug: 20066058
Change-Id: I336040a52c44c21fd0d78b02ec9a19d448c64b40
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 640e387ce4e8aa97a8139fda54a5f5468e2ff18b |
|
21-Apr-2015 |
Chris Wren <cwren@android.com> |
Add notification lifetime to the cancel message.
Also track the total lifetime in the notificaiton record.
Bug: 20122735
Change-Id: I09668be0161de0e1d8201b069e533a9a2203c83c
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 1d881a1e986c706963c254fbe2b6296a1cd10b75 |
|
19-Mar-2015 |
John Spurlock <jspurlock@google.com> |
HUN: Implement per-package config.
- Keep track of whether or not HUNs are allowed per-package.
- No impact on ranking, purely presentational.
- Simplify RankingHelper with a package table.
- Improve RankingHelper dump.
- Fix some warnings and typos.
Bug: 19776495
Change-Id: I28d69df69b576f4eabbb528eabecb1f736f0e830
/frameworks/base/services/core/java/com/android/server/notification/NotificationRecord.java
|
| 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
|