| 1b8b22b1a412539020f78a132cff7c8fa7fae258 |
|
20-May-2015 |
John Spurlock <jspurlock@google.com> |
Zen: Calendar auto-rule tracks primary calendar for corp profile.
- Track the calendar provider for the managed profile user if found.
- Add userId to the shared data structure to disambig calendar ids.
- Delay rule update a bit to guard against chatty updates.
- Fix logging in calendar rule.
Bug: 21155107
Change-Id: Id2303fcc39b1fa7417b1844b7869d773ef92434c
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 807749301fcbda892dfc8a5832b19acf7d1cf53b |
|
07-May-2015 |
John Spurlock <jspurlock@google.com> |
Zen: Simplify notification policy api, add zenmode api.
- Remove the concept of a notification policy management token
in favor of a simple grant/deny per app. Currently, all requests
are immediately granted.
- Add zen mode getter/setting, limit to apps that have been granted
policy access.
- Add intent for zen mode changes.
- Public name for zen mode = "interruption filter", moved from
NotificationListenerService to NotificationManager.
- Add settings metadata for new DND access Settings screen.
- Add the split sender settings for calls vs messages to the public
Policy api.
- This change is meant to finalize the public api, persisting
granted app status and showing the user-visible dialog will be
done as followups.
Bug: 18298798
Change-Id: I511be98d69939f057c0c7dc1a6dfe63d1c468193
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| d69e4c1460017062e7c36be55801cb434ad19d97 |
|
24-Apr-2015 |
Dianne Hackborn <hackbod@google.com> |
Update use of procstate for services.
Now that we have a separate foreground service proc state
(above a sleeping top app), update various system services
to put their bindings into this state when appropriate.
There are two new bind flags for this -- one that just always
makes it a foreground service, another that only does it when
the device is awake (useful for things like the wallpaper).
And with all of that, tweak network policy manager to only
include apps that are at least foreground service state when
in power save and device idle modes. This will allow us to
further reduce the set of apps that have network access
(in particular not giving access to the current top app when
the screen is off), hopefully leading to even better battery
life.
Change-Id: I91d85a5c5ed64e856149e9a5d94a634a7925ec7f
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 6597e3435f8abfedbb9a4f1bfb10cc17ea7f38bf |
|
17-Feb-2015 |
Christopher Tate <ctate@google.com> |
Notification listener backup & restore
We now back up & restore the set of enabled notification listeners. Post-
restore, a listener that had been enabled on the ancestral device will be
enabled on the current device as soon as it's installed, matching the
user's previous configuration. After this has happened the enable/disable
state for that app is not "sticky"; disabling it again will work as
expected.
The infrastructure for accomplishing this is general: it can be leveraged
by any ManagedServices derivative. There's a bit of extra wiring in the
settings provider to support the restore-time information flow as well.
This is because ManagedServices -- like many other parts of the system --
monitors writes to the settings provider and does work in response to new
writes of the elements that it cares about. Unfortunately this means that
there is no way to use the BackupAgent's restoreFinished() hook to post-
process the restored data: by the time it is run, the ManagedService's
observers have already executed and culled any unknown components from
the description that was just pushed into settings.
As of this patch, the settings provider's restore logic knows that a
particular settings element will require a message to interested observers
about the restore-driven change. The message is delivered as a broadcast,
and is sent after the new value has been committed to the settings db.
Adding other system ManagedService handling that parallels this will only
require adding a new corresponding entry to the table of individual settings
for which the relevant "this settings element is being restored" broadcast
is sent, found in SettingsHelper.
(It isn't sent for all settings elements because very few settings elements
have semantics that require it; 3rd party code won't be running yet during
platform restore anyway; and sending up to hundreds of broadcasts during
setup & restore is far from ideal.)
Bug 19254153
Change-Id: Ib8268c6cb273862a3ee089d2764f3bff4a299103
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 955d8d69ea6caabce1461dc25b339b9bf9dc61a6 |
|
08-Oct-2014 |
Dianne Hackborn <hackbod@google.com> |
Put in real "code" (aka marketing) name.
Change-Id: Idb3976edfae37293ed75cb5b869b4b42d8042bbe
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| b53dfd4faeb57a51b6cdfc6bde6a441ef9a7ec31 |
|
12-Sep-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Refresh ManagedServices on user switch
Fix a bug where ManagedServices didn't unbind from obsolete and
bind to new services after switching the current user.
Bug: 17477093
Change-Id: Ica28978a01f84ba17bdd93e2feaf68547e837bcc
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 4db0d98b42a723f2e16c6595e85e866fd26c6d98 |
|
13-Aug-2014 |
John Spurlock <jspurlock@google.com> |
Zen: Downtime now a condition provider, persist conditions.
- Persist the entire exit condition instead of only the id.
- Make downtime a proper condition provider (similar to the
existing countdown provider for time-based conditions)
- Move all downtime-related items out of ZenModeHelper and
into the new condition provider.
- Reevaluate downtime more often, when any of its inputs change.
- Make sure downtime appears as an available condition in the
condition panel when applicable.
Bug:16296125
Bug:16211189
Bug:17031767
Change-Id: I1d8269a4e6fe170ce776bf932dbbdfb29dd25dd7
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 25e2d24f24040e58a61169db797f760b16c11f5d |
|
27-Jun-2014 |
John Spurlock <jspurlock@google.com> |
Add optional package filtering to notification dumpsys.
$ adb shell dumpsys notification p <fragment>
Change-Id: Iddcc45066187e0e9d5812275de132dd6bba2a135
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 5d423844f253951a1d79dabe638aba81a21207bc |
|
23-May-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Don't unbind system listeners
Listeners registered via INotificationMananger.registerListener()
must not be unbound by NoMan because it won't be able to re-bind
them later.
Bug: 15131411
Change-Id: Ic5088252c86e7c32c522ba1606f123cefde3720d
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 3e144d3dfcf209349ead9995877f53feb0b5a66e |
|
22-May-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Allow SysUI to register as listener
Expand ACL of INotificationManger.registerListener() from
system only to system or SysUI.
Also call onListenerConnected() on listeners connected via
INotificationManger.registerListener().
Bug: 15131411
Change-Id: I8f2ce34325ad72c7740b383de2ebb9fb88dea5d3
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| af8d6c44f06d2f8baac2c5774a9efdae3fc36797 |
|
07-May-2014 |
John Spurlock <jspurlock@google.com> |
New quick settings implementation.
Bug:14133785
Change-Id: I7f57f8e7ebcc3e1a06fa5204f477470f14299e1f
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 3b98b3f1f85aff0c84ebef4dd497c146d1b4d248 |
|
01-May-2014 |
John Spurlock <jspurlock@google.com> |
Implement long-term condition subscriptions.
Bind long-term conditions (like "in a meeting") to enter/exit
zen mode automatically.
Persist automatic condition subscriptions to maintain them across
reboots.
Normalize condition state binding: true => enter zen, false => exit.
Change-Id: Icba2b8b25c0a352ae8215f4c0a324e4f966c0165
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| e77bb36d48b6b8b5c3bb6a1195aca469bb237919 |
|
26-Apr-2014 |
John Spurlock <jspurlock@google.com> |
Wire up condition providers to zen mode exit triggers.
Bug:13743109
Change-Id: I4e45d7050d1f9aaa379f46379a3203e61e216a3d
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|
| 7340fc8665ae3f9f1978f42aa0e5e1da85036158 |
|
25-Apr-2014 |
John Spurlock <jspurlock@google.com> |
Introduce condition provider services.
Add the condition provider interface, base class, and associated
system metadata.
Pull out common service management code into a reusable helper,
used by notification listeners and condition providers. The
helper, ManagedServices, is now completely self-contained - it
has no dependencies on NoMan or NoMan abstractions.
Bug:13743109
Change-Id: I6856d40f0a2ead78ac9b5707568559a57e7eb009
/frameworks/base/services/core/java/com/android/server/notification/ManagedServices.java
|