summaryrefslogtreecommitdiff
path: root/core/java/android/util/DumpableContainer.java
Commit message (Collapse)AuthorAgeFilesLines
* Improves DumpableContainer javadoc.Felipe Leme2022-02-221-2/+1
| | | | | | | Test: n/a Fixes: 220889663 Change-Id: I0d2fbd623d00ca44b5b2a84b7c6cc3b89edd4d63
* New API: DumpableContainer.removeDumpable.Felipe Leme2022-02-071-0/+11
| | | | | | | | | | | Test: m update-api Test: atest com.android.internal.util.DumpableContainerImplTest Bug: 149254050 Bug: 217567642 CTS-Coverage-Bug: 149254050 Change-Id: I4efe99a545bd3db2308d0956eaa85e0f799f0f1d
* Creates a generic mechanism to dump app-side information.Felipe Leme2022-01-131-0/+40
Currently, 'dumpsys activity' can dump the state of some managers: - AutofillManager - ContentCapturemaanger - UiTranslationController But the support for these custom dumping is hardcoded into Activity itself, which makes it harder to extend. For example, automotive builds provide an app-side Car object, which currently cannot be dumped. This CL makes the mechanism more flexible by providing a couple new public / SystemAPIs that let Automotive (or other mainline modules) extend it. Examples: $ adb shell dumpsys activity com.android.car.carlauncher/.CarLauncher --list-dumpables $ adb shell dumpsys activity com.android.car.carlauncher/.CarLauncher --dump-dumpable CarUserManager $ adb shell dumpsys activity service com.android.systemui/.SystemUIService CarUserManager NOTE: this CL only adds the new APIs; a follow-up CL will change the existing managers to use them. Test: see above Test: m update-api Bug: 149254050 CTS-Coverage-Bug: 149254050 Change-Id: I6920ff3542d3d75edd667c2c7658e9d0a7af534f