530052a2fe3b6a6a4246ce28ab0ced647fe7f470 |
|
30-Nov-2014 |
John Spurlock <jspurlock@google.com> |
Zen: New behavior for built-in downtime + nextalarm conditions. - Downtime: Allow user to enter downtime early, offer as an end condition four hours before downtime starts. Available in either none or priority, regardless of settings configuration. - Downtime: Always exit before next alarm if zen=none. - Downtime: Make more like any other condition provider, remove special status (mostly). - Downtime: New auto-triggering rules, allow triggering after a manual condition ends, once. - Decouple NextAlarm + Downtime providers, allow them to offer their conditions at the same time. - Downtime/NextAlarm: Update conditions if they change while being requested, even if unsubscribed. - Make all three built-in condition providers optional, via config. - New internal helper for runtime config. - Don't follow changes to next alarm, consider the condition false. - Isolate downtime calendar logic into separate class (for testing). - Allow a:bb -> a:bb as a valid downtime range (all day). - Volume dialog: configuration establishes maximum number of visible conditions, including built-ins. - Zen mode panel: avoid widget updates during layout transition. - Zen mode panel: move controller callers to background thread. - Zen mode panel: hide/show/rebind rows instead of adding/removing. - ZenLog: Add downtime autotrigger results. - Volume panel: Smarter refresh on ringer/zen changes. Bug: 16373455 Change-Id: I4f801018ddb0beb6eb9fa03a81c79f7949888a3f
/frameworks/base/services/core/java/com/android/server/notification/NextAlarmConditionProvider.java
|
6b0623a1129a7e1bc4949b7dca4fa133ff322c4a |
|
10-Nov-2014 |
John Spurlock <jspurlock@google.com> |
Zen: Pull next-alarm tracking out into separate helper. In preparation for sharing with DowntimeConditionProvider. Bug: 16373455 Change-Id: If8d90187fa399935137c7ba6152925a9106a4596
/frameworks/base/services/core/java/com/android/server/notification/NextAlarmConditionProvider.java
|
7ab8ecd053d08aec230a81fccfcc5a5c780f15c7 |
|
05-Nov-2014 |
John Spurlock <jspurlock@google.com> |
Zen: Track next-alarm condition across reboots. During a reboot, wait for the initial alarm registration - which is traditionally done in response to ACTION_BOOT_COMPLETED. Bug: 16373455 Change-Id: I00dd737fa5c9ea15d646779c5b92e5637a69595a
/frameworks/base/services/core/java/com/android/server/notification/NextAlarmConditionProvider.java
|
37bc92cc2332eb6f864977381135c19d6a081a92 |
|
03-Nov-2014 |
John Spurlock <jspurlock@google.com> |
Zen: Create a new exit condition for "next alarm". - If the user's next alarm is in the next 12 hrs, provide this as an exit condition trigger for leaving none/priority. - Don't display the next alarm condition when downtime is active. - When the next-alarm exit condition is active, follow changes to the next alarm, assuming it remains within the 12-hr window. - Tweak the downtime condition strings to be consistent. Bug: 16373455 Change-Id: I4020b91d323dead998e62d655132eca07438b148
/frameworks/base/services/core/java/com/android/server/notification/NextAlarmConditionProvider.java
|