- Tasks were drawing under the navigation in landscape since we did
not account for the nav bar space
- Fixing issue with tiny tasks in landscape
- Fixing issue where pooled views were not being measured or laid out
after resizing.
- Fixing issue where the stack scroll would have out of bounds when
tasks were resized (we animate them into bounds)
Change-Id: Id301dc6891e7ff2692cb040a7df1a5a854ac84a3
- Moving constants to a more explicit flags class, which also handles
tuner changes.
- Removing some unused flags
Change-Id: If370581d431784f606c4b8d0c0face5b9a4b9fad
Recents to freeform animation must hang on the first frame and inform
Recents to hide its views. This mirrors the transition from freeform
to Recents, where the animation needs to hang on the last frame.
We need a special window flag for recents to force a redraw after the
animation launches. At this point Recents will become not visible
from the perspective of the activity manager, which would prevent
further drawing. We make recents ignore that and instead depend on
window visibility which will change after recents exit animation
finishes.
Bug: 24913782
Change-Id: Ief743b7e6fcebb3d8789d4745fb122ac607c1cf0
We should use freeform animation spec not only when the task is already
freeform, but also when it is entering freeform.
Bug: 25669457
Change-Id: I30cba79a149183b0a8b9e1e4751a215cef6a490f
When setting the stack bounds from the system UI we need depend on
DisplayInfo.logicalWidth/Height instead of DisplayMetrics.
DisplayMetrics have values adjusted for status bar and nav bar, but the
Activity Manager doesn't know about that. It expects the stack bounds to
use full display size.
Bug: 25665425
Change-Id: Idf5f3192105b72686d1ad11fe4f42c894bb87fbe
- We should have been using onEnterAnimationComplete instead, which is
more reliable and respects the window transition developer option.
Change-Id: Ib7cd2868283cfe0e5fc79863818a614375072e0f
If the device provisioning is complete, check if we need to show
the keyguard. We don't want it to show launcher after finishing
with setupwizard in the system user.
Bug: 25326078
Change-Id: I326069e29122ebf19a59fc00a9120cd5de70f231
Add granular StorageManager APIs for key creation/destruction and
unlocking/locking. Start passing through an opaque token as part
of the unlock command, but leave it empty for now. We now have a
separate "prepare" method that sanity checks that user directories
are correctly setup.
Define a handful of system properties used for marking devices that
should be operating in FBE mode, and if they're emulating FBE. Wire
a command to "sm", but persisting will come later.
Start using new "encryptionAware" flag on apps previously marked with
coreApp flag, which were apps running in the legacy CryptKeeper
model. Small tweaks to handle non-encryptionAware voice interaction
services. Switch PackageManager to consult StorageManager about the
unlocked state of a user.
Bug: 22358539
Change-Id: Ic2865f9b81c10ea39369c441422f7427a3c3c3d6
- Fixing issue with wrong animation specs being created for tasks that
are offscreen
- Removing unused code and simplifying the logic for task launching, also
pulling this out into another file so that it is easier to read and
understand
- Removing old incorrect call to moveTaskToFront() instead of
startActivityFromRecents()
Bug: 25590404
Change-Id: I25d9530d089a7984fb8c94954a34dd124420755a
So we don't run into race conditions when both the main thread and
the executor thread are calling into window manager.
Bug: 25591212
Change-Id: I6d02170f6b105c9b7b861b6dfc4b76452632d562
It seems common for apk to not have launcher activity. I see it quite
a lot during SUW. It does not seems to be an error.
Change-Id: Iee417b0614ef17940371da9710ff14adbad82e3a
- Only update the focused task as you scroll if we are in touch
exploration mode.
- Use stack's notion of focused task as the currently focused task may
not have a TaskView and can be scrolled offscreen.
Bug: 25590404
Change-Id: I5ef1b66ec74aa1a3131993ed84905210f1e45f18
Because we didn't reset it after sending it to window manager,
they were used again in the next transition, leading to a
wrong animation.
Also fix a bug where we waited forever because
getAppTransitionAnimationSpecs returned null.
Bug: 25583739
Change-Id: Ifcccf2d3cee649f66b4ded1d92c059acfa02ba5b
When the window gets resized, we need to synchronize the
views with the model.
Bug: 25584567
Bug: 25584399
Change-Id: I27d6738cb4984ce91ce79671298bcdc0d317c6e1
- Disallow touch while alt-tabbing
- Allow keyboard to focus tab while scrolling
- Cleaning up some old classes that aren’t really being used
Change-Id: Ibabea093afb711b07f398677d25735421b7c7e53
In a split-user mode, allow SUW and related apps to show UI
until the device is provisioned. Basically this changes the
logic a bit for when to force keyguard to always show on user 0.
Bug: 25326078
Change-Id: I8e862adae1c38efe9874479b532baa7446070035
- Update visuals to spec
- Divider lifts when touching
- Implement basic version of snap points and animations
- Implement touch conflict behavior: If touched around 48x48dp
area around the handle, the divider handles all these touches.
If touched outside of the black background divider, touch goes
directly to underlying window. If touch on the black background
divider, touch is considered slippery and thus the window in
which the touch trace moves gets the touches.
Change-Id: I0307c191ae032672c4b73d439c23cf9833d3fce6
Move docked divider drawing to SysUI. This let's us have real
time shadows in the future. Keep DockedStackDividerController
for placing/visibility in window manager.
Change-Id: I82c10add626d30f2ba180ee2a21cdbe6ddfe0371
Because we retain activity surfaces now, the app transition specs
which were calculated/generated after the onPause() call when going
from recents -> app were too slow. Instead, supply a cross-process
future, which gets fetched when the window manager is about to be
ready to execute the app transition. In practice, this still gets
executed immediately after the onPause call.
If we have a retained surface, this adds some latency, but since we
absolutely need the specs to execute the transition, we have that
latency no matter where exactly we generate the specs.
If we don't have a retained surface, the specs are not calculated on
the critical path, so it's faster.
Bug: 19940527
Change-Id: I80d2c6f6b3a6568a70339619ecefbc3bd8409bd8
