- When in split screen, the PiP needs to animate to the fullscreen stack
bounds when expanding.
- Created PinnedStackWindowController to house pinned-stack specific
logic.
Bug: 35396882
Test: Expand PiP activity while split
Change-Id: If7397843743ce11b676f5566eba90e3442289fec
Signed-off-by: Winson Chung <winsonc@google.com>
Add API for VideoView to select whether it uses audio focus during
playback, and how.
Add support for AudioAttributes
Test: cts-tradefed run cts -m CtsWidgetTestCases -t android.widget.cts.VideoViewTest
Bug 30955183
Bug 30258418
Change-Id: I581d32c79c78b8197ded2319e0d5bfdc35b93c5e
It was accidentally broken during a previous commit where the CTS test
failure was ignored by a known issue being fixed in another change -
this change fixes both problems.
Bug: 33550221
Bug: 3380254
Test: CtsAutoFillServiceTestCases pass (for real now :-)
Change-Id: I5b2aa6060995ca255e51d85aa6ec93a886fa522f
Also improve descriptions of the attributes, constants and methods.
Test: Ran updated ViewAttributesTest
Bug: 34077687
Change-Id: I532f1b26b97ba113f316eed6fc68dae2ed33ea6a
Use newly defined "V2_DEFY_QUOTA" flag to split cache clearing into
two phases: clearing data for apps above their quotas, and then
pushing deeper by clearing data for apps below their quotas.
Add placeholder comments for other data types that we're planning to
add shortly. Route all clearing behavior through this new method,
which remains guarded behind a flag for now.
Test: builds, boots
Bug: 34692014
Change-Id: I678d7b4e2bf6c837dd8a9adbc36a53015907f75f
Previously, a copy of DisplayAdjustments was provided during Display
construction. If the Display instance is held, the adjustments would
not update. However, the DisplayInfo would, leading to a mismatch.
This changelist adds a reference to the Resources, which can be
queried to provide the latest adjustments.
Fixes: 33430498
Test: manual from bug repro steps.
Test: make -j32 cts; cts-tradefed; run cts --module CtsAppTestCases --test android.app.cts.DisplayTest#testRotation
Change-Id: Ida2ed3990add885d06b011494af24b055343f3fa
Bug 35594367
Protect the FragmentManager during onBackPressed() from
changing the state after the state was saved.
Test: I15891a70699308eddda4e55fa0eb96064ffa7b17
Change-Id: I10f823801e85ca200351a64b14975c4421b9068b
They were all broken in that they returned profile admins for parent
queries even when they clearly shouldn't.
Examples:
- disable unredacted notifications
- disable fingerprint
This doesn't seem to have been tested beyond the bare basics of one
user with one device admin. Added some reasonable coverage. It could
still do with more.
Test: make RunSettingsLibRoboTests
Bug: 34929375
Change-Id: I1b0e986056ffa62d47091c0010977ac810ebd690
Problem:
Home screen isn't allowed to enter VR mode as part of boot.
Root-cause:
VRManager is not indicating VR Mode is allowed until the system sleep
state gets synchronized.
Because the initial sleep state during boot is AWAKE and remains AWAKE if no
lock-screen is set, VrManager fails to mark VrMode as available due to a
mismatch between its initial internal sleep state and the systems sleep state.
VrManager's initial sleep state is SLEEP, where the system's initial sleep
state is AWAKE.
Solution: Set VrManager's initial sleep state to AWAKE to match the system.
Bug: 35469244
Test: - Validated VrHome comes up properly
- Tested VrMode is not allowed when the lock-screen is shown
- Tested VrMode is not allowed when the display is off
- Tested VrMode is allowed when no lock-screen is set AND the display
is on.
Change-Id: I42e9da07db21b3ed034c4173fe329cbb7796ee7e
- Ensure that we don't mark the docked or fullscreen stacks as
invisible when the assistant stack is over them and translucent.
Bug: 35363819
Test: android.server.cts.ActivityManagerAssistantStackTests
Test: #testTranslucentAssistantActivityStackVisibility
Change-Id: I86698beec4963942dd3816e7d3f43c6614d892ac
