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
Finishing the suspend dialog when the package for which it was shown
gets unsuspended for any reason.
Also, attributing any interaction with this dialog to the suspending
package, as the system is showing the dialog on its behalf.
Test: Manual, from an unrooted shell:
adb shell pm suspend com.android.chrome
Tap to start chrome and wait for the dialog to appear. Then:
adb shell pm unsuspend com.android.chrome
The dialog should disappear. Further,
adb shell dumpsys usagestats
should show USER_INTERACTION for com.android.shell.
Bug: 169137795
Fixes: 180336589
Change-Id: I70b6f23e2994d8802335e35932ed09209754697c
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
gets sent to
This adds an API to allow sending a broadcast to an app that has permission FOO but not permission BAR.
Earlier, a lack of this option was causing a double send problem for broadcasts, which should now be resolved.
Test: manual
Bug: 183537857
Change-Id: I13287d63e039164694be4daa832bb23709990054
This addresses API council feedback.
SUPPORTED_MODES_ORGANIZATION_OWNED is now
FLAG_SUPPORTED_MODES_ORGANIZATION_OWNED.
SUPPORTED_MODES_PERSONALLY_OWNED is
FLAG_SUPPORTED_MODES_PERSONALLY_OWNED.
SUPPORTED_MODES_DEVICE_OWNER is
FLAG_SUPPORTED_MODES_DEVICE_OWNER.
SUPPORTED_MODES_ORGANIZATION_AND_PERSONALLY_OWNED is now
FLAG_SUPPORTED_MODES_ORGANIZATION_OWNED |
FLAG_SUPPORTED_MODES_PERSONALLY_OWNED.
Note that these new flags have the same exact values as
the original values, so no changes are needed to be done
for the provisioning trigger.
Fixes: 179709752
Test: atest ManagedProvisioningTests
Test: atest ManagedProvisioningRoboTests
Change-Id: I1845837e752df5750083dc3bf31cbc356f4d24b7
Currently getKeyPairGrants returns Set<Set<String>> which is used
to encode the fact that packages that share UID will always have
access to a given key together. This change makes this UID explicit
by changing return value to Map<Integer, Set<String>>.
Bug: 184018067
Test: atest MixedDeviceOwnerTest#testDelegatedCertInstallerDirectly
Test: atest MixedDeviceOwnerTest#testKeyManagement
Change-Id: I571e67bda1709ddb48012003de055c7211edb786
The methods setTaskWindowingMode and resizePrimarySplitScreen
can be replaced with the methods of WindowContainerTransaction
and TaskOrganizer.
Bug: 174040691
Test: CtsWindowManagerDeviceTestCases
Change-Id: I975457887a87464456675010c7531738fa5f62f4
* Collapsed state now appears with the 'headerless' style used for all other collapsed notification templates (except conversations / calls which have their own style).
* Expanded state contnues to use the 'header' treatment of all our big states, but messaging faces will now appear in the left icon gutter, and text will always align with other styles.
* Image messages show up in the 'right icon' location when collapsed, but will not be moved to the 'left icon' when grouped.
* 1-1 conversations will highlight the other user's name as the title, in the collapsed state.
Fixes: 173204301
Test: post and inspect lots of messaging notifications
Change-Id: I5a56d11ea98be1a22caca0d85040ab3fc375216f
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
Rename getLastTimeComponentUsed to getLastTimeAnyComponentUsed based on
the API review feedback.
Bug: 183656434
Test: atest CtsUsageStatsTestCases:UsageStatsTest
Change-Id: Ie3388150ab49d0f4b2f16e4d5aacda1cc8b3663b
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
