Make sure not to overwrite any current user selection for
Secure.STATUS_BAR_SHOW_VIBRATE_ICON that the user may have
made.
Issue: 253992986
Test: Manual - see issue
Change-Id: I33155a27707e6d30ff56fb090c71b9670a98fc31
If a device is configured to dream on short power press, also make sure
it locks as well.
Also fixes an issue where the screen does not turn off when another
user (not user zero) presses the power button.
Bug: 260135090
Test: manually by configuring device to dream on short power press and
then making sure it is also locked after press.
Change-Id: I16ca4eab7a0e8a3f2ef42c090147bd7e62445c69
DreamManagerService#canStartDreaming should not return true if the
current user is not allowed to dream.
Bug: 261907079
Test: manually by switching to a user that can't dream and making
sure that the screen turns off on power press while docked.
Change-Id: Ia4a46dff5360d3565762b82fb4353e66f0b8f661
If there is at least one panel (resolved), we should show the
affordance, even when we have no favorites.
Also, fix a bug in ControlsUiController.resolveActivity: anyPanels
should use `List.any`.
Test: atest DreamHomeControlsComplicationTest
Test: atest HomeControlsKeyguardQuickAffordanceConfigParameterizedTest
Test: atest ControlsUiControllerImplTest
Test: manual on lockscreen and dream
Test: launch device controls from tile for first time
Fixes: 261751925
Change-Id: I832473d243746015a1f20a7fa9b6d0e05d6c668c
These tests appear inconsistent now. It's not flaky, but it does
appear to change depending on the test environment.
Bug: 261472011
Test: atest NotificationPanelViewControllerTest
Change-Id: I6fc772d1ee85971072147e073b15f1feb8137107
The problem happened when going form the expanded clock layout (when QS are fully expanded), to the large screen transition layout.
This fix sets the header transition to start when on large screens.
Without doing this, the transition was staying at the latest progress in the previous constraintSet.
Bug: 261791489
Test: presubmits + tested locally
Change-Id: Ice698e169b1328c3a83189c268dbac820b564cf7
There can be 2 reasons that we need to apply compatible scale to a
window:
1. The app doesn't support large screen. We would layout the window as
if it is on a small display. And then we need to scale its window up
to match the display.
2. We put a running app into a container that the size doesn't fit. We
need to down-scale the app so that it can fit the container.
The scaling of case 2 is also known as size-compat-scale which is fully
controlled at the server side. The client shouldn't know about it. And
this CL refines the naming.
Fix: 258393096
Bug: 254187021
Test: presubmit
Change-Id: Ifbd2ca725bed231d9e6dd8190df3dc773d4402b7
(cherry picked from commit bcbd60c45c)
Merged-In: Ifbd2ca725bed231d9e6dd8190df3dc773d4402b7
d41841f469, always checks whether the home task is violated
with lock-task mode while moving the task to the front. That result in
the pinned toast was shown even applications don’t not request to have
task_on_home behavior.
This CL checks the home task violation with lock-task mode after the
task-on-home flag is applyed.
Bug: 261383209
Test: atest TaskTests#testReturnsToHomeRootTask
atest ActivityVisibilityTests#testLaunchTaskOnHome
Change-Id: Iccc7e595b043a712c5959d28ba14f54825bcadd6
This CL adds a method to trim lrucache size dynamically based on the
level of onLowMemory to avoid calling evictAll to frequently, and to make cache resize more reasonable.
Bug: 259630755
Test: atest AppIconCacheManagerTest -c
Change-Id: I1b9692a0fad8c13722da4906cf844232707e74b2
Before, we remove the changing window from transition onDisplayChanged
even if it is a display info change on the same display. Now, we only do
that when the window is moved from the old display.
Fix: 251001013
Test: atest WmTests:WindowContainerTests
Change-Id: Id3ab6db47dad8e2541a14b5529694c290e4d2b66
Some features relying on API version 2 are not fully ready yet.
Bug: 261780650
Test: N/A
Merged-In: I0a4f2bfcddd7f20f53e702f2bc2144d2fd939a21
Change-Id: I0a4f2bfcddd7f20f53e702f2bc2144d2fd939a21
This adds a new method which allows applications to use mdoc ECDSA
authentication instead of mdoc MAC authentication. Additionally, also
relax requirements on SessionTranscript so the APIs can be used even
when mdoc session encryption isn't being used.
Bug: 241912421
Test: atest VtsHalIdentityTargetTest
Test: atest android.security.identity.cts
Change-Id: I25336f1352102208887531d066ec432a9ae3cd36
This is a semi-automatic change.
See https://errorprone.info/bugpattern/JdkObsolete for the rationale.
Test: make
Bug: 221046110
Change-Id: I84591e3963b54e69570e77354e54027e17f17293
Merged-In: I84591e3963b54e69570e77354e54027e17f17293
The caller activity and its task should be able to reuse. There's
no need to migrate the launching activity to another Task.
Bug: 233591548
Bug: 260978212
Test: wm presubmit
Change-Id: I2bd5f01ef9196010f1af1aa7cb9e6a45984e960d
(cherry picked from commit a7269cd7e1)
See other changes in the topic for context
Bug: 260123067
Test: verified on local device that timeout is 60s by default
Change-Id: I72b5fb35aef14e90f98fa9b281134a5af0f16813
Revert submission 20517233-Cloned User Storage Issue-tm-qpr-dev
Reason for revert: “DroidMonitor: Potential culprit for Bug 261921307 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.”
Reverted Changes:
I6835cc4d2:Fixing Storage Volume(s) Retrieval.
I617bae9b2:Fixing Storage Volume listing for Cloned User.
Change-Id: I08722e8467fafa53ab914ec5de0380d2df62b55d
Revert submission 20517233-Cloned User Storage Issue-tm-qpr-dev
Reason for revert: “DroidMonitor: Potential culprit for Bug 261921307 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.”
Reverted Changes:
I6835cc4d2:Fixing Storage Volume(s) Retrieval.
I617bae9b2:Fixing Storage Volume listing for Cloned User.
Change-Id: Ia8b8b4f35bf9bdfe7eefa36372ae3525dc405e53
Add methods to move a task to fullscreen of freeform in proto2
controller.
Use these methods in window captions to move a task to desktop and back
to fullscreen.
Bug: 261234251
Test: atest DesktopTasksControllerTest
Change-Id: I9907038ad3882240b1f70b6f0c29c677cb4f4a51
Copy logic over from proto1 to bring desktop apps to front.
There is one key difference from proto1 logic. In proto2, before desktop
tasks are shown, we ensure that the home task is brought to front. And then
place desktop tasks on top. This is due to proto2 having fullscreen and
freeform tasks running at the same time.
Bug: 260645044
Test: atest DesktopTasksControllerTest
Change-Id: Ic5de4d431b96893ef5d685a4dce28e08f17f6f97
Create the controller class, set up dagger.
Ensure controller is not initialized when flag is off.
Bug: 260645044
Test: atest DesktopTasksControllerTest
Change-Id: I0435e07a22e379f403ae5d1b23f39a67a12e8a6d
