There are two extended ways to get access to Logcat, through Android Studio or through command line. That is why firstly we need an Android OS running in an emulator or a physical device. How can I access Logcat?Īs we said, Logcat is an Android developing tool to see logs. To achieve this, the starting point would be to know how to see logs and how to interpret them. In a crash case, or if an action is not working, it might be interesting to get access to logs in order to understand when the program stopped and get a general idea of what might be causing it. Those logs are important in order to understand root causes for OS malfunction.Īlso, app’s logs are really interesting if you are developing an app from scratch or trying to understand how a third party app works or why it fails. In turn, they are split in different classes which we will talk about in detail in the “ Logs structure in Logcat” section. These logs provide details about executions in inner layers of the operating system. We can distinguish between several kinds of logs depending on their origin.įirst, we will talk about logs related to the Android OS internal events.

In this post we will focus on Logcat, which is an Android developing tool to show those log messages. Logs are messages that show events occurring in an operating system or other software sources such as apps.

Where is android studio logcat