summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Lee <anwlee@google.com>2015-10-29 17:28:48 -0700
committerAndrew Lee <anwlee@google.com>2015-10-29 17:28:48 -0700
commitf2603cdd864e1b60b0f0e47a082b67a5405756bc (patch)
tree78ad1afd45d3cdfc50b6b014b3d4daaf305ad150
parent72579fe971e0a0c3711438e8852d9659f48101c8 (diff)
Dismiss blocking disabled notification after touch.
Before, it would linger around, even after the user had touched it and visited the settings screen. Feels like more standard behavior for it to be dismissed at this point (user has clearly seen it, and it doesn't really contain any info which needs to persist). Bug: 25377379 Change-Id: I5608a3d735fd084f4493c0fcd51d9dcedf04dc6f
-rw-r--r--src/com/android/dialer/filterednumber/FilteredNumbersUtil.java3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/com/android/dialer/filterednumber/FilteredNumbersUtil.java b/src/com/android/dialer/filterednumber/FilteredNumbersUtil.java
index 8a0d79233..1f977de9a 100644
--- a/src/com/android/dialer/filterednumber/FilteredNumbersUtil.java
+++ b/src/com/android/dialer/filterednumber/FilteredNumbersUtil.java
@@ -336,7 +336,8 @@ public class FilteredNumbersUtil {
.setContentTitle(context.getString(
R.string.call_blocking_disabled_notification_title))
.setContentText(context.getString(
- R.string.call_blocking_disabled_notification_text));
+ R.string.call_blocking_disabled_notification_text))
+ .setAutoCancel(true);
final Intent contentIntent =
new Intent(context, BlockedNumbersSettingsActivity.class);