Add the link in the java doc to guide developers how to use the LocaleConfig
Bug: 214154050
Test: Verify the link can be accessed successfully
Change-Id: I19042b485bdf69b8bd8a6465176226109ce1d338
Deprecate the DevicePolicyManager.ENCRYPTION_STATUS_* constants that can
no longer be returned by
DevicePolicyManager.getStorageEncryptionStatus() due to them being
specific to Full Disk Encryption.
Also update DevicePolicyManagerService.getEncryptionStatusName() to stop
referring to the deprecated constants when it doesn't need to.
This is a follow-up from "Drop FDE status checks from
DevicePolicyManagerService" (https://r.android.com/2052073).
Bug: 208476087
Change-Id: I7110711dfc3d32045ee443dc1ae00e8efb4f8d6e
Javadoc stated that org-owned provisioning modes won't receive
the IMEI and serial number, but that's incorrect. That actually
applies to personally-owned.
Bug: 187112267
Test: compiled
Change-Id: I257d1b45b2921891b1d8e6869fb77ce281d2ce90
This reverts commit 6b3c6cae3f.
Changes from revert:
- Explicitly maintain the same behavior as previous versions of Android,
where injection is allowed into all window if the caller has the
INJECT_EVENTS permission, even if it is targeting a certain uid. This
fallback will be removed separately in b/228161340.
- Clear the calling identity before checking if the injection source has
a permisssion to avoid hitting blanket-checks in PackageManager that
denys permissions in some cases, such as if the permission check call
is coming from an instant app (b/228319794).
- Leave the existing IInputManager#injectInputEvent method signature
unchanged, and add a new input method injectInputEventToTarget to
perform targeted injection. This makes it so that tools or apps
relying on the @UnsupportedAppUsage injection method will not be
broken by a change in the method's signature (b/228583652).
Bug: 207667844
Bug: 194952792
Test: Run tests affected by b/228319794 and its duplicates using
cts-tradefed, so that they are also run as instant apps.
Test: Test scrcpy tool works locally
Change-Id: I503e4f087501e3aecf2c18b4b1d27e51ecda59ac
Add a Y2038 check into the time_detector and add infrastructure to allow
command-line testing to confirm it works.
This is before removing a Y2038 check from NITZ parsing code in the
telephony process. After this change, Androdi will consistently block
>= Y2038 suggestions, not just time signals that come in via telephony.
The initial checks attempt to limit the restriction to devices with
32-bit ABIs, since the main issue we're aware of is that time_t is a
32-bit signed int under bionic, hence there could be issues with that
type in 32-bit processes on 32-bit / mixed 32/64-bit devices.
Bug: 204193177
Test: adb shell cmd time_detector suggest_network_time --reference_time 2480587 --unix_epoch_time 1646473966056
Test: Run with 32-bit + 64-bit only builds, inspect adb shell dumpsys time_detector
Ignore-AOSP-First: The change will be cherry-picked upstream
Change-Id: Ib9d6472f5ca7a62d59b3224f1845846f99a0b52d
Adds explanation of MessagingStyle fields, and corrects some
typographic errors that lead to some javadocs not being rendered
completely.
Bug: 159367102
Test: Only documentation change
Change-Id: I751a15d0abf35cdcb7ad2caacf954bdeec23a394
Add some detail about migrating to OnBackInvokedDispatcher and the
reason behing the deprecation of onBackPressed methods.
Fixes: 227563202
Test: Documentation change only
Change-Id: Ifc2dd88cb9600efae84cd353549811e7b07ae4bc
If the role holder updater fails to update the role holder, it can
specify how the platform should handle the failure. It can either
fail provisioning, or it can carry on using the platform-driven
provisioning.
Bug: 230749552
Test: compiled
Change-Id: Id24b24e5d7386d9806efa232f8c71287c9b7704b
This bypass was originally allowed to let restricted users who can't use
location to pair bluetooth devices. This isn't needed anymore with the
bluetooth permissions.
Test: Set up restricted profile and pair bluetooth
Verify com.android.phone gets rejected
Fixes: 230861324
Change-Id: Ib34c0b56ef52f5ee2deceb84b02cd0ff73d8181d
Bug: 227383489
'dumpsys cacheinfo' can now dump more information about caches, by
supplying arguments to the command. If no switches are specified
then the behavior is unchanged from the baseline. If any switches are
specified then zero or more caches are selected; the command dumps
statistics and content for every selected cache.
The four switches each include a key string.
The switch Selects a cache if
--------------------- ------------------
-name-has=<key> the cache name contains the key
-property-has=<key> the property name contains the key
-name-like=<regex> the cache name matches the regex key
-property-like=<regex> the property name matches the regex key
Tested by running the following commands and manually verifying the
output.
dumpsys cacheinfo com.android.systemui
dumpsys cacheinfo com.android.systemui -name-has=OrganizationOwned
dumpsys cacheinfo com.android.systemui -name-like=OrganizationOwned
- no results, as this regex does not match any cache
dumpsys cacheinfo com.android.systemui -name-like=.*OrganizationOwned.*
dumpsys cacheinfo com.android.systemui -property-has=package_info
dumpsys cacheinfo com.android.systemui -property-like=cache_key.package.*
Test:
* atest FrameworksCoreTests:IpcDataCacheTest
* atest FrameworksCoreTests:PropertyInvalidatedCacheTests
Change-Id: I141d7e85ba3ea8b0f2615bbd49537c1170fb5449
