GettingLogs » History » Version 5
Wolfgang Wiedmeyer, 03/06/2017 05:57 PM
add helpful command to save log to a file
1 | 4 | Paul Kocialkowski | h1. Getting logs |
---|---|---|---|
2 | 1 | Paul Kocialkowski | |
3 | When some component misbehaves or stops working on Replicant, it is recommended to: |
||
4 | # Get logs showing the issue |
||
5 | # Open a ticket on our tracker to report the issue (*New issue* tab) |
||
6 | |||
7 | 4 | Paul Kocialkowski | h2. Buffers |
8 | 1 | Paul Kocialkowski | |
9 | The Android logging subsystem uses different log buffers: @events@, @main@, @radio@ and @system@. |
||
10 | Generally speaking, when the issue you encountered concerned telephony, including data (3G), the buffer you want is @radio@. In any other case, that's the @main@ buffer you want. |
||
11 | |||
12 | There are various ways to obtain logs: |
||
13 | |||
14 | 4 | Paul Kocialkowski | h2. Using ADB |
15 | 3 | Paul Kocialkowski | |
16 | 4 | Paul Kocialkowski | After [[ToolsInstallation#ADB|installing ADB]], use it this way: |
17 | 5 | Wolfgang Wiedmeyer | |
18 | 3 | Paul Kocialkowski | <pre> |
19 | 1 | Paul Kocialkowski | adb logcat -b [BUFFER] |
20 | </pre> |
||
21 | 5 | Wolfgang Wiedmeyer | |
22 | To prepare a new issue report, you need to save the output to a file: |
||
23 | |||
24 | <pre> |
||
25 | adb logcat -b [BUFFER] -d > path/to/file |
||
26 | </pre> |
||
27 | |||
28 | Attach the file to the issue report. |
||
29 | 1 | Paul Kocialkowski | |
30 | 4 | Paul Kocialkowski | h2. Using aLogcat |
31 | 1 | Paul Kocialkowski | |
32 | aLogcat is a (free) Android app that will collect logs and save them to a file, either regularly or when you press the *Save* button from the app menu. |
||
33 | You can set the desired buffer from the @Preferences@. |
||
34 | |||
35 | After saving the log, you can get it from a file stored in the @alogcat@ folder on the root of storage. |