| commit | 89aa2261903fd09b08a2210a7a1b35d329f8330a | [log] [tgz] |
|---|---|---|
| author | Chris Wren <cwren@google.com> | Fri May 05 18:05:56 2017 -0400 |
| committer | Chris Wren <cwren@google.com> | Thu May 11 17:19:01 2017 -0400 |
| tree | 938eb2216b70c0b507d87f814b6a12c9885edf9d | |
| parent | 629c20c9991ab8da3732ba554794fffd7922f185 [diff] [blame] |
add a global control for badging Content observer callbacks don't specify the user, so scan all the users we know about. User switches will also trigger an update which will explicitly check the setting for the (now) current user. Migrate tests to TestableContext to allow the test to safely override secure settings. Bug: 36021111 Test: runtest systemui-notification Change-Id: I588068382912955da114cc351df7a1e7b4f0733f
diff --git a/packages/SettingsProvider/src/com/android/providers/settings/SettingsProtoDumpUtil.java b/packages/SettingsProvider/src/com/android/providers/settings/SettingsProtoDumpUtil.java index f475361..9309359 100644 --- a/packages/SettingsProvider/src/com/android/providers/settings/SettingsProtoDumpUtil.java +++ b/packages/SettingsProvider/src/com/android/providers/settings/SettingsProtoDumpUtil.java
@@ -1434,6 +1434,9 @@ dumpSetting(s, p, Settings.Secure.DEVICE_PAIRED, SecureSettingsProto.DEVICE_PAIRED); + dumpSetting(s, p, + Settings.Secure.NOTIFICATION_BADGING, + SecureSettingsProto.NOTIFICATION_BADGING); } private static void dumpProtoSystemSettingsLocked(