Code transformation tool and viewer for ProtoLog.
ProtoLogTool incorporates three different modes of operation:
Command: protologtool transform-protolog-calls --protolog-class <protolog class name> --loggroups-class <protolog groups class name> --loggroups-jar <config jar path> --viewer-config-file-path <protobuf viewer config file path> --legacy-viewer-config-file-path <legacy json.gz viewer config file path> --legacy-output-file-path <.winscope file path to write the legacy trace to> --output-srcjar <output.srcjar> [<input.java>]
In this mode ProtoLogTool transforms every ProtoLog logging call in form of:
ProtoLog.x(ProtoLogGroup.GROUP_NAME, "Format string %d %s", value1, value2);
into:
if (ProtoLogImpl.isEnabled(GROUP_NAME)) { int protoLogParam0 = value1; String protoLogParam1 = String.valueOf(value2); ProtoLogImpl.x(ProtoLogGroup.GROUP_NAME, 123456, 0b0100, "Format string %d %s or null", protoLogParam0, protoLogParam1); }
where ProtoLog, ProtoLogImpl and ProtoLogGroup are the classes provided as arguments (can be imported, static imported or full path, wildcard imports are not allowed) and, x is the logging method. The transformation is done on the source level. A hash is generated from the format string, log level and log group name and inserted after the ProtoLogGroup argument. After the hash we insert a bitmask specifying the types of logged parameters. The format string is replaced by null if ProtoLogGroup.GROUP_NAME.isLogToLogcat() returns false. If ProtoLogGroup.GROUP_NAME.isEnabled() returns false the log statement is removed entirely from the resultant code. The real generated code is inlined and a number of new line characters is added as to preserve line numbering in file.
Input is provided as a list of java source file names. Transformed source is saved to a single source jar file. The ProtoLogGroup class with all dependencies should be provided as a compiled jar file (config.jar).
Command: generate-viewer-config --protolog-class <protolog class name> --loggroups-class <protolog groups class name> --loggroups-jar <config jar path> --viewer-config-type <proto|json> --viewer-config <viewer.json> [<input.java>]
This command is similar in it's syntax to the previous one, only instead of creating a processed source jar it writes a viewer configuration file with following schema:
{ "version": "1.0.0", "messages": { "123456": { "message": "Format string %d %s", "level": "ERROR", "group": "GROUP_NAME", "at": "com\/android\/server\/example\/Class.java" } }, "groups": { "GROUP_NAME": { "tag": "TestLog" } } }
Command: read-log --viewer-config <viewer.json> <wm_log.pb>
Reads the binary ProtoLog log file and outputs a human-readable LogCat-like text log.
ProtoLog is a generic logging system created for the WindowManager project. It allows both binary and text logging and is tunable in runtime. It consists of 3 different submodules:
ProtoLog is designed to reduce both application size (and by that memory usage) and amount of resources needed for logging. This is achieved by replacing log message strings with their hashes and only loading to memory/writing full log messages when necessary.
For text-based logs Android LogCat is used as a backend. Message strings are loaded from a viewer config located on the device when needed.
Binary logs are saved as Protocol Buffers file. They can be read using the ProtoLog tool or specialised viewer like Winscope.
To add a new ProtoLogGroup simple create a new enum ProtoLogGroup member with desired parameters.
To add a new logging statement just add a new call to ProtoLog.x where x is a log level.
After doing any changes to logging groups or statements you should build the project and follow instructions printed by the tool.
Use the adb shell su root cmd window logging command. To get help just type adb shell su root cmd window logging help.