| /frameworks/native/cmds/dumpsys/ |
| D | Android.bp | 10 "dumpsys.cpp",
42 name: "dumpsys",
53 stem: "dumpsys",
|
| D | main.cpp | 40 Dumpsys dumpsys(sm.get()); in main() local
41 return dumpsys.main(argc, argv); in main()
|
| D | TEST_MAPPING | 4 // small test which assumes the output format of dumpsys, however
|
| /frameworks/base/tests/JankBench/scripts/ |
| D | adbutil.py | 23 def dumpsys(serial, topic): function
33 output = dumpsys(serial, "power")
|
| /frameworks/base/core/proto/ |
| D | README.md | 8 1. If the proto describes the top level output of dumpsys, it should contain
9 `Dump`. This makes it easy to understand that the proto is the dumpsys output
|
| /frameworks/base/core/proto/android/service/ |
| D | batterystats.proto | 26 // Dump of batterystats aggregate data (dumpsys batterystats --proto).
33 // Dump of batterystats history data (dumpsys batterystats --proto --history).
|
| D | runtime.proto | 25 // Represents dumpsys info from RuntimeService.
|
| D | netstats.proto | 25 // Represents dumpsys from NetworkStatsService (netstats).
|
| D | package.proto | 129 // From "dumpsys package" - name of package which installed this one.
|
| /frameworks/native/cmds/dumpsys/tests/ |
| D | Android.bp | 1 // Build the unit tests for dumpsys
|
| /frameworks/base/tests/backup/ |
| D | test_backup.sh | 22 b_pkgs=$(a shell dumpsys backup | \
|
| /frameworks/base/core/tests/coretests/src/com/android/internal/os/ |
| D | BatteryStatsUserLifecycleTests.java | 123 final String dumpsys = executeShellCommand("dumpsys batterystats --checkin"); in getNumberOfUidsInBatteryStats() local
124 for (String line : dumpsys.split("\n")) { in getNumberOfUidsInBatteryStats()
|
| /frameworks/native/cmds/dumpstate/ |
| D | bugreport-format.md | 50 - Some dumpsys sections (memory and cpuinfo) are reported earlier in the file.
74 - Two additional dumpsys sections are generated. The two new sections can be
97 **1.0-dev1**. When `dumpsys` was split in 2 sections but not all tools were
99 which had to be passed to `dumpsys` explicitly (by setting the `dumpstate.version` system property).
|
| D | dumpstate.cpp | 1091 Dumpsys dumpsys(sm.get()); in RunDumpsysTextByPriority() local
1094 Vector<String16> services = dumpsys.listServices(priority, /* supports_proto = */ false); in RunDumpsysTextByPriority()
1100 status_t status = dumpsys.startDumpThread(Dumpsys::Type::DUMP, service, args); in RunDumpsysTextByPriority()
1102 dumpsys.writeDumpHeader(STDOUT_FILENO, service, priority); in RunDumpsysTextByPriority()
1104 status = dumpsys.writeDump(STDOUT_FILENO, service, service_timeout, in RunDumpsysTextByPriority()
1106 dumpsys.writeDumpFooter(STDOUT_FILENO, service, elapsed_seconds); in RunDumpsysTextByPriority()
1108 dumpsys.stopDumpThread(dump_complete); in RunDumpsysTextByPriority()
1155 Dumpsys dumpsys(sm.get()); in RunDumpsysProto() local
1161 Vector<String16> services = dumpsys.listServices(priority, /* supports_proto = */ true); in RunDumpsysProto()
1172 status_t status = dumpsys.startDumpThread(Dumpsys::Type::DUMP, service, args); in RunDumpsysProto()
[all …]
|
| D | README.md | 86 adb shell setprop dumpstate.version split-dumpsys && adb shell dumpstate -v
|
| /frameworks/base/cmds/statsd/tools/loadtest/ |
| D | run_loadtest.sh | 32 get_mem=$(adb shell dumpsys meminfo |grep statsd)
|
| /frameworks/native/ |
| D | PREUPLOAD.cfg | 28 …sys_hook = ${REPO_ROOT}/frameworks/base/tools/aosp/aosp_sha.sh ${PREUPLOAD_COMMIT} "^cmds/dumpsys/"
|
| /frameworks/base/core/proto/android/os/ |
| D | statsdata.proto | 24 // Dump of statsd report data (dumpsys stats --proto).
|
| D | incident.proto | 149 // 2. the same information is able to be accessed by meminfo dumpsys.
|
| /frameworks/base/core/proto/android/ |
| D | section.proto | 38 // incidentd calls dumpsys for annotated field
|
| /frameworks/opt/net/wifi/service/proto/src/ |
| D | scorecard.proto | 34 // the access points of a network together in dumpsys output or similar.
|
| /frameworks/base/services/tests/servicestests/src/com/android/server/pm/ |
| D | ShortcutManagerTest7.java | 358 String dump = dumpsys(args); in checkDumpsysArgs()
|
| D | BaseShortcutManagerTest.java | 1332 for (String line : dumpsys("-u").split("\n")) { in dumpsysOnLogcat()
1338 return dumpsys("--checkin"); in dumpCheckin()
1341 protected String dumpsys(String... args) { in dumpsys() method in BaseShortcutManagerTest
|
| /frameworks/base/core/proto/android/server/ |
| D | activitymanagerservice.proto | 53 // "dumpsys activity --proto activities"
145 // "dumpsys activity --proto broadcasts"
434 // "dumpsys activity --proto service"
623 // TODO: "dumpsys activity --proto processes"
|
| /frameworks/native/services/surfaceflinger/sysprop/ |
| D | SurfaceFlingerProperties.sysprop | 31 # automated testing using dumpsys gfxinfo [2] are recommended), they should not
|