Age | Commit message (Collapse) | Author |
|
Bug: 384727394
Test: UdfpsControllerTest
Test: UdfpsControllerOverlayTest
Flag: EXEMPT bugfix
Change-Id: Ifce421be7997eca4323a2e0412abca5753b6b787
(cherry picked from commit 47fd897138eb2c9ee3a25ca35970d34178226f6a)
|
|
Also do not draw non-system windows on top of ControlsSettingsDialog
Bug: 404256832
Flag: EXEMPT bugfix
Test: atest ControlsSettingsDialogManagerImplTest
Change-Id: I63e98794e1a93e3c208ee421654d73542d2bd34a
(cherry picked from commit 0042369de2a626f462b3d0dff8db2294aa24ffec)
|
|
On foldables, if the "Continue using apps on fold" is set
to "Swipe up to continue", when closing the device,
a dismissible keyguard will show.
If this setting is set, and there's a pinned app, instead
of showing the dismissible keyguard on fold, we keep the
screen on with the app displayed.
This keeps the app pinned and in the same security state as
when it was unfolded.
Bug: 404252173
Flag: EXEMPT bugfix
Test: manually (given settings described above), pin app, fold;
observe app still shows with screen on
Change-Id: I61e2014b9d21862859090707e5531a61bf966fc3
(cherry picked from commit 14f874decfdd5616b9fb3804154dd2560ebad0a1)
|
|
This reverts commit f022b03cf4d6b3272ce683f51ae40c742c7c5283.
Reason for revert: reverting to original accessibility state with announcements
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:43a88d99f359d6a1760272e91d528f7a48a2dd3b)
Merged-In: Ie835fa8a190603b5f3183ce030514b09ac25de3c
Change-Id: Ie835fa8a190603b5f3183ce030514b09ac25de3c
|
|
This reverts commit d0ac6337d687cc0c329e13312cc5fcc2f6272226.
Reason for revert: reverting to original accessibility state with announcements
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:928ef2944e153bd5a341a1001ed73c0f2a07665c)
Merged-In: I987eb33ca9192aff751510fc245bf6cb055b3428
Change-Id: I987eb33ca9192aff751510fc245bf6cb055b3428
|
|
This reverts commit 868f3d76bf1e94bc904432ecd49aa384d96336d5.
Reason for revert: reverting to original accessibility state with announcements
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:28c239fd5be8202fc9aa286abef43629a6d3917f)
Merged-In: I5b7cf536cf0277a88e89f71f95bdd6d454c69a57
Change-Id: I5b7cf536cf0277a88e89f71f95bdd6d454c69a57
|
|
read by talkback"
This reverts commit cf9a0559d34d6021df3ce8f5fc4bc1a9e2875707.
Reason for revert: reverting to original accessibility state
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:f7170344e26c09afa2684d7c123ab750fca702c1)
Merged-In: I02980a86a2d7d7bd79f2c22e97366ffcbcea6ba6
Change-Id: I02980a86a2d7d7bd79f2c22e97366ffcbcea6ba6
|
|
Fixes: 406608685
Test: presubmit
Flag: EXEMPT bugfix
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:ac3324800128693729ccec953fa997598802f5a0)
Merged-In: Ida5384997100707fdd7afb1b407b3e3883676691
Change-Id: Ida5384997100707fdd7afb1b407b3e3883676691
|
|
Adding flag to guard this Fix ag/32498740
Also modified test so that it fails with flag off and passes with flag
on - This makes more sense.
Test: CustomShortcutCategoriesRepositoryTest
Flag: com.android.systemui.app_shortcut_removal_fix
Fix: 405058325
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:c92830fb84aa243989f431a4dd5a03cfeb26309a)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:ed6b6d67dd70db84c7654979b91ae214615748bf)
Merged-In: I90c3361b75cacecac8045d3061fb0e588c5b3661
Change-Id: I90c3361b75cacecac8045d3061fb0e588c5b3661
|
|
Shortcut commands can uniquely identify key Input Gestures to be
deleted, while Key_gesture_type may not be unique, E.g For Application
shortcuts they all share the same key_gesture_type
Flag: com.android.systemui.extended_apps_shortcut_category
Test: customShortcutCategoriesRepositoryTest
Fix: 405058325
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:45f3acfb441bd86af105321bde3357c9e8aa6bfc)
Merged-In: I891ab972456e0799700bc1bbaff29a4b9c6faed5
Change-Id: I891ab972456e0799700bc1bbaff29a4b9c6faed5
|
|
This works around around a Jetpack Compose bug where if we add a child
to the element inside an AndroidView composable before the element has
been laid out, it will fail to render. We therefore delay processing the
RemoteViews for the widget until after the parent has been laid out.
Test: manually on device by verifying widgets properly show up
Flag: EXEMPT bugfix
Bug: 387938328
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:9c4b228662a1881efdd42e8f2fac3f50899c311f)
Merged-In: I3b094086dd133981c37fa9709547334091fcb580
Change-Id: I3b094086dd133981c37fa9709547334091fcb580
|
|
PerDisplayRepository<CoroutineScope>" into main
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bug: 364653005
Flag: com.android.systemui.status_bar_chips_modernization
Test: Dump `StatusBarChips` log buffer -> verify output (verify with
status_bar_chips_return_animation both off and on)
Test: atest CallChipViewModelTest
Change-Id: I4ad9c4fff999aad474e74e04da553631a01630e3
Change-Id: If761774251d0b4970800b31f2cf20ee24e76e259
|
|
|
|
|
|
|
|
To avoid accidental dismissals, we also consider the magnitude and
direction of velocity to determine if a notification is dismissible
after it has been magnetically detached from its neighbors. When
detached, a notification snaps back when there is a fast enough fling in
the opposite direction relative to the detachment direction. In any
other case, the notification dismisses when let go.
Test: modified and added new Unit tests
Flag: com.android.systemui.magnetic_notification_swipes
Bug: 405126597
Change-Id: Ic4c9074d2dc2e995c1b28b11529aa97395d1144e
|
|
open" into main
|
|
|
|
This allows classes outside the components to use the scope created inside the component.
As there are several places outside the display component using this scope, this is an intermediate step in the refactor.
Future classes requiring the coroutine scope are expected to be created inside the display subcomponent
Bug: 403481022
Test: DisplayScopeRepositoryInstanceProviderTest, DisplayComponentPerDisplayRepositoryTest
Flag: NONE - refactor without behaviour changes
Change-Id: I95cf815cbfdc3c334ff404434d7ff847a3342330
|
|
Flag: EXEMPT unreleased legacy flag
Fixes: 270437894
Test: atest LegacyMediaDataManagerImplTest
Test: atest MediaDataProcessorTest
Test: atest MediaResumeListenerTest
Change-Id: I8203850ca3f330a238681ac38711d4a59a28b6ca
|
|
|
|
This is to make the call chip padding & screen record chip padding look
similar (b/397494654). Mostly, this re-writes a few things:
- Renames the old padding dimen to _legacy
- Updates the ChipIcon data class to say whether it has embedded
padding
- Adds some comments about how paddings work (when I originally wrote
this CL, I tried to simplify things but ended up making it worse
because I forgot why the paddings were in certain places)
- Always apply the minimum width, but make sure the min width uses
2*padding
Luckily the screenshot tests will show that most chips are unchanged.
Fixes: 397494654
Bug: 364653005
Flag: com.android.systemui.status_bar_chips_modernization
Test: Trigger screen record chip -> verify it has slightly less side
padding
Test: Verify other chips still have the same padding as before
Change-Id: Iab3d4f043f008fdef1a158e37391007afe6630ce
|
|
Running dismiss from keyguard does not matter because we need to reset blur to min anyway if we're going to keyguard or gone without shade.
Bug: 370555003
Flag: com.android.systemui.bouncer_ui_revamp
Flag: com.android.systemui.notification_shade_blur
Test: verified blur is still applied using logs, shade alpha becomes 1.0 immediately after that so blur is still not visible.
Change-Id: I7b5174bbe1ddadc1ba536b58de1756cd38c4a9fc
|
|
|
|
|
|
|
|
into main
|
|
Behavior for ALL_APPS and ACCESSIBILITY_ALL_APPS is exactly
the same so reducing the enum conflict.
Test: atest InputTests
Bug: 245989146
Flag: EXEMPT refactor
Change-Id: I729362351e7384f7119f1588f3f3be80e12df5fe
|
|
into main am: ee18dbb30b
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3530124
Change-Id: I490000e2182043e82a3bb3a822f0aad6db65ece4
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
The last condition (currentState == GONE && startedState == GONE) results in this flow emitting true when we're GONE. It needs to emit false as soon as we transition from GONE -> *.
This was happening most of the time when canIgnoreAuthAndReturnToGone emitted, but we can't rely on that to happen quickly enough since that flow maps wakefulness, not keyguard transition state.
Bug: 278086361
Test: quickly cancel sleep transition
Flag: com.android.systemui.keyguard_wm_state_refactor
Change-Id: I568c74029766681f2fcd8a8d90eca0d15a9d1cfa
|
|
* changes:
Fix WindowManager instance used in WindowMagnificationSettings window.
Revert "Removing use of WindowManagerProvider to create window manager for"
|
|
This should fix multiple performance regressions.
Bug: 278086361
Test: atest WindowManagerLockscreenVisibilityManagerTest
Flag: com.android.systemui.keyguard_wm_state_refactor
Change-Id: I0b39f818c6b317a18196d26c2f764d7c611a37f7
|
|
Move isClassified check to BundleUtil
Move makeClassifiedConversation to kosmos for test
Bug: 402358371
Test: ColorizedFgsCoordinatorTest
Test: ConversationCoordinatorTest
Test: HeadsUpCoordinatorTest
Test: LockScreenMinimalismCoordinatorTest
Test: RankingCoordinatorTest
Flag: android.service.notification.notification_classification
Change-Id: I87161130e063f5f2c01c7c0cfba8563528ad17b0
|
|
Bug: 386411078
Fix: 386411078
Flag: com.android.media.flags.enable_output_switcher_redesign
Test: atest SystemUITests:com.android.systemui.media.dialog,
SystemUIGoogleScreenshotTests: com.android.systemui.media.dialog
Change-Id: I3d71561fedff578ad573867c6c8b0306bdf6850d
|
|
* changes:
Listen to DisplayStateInteractor for LowLightMonitor display changes.
Convert LowLightMonitor to kotlin.
|
|
|
|
|
|
change." into main
|
|
|
|
|
|
|
|
And more media host state logging
Bug: 342175696
Test: build
Flag: EXEMPT bugfix
Change-Id: I584e3040c3debbc220791059b42356a7db291402
|