h1. Getting logs

When some component misbehaves or stops working on Replicant, it is recommended to:
# Get logs showing the issue
# Open a ticket on our tracker to report the issue (*New issue* tab)

h2. Buffers

The Android logging subsystem uses different log buffers: @events@, @main@, @radio@ and @system@.
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.

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.

There are various ways to obtain the logs:

h2. Using ADB

First, you need to [[ToolsInstallation#ADB|install ADB]].

h3. Retrieving a buffer from the Android logging subsystem

Display a buffer from the Android logging subsystem:

<pre>
adb logcat -b [BUFFER]
</pre>

To prepare a new issue report, you need to save the output to a file:

<pre>
adb logcat -b [BUFFER] -d > path/to/file
</pre>

Attach the file to the issue report.

h3. Retrieving the kernel message buffer

Display the kernel message buffer:

<pre>
adb shell dmesg
</pre>

To prepare a new issue report, you need to save the output to a file:

<pre>
adb shell dmesg > path/to/file
</pre>

Attach the file to the issue report.

h2. Using aLogcat

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.
You can set the desired buffer from the @Preferences@.

After saving the log, you can get it from a file stored in the @alogcat@ folder on the root of storage.