By supporting multiple filters per one request we should be able to cover
multiple kinds of use cases such as:
- Letting the user select from a list of devices of more then one medium
type (e.g. Bluetooth and BLE)
- Allowing to provide multiple criteria for any field (e.g. filtering by
more than one service UUID)
Bug: 30932767
Test: Provide multiple filters and ensure that devices matching either are
shown in the list to choose from.
Ensure wifi SSIDs are shown in the list if wifi filter is provided
Change-Id: I6621da388e2bf4ed97c5af2692629a321d0b63c7
But only when targeting O; if they're old apps then log and pass
a soft failure message to their callback.
Test: builds, boots
Bug: 35749102
Change-Id: I6c6b5a37c23669e7b1ed3c30207bca610821eb1f
Over the last month we've been moving everyone over to the new
StorageStatsManager public APIs, but we missed these users.
The ApplicationsState changes are straightforward, but we had to
completely rewrite StorageMeasurement to use the new fast-path
quota APIs.
Test: builds, boots, UI using StorageMeasurement works.
Bug: 36056120
Change-Id: If02177c95bf8c96ae4eceac4d631a168f99bef84
- fs_mgr reports fs_stat int value during bootup when mounting
an ext4 partition.
- This includes information like:
if previous shutdown was clean
if e2fsck has fixed any fs issue
if any mounting or quota related operations has failed.
- Each information is set as flag. Flag definitions are avaiable from
FsStatFlags in system/core/fs_mgr/fs_mgr.cpp
- log ro.boottime.init.mount_all.[early|default|late] which represent
time duration for each mount stage. Depending on device's config, some of
these stages may not exist. So do not log if value is 0, which means not existing.
bug: 32246772
bug: 35949600
bug: 35329915
Test: manual, check log after boot-up.
Change-Id: I4ceca88776119d88d5352d6793be122e82688279
Some names can include commas, and if they're not surrounded by quotes,
then CSV parsing breaks, as was the case in
https://github.com/google/battery-historian/issues/94#issuecomment-282790498
and several other circumstances.
Test: flashed local device and ran batterystats output through Historian
Change-Id: I070c5d873d9f79996a581bf0a5f664136c0af454
- When a PiP activity calls moveTaskToBack(), we should fall through to
the same behaviour as dismissing the PiP if there are no other tasks
to show.
Bug: 36034065
Test: android.server.cts.ActivityManagerPinnedStackTests
Test: #testMovePipToBackWithNoFullscreenStack
Test: #testMovePipToBackWithVisibleFullscreenStack
Test: #testMovePipToBackWithHiddenFullscreenStack
Change-Id: I83c3d27dabc031546f9f1cf20b808bb8f13d4646
Signed-off-by: Winson Chung <winsonc@google.com>
