We were setting the alpha of the target window to 0 on the UI thread, and setting it
back to 1, through ClipAnimationHelper on background thread
Bug:109701914
Change-Id: I4abb73298b5e957a66f91c5654b184cdd398724b
* changes:
[automerger] Log source component instead of current task base intent am: 3cc3df59af am: dee4137e5e
[automerger] Log source component instead of current task base intent am: 3cc3df59af
Log source component instead of current task base intent
* changes:
[automerger] Log source component instead of current task base intent am: 3cc3df59af
Log source component instead of current task base intent
is not really invisible, but consider it invisible for window transitions
When a recents animation is cancelled, the callback can be received before or after the
wallpaper animation. To ensure that wallpaper animaiton runs properly, we keep the launcher
forceInvisible=true, only for that particular animaiton and false everywhere
Bug: 109735443
Change-Id: I5b22cc3327c8cd53a836d10e09fc88ae103becfc
- Report original launch source component to ensure app relaunches can be
associated with the same app for predictions.
Bug: 109698096
Bug: 109675704
Change-Id: Icc5e95560777ad827fd2430cf3b3b052b65eb1b6
* changes:
[automerger] Use getLocationOnScreen() to determine home bounds am: 678be9b823 am: 23c2b8c8ec
[automerger] Use getLocationOnScreen() to determine home bounds am: 678be9b823
Use getLocationOnScreen() to determine home bounds
Changing states causing quickscrub to get cancelled and recentsView to
get reset to page 0, causing an abrupt jump.
Bug: 80537625
Bug: 80497058
Change-Id: I19cfe4380bbff15734b9d90dc31596904da27483
Since recentsAnimation and animationCancel come on the event queue, we may skip
recentsAnimation and only process animationCancel if they happen too close to
each other, before the first event is scheduled on eventQueue.
As a result deviceProfile is never initialized.
Prevent crash by skipping logging in this case, we shouldn't be logging it anyway
Bug: 80515833
Change-Id: Ife1d6009bcdc34af6c281d848665145cd235fa40
* changes:
[automerger] Use SyncRtSurfaceTransactionApplier for recents enter/exit am: 80b9314781 am: a7fdc39755
[automerger] Use SyncRtSurfaceTransactionApplier for recents enter/exit am: 80b9314781
Use SyncRtSurfaceTransactionApplier for recents enter/exit
[automerger] Use SyncRtSurfaceTransactionApplier for app opening am: 1008f6d72e am: 65456764cb
[automerger] Use SyncRtSurfaceTransactionApplier for app opening am: 1008f6d72e
Use SyncRtSurfaceTransactionApplier for app opening
* changes:
[automerger] Use SyncRtSurfaceTransactionApplier for recents enter/exit am: 80b9314781
Use SyncRtSurfaceTransactionApplier for recents enter/exit
[automerger] Use SyncRtSurfaceTransactionApplier for app opening am: 1008f6d72e
Use SyncRtSurfaceTransactionApplier for app opening
> Using white scrim on adjescent tiles in overview
> Using a ligher scrim in dark-theme+dark-text
Bug: 80253867
Change-Id: I3f257d3addaca8bc5970a61722f5ae0e7af89382
Now that Clear-all button is visible for accessibility, there is no need
in it.
Bug: 80156299
Test: Manual
Change-Id: I5997692be015947692a8bb720a449d1d36302526
* changes:
[automerger] Accounting for one frame jump when starting a fling animation am: 9c3f172d9c am: 4205b54ca8
[automerger] Accounting for one frame jump when starting a fling animation am: 9c3f172d9c
Accounting for one frame jump when starting a fling animation
* changes:
[automerger] Enable accessibility of Clear All button. am: a3e48d8035 am: 6ad288f99b
[automerger] Enable accessibility of Clear All button. am: a3e48d8035
Enable accessibility of Clear All button.
* changes:
[automerger] Fix clipping recents when scaling down am: 615ad40c38 am: 7f510c5886
[automerger] Fix clipping recents when scaling down am: 615ad40c38
Fix clipping recents when scaling down
Android Build Merger (Role)
Sunny Goyal
Winson Chung
TreeHugger Robot
Tony Wickham
Tracy Zhou
Jorim Jaggi
Vadim Tryshev