1. Collect the TaskFragment when reparenting an activity into it.
2. Check adjacent TaskFragment for transition flag FLAG_TRANSLUCENT.
3. Offset the relative position for default animation.
Bug: 207070762
Test: pass existing
Change-Id: I62b533dbb087007e3ef126170691a59929eb75e1
If the app window is drawn before the starting window, the
visibility flags of starting window will be cleared in
ActivityRecord#commitVisibility. Then it is unnecessary to
play the reveal animation for an invisible starting window.
Bug: 240239537
Test: com.android.server.wm.flicker.launch.OpenAppWarmTest
Change-Id: Ib1d585e9384989cc8aab95e3b3d891555106713c
This CL allows
com.android.settings
to have a "signature|privileged" permission
android.permission.CONTROL_UI_TRACING
permission. This permission will be used for QS DevelopmentTiles to
continue being allowed to access WM/IME tracing IPCs.
Bug: 172444310
Test: cf_x86_64_phone-userdebug still boots up
Test: cf_x86_64_auto-userdebug still boots up
Change-Id: I9aa69247f02447f2454e42e3625f0ed764991edf
The Stratus+ is somehow bugged when it uses the generic gamepad file; to
fix this, a Stratus+-specific key layout file is added, similar to the
one for the Stratus Duo.
Bug: b/232827632
Test: Stratus+ USB connection, playing SF4 on eve (ARC-R)
Change-Id: Ied0e27a57b159fd35915634bd62ffced58ced4f2
This CL allows
com.android.settings
to have a "signature|privileged" permission
android.permission.CONTROL_UI_TRACING
permission. This permission will be used for QS DevelopmentTiles to
continue being allowed to access WM/IME tracing IPCs.
Bug: 172444310
Test: the device still boots up
Change-Id: I34bc22392cb4fa233126b46fb979638c90a3c3c6
..to reflect the app transition animating state when shell-transition
enabled for below cases:
1) ImeInsetsSourceProvider#isReadyToShowIme will use WS#isClosing ->
AR#isClosingOrEnteringPip to check if the IME layering target window
is in closing transition. (i.e. It won't be ready to show IME while
the target is in closing app transition.) Also, given isClosing and
isClosingOrEnteringPip currently is only used for checking IME target
validity, wraping those logic into isImeTargetWindowClosing() for
simplicity.
2) With Shell-Transition, the activity will running a transition when
it is visible, it won't be included when fromTransition is true means
the call from finishTransition. As a result, in AR#commitVisibility,
callback onAppVisibilityChanged(visible, runningAppAnimation) with
using the above checking logic and adding logs for tracking. In case
a11y controller will always callback onWindowTransition with
TRANSIT_EXIT due to runningAppAnimation always being false by
isAnimating no-op.
Fix: 212570341
Test: No visible change & Pass existing tests.
Change-Id: I9cc77956b3ff61ae83f5bd120c395cc6aca93af9
When making subsequent draw requests for the same window, drop
any existing buffers since they will be replaced by the new one.
Sometimes the "old" buffer will still be "in-flight" (either
drawing still or in binder). So, also drop incoming buffers
for seqIds that are earlier than the latest prepareSync.
Additionally, immediately apply any applyWithNextDraw that were
requested before the sync, but arrive after the sync started --
otherwise they can get put on pending (which waits for sync
apply) and thus also block the buffer queue.
Bug: 233625646
Test: run tests and check for ANRs
Change-Id: I156a9a73eea8346dc241b5d782a863b99127ca9f
The Task was moved to front while making an Activity to be the
focused app. In that case, the resumed activity will be reset
to the top-most resumed activity in the Task.
However, the top-most resumed activity in the Task should not
always be the current focused activity when activity embedded.
This CL skips unnecessary task movement and making the target
activity to be focused if the task is already on top and focused.
Bug: 236565088
Test: atest TaskFragmentTest
Change-Id: I6cbea10bdfa422e9d51c051595ed592843f5ba79
Some olders kernels don't yet support HID_PLAYSTATION. While they are
working on supporting this driver, provide this temporary solution.
Before this patch, if the key layout is loaded, but there is no
HID_PLAYSTATION, then the mappings on the device will be incorrect.
With this patch, this key layout will not be loaded unless there is a
CONFIG_HID_PLAYSTATION enabled on the device.
Instead, when the main layout cannot be loaded, we make another attempt
to load a fallback layout. This way, the mappings on DualSense can be
correct even if the HID_PLAYSTATION module is not loaded.
In this CL, the fallback layout was tested using controllerTester.
Bug: 228005926
Test: tested mappings with a DualSense controller on a device that does
not have CONFIG_HID_PLAYSTATION
Change-Id: I7e46ae1943cd2c63b8c0b03fdf5d71adeea89f6f
Merged-In: I7e46ae1943cd2c63b8c0b03fdf5d71adeea89f6f
Some Reference RCUs came with PID = 0x0006.
This change assigns the default keylayout file
Vendor_0957_Product_0001.kl
to the RCUs with VID/PID 0957/0006.
bug: 234774631
Change-Id: I1387313f2ab00ab06575f4a9e258c8660212f39f
Some olders kernels don't yet support HID_PLAYSTATION. While they are
working on supporting this driver, provide this temporary solution.
Before this patch, if the key layout is loaded, but there is no
HID_PLAYSTATION, then the mappings on the device will be incorrect.
With this patch, this key layout will not be loaded unless there is a
CONFIG_HID_PLAYSTATION enabled on the device.
Instead, when the main layout cannot be loaded, we make another attempt
to load a fallback layout. This way, the mappings on DualSense can be
correct even if the HID_PLAYSTATION module is not loaded.
In this CL, the fallback layout was tested using controllerTester.
Bug: 228005926
Test: tested mappings with a DualSense controller on a device that does
not have CONFIG_HID_PLAYSTATION
Change-Id: I7e46ae1943cd2c63b8c0b03fdf5d71adeea89f6f
group name was changed during review but not updated
in the permission mapping.
Bug: 232283779
Test: manual
Change-Id: Ib7df61fa4fd49c8419f0543fd6c54186a33ebeb6
(cherry picked from commit 4486314be6)
Merged-In: Ib7df61fa4fd49c8419f0543fd6c54186a33ebeb6
