When an app is show when locked and in screen pinning the 'overview'
button needs to be shown, regardless of its disabled state.
Bug: 18224921
Change-Id: I896c803347738c936873c0ce5a7480562eb9f639
This change incorporates API council feedback and enables the
TrustAgent whitelisting API.
It also contains a minor cleanup of DPM's use of UserHandle
to eliminate unnecessary object creation.
Fixes bug 17008504
Change-Id: I63cc50169fde54b34406845818bcaf6aadc1a3db
Ensure that we don't reinflate new TaskViews whenever we enter Recents by
keeping the existing TaskStackViews active and returning the existing
TaskViews back into the view pool when Recents is no longer visible.
This CL also ensures that we are preloading the appropriate task metadata
when the user first touches the nav bar, and also reverts the change to use
onEnterAnimationComplete() in favor of the explicitly animation-started
broadcast (to ensure we always get the signal) which fixes a regression
with launching Recents in landscape.
Change-Id: I169fea3cf07a6da3f90b32b005819773c6049ada
It's not dismissed anymore but pushed into the shade
when swiping up.
Also, when swiping down, we now dimiss the HUN.
Bug: 15594813
Change-Id: I0b6a761bebbe281e31bf3b1e20704e2e5da07861
- 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
We previously killed a process when one of its task was
swiped away in the recents UI. This had negative performance
implications for apps with multiple tasks in recents. Now we
will only kill the process if there are no more tasks associated
with it.
Changed also removes the need for the
ActivityManager.REMOVE_TASK_KILL_PROCESS since ActivityManager
will now only kill a task process if it process has no out
standing tasks.
Bug: 17305377
Change-Id: Ibc39bb328d13c7eab05c04798c2f14887923d9d4
Fixes a bug where the keyguard was showing
a charging state even though the device was
not plugged in.
Bug: 18166083
Change-Id: I85a2cda674ffdafb37df70598f4028414a639def
isOccluded is set delayed when unlocking the phone from a
notification, so updatePublicMode used a stale state. Now, only
the fact whether the Keyguard is showing (no matter if occluded or
not) is used to determine the public mode, which is set in a
synchronous manner.
Bug: 18026898
Change-Id: I3e4988f3e806cf15616ee5aa452f81f19d4aa716
So the visibility state is up-to-date when we do a two-finger
expansion gesture, so the height is correct. Also fixes flickering
when overscrolling the initial panel expansion.
Also set thread priority of QS handler thread to background priority,
so it doesn't eat away precious cycles during animations.
Bug: 18183633
Change-Id: I0609509484582d82f0dc307eb2535bc3711b30e3
This fixes a problem where EDU devices show a black screen if
the device is rebooted after setting a pin/pattern/password but
before completing SetupWizard.
The issue is that the system doesn't expect to see a state
where the device is not provisioned but has a pin/pattern/password
because it wasn't possible before. With the addition of the ability
for EDU devices to add a pin/pattern/password, we can now get
into this unforseen state.
The fix ignores provisioning if a password is set so that the
user can reach the security screen to unlock the device and
continue with SetupWizard.
Fixes bug 18022051
Change-Id: Ie88a75530d964c02458c25866f0629877214edf4
If apps are writing malformed content (typically not a PDF file) or if the
PDF content they provide to the print system is password protected, are now
crashed as both of these are app bugs.
bug:17636435
Change-Id: Ifce6a3199e587448dd38f6a84290a965c24b698b
When the notification was updated within the heads up, touches were being
dropped due to an invalid actual height, after a height reset in the update code.
Bug: 18102199
Change-Id: I6c95d360452665464a868b2bc5ce4f6e104b6652
To make the difference from 2-bars more pronounced.
Also fix a tragic regression in status bar demo icon scale.
Bug: 18019421
Change-Id: I4f4e3fea3ed07de5705ea7a1420deb4ccaa398b0
