GettingLogs » History » Version 6
Wolfgang Wiedmeyer, 03/06/2017 06:20 PM
add instructions to retrieve dmesg
| 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 | 6 | Wolfgang Wiedmeyer | In some cases, the information provided by the Android log buffers is not sufficient and the message buffer of the Linux kernel is additionally required for investigating the issue. |
| 13 | 1 | Paul Kocialkowski | |
| 14 | 6 | Wolfgang Wiedmeyer | There are various ways to obtain the logs: |
| 15 | |||
| 16 | 1 | Paul Kocialkowski | h2. Using ADB |
| 17 | 3 | Paul Kocialkowski | |
| 18 | 6 | Wolfgang Wiedmeyer | First, you need to [[ToolsInstallation#ADB|install ADB]]. |
| 19 | 1 | Paul Kocialkowski | |
| 20 | 6 | Wolfgang Wiedmeyer | h3. Retrieving a buffer from the Android logging subsystem |
| 21 | |||
| 22 | Display a buffer from the Android logging subsystem: |
||
| 23 | |||
| 24 | 3 | Paul Kocialkowski | <pre> |
| 25 | 1 | Paul Kocialkowski | adb logcat -b [BUFFER] |
| 26 | 5 | Wolfgang Wiedmeyer | </pre> |
| 27 | |||
| 28 | To prepare a new issue report, you need to save the output to a file: |
||
| 29 | |||
| 30 | <pre> |
||
| 31 | 1 | Paul Kocialkowski | adb logcat -b [BUFFER] -d > path/to/file |
| 32 | </pre> |
||
| 33 | |||
| 34 | 6 | Wolfgang Wiedmeyer | Attach the file to the issue report. |
| 35 | |||
| 36 | h3. Retrieving the kernel message buffer |
||
| 37 | |||
| 38 | Display the kernel message buffer: |
||
| 39 | |||
| 40 | <pre> |
||
| 41 | adb shell dmesg |
||
| 42 | </pre> |
||
| 43 | |||
| 44 | To prepare a new issue report, you need to save the output to a file: |
||
| 45 | |||
| 46 | <pre> |
||
| 47 | adb shell dmesg > path/to/file |
||
| 48 | </pre> |
||
| 49 | |||
| 50 | Attach the file to the issue report. |
||
| 51 | 1 | Paul Kocialkowski | |
| 52 | 4 | Paul Kocialkowski | h2. Using aLogcat |
| 53 | 1 | Paul Kocialkowski | |
| 54 | 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. |
||
| 55 | You can set the desired buffer from the @Preferences@. |
||
| 56 | |||
| 57 | After saving the log, you can get it from a file stored in the @alogcat@ folder on the root of storage. |