dist_group replaces owner and the default is going to change, set it
to the current default "android" for frameworks/base java_sdk_libraries.
Bug: 186723288
Test: m checkbuild
Change-Id: I1526853951bcffbe5c5aec6fbc6ba8e0dbea95ad
ResourcesHardeningTest is not a test module name.
This is a partial revert of ag/14505818
Bug: 189953380
Test: none
Change-Id: Iebf50714918d64eb52183c1f140ac8dba38b2ae5
Prevent unnecessary use of HBM. This change decouples illumination
state from touch state. onFingerUp should always be called whenever
the finger leaves the HBM area, and not only when illumination was
requested (isFingerDown was actually isIlluminationRequested()).
Moves the check to onFingerUp to stop illumination only if illumination
was actually happening.
Bug: 187460696
Test: atest UdfpsControllerTest
Change-Id: I2eebe32990761d2fbf86cab228e4a7221a209b42
Static shared libraries were not being properly tracked and snapshotted.
This meant that any lookups that didn't involve the live data structure
were incorrect; it was as if the platform had no static shared libraries
at all.
Fixes: 189851804
Bug: 188661399
Bug: 189851804
Test: atest StaticSharedLibsHostTests
Change-Id: Ia48cf95903bfc8ad194890b5408c8b1f96793ec4
Since commit 23c07ad that changes the order of createSurfaceControl
and performSurfacePlacement, the window in relayout will have
mHasSurface=true. And because isLastConfigReportedToClient is not
set yet at the end of relayout, that causes to report resize for
config change.
In relayoutWindow, the latest merged configuration will be
returned from fillClientWindowFramesAndConfiguration that sets
mLastConfigReportedToClient(isLastConfigReportedToClient), so
the resize is usually unnecessary. Actually most of cases, the
client receives the resize message and just skip because nothing
is different from its states.
Bug: 189915038
Test: CtsWindowManagerDeviceTestCases
Test: Check trace of adding a new simple window. There won't be
a MSG_RESIZED after the first relayout.
Change-Id: Ieaf709907342780e4458c9c3c27902c86068de6e
The validation does not exist in Android R and is causing apps to start
crashing in S.
The validation for the static API createOneShot was maintained, as it
already existed in previous releases.
Fix: 184890231
Test: VibrationEffectTest
Change-Id: I606c943a35ddd68ccacab76f0047b9a276b5cf28
Currently, TCMS will try to bind TCS even the package doesn't install
for certain user. If there are a lot of API calls come, we may call
bindService() many times, this may cause system stability problem. We
received the system reboot problem before.
We already have preload TextClassifierService in ExtServices on primary
user but it's possible the TextClassifierService doesn't install on the
profile user or users unintall package. It's possible the package may
not be installed on non-primary user.
Users also can disable TextClassifierService from ui interface easily,
it's possible occur on both primary and non-primary users, system should
also not bind TextClassifierService in this case.
In this change, system will avoid trying to call bindService() if the
TCS deosn't install or disabled to minimize binder calls.
Bug: 188825683
Bug: 170014504
Test: atest CtsTextClassifierTestCases
Test: manual. Create work profile, turn on/off it and reboot to check
the status. Disable app from Settings and check the status.
Change-Id: Ifa2bccc0d2435712461067d650b52cb02a903c59
When unlock animation is finished, SysUI clears FLAG_SHOW_WALLPAPER
flag from the NotificationShade window to change wallpaper target
from NotificationShade to Launcher, and make NotificationShade window
invisible.
Wallpaper target change must be processed before disposing surface
of NotificationShade.
Bug: 186984629
Bug: 166736690
Test: manual, enabled remote animation and unlock the device.
Change-Id: Id4c2ae65d9dd5aa903c1a25c920df6ed12a1ba1d
- Currently, SystemGesturesPointerEventListener config change is only
called when initializing and if the overlays change, which causes
the swipe threshold to be adjusted for the display cutout touchable
region in the other orientations as well.
In addition, the context used to pull the status bar height is not
updated on config changes which results the portrait status bar
height to be used for landscape gesture recognition as well (the
same height is used for both status and nav bar thresholds).
Together, these two issues make the swipe area almost 3x larger, which
conflicts with immersive games. Instead, we should load the right
status bar height based on the current orientation, and also
update the thresholds when the display info changes.
Bug: 189220056
Test: Enable a display cutout on the device, open a game and try to
swipe up near the edge
Change-Id: Ic573da624756768f8b7b600831eb0b7964720760
Resizable app should be able to handle multi window by themselves, no
need to letterbox for them.
Fix: 189344515
Test: atest WmTests:ActivityRecordTests
Change-Id: I9787467246ae94c1ec9f68f5e7aa6bedf110ac4d
the name of the shared library may be quite different
than the name of the package. we shouldn't assume the
two are the same.
Fixes: 189415306
Bug: 189415306
Test: atest StaticSharedLibsHostTests
Change-Id: I5c1069d195cb37a2bb0e823a889829a7b932774c
