king
/
v811_spc009
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b394c2d4e7'
${ noResults }
v811_spc009/frameworks/native/cmds/bugreportz
History
jianglk.darker 7ee447c011
v811_spc009_project 		4 months ago
..
.clang-format v811_spc009_project 4 months ago
Android.bp v811_spc009_project 4 months ago
AndroidTest.xml v811_spc009_project 4 months ago
OWNERS v811_spc009_project 4 months ago
bugreportz.cpp v811_spc009_project 4 months ago
bugreportz.h v811_spc009_project 4 months ago
bugreportz_test.cpp v811_spc009_project 4 months ago
main.cpp v811_spc009_project 4 months ago
readme.md v811_spc009_project 4 months ago

readme.md

bugreportz protocol

bugreportz is used to generate a zippped bugreport whose path is passed back to adb, using the simple protocol defined below.

Version 1.1

On version 1.1, in addition to the OK and FAILURE lines, when bugreportz is invoked with -p, it outputs the following lines:

  • BEGIN:<path_to_bugreport_file> right away.
  • PROGRESS:<progress>/<total> as dumpstate progresses (where <progress> is the current progress units out of a max of <total>).

Version 1.0

On version 1.0, bugreportz does not generate any output on stdout until the bugreport is finished, when it then prints one line with the result:

  • OK:<path_to_bugreport_file> in case of success.
  • FAIL:<error message> in case of failure.