Useful tip for collecting Logcat files

[Guest pellonet]

Apologies for cross posting this here, but this was originally the intended location on the basis that a lot of the 'ROM addicts' may come straight here & don't bother with the parent section. :D

This useful tip from 'reinhardholzner' at the 'Theft Aware' support forum for an easy way to collect logcat files

- go to Android Market

- search for aLogcat

- download and install the app

- start aLogcat from the app menu -> aLogcat will start gathering the log messages

- now use the HOME button to go back to the phone interface (do NOT use the BACK key as this will CLOSE aLogcat, HOME just puts it to the back)

- use the method or scenario to simulate your issue then

- once the unwanted behaviour occured long-press the HOME key

- select aLogcat app

- press the MENU key

May have been mentioned in the past but with all these exciting new ROMs appearing, accurate feedback is becoming crucial.

[Guest targetbsp]

I use that. :D

You'll likely want to change the options to include the timestamp. I don't have my phone with me so I can't see what exactly that option is called.

[Guest t0mm13b]

I use that. :D

You'll likely want to change the options to include the timestamp. I don't have my phone with me so I can't see what exactly that option is called.

Even easier - this is for linux only, plug in the handset cable into blade,

adb logcat -c # clears the log

then

adb logcat -v time > some_log.log

Then you can ctrl+C when done. It's more instant as, then, from another terminal I can view the some_log with multitail and scroll backwards, or grep it out to get at the proper pid of the application currently debugged, and the log stripped of excess noise as shown below

cat some_log.log | grep "(nnnn)" | grep -v "ViewRoot" | grep -v "I/ActivityThread" > new_some_log.log

then when done I clear it again. You can also make the log bigger by doing it this way (this step is handy if you use Eclipse and trying to watch the log and see only a portion of it then it rolls over), again, from Linux terminal, with cable plugged into blade

adb -r 1048576 -n 6 -v time

That sets the log size to 1Mb, rotate it once the limit is reached, (wraps around) 6 times, with displaying time/date of logged messages.

You need to do this once... adb logcat on the device will remember it :D

adb logcat --help

Usage: logcat [options] [filterspecs]

options include:

-s Set default filter to silent.

Like specifying filterspec '*:s'

-f <filename> Log to file. Default to stdout

-r [<kbytes>] Rotate log every kbytes. (16 if unspecified). Requires -f

-n <count> Sets max number of rotated logs to <count>, default 4

-v <format> Sets the log print format, where <format> is one of:

brief process tag thread raw time threadtime long

-c clear (flush) the entire log and exit

-d dump the log and then exit (don't block)

-t <count> print only the most recent <count> lines (implies -d)

-g get the size of the log's ring buffer and exit

-b <buffer> request alternate ring buffer

('main' (default), 'radio', 'events')

-B output the log in binary

filterspecs are a series of

<tag>[:priority]

where <tag> is a log component tag (or * for all) and priority is:

V Verbose

D Debug

I Info

W Warn

E Error

F Fatal

S Silent (supress all output)

'*' means '*:(' and <tag> by itself means <tag>:v

If not specified on the commandline, filterspec is set from ANDROID_LOG_TAGS.

If no filterspec is found, filter defaults to '*:I'

If not specified with -v, format is set from ANDROID_PRINTF_LOG

or defaults to "brief"

My 2cents :o

[Guest shadowninty]

In terminal;

logcat

Exit terminal and do what you need to do

su su

/data/logcat.txt

logcat >/data/logcat.txt

Seems to work and no need for PC

[Guest targetbsp]

Call me lazy, but I still favour clicking on an app icon, the end, as detailed in the first post personally. :D