* changes:
[automerger] Use device api level if first_api_level is not set. Bug: 79429532 am: a30bf371e4
Use device api level if first_api_level is not set. Bug: 79429532
- Don't lock when making WM calls (only lock when resetting), and use own
executor since the background executor is fixed to only two threads and
other things can be running on them already (like task loading).
Bug: 78585335
Change-Id: I73dfc380dd99908cfc30ff7c164a9677a5a126e0
- Don't lock when making WM calls (only lock when resetting), and use own
executor since the background executor is fixed to only two threads and
other things can be running on them already (like task loading).
Bug: 78585335
Change-Id: I56e24fbbdeb3b673837982df3fa67e485d03b3b2
> Caret is only visible when the accessibility is enabled
> It is visible in NOTMAL and OVERVIEW state and moves out of the
scrim along with the scrim.
> Acts as an accessible target for various options
Bug: 78172350
Bug: 79215734
Change-Id: I8a968b67e36901859649546295f6491d49cc9ce9
State handlers can now specify atomic and non-atomic components of
their animations to states, which can be specified when creating a
new animation. There is now one atomic animation, when going from
NORMAL to OVERVIEW (and in reverse):
- RecentsViewStateController's animation (scale/alpha) is all atomic
- WorkspaceStateTransitionAnimation has atomic and non-atomic:
- Hotseat and workspace alpha is atomic, as is workspace scale
- Everything else (scrim, translation, qsb and drag handle alpha) is
non-atomic
- All apps progress is non-atomic
Also simplified dragging through overview; no longer pulls against you,
so we use an OvershootInterpolator when flinging instead of our custom
interpolator for the spring effect.
Bug: 76449024
Bug: 78089840
Change-Id: Iafac84d0c2b99ee9cf9dd5b30e2218286713b449
* changes:
[automerger] Enforce Swipe Up gesture to be enabled based on the shipped SDK version am: 2a8f265ab0
Enforce Swipe Up gesture to be enabled based on the shipped SDK version
* changes:
[automerger] Using surface rotation instead of insets to determine seascape configuration am: 59d086c3ce
Using surface rotation instead of insets to determine seascape configuration
- Scale icon down/up atomically at a threshold
- Fix scale of tasks to properly take curve/zoom scale into account
Bug: 78779525
Change-Id: I5909c63b18a993433de7a38b9641f4f38a219807
> Converting the scrim to View, to better avoid overdraw
> Overview and Spring loaded state have different scrim alpha
> When going from overview to all-apps, there is a color scrim drawn over the overview panel.
The slef color is merged with this color to prevent overdraw, and the remaining screen is drawn
with a cut-out round rect path
Bug: 79111591
Change-Id: I26801fde13dd6adb4b06110bbe8087e35cc31847
* changes:
[automerger] Insted of animating the icon of the first task, animating the running task icon am: 28254eec60
Insted of animating the icon of the first task, animating the running task icon
Insets may not correctly indicate seascape configuration in multi-window or
when the presence of device-cutouts
Bug: 79376298
Change-Id: I8268efca0001fe527a0ffefe48cc71e774fad01c
Hyunyoung Song
Tony Wickham
Android Build Merger (Role)
Winson Chung
android-build-team Robot
Sunny Goyal
Jon Miranda
Tracy Zhou
Mehdi Alizadeh
Vadim Tryshev
Bill Yi