mode.
Test: manual: Do a swipe up on the status bar while not in immersive,
then open a landscape immersive app and verify the status bar still
shows (i.e. it wasn't dismissed by the previous swipe)
Test: new unit tests
Bug: 195839150
Change-Id: I1913c25c29b635979b0cb89d815b2d2c6cc40530
Binder tracing can be very expensive. In dogfood builds its triggered
time to time and it should only be called manually when needed.
Fix: 202721321
Test: atest CtsInputMethodtestCases
tested with winscope trace.
Change-Id: I0a4ee1b90e56ed1b20e44b5a0b42c17d565d05dd
ScrimController.
No need for PanelBar to calculate scrim values and notify
ScrimController of them, when ScrimController can just calculate them
directly.
Test: Manually verifying scrim fraction is still updated correctly via
logs
Bug: 200063118
Change-Id: I37df95015002825adf7217c4144950e85485af84
Merged-In: I37df95015002825adf7217c4144950e85485af84
swiped it away.
Test: Manual (see video in b/195839150#comment6)
Test: TODO unit tests if general structure is approved
Bug: 195839150
Change-Id: Iee58416973becf9d66db6f50c7512cf65722766b
- always update lock icon visibility if the state changes
(ie: fp running state or userUnlockedWithBiomtric)
- show the lock icon if mUserUnlockedWithBiometric is true so
that mShowLockIcon or mShowUnlockedIcon are converse (aside from
fingeprint listening state)
Test: manual, atest LockIconViewControllerTest
Fixes: 201264245
Change-Id: I5d4e2f7566bf724923f2f24808e96aa0d789ff07
This is necessary to fix "Unable to save trace file /sdcard/flicker/startRotationServiceTest_layers_trace.winscope" in the library self tests
Bug: 202288112
Bug: 202366188
Bug: 188993244
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I9d6d6025be8b659d2f062771cfbd2f6c0982c2be
Before, when trigger change transition and screen freeze before the
previous transition is finished, it will cancel the animation and call
to unfreeze. However, it will then unfreeze the new snapshot instead of
the old one, which cause a client crash because of missing leash.
The fix contains two changes:
1. Let SurfaceAnimator to take the snapshot from the freezer as it does
for animation leash.
2. When an animation leash needs to be removed, check if it is the
current animation leash (parent of the window surface) before
reparenting the window surface back to the parent window surface.
Bug: 201622511
Bug: 196173550
Test: atest WmTests:WindowContainerTests
#testStartChangeTransitionWhenPreviousIsNotFinished
Test: click demo app launch spit before the previous one is finished
Change-Id: I58fb05a971b49981d168d00c9fb42014b4d3cd4d
- When swiping up to enter PIP w/ auto-enter, SysUI applies a transform
on the leash which is seamlessly applied to the task (to prevent jumps
when the leash is removed). This was intended to be applied in both
single and multiple activity PIP cases, but if that doesn't happen,
then when the transform is later cleared, it will inadvertently reset
the task's crop and matrix.
Bug: 201127015
Test: atest PinnedStackTests
Test: Open YT, enter PIP, turn screen off, turn screen back on
Change-Id: I0d6d46c7c52f7a43058902b50a26131f626ae92d
The advanced extension session request processor must not hold the
'mInterfaceLock' when calling the camera device implementation as it
could result in a deadlock with the camera device close that can
run at the same time and try to acquire the same locks in reverse order.
The request processor will only read from 'mCameraConfigMap' which is
initialized only once during session setup and will not change during
the session lifetime.
A sample stack trace will look like this:
Service thread:
1) android.hardware.camera2.impl.CameraCaptureSessionImpl.stopRepeating
2) android.hardware.camera2.impl.CameraAdvancedExtensionSessionImpl$RequestProcessor.stopRepeating
Client thread:
1) android.hardware.camera2.impl.CameraAdvancedExtensionSessionImpl.release
2) android.hardware.camera2.impl.CameraDeviceImpl.close
Bug: 202074988
Test: Manual using application,
Camera CTS
Change-Id: If992667a7d7e54be5bea1fcc4b1d71ec1b895ca0
