Project

General

Profile

GettingLogs » History » Version 4

Paul Kocialkowski, 06/30/2015 09:44 PM

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 3 Paul Kocialkowski
<pre>
18 1 Paul Kocialkowski
adb logcat -b [BUFFER]
19
</pre>
20
Save the output to a file and attach it to the new issue report. 
21
22 4 Paul Kocialkowski
h2. Using aLogcat
23 1 Paul Kocialkowski
24
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.
25
You can set the desired buffer from the @Preferences@.
26
27
After saving the log, you can get it from a file stored in the @alogcat@ folder on the root of storage.