* changes:
Add a TunerResourceManagerService as an Android System Serivce.
Add Lnb related APIs into the TunerResourceManager interface
Add Cas related APIs into the Tuner Resource Manager
Adding ITunerResourceManagerService interface into android.media.tv
The camera-specific pinning needs to be disabled for iorap to be able to trace the camera
APK.
Saves 40-70MB of memory system-wide depending on the device.
Bug: 149426956
Test: adb shell dumpsys pinner
Change-Id: If98eb82a9d741a41e76565d37cfe2dd828e7a653
These were never meant to be 2way, and are calling application callbacks,
from system server which can potentially take long time.
Thses should not be sensitive to ordering with any other IPCs, so moving them
from 2way to 1way should be safe.
Fixes: 147705675
Test: presubmit
Change-Id: Ie4e8941fba2c8a388697c3a42ad6ef76512eba9f
1) Always update strength after registerAuthenticator. Otherwise the
flag will not be applied (e.g. after reboot)
2) Add strings for onAuthenticationError
Bug: 148419762
Test: manual
Test: atest BiometricServiceTest
Change-Id: Ia20a91e401d6753b55d6aa4a36d487fc15465ba5
Also fixes bug where we autolaunch without waiting for the inactive
tab list to load. If the inactive tab's targets are 0 since they
are not loaded, if the active tab's targets are 1, it would
incorrectly autolaunch.
Test: manually tried attaching a file in gmail with no cross-profile
intents
Fixes: 149383054
Change-Id: I1a2455088762dce7265ae4b7ad2c6bc8b217f99e
* Enable perfetto tracing and readahead for testing.
* Extend time limit for JUnit test to 5min.
Bug: 148936893
Test: run atest iorap-functional-tests on Forrest
Change-Id: Iad2b2201abf7736a9c86e4e5f7c1579eb78b2e23
Add support to the TaskOrganizerMultiWindowTest for resizing
two tasks synchronously.
Bug: 139371701
Test: TaskOrganizerMultiWindowTest
Change-Id: I57fabf9a32fd02d461acd0e6ef4265df844eb2b7
Field name notification_panel_modified was meant to be
notification_channel_modified, matching the atom name.
Test: build
Bug: 146488473
Change-Id: Iafe46334e74df5224e6f6b5e26f30841b3c94aa6
Now NotifCollection has three methods for sending dismissals to system
server:
1. dismissNotification
- dismisses a single notification
- use case: when user swipes away a single notification
- ends up calling IStatusBarService#onNotificationClear to
update system server
2. dismissNotifications - dismisses multiple notifications it's passed.
- use case: user dismisses all 'gentle/silent' notifications
- ends up calling dismissNotification (#1) multiple times
3. dismissAllNotification
- dismisses all clearable notifications associated with a given userId
- use case: user clicks on "clear all" to clear all their notifications
- ends up calling IStatusBarService#onClearAllNotifications to
update system server
Test: atest NotifCollectionTest
Test: atest SystemUITests
Change-Id: I1fdf38fd192824b1dfc45dd3a5e1fea0a51e2e75
Fixes: 149241859
These are currently logged in NotificationRecord.setVisibility().
Rather than add a dependency on the NotificationRecordLogger to
NotificationRecord, I've passed one in to that method.
I considered but rejected doing the same for
NOTIFICATION_INTERRUPTION, which is logged similarly in
NotificationRecord.setInterruptive(). The circumstances under which
that log gets written are challenging to understand, and I'm not
currently convinced that it is worth porting.
Test: atest NotificationManagerServiceTest NotificiationRecordLoggerTest
Bug: 146488473
Change-Id: I956cd4ededa470f91244305d4c26fb981d4c94a4
Per API council guidance, setLoaders, getLoaders, and clearLoaders
are no longer part of the public API. addLoader and removeLoader
are now consume variadic loaders.
Bug: 142716192
Test: atest FrameworksResourceLoaderTests
Change-Id: If29d47b526ae6acd582b14206b2c6372f3c497be
If the load call times out or fails in some other way, the management
acitivity will show that and just show all favorites (without the
removed tag).
Also, added many docs
Test: atest
Test: manual
Fixes: 149138396
Change-Id: I58e391b65df1e40989101f227c46fd47e3fb419a
frameworks/base/services/core/java/com/android/server/content/SyncStorageEngine.java:1739:
warning: Replaced KLP with KitKat in the documentation for method
com.android.server.content.SyncStorageEngine.maybeDeleteLegacyPendingInfoLocked(java.io.File)
[Typo]
Change-Id: I167b58d5a3a4b994bb95f5401d5db70df5c4a313
Test: make build
This undoes part of the work to remove parole windows from
AppStandbyController. In the past, UsageStatsManager.isAppInactive would
return false when the device was charging. This wasn't documented
behavior, but was intentional, so removing it was the wrong thing to do.
I've updated the documentation to explicitly call out the behavior and
added it back so that the behavior is consistent with previous versions.
Bug: 148988544
Test: atest CtsUsageStatsTestCases:UsageStatsTest
Test: atest AppIdleHistoryTests
Test: atest AppStandbyControllerTests
Change-Id: If5cad80b693a1e043ae64b8206e28abb60f83853
1. Technically there can be multiple notifications enqueued which
haven't posted yet. Check the entire set of them instead of just the
first.
2. If there is a posted notification that showed up _after_ the request
to cancel, then cancel the cancel (don't cancel is what I'm saying)
Bug: 147420515
Test: atest NotificationManagerServiceTest
Change-Id: I0f401eb3cc6b8c15fb34593f7afc3293daed0726
