This will allow us to add some test cases to verify that under
certain phone/signal conditions we get out the icons we expect.
This will let us break less things when refactoring for MSIM.
Bug: 18222975
Change-Id: I7bd3e66e7de6b30fede72e40fb6aa37dd523336c
Switching from a dialog to a cling-like view to be more material.
Also moving it into SysUI as it highlights the buttons in nav bar.
This will be triggered directly from recents, but from apps it
will be triggered by the PhoneStatusBar. In the case that apps
trigger the request, there will be a 'no thanks' button so that
users can refuse.
Bug: 16957435
Change-Id: Ie880f82c66f4b2be98283ed3fa789703c4bd7ed5
Removes lock-to-app request dialog from the AM.
Added a showScreenPinningRequest to IStatusBar to handle the
flow from app requesting lock task to showing the dialog.
This CL also allows startLockTaskOnCurrent (system|signature) to
start lock task directly. (Note: this is the less locked version
that always allows exit through back + recents)
Bug: 16957435
Change-Id: I284918dd5989de6cb2767c2a717529eb5e9c6db4
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
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
