mUnexempted... was using the value of the EXEMPTED_... flag. The default
values were the same, but this would have caused a problem if we tried
to update the value via a flag.
Also removing deprecated flags.
Bug: 141645789
Test: N/A
Change-Id: I2ace1b510b2d7f5d6f92c16dd6302ae4e5525456
It was already supposed to be a singleton, but multiple instances ended
up being created during the Dagger migration.
Fixes: 142219747
Bug: 141751146
Bug: 136279712
Test: manual
Change-Id: Iada305bd424c7de53bc3148459afb3a4b764e44c
Allow the active supervision component to access app usage limit APIs.
This includes #registerAppUsageLimitObserver
and #unregisterAppUsageLimitObserver.
Bug: 138681869
Test: atest com.android.server.devicepolicy.DevicePolicyManagerTest#testIsActiveSupervisor
Test: atest AppTimeLimitControllerTests
Test: atest android.app.usage.cts.UsageStatsTest
Change-Id: I3daafc14ccdbf27558c1325b965f2bc6d2dab2f6
Define a new change id and use it for gating the change.
Test: atest -p cts/tests/signature, atest AndroidTestBaseUpdaterTest
Bug: 30188076
Change-Id: Ic8c85eae0c490a7eca117b74c4326dd50df2b352
Sometimes, we have seen cases that 'set as default' feature does not work properly in ResolverActivity.
This issue occurs when an activity, with 'exported=false' attribute, is included in the list returned by PackageManager.queryIntentActivities().
By the logics in ResolverListController.java#getResolversForIntent(), the activity is removed from the list.
This creates a difference between the list that ResolverActivity sends to PackageManager when calling addPreferredActivity() and
the list PackageManager maintains. Due to the difference, PackageManager does not set preferredActivity requested from ResolverActivity,
which results the showing of ResolverActivity the next time with same action(even though user has set preferred activity).
To handle this issue, we recommend that the removal logic should be removed from getResolversForIntent() method
because it is already handled in ResolverListController.java#filterIneligibleActivities() through ActivityManager.checkComponentPermission() api.
As the result of that, the list which will be delivered to PackageManager is not changed.
Bug: b/135738126
Test: 1. Install 'JustDial' application via Play store
2. Try below command to launch ResolverActivity
adb shell am start –a android.intent.action.VOICE_COMMAND
3. Pick an item on ResolverActivity, then press 'Always' button
4. Repeat the second step again.
(you will see ResolverActivity comes again)
(cherry picked from commit 5cdfeeaca5516a6d64fa259f9a4ffd2955f8d2ab)
When an automatically generated notification group has 4+ persistent
notifications, hitting "clear all" will cause the group to lose its
automatically generated group summary notification. The solution is to
count the number of notifications belonging to a specific group as well
as the number of ongoing notifications. if the number of grouped
notifications > min before grouping limit & the group has at least one
ongoing notification, then the group summary notification will be marked
as ongoing with the flag FLAG_ONGOING_EVENT. otherwise the flag will
be removed.
Bug: 129562864
Change-Id: I65412935fbb4a74de6ac4cf159d4fd2ebe96dae8
Fix: 129562864
Test: atest NotificationManagerServiceTest
