This CL instroduces WMS#attachWindowContextToWindowToken
and the corresponding API in WindowContextController to make
WindowContext able to associate with a WindowToken.
Test: atest WindowContextControllerTest
Test: atest WindowManagerServiceTests#testAttachWindowContextToWindowToken*
Bug: 159767464
Change-Id: I807a67fba149cbdc4267442bab0b64e6a95bd4b5
This reverts commit 8dd5021359.
Reason for revert: DroidMonitor: Potential culprit for Bug 185150796 - verifying through Forrest before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Bug: 185150796
Change-Id: Ie6809d9e20b5c32c076e7a790095c65a2295781a
The methods setTaskWindowingMode and resizePrimarySplitScreen
can be replaced with the methods of WindowContainerTransaction
and TaskOrganizer.
Bug: 174040691
Test: CtsWindowManagerDeviceTestCases
Change-Id: I975457887a87464456675010c7531738fa5f62f4
If the new password is numeric only, treat it as numeric
PIN when setting it as new lockscreen password.
Bug: 172054475
Bug: 181489206
Test: atest FrameworksServicesTests:DevicePolicyManagerTest
Change-Id: Ie15f1966a76344d3bb8e8778599fbd604bfa8c69
This change is part of defining a distinct BLUETOOTH_ADVERTISE
permission to guard the BluetoothLeAdvertiser APIs, since that's a
distinct enough of an operation from SCAN and CONNECT. It'll
continue to be covered under the general "Nearby devices" runtime
permission group.
Bug: 181813006
Test: atest CtsPermission2TestCases
Test: atest CtsPermission3TestCases
Change-Id: I8b62e4d625df1e201f12a73025cd29c431feea79
(manual cherry-pick from AOSP to fix merge conflict)
Minimizing cost for using libbinder.
Bug: 183654927
Test: boot
Change-Id: I1a4785a58afcaf2d312ef52a07f41fe3dd3a8fa6
Apps can't actually suppress the bubble, that is only
done by the system so that method is @hide.
Did a similar thing for setSuppressNotification for
consistency.
Test: atest NotificationManagerTest (see CTS CL)
Bug: 184204395
Change-Id: Ia17453507daf5bba4408bd6b386efa225c3051dd
This code was not meant to be shipped and was disabled by default. It
was accidentally enabled when productionizing the final version of FSD2D.
Bug: 184781934
Test: 1. atest CtsBackupTestCases
2. atest CtsBackupHostTestCases
3. Run a D2D transfer and verify system apps are properly restored
Change-Id: I47dbc769a316b17a38b6c21d7a1294d7ff977491
* If the password quality is NUMERIC
or NUMERIC_COMPLEX, the credential
type should be CREDENTIAL_TYPE_PIN
Bug: 184103377
Test: atest com.android.server.devicepolicy.PasswordPolicyTest
make RunSettingsRoboTests -j ROBOTEST_FILTER=com.android.settings.password
CtsVerifier > Device owner tests > policy transparency test
> set password quality
Change-Id: If0b1fbc71bbd0b4e59bc05594cd14e99a32d8bd1
Address API review for changes related to admin-granted permissions:
* Change the provisioning extra to indicate it only affects
sensors-related permissions.
* Add an IntDef for the AdminPermissionControlParams grant state.
Bug: 184204476
Bug: 184204334
Test: atest ManagedProvisioningTests
Change-Id: I75c8b6de1e897e02916b17f0ae3a521f8384c242
Besides UI contexts, the context created via
Context#createConfigurationContext with a proper configuration
should be allowed to inflate views or obtain ViewConfiguration.
An example is that a wear device inflate views into bitmap and pass
the bitmap to the Wear OS Companion app on the phone.
Bug: 177847640
Test: atest StrictModeTest
Change-Id: Iab232a80a973f54bf0484262d45af3e4c2f0e5dc
A set of related changes under the heading of "configuration logic
changes".
The ability to 'discover' the package of a LTZP has been removed. A
provider's package name must now match the package name held in
config.xml. This takes advantage of changes in ServiceWatcher (which,
due to a recent change, no longer insists on specific configuration
options). It will allow the package name to be determined at runtime via
server flags in a future change, which will make future testing easier.
The overall location time zone detection feature can also now be
configured on and will not "show up" if there are no providers currently
enabled. The ability to have the location time zone detection feature
"supported" on the device be on and not have it "show up" in the UI when
there are no providers will make testing easier when the secondary
provider has been removed from AOSP (bug 178169250).
To remove command line duplication of things that can now be achieved
via device_config (AKA server flags), there have been various command
line changes. It is also now possible to override a provider's "mode"
via the command line to be "enabled". Previously, a provider could only
be disabled or set into a simulation mode via the command line, which
assumed the default state was "enabled" (bug 178169250).
Bug: 175718363
Bug: 178169250
Test: See the associated change in cts/
Change-Id: I0d3314155cef4f122cae0d569b4687b658e777b1
If the app doesn't call startForeground() in time, throw a new exception
ForegroundServiceDidNotStartInTimeException.
Test: Manual test with a test app:
04-01 15:24:39.438 10293 9078 9078 E AndroidRuntime: FATAL EXCEPTION: main
04-01 15:24:39.438 10293 9078 9078 E AndroidRuntime: Process: com.google.omakoto.testapp, PID: 9078
04-01 15:24:39.438 10293 9078 9078 E AndroidRuntime: android.app.ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{92c1599 u0 com.google.omakoto.testapp/.MyFgs}
04-01 15:24:39.438 10293 9078 9078 E AndroidRuntime: at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:1894)
Bug: 124137635
Change-Id: I7d97e15ba47a32a242fb461e7312adf3f28ab3a6
The activity recognition source may access activity
recognition in its operation as being the activity
recognition source. Accesses from an AR source
(for special tags it designates - the APK may contain
other components) for location and AR are tracked in
a dedicated app op.
bug: 182204957
Test: atest CtsActivityRecognitionTestCases
Change-Id: If29fba1c51d70a2806a0907a73a96d3d8d7a3100
Added the following testAPIs that are guarded by
SET_AND_VERIFY_LOCKSCREEN_CREDENTIALS and
ACCESS_KEYGUARD_SECURE_STORAGE permissions:
* setLock
* checkLockCredentials
Also refactored methods out of LockPatternUtils
to LockSettingsService to allow clearing the caller identity.
Test: atest com.android.server.locksettings
Test: atest LockscreenCredentialTest
Test: atest PasswordComplexityTest after replacing usage of adb
commands with the new testAPIs
Bug: 182260585
Change-Id: Idc0432773c92ada9deb3e370526cb2ce219595dc
Change-Id: I28cbe6093a56a231022c61a6821accf01d28cda6
Added a new testAPI in UiAutomation to get the currently adopted
shell permissions using adoptShellPermissionIdentity.
Test: atest UiAutomationTest
Bug: 183716601
Change-Id: I66a6c753480cecf971f7354daaddbb404f5c1453
This attribution source is going to be used by Gmscore to proxy
the blame for uwb_ranging runtime permission check (since Gmscore which
is the direct caller of this surface is in most cases proxying the
request from 1p/3p apps).
Note: This CL just adds the skeletal API to start the API reviews. The
actual implementation needs a major refactor of the stack which is WIP.
Bug: 183904955
Test: atest android.uwb
Change-Id: Ia0338b573306f44c493bf1c136e68b4f46877816
Clients can register for listening to changes in procstates and if
they are only interested in knowing if the procstate crosses a certain
threshold, they can specify a "cutpoint" and they will only get
a callback if the procstate crosses that "cutpoint" but clients cannot
use this if they are also interested in changes in capabilities. So,
add a way for clients to use the "cutpoint" facility and also listen
to changes in capabilities.
Bug: 177641226
Test: atest services/tests/servicestests/src/com/android/server/am/ActivityManagerServiceTest.java
Test: atest services/tests/servicestests/src/com/android/server/am/UidObserverControllerTest.java
Test: atest ./tests/cts/hostside/src/com/android/cts/net/HostsideRestrictBackgroundNetworkTests.java
Change-Id: I1198e602ca81382975500b10f930dacfd16919e3
