Project

General

Profile

GettingLogs » History » Version 2

Paul Kocialkowski, 09/06/2012 03:45 PM

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
Start by installing adb:
19 2 Paul Kocialkowski
* Using the (i386) prebuilt binary from the [[ReplicantImages|latest image]]. It is located in the *tools/* directory, from the *Base URL*. Download it and make sure it's executable (with @chmod a+x adb@).
20 1 Paul Kocialkowski
* Building your own, with the sources from: @git://git.paulk.fr/adb-autotools.git@
21
22
Now use adb like:
23
<pre>
24
adb logcat -b [BUFFER]
25
</pre>
26
Save the output to a file and attach it to the new issue report. 
27
28
h3. Using aLogcat
29
30
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.
31
You can set the desired buffer from the @Preferences@.
32
33
After saving the log, you can get it from a file stored in the @alogcat@ folder on the root of storage.