The latest plan is only system apps with a certain privilege permission
could become NAS. And DeviceConfig could specify any of these valid
candidate to be the default NAS.
So the logic would be like this:
1. If user has set the NAS manually, NMS will persist the user_set bit
and never mess with it.
2. If it is not the case, NMS will try the NAS defined in DeviceConfig,
and then the one defined in config.xml
Also added some new shell commands for easy debugging.
Test: atest NotificationAssistantTest.java
Test: atest NotificationManagerServiceTest.java
Test: Use "device_config put" command to set a valid one. Observe that
NAS is updated and persisted across reboot.
Test: Repeat the command with an invalid one, observe that NAS is not
updated.
Test: Go to settings, set a NAS, and repeat the device_config command,
observe that NAS is not changed.
Test: Go to settings, set NAS to be none. Reboot the device, and "none"
is persisted.
FIXES: 123566150
Change-Id: Ibf8e498944afd5d1fa8659a856a8abdcce41f092
@IntDefs and @LongDefs cannot be stored in a .class file, because the constant
names are lost. Instead, they are packaged out-of-band.
Therefore, they should never be in the API.
Test: python tools/apilint/apilint.py api/current.txt
Change-Id: If22e0cf7db0bb90dae6174bf546f2ec8be4e5458
This reverts commit f3e0eb8b0c.
Reason for revert: Droid Cop revert this CL due to it cause Cts fail on PermissionPolicyTest.testPlatformPermissionPolicyUnaltered
Change-Id: I062b2b9f25dbf388940930a81fd8e036b82b7f45
Allow PackageWatchdog to monitor packages with explicit health checks
enabled. In this case, at the end of a monitoring duration if a
passed-health-check callback is not triggered, the package would be
regarded as failed (in a later cl) and the observer is notified.
If monitoring without explicit health checks, the behavior is the same
as before, packages expire silently.
TODO: Implement the package failure trigger on expiry with failed
explict checks and enable added tests
Removed username from TODO comments
Bug: 120598832
Test: atest PackageWatchdogTest
Change-Id: Ib4322c327bcb00ca9a3fbdc83579e7b5f2fd633b
am: 52910403c5 -s ours
am skip reason: change_id Idd11441e1a6d79954aa1bdb0f93a3567aaf2ecc1 with SHA1 4933ef2310 is in history
Change-Id: I322f64d408457ddc536eef9fc8519a902cf61de4
This module is for API check of java file generated from
default-permissions.xsd
Bug: 80453829
Test: m -j
Change-Id: Ic2d6b9a64ceb19711ce6f3fb2da0f1f01d17ebc5
am: f19990f19e -s ours
am skip reason: change_id I1ec160883282c8819727d3d56c909d9a1c7fd5d2 with SHA1 eb07e4ebff is in history
Change-Id: Ib097ce2a1b92f0e79515ff45b3ae625ee6dc242b
1. Permissions for wallpaper settings Slice.
2. Return value must be marked either @NonNull or @Nullable.
Solution:
1. Add more explanation for settingsSliceUri API usage in javadoc.
2. Follow the public API annotation rule.
Bug: 119118548
Bug: 126699851
Test: atest tests/Internal/src/android/app/WallpaperInfoTest.java
Change-Id: I5db88ce35ba11b018abe42f2192afed44a19fea5
