This reverts commit 62b08743c6.
Reason for revert: The tests are failing consistently now, not just flaking. The problem is that `adb shell input keyevent --longpress 26` doesn't open global actions dialog after a reboot. After the dialog has been opened the first time, it will start working.
Change-Id: I32faba89d19b24bc4141cc9bb56abffb70aeb52f
Bug: 156037650
Fix a potential race condtion when the same message object
is being enqueued by two threads.
Bug: 150263007
Bug: 154867444
Test: atest android.os.cts.MessageQueueTest
Change-Id: Id79448ba8719479cbdb054f2cdd172fdcbe86d47
(cherry picked from commit 96a6fec4d6)
Revert "opt/net/wifi/tests: Run mts-wifi on AOSP builds"
Revert submission 10814415-mts-wifi-com-androi-wifi
Reason for revert: Workaround no longer necessary: b/152559881#comment2
Reverted Changes:
I11baae67e:frameworks/base/wifi/tests: Run mts-wifi on AOSP b...
I66febcbb2:opt/net/wifi/tests: Run mts-wifi on AOSP builds
Bug: 152559881
Test: in continuous runs
Change-Id: I1d5f4d312f4e15ae5e2e56965b3fc76fdefcdcea
The SYSTEM user does not get its default restrictions
from UserTypeDetails.mDefaultRestrictions; rather it gets
it from config_defaultFirstUserRestrictions. Therefore, we
now dump those restrictions from the latter (instead of
the former) for the SYSTEM user.
Fixes: 146793707
Test: manual check of: adb shell dumpsys user
Change-Id: I5cf04d20fe9edd748803634ec80336b267695ce6
Merged-In: I5cf04d20fe9edd748803634ec80336b267695ce6
- If the profile has disable screen capture enabled on their work
profile, then DPM service will directly set the secure state on
the surfaces, but the window flags aren't updated. Callers need
to check the cache state to also ensure that they report the
right secure state when taking a snapshot and when rotating.
Bug: 156104186
Test: Open a work profile app with screen capture disabled and
ensure the task snapshot dump state reflects the secure
state
Change-Id: I7cc6d525c818346846d27bdfad1961b464dfb46d
When IME switches, InputMethodService will be rebound and re-initialize
input view, since it needs take time to update the layout, if the insets
calculation happens during the layout, the givenContentInsets are not ready
yet during this phases, then the insets size will abnormal
and may cause the IME target layout will be resized to zero height after
applied insets change.
If the view layout is focused, system will clear such 0-sized view
focus, since user can't easily aware and it's not safe to focus on invisible view
(refer CL[1]), then after IME switches, input connection will break because
the view focus lost.
Make sure to set the valid IME insets sources frame when the server side visible
set as true in InsetSourceProvider.
[1]: 5db64eb1da
Fix: 153612876
Test: atest InsetsSourceProviderTest#testUpdateSourceFrameForIme
Test: atest InsetsSourceTest InsetsStateTest InsetsSourceProviderTest \
InsetsControllerTest InsetsStateControllerTest \
InsetsSourceConsumerTest
Test: atest ImeInsetsControllerTest
Change-Id: Id2c482e112c1d73cf7d5b3ba5e1a2d5775f47298
