updateClockViews may change the view hiearchy and
calling it within onLayout was causing view measurement issues.
remove chatty debugging logs
Test: manually force updateClockViews to occur in onLayout,
see the clock is cutoff when notifications are hidden (can use adb:
adb shell locksettings require-strong-auth
STRONG_AUTH_REQUIRED_AFTER_USER_LOCKDOWN) w/o change, with this
change, the clock is never cutoff
Bug: 222260948
Fixes: 233081863
Change-Id: I4ea5dae1dc8018478cc98e5e2520ef2afd2fdc58
Merged-In: I4ea5dae1dc8018478cc98e5e2520ef2afd2fdc58
This fixed a request leak problem which was introduced in previous
Android release but caught recently, where the budget of
MultipathPolicyTracker was cleaned before unregistering requests,
the logic in the tracker would skip the unregister if there is
no budget.
Ignore-AOSP-First: Urgent fix
Test: MultipathPolicyTrackerTest#testOnThresholdReached
Bug: 233733267
Fix: 145963406
Change-Id: Icee43a4ee913a6459a47632f608fa6cb8b2ed4c2
When the screen times out, the device may not immediately lock based
upon a user setting. In this case, keyguard is visible but not fully
locked. If the user uses finger auth, MODE_ONLY_WAKE is used but the
keyguard is not properly dismissed. Use MODE_WAKE_AND_UNLOCK to run
all animations.
Fixes: 231553219
Test: atest BiometricsUnlockControllerTest
Change-Id: I8ff2c2f983b64c7f62d7025fce227a2dd9eabf04
Revert "Update smartspace shadow"
Revert "Update app icon shadows"
Revert submission 17935777-lightDarkDetection
Reason for revert: Talked with Adam Cohen, white shadows are controverstial and we'd need to escalate to senior UX if we want to ship. James would rather do it in U timeframe, will flag to UXers we work with that the opportunity to escalate is available if needed.
Reverted Changes:
Ia91221427:Update light/dark detection.
Ie12d3d054:Update app icon shadows
Icc88c3496:Update smartspace shadow
Change-Id: I7d6b972d29b328a7d5ca7ac7241156b6e51a2cd6
This fixes an issue where activities are started below the dream.
Bug: 198041170
Test: atest CentralSurfacesImplTest
Test: manually on device
Change-Id: Iec7324f397161c3e0bbf626153f8cb453e6a86ca
Or the smallest screen width dp could be the same as the
display size.
Bug: 230035382
Test: verify sw config of an embedded activity
Change-Id: Ic085c6ed134c2787a26fd2b02b4345b04fb693e6
Merged-In: Ic085c6ed134c2787a26fd2b02b4345b04fb693e6
(cherry picked from commit 9cee26e261)
While starting an activity with FLAG_ACTIVITY_CLEAR_TOP, the
existing activity could also be finished and therefore the new
activity is added on the same TF of the top running activity.
However, the top running activity could be on a TF which is
different from the cleared activity.
Bug: 233860721
Test: start Settings' shortcut activity
Test: atest TaskTests
Change-Id: I5607a2737e7d0d5986adf14f44f169791da3d38a
By the original design, we register the activity event in the
ActivityManagerService. After getting the activity event, we will
query current visible activities and report them to Assistant.
Assistant will start to get direct actions of those visible
activities. But sometimes they can not get the direct actions
due to the stage of activity lifecycle before onStart().
We will postpone the request direct actions a few times
before onStart().
Bug: 224789902
Test: atest CtsVoiceInteractionTestCases
Change-Id: If7cd52c5ba749523e575c0be5595e8f20704c4f2
Currently the cloned windows is avaialbe from window list,
however the node info from the cloned window is incorrect.
To avoid confusion, we would drop them for a short term solution.
Bug: 230300971
Test: manually test with switchaccess
adb shell dumpsys accessibility to observe the window list
Change-Id: I7a03376567698a493c9eb5e26d1f3390aacdb408
Even if the brightness is the same we still need to invoke any listeners
as just the act of setting the brightness has side effects, like
clearing the temporary brightness. Skipping these callbacks mean we can
possibly get stuck in a state where we don't adjust the brightness at
all until the next time a user touches the brightness slider -- this
persists even through screen off.
Fixes: 218600709
Test: Manual
Change-Id: I918636a61424a51f9d22d32fd692beb6eb2b8f2d
As IME window will be hidden by AsyncFadeAnimationController when
receiving IME show request in IMMS side during fixed-rotation.
we could remove the previous logic from CL[1] in case snapshot starting
window surface may not apply fixed-rotation when IME snapshot visible in
the first place, since in CL[2] has already removed the disable
fixed-rotation when animating snapshot starting window with IME visible.
[1]: Idfdf129adbfbee6634d8a27aa78da1f631bd213b
[2]: Iceaedbfdb75e68e9f7fb8fd4a1bf8f35a779797e
Bug: 230733128
Test: 1. Launch a portrait app which keeps showing IME. (e.g. Chrome)
2. Return to home be home key or swiping.
3. Hold the device in landscape.
4. Launch the app again.
The app should show in landscape directly and IME will
fade-in when it is drawn in landscape.
Change-Id: Ieb656aaa9f76d0f5dcc5487a6602e528ec771552
Remember the latest InlineSuggestionsRequestCallback coming from the
autofill service, so that its autofill session can be invalidated
when the IME process is unbound or stopped.
Test: atest InlineWebViewActivityTest#testAutofillOneDataset
Bug: 226240255
Change-Id: I49cf295b95cec33b7eb404eab62b900014d09e26
(cherry picked from commit 33dc7f89c8)
Merged-In: I49cf295b95cec33b7eb404eab62b900014d09e26
