Without this, EdgeBackGestureHandler doesn't know that gesture nav is
enabled until you toggle the setting explicitly.
Bug: 198639199
Test: Manual
Change-Id: Ie732469726318a335401a13f68083256f5b9a231
When this helper method is called on a binder thread it checks the caller's permission instead of just using the system service privileges to make the call, resulting in erroneous SecurityExceptions.
Bug: 182832208
Bug: 198860541
Test: CTS/unit tests
Change-Id: I2c71109f2556a47b8e44150565800528496173f5
Use ConcurrentHashMap instead of a SparseLongArray guarded by a
reentrant readwrite lock to make CompatConfig.isChangeEnabled as fast as
possible.
Test: atest CompatConfigTest
Bug: 197712476
Bug: 191398285
Change-Id: I498c439baf3e060ec7feb68ed581ca680e2ebcad
Merged-In: 498c439baf3e060ec7feb68ed581ca680e2ebcad
(cherry picked from commit 42090b95e1)
The issue was caused by MultiUserSwitchController always having reference and acting upon multiuser button in expanded QS - that's a different button than collapsed QS.
That reference was provided by dagger and while this issue could be fixed in dagger, that would require providing separate multiuser button and separate MultiUserSwitchController. That would require adding qualifier like @Named in multiple places (both providers and receivers) so seems like too much boilerplate (or opportunity for separate module?) and I went with adding factory for MultiUserSwitchController.
Another issue is MultiUserSwitchController opening multiuser detail always in expanded QS - collapsed QS currently doesn't support opening detail view. Looks like that requires non-trivial code changes, so for now I did it in a hacky way - forcing panel to expand and only then showing multiuser detail (as seen in QSPanelController). I think this hacky way is better than having non-functioning button.
Fixes: 196805122
Test: enable multiuser support -> expand split shade (but not expand QS)
-> click on multiuser button -> multiuser panel should open within QS
Change-Id: I76c9bb77c870b8a1a4e25221c63821786057d7f2
Merged-In: I76c9bb77c870b8a1a4e25221c63821786057d7f2
It was mistake on previos change, we should exit split when both
stages are invisible.
Bug: 199369390
Test: manual
Test: pass existing tests
Change-Id: I9f237155fd75b4ee16db647f4849f929cbba1056
BYPASS_INCLUSIVE_LANGUAGE_REASON=legacy naming, not edit by this code change
Bug: 199892006
Test: make SettingsLibRoboTests
Change-Id: Ie609233ab820bf9079d7e4dc37eb61a4195a4a97
When unlocking from AOD, we now wait visually before
starting the reveal animation
Test: atest SystemUITests
Bug: 197113783
Change-Id: I5180ec48e6e100832741273277ac9d2ff4c289b0
When task move to back, the task visibility will be invisible
temporarily because visile app task reparent to TDA and below task
still not move to front.
Because this visibility change, we will hide divider and stage root
task then it cause flicker.
Fix this by only update divider and stage visibility when both stage
visible or invisible.
Bug: 199369390
Test: manual
Test: pass existing tests
Change-Id: Ide0b277e26e03ea3d7fb20132ff0e21807eee332
onDisplayAreaInfoChanged might callback many times in one action
such like fold to unfold, it might cause some issues because we
don't use lastet config resources to set SplitLayout.
Another bug is we cannot get divider leash immediately after we
init it because leash is built after attachToParentSurface.
Fix both bug by always do whole SplitLayout setting if any cared
configs changed. And add a callback after divider leash build,
show the leash on this callback to ensure we got null leash.
Fix: 198581512
Fix: 197296095
Test: manual
Test: pass existing tests
Change-Id: I06a4093927d6469a85b2104b36c16d6e16519a51
Targeted effect:
* Immediate visual response on touch down at
sufficiently visible radius for variable finger sizes.
* Then decelerate radius expansion to convey tension / elicit
force and constrain at limited max radius past first stage.
* Bump values on non-AOD surface to improve visibility with
more variable backgrounds.
Test: `adb shell cmd statusbar auth-ripple dwell` expands ripple (but
doesn't animate the retract)
Test: manual, atest SystemUITests
Bug: 198864174
Change-Id: I1fb2e456e89a824b1b749150e3d82c6bc3223f47
