* ChangeId DROP_CLOSE_SYSTEM_DIALOGS doesn't need to be @TestApi.
* BROADCAST_CLOSE_SYSTEM_DIALOGS permission needs to be @SystemApi given
its protectionLevel
Bug: 181593849
Test: Builds
Test: atest CloseSystemDialogsTest
Change-Id: I6cbbc4a396f920e6cc60299ba827c76158e2e7cf
These flaky tests have been stable for the past week and can be promoted
Test: atest FlickerTests:com.android.server.wm.flicker.ime
Bug: 171049649
Bug: 167521849
Change-Id: Iae35556c20ce2928b36fd1dfdcdf80633e802dba
- Refactor OneHandedSettingsUtil.java
- Remove redundant test for SettingProvider
New policy: b/175024829
Settings key: <one_handed_*> is not readable.
From S+, new public settings keys need to be annotated
with @Readable unless they are annotated with @hide.
Recent changes :
ag/13764747 Remove @Readable for hidden fields added in S
Test: atest WMShellUnitTests
Bug: 183064974
Change-Id: I85bf3680cbcdba4c85aa96de058bc85cfabead46
These flaky tests have been stable for the past week and can be promoted
Test: atest FlickerTests:com.android.server.wm.flicker.rotation
Bug: 171049719
Bug: 167521849
Change-Id: Iebe3abe89857e96d1985ab3f840e92fa7b168844
These flaky tests have been stable for the past week and can be promoted
Test: atest FlickerTests:com.android.server.wm.flicker.close
Bug: 171049683
Bug: 171049760
Bug: 167521849
Change-Id: I8fb98f3c9a4866bd82e2e39fb90b861719401960
These flaky tests have been stable for the past week and can be promoted
Test: atest FlickerTests:com.android.server.wm.flicker.close
Bug: 171049778
Bug: 171049647
Bug: 167521849
Change-Id: Ic7e45a27120f69b4a4d5e5ca9266809fcd969939
Use ServiceConnectivityResources instead.
Start by creating resources in the ServiceConnectivityResources package
to match the internal configuration, and common overlays.
Bug: 182125649
Test: device boots, has connectivity
Change-Id: I77a3efca2cd644f9828db1ed5d3cae8070fb8363
The protos are built separately by framework-connectivity from framework
protos, keeping only android.net protos for the connectivity jar.
Bug: 171860710
Test: m framework-connectivity.impl
Change-Id: I2c4a37ff2ee9e8efde49885feeafa27dcff7ca2c
This fixes a merge conflict with downstream branches due to an
incomplete cherry-pick.
Bug: 171540887
Test: m
Merged-In: I0c0daa91ef272a19c548cf55eb2f764c95f8f844
Change-Id: I0ec602f573698578e4d72d38772c39a1b88b87d2
New policy: b/175024829
Settings key: <one_handed_*> is not readable.
From S+, new public settings keys need to be annotated
with @Readable unless they are annotated with @hide.
Recent changes :
ag/13764747 Remove @Readable for hidden fields added in S
Test: atest WMShellUnitTests
Bug: 183064974
Change-Id: I185491189a3804d7038be3c117583ab571e7a961
Given that ConnectivityService is moving to a mainline module, we need
a @SystemApi for it to listen for changes in blocked status of an uid.
So, we decided to create a new API for this which can provide
ConnectivityService with more info about why an uid is blocked (which
will be useful for adding a new similar onBlockedStatusChanged callback
in CM.NetworkCallback) and also captures data saver restriction without
having out to track it separately.
Currently, NPMS does some redundant computations because we are
calculating both uid rules and blocked reasons separately. In a
follow-up change, we will compute uid rules using blocked reasons
and later possibly remove that onUidRulesChanged callback.
Bug: 176289731
Test: atest ./tests/cts/hostside/src/com/android/cts/net/HostsideRestrictBackgroundNetworkTests.java
Test: atest ./tests/net/java/com/android/server/ConnectivityServiceTest.java
Test: atest ./services/tests/servicestests/src/com/android/server/net/NetworkPolicyManagerServiceTest.java
Change-Id: Ib9949b8619c6b148f73630b314c4113d76c31ec1
This tile is gated by a feature flag and the QAW Client service availability.
Also add a new icon for the wallet tile as a fallback option - if it fails fetching the icon from QAW Client, the fallback icon will be used.
Bug: 180959290
Test: atest
Change-Id: I56bdbef5b4d5d41abacb598422d8a2a4716a79fd
On devices with multiple sensors, lockout should be reset whenever
any strong sensor authenticates.
Bug: 163058911
Test: atest CtsBiometricsTestCases
Change-Id: I4bcdc0279cdaa444e59cf0fac6645d9a67e7d11d
