How to capture a log with adb logcat

From dmfswiki
Revision as of 11:41, 2 January 2016 by Yannic (Talk | contribs) (Created page with "Usually a full sync log is sufficient to find out what's wrong when the synchronisation fails. However, in some cases a full *system* log is necessary to track down the origin...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Usually a full sync log is sufficient to find out what's wrong when the synchronisation fails. However, in some cases a full *system* log is necessary to track down the original cause. If the device is rooted "CatLog" is the weapon of choice. If it's not we need to resort to a tool called 'adb logcat'.

Note that you need to have a Linux machine or Mac for this.

1.) Download or install the Android-SDK (http://developer.android.com/sdk/index.html#Other). If you're using Ubuntu you can also run "sudo apt-get install android-tools-adb".

2.) Connect your smartphone via USB to your machine

3.) Run "adb logcat > logfile" in the commandline. Note: this overwrites "logfile" if it already exists.

4.) Reproduce the original issue e.g. by starting a synchronisation on your smartphone.

5.) Afterwards kill adb by pressing the combination "Ctrl + c" in the commandline window.

6.) Forward the file "logfile" to us.

Retrieved from "https://dmfs.org/wiki/index.php?title=How_to_capture_a_log_with_adb_logcat&oldid=1360"