The wifi spacer should only be shown if the first mobile
network has a data type indicator.
Bug: 18665813
Change-Id: Ifcd3a61ebc8cdb76d134baa23b22f1291edadd28
* commit '16158852e2d91041df6d3c031cefe4b77f0583aa':
Ensure that loading and unloading of tasks happen symmetrically with lifecycle events. (Bug 18574950)
Also protect against a crash that might happen when the notification
is updated during an animation.
Bug: 18572620
Change-Id: Ifd6279df395974f7afd0c708a6c87c64de935c62
When the template of a notification changes during a notification
update, we reinflate all the views but didn't update the dark mode.
Bug: 18537470
Change-Id: Iab9278adcbe3bdf39f86019e61b252db0dda7390
- 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
The user can still snooze the heads up as its in the process of timing
out. In this case, mHeadsUp is already null. We save the package
name so that we can still snooze the package.
Bug: 18639224
Change-Id: I9bcce99a5c912e70a6856b277b61adab9cdcbc33
The ActivityManager.closeSystemDialogs() call (used by,
among other things, the home button) broadcasts
ACTION_CLOSE_SYSTEM_DIALOGS for UserHandle.USER_ALL, rather
than any one user.
Bug: 18629414
Change-Id: I89bfa3f556866e1b27987be2753ce83fd0313998
To do this need to handle the subscription id that comes with all
spn broadcasts and concatenate properly as needed.
Bug: 18223317
Change-Id: I2a1cde0a4bf2f50082288cc5cdeb968fa9aa7dd0
Since we were unloading tasks when the activity was stopped, but only reloading
tasks on the next onCreate()/onNewIntent(), there were cases where the system
would create the activity but then immediately stop and start it (ie. when the
screen is turned off while the activity has resumeWhilePausing=True set in its
manifest). This CL ensures that we reload the tasks with the same state used
the last time the Recents activity was started.
The CL also cleans up some visibility state that was confusing and is no longer
necessary, fixes a small issue with the dismiss button flashing when toggling
Recents quickly, and fixes some cases where the initial stack scroll is set
incorrectly.
+ Calling activity which calls provisioning app only if provisioning
is needed.
+ Hiding Hotspot tile from quick settings when screen is locked.
Bug: 18368949
Change-Id: I5b92a7f2d46c8b5d9b323d6a5d49315694c599f7
