- Apr 18, 2024
-
-
wilsonshih authored
While starting app & before app window draw, letterbox can only check whether to show letterbox by starting window, but starting window can transfer to another activity during start app process. To ensure letterbox state stable during animation, only check the visibility state of activity, so it won't affected by window. Bug: 328598627 Test: atest SizeCompatTests LetterboxUiControllerTest Test: launch app throught trampoline activity, verify the letterbox of closing activity stay visible during transition animation. Change-Id: I6c18c9b507f0c732d58c739bee068f835fad4391
-
- Apr 17, 2024
-
-
Siim Sammul authored
-
Oleg Blinnikov authored
-
Alex Dadukin authored
-
Eric Laurent authored
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/26982857 Change-Id: I1ad42d57caba2c6e0ffacd8481c06d18d6ff3957 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Ioana Alexandru authored
-
Ioana Alexandru authored
-
Eric Laurent authored
-
Piotr Wilczyński authored
-
Shaowei Shen authored
-
Jernej Virag authored
-
Tetiana Meronyk authored
-
Riddle Hsu authored
-
Treehugger Robot authored
[automerger skipped] Merge "Remove rundundant <test> tag" into android14-tests-dev am: 629a92de am: d49cc1ef am: 8b68d0a8 am: c470364b -s ours am skip reason: Merged-In I1e3fa112edcac79cceaa64fee170a2633ee131b2 with SHA-1 94be3681 is already in history Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: I029f612705a748606e79ad73ea65b5dff1404493 Signed-off-by:
-
Automerger Merge Worker authored
Merge "[automerger skipped] Merge "Remove rundundant <test> tag" into android14-tests-dev am: 629a92de am: d49cc1ef am: bd14b31c -s ours" into main
-
Treehugger Robot authored
Merge "Remove rundundant <test> tag" into android14-tests-dev am: 629a92de am: d49cc1ef am: 8b68d0a8 Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: I9c20196e4e8d8e4e0942605ab9c2c9beebb94ec5 Signed-off-by:
-
Automerger Merge Worker authored
[automerger skipped] Merge "Merge "Remove rundundant <test> tag" into android14-tests-dev am: 629a92de" into main am: 1bd43fbb am: 7dedbd7e -s ours am skip reason: Merged-In I1e3fa112edcac79cceaa64fee170a2633ee131b2 with SHA-1 94be3681 is already in history Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: Id1e66b2d856b2e73ff05024e6f065019b1a57d02 Signed-off-by:
-
Treehugger Robot authored
[automerger skipped] Merge "Remove rundundant <test> tag" into android14-tests-dev am: 629a92de am: d49cc1ef am: bd14b31c -s ours am skip reason: Merged-In I1e3fa112edcac79cceaa64fee170a2633ee131b2 with SHA-1 94be3681 is already in history Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: Ib70acc367422a92437d5e276254dba37475a7af0 Signed-off-by:
-
shaoweishen authored
Delete obsolete SETTINGS_NEW_KEYBOARD_UI flag Bug: 330517633 Test: atest FeatureFlagUtilsTest Change-Id: I5fe52a3018ae78fa036127963982f7bfd1b18f7d
-
Automerger Merge Worker authored
Merge "Merge "Remove rundundant <test> tag" into android14-tests-dev am: 629a92de" into main am: 1bd43fbb Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: I812ef658897fe6407a499ec1af7ee08e55f1baaa Signed-off-by:
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: I8609ecd33ed5f73acb54dd1a88fb2cb7ab415861 Signed-off-by:
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: I6d358c35df88105399f975fd0ce86cf0a2190c82 Signed-off-by:
-
Treehugger Robot authored
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: I020406b539afe7825944d3ed6b2d5a2cc234bc5b Signed-off-by:
-
Automerger Merge Worker authored
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3045692 Change-Id: I0804e02e21071cfc9ea4167c7ba3e8aaff81ee70 Signed-off-by:
-
Treehugger Robot authored
-
Treehugger Robot authored
-
SongFerng Wang authored
-
Sherry Zhou authored
When transitioning from AOD to Lockscreen, translationY is calculated from `aodToLockscreenTransitionViewModel`, and we need to provide currentTranslationY function, which is wired from BurnInParameters. Otherwise, translationY is always 0. Test: manually verified that the small clock and smartspace don't jump when transitioning from AOD to lockscreen. In order to do this, I turned on AOD in settings, pressed the power button to get into AOD and then pressed the power button again, to wake up from AOD. I verified that the small clock and smartspace don't "jump"; instead they translate smoothly from burnIn prevent position in AOD to Lockscreen position. I attached videos for before and after in the second comment of b/334982979. Bug: 334982979 Flag: ACONFIG com.android.systemui.compose_lockscreen DEVELOPMENT Change-Id: I707bf1354b14df5e04309b40c6080e26a7ac2bdc
-
Reema Bajwa authored
-
YK Hung authored
-
Chelsea Hao authored
[automerger skipped] Merge "Use context from SystemUiDialog to fix button style." into 24D1-dev am: 931000e0 -s ours am skip reason: Merged-In I4e0bd33975fc4d44bb0680a69fca4232328a45b2 with SHA-1 f8c88c67 is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/26955220 Change-Id: I355544d33fa47c18ba5d9358d358b461e9f8a90d Signed-off-by:
-
chelseahao authored
am skip reason: Merged-In I4e0bd33975fc4d44bb0680a69fca4232328a45b2 with SHA-1 f8c88c67 is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/26955220 Change-Id: I49867604f36a038c212096f24f362e2e3a2cdd60 Signed-off-by:
-
Tiger Huang authored
-
Chelsea Hao authored
-
Reema Bajwa authored
Bug: 335048787 Test: Cts Change-Id: If37ad211bb044c870f0c84bb15df754268402c73
-
Treehugger Robot authored
Merge "Clear the messages and callbacks in the AccessibilityInteractionController when the ViewRootImpl is detached from the window." into main
-
Chris Li authored
-
seokgyun.hong authored
Previously, AppWarning dialogs were not handled per-user per-display and that caused the following issues: - AppWarning dialogs were managed based on the default display and the system user. Therefore, all the warning dialogs were only shown on the default display even if it's for the app running on the secondary display. In addition, it could only receive Intent.ACTION_CLOSE_SYSTEM_DIALOGS delivered to the system user regardless of who the actual user is. - The warning dialog could be shown to the only one user at a time. In 'MUMD'(multi-user on multiple displays), each warning dialog should be shown to each user independently, but it wasn't. - The flags that determine whether to hide the warning dialog were handled per package, but not per user. As a result, flags set by one user for specific package were also applied to other users. To fix these, ensure that the warning dialogs are handled per-user and per-display for MUMD devices. Please note that handling the warning dialogs per-user per-display is only applicable to the devices that enable the visible background users. Bug: 296334639 Test: Manual test (cherry picked from https://partner-android-review.googlesource.com/q/commit:1e099c7254ab802b747595b1180ee39b9a1674ba) Change-Id: I3cdad53172748c452a941b8a798c3a799d9028c0
-
