By default.
Fix: 149930393
Test: "adb shell dumpsys activity -a", system process record have
curCapability=7.
Change-Id: I9dacaefbb33a6e595044b452dcbfd3b26fc9df2b
am skip reason: Change-Id I37ba02eb3003ea28e66f50ca0b612597ef48f6d5 with SHA-1 daeb328e32 is in history
Change-Id: I6613d433d89d8e3fa324f6c3062210a8d683fb52
1) BiometricService / AuthService always need to be started, since on
Android 11 and later, the public credential auth API comes through this
path.
2) Consolidate getAuthenticatorId() and expose via AuthService. This is
used only by the platform during key generation. Instead of asking
each individual service, AuthService will return a list of IDs for
sensors which are enrolled and meet the required strength.
Test: atest com.android.server.biometrics
Test: fingerprint device, CtsVerifier biometric section
Test: face unlock device, CtsVerifier biometric section
Test: remove biometrics from device, CtsVerifier biometric section
Bug: 148419762
Bug: 149795050
Change-Id: I2c5385b1cd4f343fabb0010e1fe6fb1ea8283391
It generally shouldn't be depended on. Only by droidstubs for
modules.
Bug: 137191822
Bug: 149906971
Test: m
Change-Id: I16e672aaae80d8bcce25e46c34984797740aae1b
Merged-In: I16e672aaae80d8bcce25e46c34984797740aae1b
(cherry picked from commit 6fb18bbfdb)
The AssetManager constructor is marked UnsupportedAppUsage and the
recent changes to OverlayConfig caused an exception to be thrown when
the function is not called from the root process.
Previously a warning message would be logged indicating that no static
overlays would be loaded. Removing the uid check will restore the
previous behavior.
Also remove the system uid checks for initializeSystemInstance so PMS
service can also be constructed during testing.
Bug: 149806146
Test: invoke new AssetManager() from non-root thread
Change-Id: I55af2cddeba4df7a99c281c93e0181b9e2139139
Moves the anchor point of the animation into the corner from the
top left corner to the center. This fixes the issue where the preview
appeared to move "up" before following the correct path.
Bug: 149100933
Test: manual; changes animations only
Change-Id: I45edf9a82db5f67efa129bdb8a0fd091189e7c7a
They needn't be here, because they don't contribute to the
bootclasspath. Modules should only be depended on via stubs,
except for current.txt generation.
Test: m
Change-Id: Id9e43205fe1badace66fc580effd77e4863265d0
Since RebootEscrowKey started wrapping SecretKey, it is necessary to check
equivalence via a method that does not do object equivalence. Use the
underlying byte array in the tests. equals() could be implemented, but then
hashCode() would need to be implemented which would be based on the private
key.
Test: atest RebootEscrowDataTest
Change-Id: Ia5b0bb822dcd3e59b5898f390fa8670db0b8d4c9
We use the package settings class as a central point for invalidating
on package information changes; for permission changes, we invalidate
from inside the individual permission data objects.
Bug: 140788621
Test: boots, package tests (pending)
Change-Id: Iec14d4ec872124e7ef4612c72d94c89a7319ace0
Print provider network home or roaming in the toString()
method of WifiConfiguration.
Bug: 149881869
Test: Verify new field is printed
Change-Id: Iddcd03435eb416bd6dc73bd0e7e32f180e0265d6
By default, intents are broadcast on a background queue, which can
accrue a lot of backed-up tasks especially when the phone was
recently rebooted. In the case of the screenshot action shade, this
causes a long pause (up to ~minutes!) between tapping on an action
chip and seeing the app actually open.
This change adds a flag to the intents to cause them to be queued
in the foreground. In the notifications flow, this flag gets added
in NotificationManagerService (so this is preserving behavior). In
addition, these intents are user-generated (by tapping on the chip
or screenshot preview), so it's reasonable to send them in the
foreground.
Bug: 149481318
Test: manual
Change-Id: Idfcb8ade3fee232b140299585296e85093eeb1fe
For procstats aggregated stats collection, we need to expose the
aggregated ProcessStats object back to the caller.
Change-Id: Ifb52f813d679e3e0a1e061f983d8b4f539d6d72a
Test: nothing yet
Some ANRs have no stack traces uploaded through dropbox. This appears to be because the file holding them was not created
So in the case where we can't create the file, add an exception message to the string part of the dropbox upload.
Change-Id: Ic06ac9c25974633905b1a0bfcfcef8ed833795e8
Bug: 148848039
Test: Manually threw exception in createAnrDumpFile() and triggered ANR.
This stops KeyChain from throwing AssertionError when binding to
service fails due to user being locked, which would have crashed
the entire system server.
Bug: 149912024
Test: atest KeyChainTests
Change-Id: Ie110a4210e157cc9b111d845478bdf21e948ba4f
When security logging is enabled on org-owned profile devices,
Security events will be redacted to preserve privacy on the personal
profile as follows:
* TAG_ADB_SHELL_CMD
Shell command will be redacted.
* TAG_MEDIA_MOUNT
* TAG_MEDIA_UNMOUNT
The media's volume name will be redacted.
* TAG_APP_PROCESS_START
* TAG_CERT_AUTHORITY_INSTALLED
* TAG_CERT_AUTHORITY_REMOVED
* TAG_KEY_GENERATED
* TAG_KEY_IMPORT
* TAG_KEY_DESTRUCTION
* TAG_KEY_INTEGRITY_VIOLATION
Only events happening inside the managed profile will be returned
to the admin.
Bug: 148437300
Test: atest FrameworksServicesTests:DevicePolicyManagerTest
Test: atest FrameworksServicesTests:SecurityEventTest
Test: atest FrameworksCoreTests:EventLogTest
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testSecurityLoggingWithSingleUser
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testSecurityLoggingWithTwoUsers
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testSecurityLoggingEnabledLogged
Test: atest com.android.cts.devicepolicy.OrgOwnedProfileOwnerTest#testSecurityLogging
Change-Id: I2e52229a3163b3e0dc3d80d71700023394d84587
Instead only link ParceledListSlice.aidl,
which is the only one used by
framework-wifi.
Bug: 149127842
Test: "couldn't find import for class android.content.pm.ParceledListSlice"
no longer appears when building
Change-Id: Ie9f67c58c3694bbf1f45ae8e1d99e6e65fbc3163
am skip reason: Change-Id Ib9e2c6cef7094ccac7862be249d619212f0013fd with SHA-1 779d6bee21 is in history
Change-Id: I1b8f8ae273b67d5a376c41665f8bc44c412b523f
