Some time ago, we covered a quick tutorial aimed at helping users learn how to generate a logcat. We’ve also covered a few tools that help you easily come up with output from this all important diagnostic tool. However, most of the material we have covered in the past has been geared at providing you with information that you would then send over to your favorite developer when something isn’t working right.
What if instead you learned how to read the output so that you could better diagnose your own issues? This is exactly what XDA Forum Moderator Stryke_the_Orc wants to help you accomplish with his guide. Though not an overly complicated task, spotting errors in a logcat output is often harder than it sounds.
The guide (naturally) begins by showing you how to obtain a logcat on Windows and Linux/Mac. There are, once again, quite a few tools, guides, and ways to do this. However, Stryke_the_Ork covers how to do it manually using the Android SDK\Platform Tools folder. He even shows you how to obtain a logcat during a bootloop situation. Once you already have your logcat handy, the guide shows you how to filter your logcat by application so that you only see what you want to see.
To make a little more sense out of the output from this handy tool, head over to the guide thread._________
Want something on the XDA Portal? Send us a tip! -- Join us for xda:devcon 2014!