So the embedded TaskFragment in fullscreen mode can have the same
configuration as in a normal fullscreen task. Such as the fullscreen
mode parent's smallestScreenWidthDp is calculated based on all
rotations, while the multi-window mode child calculates the value
by current size.
Bug: 256787005
Test: atest TaskFragmentTest#testOnConfigurationChanged
Change-Id: Ib79c6dc443cc0688b06035ddf64fe4dd766616a0
If split A/B then go home, and running A/B again or A/C as new
pair, it would be failed due to we could cover such case on current
implementation.
For fixing such cases, we still need to exit split first.
Fix: 262416120
Test: manual
Test: atest NexusLauncherTests:com.android.quickstep.TaplTestsTaskbar
Change-Id: I37a41ed5a87466652d7b052bc5e3b1c5627b973a
This fixes a problem where the z ordering is not correct during the launch animation of a child notification inside a notification group. The launched notification was rendered below other notifications in some cases.
Test: Manual, i.e. posting various types of notifications and analyzing the animations in screenrecordings.
Bug: 246932690
Change-Id: I658b4b3db75da5199b7b7cb416b7d7fabbc75520
Remove MULTI_WINDOW mode block on loadAnimation to make transition
animation could show. And add some specific rule for split screen
because it should just like a full screen window but contain two
tasks.
Fix: 221117079
Test: manual
Test: pass existing tests
Change-Id: I6ccf0b5344d2bd11a2cd4eacba4df5cb9164e3e2
For some unknown reason, the merged imsi list might contain
duplicated items. Deduplication for better error handling.
Test: NetworkPolicyManagerServiceTest
Bug: 243015487
Fix: 261225039
Change-Id: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
Merged-In: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
(cherry-picked from aosp/2198759)
- CentralSurfacesImpl currently takes a long time to initialize, so in
between registration and updating CommandQueue with the registered
bar's disabled flags, the service may already have updated its
disabled state. This state would have already come into CommandQueue
but would be clobbered by CSI in the post-init task.
Since there are some legacy constraints in ordering of the
initialization, we'll unblock the tests by forcing a disable flag
update following the update to CommandQueue with the previous disabled
flags. We can later investigate applying the returned flags earlier
in the cycle, or add a mechanism to skip apply the registered disable
flags if they were updated mid-init.
Bug: 260615374
Test: atest WMShellFlickerTests:com.android.wm.shell.flicker.splitscreen.CopyContentInSplit
Change-Id: I98943292ecab5cdc693149f417e5c4e8af137d1d
- update blur to blur by radius
- update timing
- add y translation on all complications and status bar
Test: atest ComplicationLayoutParamsTest
Test: manually on device http://shortn/_wY7QNZ5HIB
Bug: 260637747
Change-Id: Ib378327d65e24013845d6b86ce83a72220276467
Length of the vertical volume dialog slider (the one that pops up in response to volume button press) is now proportional to device height
Bug: b/220088292
Test: Manual. Press volume button up/down on a large screen device. Verify the slider is no longer short.
Change-Id: I70dcc2eb6748536f772aaeebd5a3a64be0050f56
Added a unit test to ensure that EventReceivers are correctly created
and destroyed on creation/destruction of WindowDecorations.
Bug: 258271539
Test: atest CaptionWindowDecorViewModelTests
Change-Id: I85ce32508174a17730f4a931d4c81616aedf92e0
Apparently, this can cause an NPE when there are multiple displays.
Someone sent us
review.git.corp.google.com/c/platform/frameworks/base/+/2296938 and the problem will reoccur if we don't fix it in that code's new location.
Bug: 256539657
Test: presubmits
Change-Id: I2c08bb5606bc8af7f3da0f3034c58b5d57b1be0f
Only send the CHECK_PACKAGE_IDLE_STATE message for
ACTION_PACKAGE_CHANGED and not for ACTION_PACKAGE_ADDED.
Bug: 214580000
Test: atest UsageStatsDatabaseTest
Test: manually verify buckets are restored
Change-Id: Iac1433b9b7e3904eb7f753cd0617ac64ab6f7944
(cherry picked from commit 69f86a6475)
Depending on the timing of the switching actions, the
KeyguardUpdateMonitor and the user tracker may have different current
users. We should use a consistent method for getting the current user in
the KeyguardViewMediator
Bug: 250675259
Test: manual
Change-Id: I2b078ac21f0546d1b8de24f55e4225a754d53aea
Adds two new states that indicates if the transfer for receiver is
succeeded or failed. (ag/16730985) is a good reference.
Bug: 257301489
Test: atest MediaTttChipControllerReceiverTest
Change-Id: Ifb1d04c445235fde432b7fd3495114e61c41fd74
Refactors to pull the action classification into a separate class for
testing. Logic flow is unchanged.
Test: make statsd_testdrive && $ANDROID_HOST_OUT/bin/statsd_testdrive 90
Test: atest ClipboardOverlayControllerTest
Bug: 261201283
Change-Id: Ie931b2c11ef1a01c16147907d730d1dd6e5febe8
The various functions in ImageWriter were not protected by a lock, which
led to segfaults under certain race conditions.
This CL adds a mutex to prevent ImageWriter methods from executing while
ImageWriter is closing. This also prevent multiple calls to close from
executing simultaneously.
It also adds a simialar mutex to WriterImageSurface to prevent
simultaneous calls to close().
Bug: 244262872
Test: mediaframeworktest:com.android.mediaframeworktest.stress
Change-Id: I44976e5a36154ce98f64e2982865b2defcec7f5e
If pressing power button 5 times is faster than 200ms, we will
not trigger the ESOS experience. This is unlikely to be done by human. The fastest recorded button press is 60ms so the whole esos gesture sequence should be 300ms or so. We are taking 200ms threshold to be conservative.
Fix: 261618088
Test: rebuild, PTS
Change-Id: Id3f1d92623d17b2921cc0fb90c1f19f896946881
This change allows notifications with full screen intents to show that FSI on a ranking update if they meet specific criteria (previously suppressed only by DND; not older than a few seconds; now no longer suppressed).
FSI on update only happens when the flag FSI_ON_DND_UPDATE is set to true.
Bug: 248325248
Test: HeadsUpCoordinatorTest, manual verifying the FSI actually shows up on update
Change-Id: I810ae951bc96908cc66a8831f88730021bdb64b6
Bug: 250588519
Test: ran the suite and it still passed. No functional changes, only
reorganizing the code to make the Runner visible.
Change-Id: If36a132bbeb1eb75571b20582ba85e1067a5925b
We want a not resizable transparent activity to inherits
the constraints from the activity below. This allows the
transparent activity to be letterboxed.
The specific logic for transparent activities is enabled
when the config_letterboxIsEnabledForTranslucentActivities
flag is true.
Fixes: 220703089
Test: Run `atest SizeCompatTests` with the following tests:
testApplyStrategyToTranslucentActivities
testTranslucentActivitiesDontGoInSizeCompactMode
testNotApplyStrategyToTranslucentActivitiesWithDifferentUid
testApplyStrategyToMultipleTranslucentActivities
Change-Id: I6b5e8517ae8286f7543c3f57c158276aab6cfbfc
