Replicant

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.

There are various ways to obtain logs:

h2. Using ADB

After [[ToolsInstallation#ADB|installing ADB]], use it this way:

<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. 

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.