* Ignore android:fullBackupContent for apps targeting Android S+ while
in D2D
* Update LocalTransport::getTransportFlags() to support
FLAG_DEVICE_TO_DEVICE_TRANSFER (required for CTS testing)
Bug: 180523564
Test: atest FullBackupRulesHostSideTest
Change-Id: I115c1c76f4b0d8b486cc9f146ef630fda3ff2a03
Deprecate/delete setTemporaryAppWhitelistDuration(int type, long duration) which is also a new API added very recently.
Bug: 171305836
Test: atest cts/tests/app/src/android/app/cts/ActivityManagerFgsBgStartTest.java
Reboot device, observe "tempAllowListReason" in logcat.
Change-Id: I29181ce224c28277db1d45ec7fd0f79e032e5c90
BYPASS_INCLUSIVE_LANGUAGE_REASON=existing public API
It was refactored to split the "create" and "manage" parts so the
new user dialog is shown in the proper times, but such changed
broke the API when caller was passing initialExtras or a different
PO component.
To fix this issue, DPMS passes a token when the user is created,
and ignores the callback when the token matches.
This change also improved logging (which helped diagnose this issue).
Test: atest com.android.cts.devicepolicy.DeviceOwnerTest#testCreateAndManageUser_LowStorage,testCreateAndManageUser_MaxUsers,testCreateAndManageUser_GetSecondaryUsers,testCreateAndManageUser_SwitchUser,testCreateAndManageUser_CannotStopCurrentUser,testCreateAndManageUser_StartInBackground,testCreateAndManageUser_StartInBackground_MaxRunningUsers,testCreateAndManageUser_StopUser,testCreateAndManageUser_StopEphemeralUser_DisallowRemoveUser,testCreateAndManageUser_LogoutUser,testCreateAndManageUser_Affiliated,testCreateAndManageUser_Ephemeral,testCreateAndManageUser_LeaveAllSystemApps,testCreateAndManageUser_SkipSetupWizard,testCreateAndManageUser_AddRestrictionSet,testCreateAndManageUser_RemoveRestrictionSet,testUserAddedOrRemovedBroadcasts # on automotive and phone
Bug: 180515783
Change-Id: Ia6bddecd13fcdfc9604f40391ab7b2a5e98c146b
* Foreground service notifications.
* Colorized notifications (where the snooze button's color would be wrong).
* FullScreenIntent notifications, which are timely.
* HUNs, since the expanded state could have the button.
Bug: 179178086
Test: manual
Change-Id: I3fa46d6493c14ddf7e9b9e28afb7de15b1ddd89a
Delete the overloaded version of setPendingIntentAllowlistDuration() without reasonCode.
Bug: 171305836
Test: atest cts/tests/app/src/android/app/cts/ActivityManagerFgsBgStartTest.java
Reboot device, observe "tempAllowListReason" in logcat.
Change-Id: Ib8bd22eefb5d5f308d2bcca17221499c2a6adc79
This reverts commit e756211374.
Reason for revert: Apparently this is used; b/179601086
NoNonSdkCheck: The original change erroneously removed the method from the block-list; this reinstates the method
Fixes: 179601086
Test: builds
Change-Id: I383bc0a0e2a319b24e11aa7a07a69603efff706f
Add more server flags that can be pushed to devices to influence geo
detection service behavior.
This renames DeviceConfig as ServerFlags and introduces an intermediary,
the ServiceConfigAccessor, to hide details and handle changes to config
values that need the location_time_zone_manager to restart.
Simulating server flag changes example:
adb shell cmd device_config put \
system_time primary_location_time_zone_provider_enabled_override false
Inspecting manager / provider states:
adb shell dump location_time_zone_manager
The following manual tests were conducted to check the plumbing:
Modifying settings behavior:
adb shell cmd device_config put \
system_time location_time_zone_detection_setting_enabled_override true
<Confirm the settings value cannot be changed by user>
adb shell cmd device_config put \
system_time location_time_zone_detection_setting_enabled_override false
<Confirm the settings value can be changed by user>
adb shell cmd device_config delete \
system_time location_time_zone_detection_setting_enabled_override
<Confirm it returns to normal>
Disabling the feature / location_time_zone_manager:
adb shell cmd device_config put \
system_time location_time_zone_detection_feature_supported false
<Confirm SettingsUI (after restart) doesn't show the geo detection option>
<Confirm manager is not started>
Enabling the feature / location_time_zone_manager:
adb shell cmd device_config put \
system_time location_time_zone_detection_feature_supported true
<Confirm manager is restarted>
Note: "cmd device_config" doesn't allow multiple config keys to be
changed at once, and any change to service config keys cause the
location_time_zone_manager to restart. When changing multiple, set
"location_time_zone_detection_feature_supported false" to stop the
manager, and "location_time_zone_detection_feature_supported true" when
all changes are done.
Test: Manual testing (see above)
Test: treehugger
Bug: 178107773
Change-Id: I07b57add1ed47197587907b9f0a85f38acc0a76a
