Tips

HOME > How to use it

Open in browser

By simply adding the --browser argument, chkbugreport will try to open the result in the default browser. You can make this the default behaviour by adding openBrowser=true to ~/.chkbugreport (create the file if needed)

Analyzing logs

You don't need to have a full bugreport to use this tool. You could download a logger application from the market, which will continuously save the system/main/event logs on the sdcard. This way you can get usage data from several hours.

When you want to process the logs, extract them from the sdcard and execute:

$ chkbugreport dummy --no-limit -sl:systemlog.txt -el:eventlog.txt

• The dummy argument is used only to generate an output filename
• The --no-limit tells chkbugreport to not trunkate the log files. By default chkbugreport trunkates log files bigger then 1MB, in order to avoid generating too huge reports (or running out of memory). Sometimes this is what you want as well, if the crash/exception is at the end of the log. However in this case we want to process the whole log file.
• The -sl:file argument will load the system/main log. If you have the main log in a separate file, you can load it with -ml:file
• The -el:file argument will load the event log

Of course the generated report will be much more limited, since a lot of information is missing (for example the name of processes), so chkbugreport tries to guess what it can. But even only from the logs many information can be extracted, for example the battery usage.