Name |
Date |
Size |
#Lines |
LOC |
||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| .clang-format | D | 14-Jan-2024 | 288 | 14 | 12 | |
| Android.bp | D | 14-Jan-2024 | 948 | 54 | 44 | |
| AndroidTest.xml | D | 14-Jan-2024 | 1.2 KiB | 27 | 12 | |
| OWNERS | D | 15-Dec-2024 | 72 | 6 | 4 | |
| bugreportz.cpp | D | 14-Jan-2024 | 3.2 KiB | 99 | 66 | |
| bugreportz.h | D | 14-Jan-2024 | 1 KiB | 27 | 5 | |
| bugreportz_test.cpp | D | 14-Jan-2024 | 4 KiB | 129 | 81 | |
| main.cpp | D | 14-Jan-2024 | 3.7 KiB | 128 | 86 | |
| readme.md | D | 14-Jan-2024 | 748 | 21 | 14 |
readme.md
1# bugreportz protocol 2 3`bugreportz` is used to generate a zipped bugreport whose path is passed back to `adb`, using 4the simple protocol defined below. 5 6# Version 1.1 7On version 1.1, in addition to the `OK` and `FAILURE` lines, when `bugreportz` is invoked with 8`-p`, it outputs the following lines: 9 10- `BEGIN:<path_to_bugreport_file>` right away. 11- `PROGRESS:<progress>/<total>` as `dumpstate` progresses (where `<progress>` is the current 12progress units out of a max of `<total>`). 13 14## Version 1.0 15On version 1.0, `bugreportz` does not generate any output on `stdout` until the bugreport is 16finished, when it then prints one line with the result: 17 18- `OK:<path_to_bugreport_file>` in case of success. 19- `FAIL:<error message>` in case of failure. 20 21