- Jun 04, 2024
-
-
Alina Zaidi authored
This is so that different Enter/Exit logging reasons can be differentiated by the DestopModeLoggerTransitionObserver. Create a TransitionSource enum which is shared with Launcher. Methods read TransitionSource passed to them and decide on which transitionType to choose when starting transitions. **CUJ -> TransitionType -> Enter/ExitReason** **Earlier** Enter: Handle button -> MOVE_TO_DESKTOP -> APP_HANDLE_MENU_BUTTON Enter: App icon(overview) -> MOVE_TO_DESKTOP -> APP_HANDLE_MENU_BUTTON Enter: Keyboard shortcut -> MOVE_TO_DESKTOP -> APP_HANDLE_MENU_BUTTON Exit: Drag to exit -> EXIT -> DRAG_TO_EXIT Exit: Handle button -> EXIT -> DRAG_TO_EXIT Exit: Keyboard shortcut -> EXIT -> DRAG_TO_EXIT **Now** Enter: Handle button -> APP_HANDLE_MENU_BUTTON -> APP_HANDLE_MENU_BUTTON Enter: App icon(overview) ->APP_ICON_FROM_OVERVIEW->UNKOWN (fix later) Enter: Keyboard shortcut -> KEYBOARD_SHORTCUT -> KEYBOARD_SHORTCUT Enter: Adb Commands -> ADB_COMMANDS -> UNKNOWN (debugging CUJ only) Exit: Drag to exit -> EXIT -> DRAG_TO_EXIT Exit: Handle button -> APP_HANDLE_MENU_BUTTON-> APP_HANDLE_MENU_BUTTON Exit: Keyboard shortcut -> KEYBOARD_SHORTCUT -> KEYBOARD_SHORTCUT Flag: EXEMPT not a major feature/ user visible change Test: Updated unit tests Bug: b/326231756 Change-Id: I9cce7abe62106cd6b11a4f353c288214ea5ee1e7
-
Chris Göllner authored
-
Treehugger Robot authored
-
Mike Schneider authored
-
Ivan Tkachenko authored
-
Siim Sammul authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3107962 Change-Id: Ia373bfacf342d015039b4c0c545a7d149c799bd1 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Siim Sammul authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3107962 Change-Id: I5468a00e3bb1062ce84ddd7469fc5bc3f1449f0a Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Wei Sheng Shih authored
-
Siim Sammul authored
-
Ebru Kurnaz authored
Merge "Update stylus battery notification string from "1% battery remaining" to "Stylus battery 1%"." into main
-
Alina Zaidi authored
Test: Just Refactoring Flag: Just Refactoring Bug: b/326231756 Change-Id: I24bf81b063aad5891510fc702a8c5e8261c2d881
-
Islam Elbanna authored
-
Aurélien Pomini authored
-
Ivan Tkachenko authored
* Launching Desktop wallpaper activity alongside other apps would reset their `mCurrentLaunchCanTurnScreenOn` flag. * Launch options flag added to prevent desktop wallpaper activity stack from moving to front More info: go/pending-intent-resets-turn-screen-on-flag Bug: 343450217 Test: atest CtsWindowManagerDeviceActivity:ActivityVisibilityTests Flag: ACONFIG com.android.window.flags.enable_desktop_windowing_wallpaper_activity DEVELOPMENT Change-Id: I2044185bb259eab5606bd22f86858ad5e708d01b
-
Mitch Phillips authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3105763 Change-Id: I0ccd3b6dc5fb3b61c776dea9653687768dad3a3a Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Mitch Phillips authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3105763 Change-Id: I3c1cc551b6356218d92e3d26a3700bc52399238c Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Siim Sammul authored
Processing the large proto tombstones can cause OOM and there is no point adding tombstones larger than dropbox max capacity as they will not get uploaded. Bug: 343135528 Change-Id: Ib308e48dcfc3282ae7ab0e9fa0827cc8fae97078
-
Mitch Phillips authored
-
Johannes Gallmann authored
-
SongFerng Wang authored
-
Parth Sane authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3099917 Change-Id: I0d29cdfb21c89b7a9f1af530e799ddb5e834413a Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Parth Sane authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3099917 Change-Id: If4a58a49a9e83ee38b46d2c0e185944f7ada89eb Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Eric Laurent authored
-
Parth Sane authored
-
Satish Yalla authored
[automerger skipped] [DO NOT MERGE] Revert "Update the leash position when gaining a new control" am: a0c5f611 -s ours am skip reason: Merged-In I5ba0c33ca4542d27bb4dee4ce849f34721f20b14 with SHA-1 8fab6279 is already in history. Merged-In was found from reverted change. Reverted change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/27453191 Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/27512382 Change-Id: Ie0f796d120ec7ecb78c7697eb5062f9e403d9d5f Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Charles Chen authored
* changes: Enable to override AnimationOptions per change Move AnimationOptions to Change
-
Johannes Gallmann authored
-
Satish Yalla authored
This reverts commit b033de9f Reason for revert: The CL made taskbar flickers Bug: 343521630 Change-Id: Ie8e7a3f4751cc71f80596099fea73f3e1a848a52
-
Charles Chen authored
Since we move AnimationOptions to each change, we should also support to override AnimationOptions per activity-target change. Test: atest TransitionTests Bug: 327332488 Bug: 295805497 Flag: com.android.window.flags.move_animation_options_to_change Change-Id: I302f64b7ad6af7bc6140c33d981f331861cb8c53
-
Charles Chen authored
There are several reasons for this requests: 1. Fix "Dim flicker on package installer" 2. Implement overlay transition by animation resources override 3. Activity Embedding Animation Customization Test: atest TransitionTests ActivityEmbeddingAnimationRunnerTests ActivityEmbeddingControllerTests Bug: 327332488 Bug: 295805497 Flag: com.android.window.flags.move_animation_options_to_change Change-Id: I060b87506a1bf732228ec6b44e7e9dd48782ec0c
-
Riddle Hsu authored
-
Shaowei Shen authored
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3033592 Change-Id: Ic689f7cdd7caa9150a8a7df950a859e217072af9 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3033592 Change-Id: I7e893947535f9321d443630ad139450559cd9d8a Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
-
wilsonshih authored
The timing issue happen when a closing dialog activity request to launch itself again before the task move to background. By default system will play an exit animation for the dialog style window, when the activity being move to foreground again, core will cancel previous exit animation so the window can be visible. But the window surface shouldn't be hide and/or destroy in onExitAnimationDone, since the window is request to be visible again. Bug: 342644763 Test: repeatly closeing the sample activity, verify the window surface of app window won't be hide after the relayout request. Change-Id: Id2718b438ef9f21b0bc4182e50b59de07c445372
-
Mac Young authored
-
Annie Lin authored
Merge "[Interactive Divider] Snap to the closest position in the fling direction when fling is triggered." into main
-
Riddle Hsu authored
Currently the entering pip bounds is applied at the end of enter animation. There could be 2 flickering cases: 1. There is an offset from display cutout while the activity is fullscreen. The offset should be gone once the task no longer overlap with display cutout. But the position change applies before the app redraws. Which looks like shift left and then right in a short time. 2. Before the window frame is recomputed, the surface position is updated with pip bounds, e.g. (0,0)-(200,1000)=(-200,-1000). So this change updates the window surface position until the app has reported its draw transaction, and then applies them at once. Replaced mResizedWhileGone because it was never read for a long time. Bug: 331315278 Test: Assume the target app support auto-pip and it doesn't draw under display cutout. E.g. LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES Enter PiP from 90 degrees to home with 0 degrees. The pip content won't shift horizontally a few frames. Change-Id: I1cd79ccb05ac61edf37dffbbec8cfe37cb85b1f3
-
Treehugger Robot authored
-