GettingLogs » History » Version 3
Paul Kocialkowski, 02/22/2014 10:40 AM
1 | 1 | Paul Kocialkowski | h1. Getting Logs |
---|---|---|---|
2 | |||
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 | h2. Obtaining logs |
||
8 | |||
9 | h3. Buffers |
||
10 | |||
11 | The Android logging subsystem uses different log buffers: @events@, @main@, @radio@ and @system@. |
||
12 | 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. |
||
13 | |||
14 | There are various ways to obtain logs: |
||
15 | |||
16 | h3. Using adb |
||
17 | |||
18 | 3 | Paul Kocialkowski | Instructions to install ADB: [[ToolsInstallation#ADB|ToolsInstallation]] |
19 | 1 | Paul Kocialkowski | |
20 | 3 | Paul Kocialkowski | Now use adb this way: |
21 | 1 | Paul Kocialkowski | <pre> |
22 | adb logcat -b [BUFFER] |
||
23 | </pre> |
||
24 | Save the output to a file and attach it to the new issue report. |
||
25 | |||
26 | h3. Using aLogcat |
||
27 | |||
28 | 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. |
||
29 | You can set the desired buffer from the @Preferences@. |
||
30 | |||
31 | After saving the log, you can get it from a file stored in the @alogcat@ folder on the root of storage. |