 Hello everyone. My name is Mr. Sandesh Pare. I am currently working as an assistant professor in the department of computer science and engineering at Walton Institute of Technology. In this video, I am going to explore the concept debugging of the Android application. So, at the end of this session, you will be able to define the landscape of the mobile app validation. So, let us start with the exploring of the tools which are used for the debugging of the Android applications. There are multiple tools available for the debugging purpose of the Android applications. And mainly in this session, we are going to focus on these five tools. The first one is the Android Studio Debugger. And the second one is the AD, that is called as the Android Device Monitor. Third one is the Android Debug Bridge. Fourth one Toast Message. And the last one is the Class Login Lock-At Utility. Mainly in this video, I am going to focus on these five tools, which are generally used for the debugging purpose. So, let us start by the first one that is the Android Studio Debugger. What happens that Android Studio, which generally makes available this debugger to the developer one in format of the emulators, or you can directly use your physical hardware device to debug this purpose. So, mainly emulator is used for the debugging purpose. And using this ID, you can say that Android Studio. Suppose we are considering we are using the Android Studio, then what can we do that first? We can select device to debug the app. Means on which device you want to debug this app. And the second one is there. You can see the logs. You can set the breakpoints to the execution of the programs. And at that time, whatever the executions are executed. And based on these, which are the values of the variables, which are changed during this execution, you can see it manually by step by step procedure using these breakpoints. So, you can run this debugging tool from the Android SDK, which is made available. And then you can take the snapshot of this, capture this snapshots and you can make the value of this. So, using this Android Studio debugger. In this, what happens? We have to build APK sign debug. And then we have to install it on the physically on the device. Or you can use the virtual emulators also. What happens that you have to first open that Android Studio. And there is one button called as the debug. And whenever you click that, it will ask for the device one that on which device it should host that application. Then you have to select the particular one. And then it will get executed on that device. So, the next tool is the Android device monitor. What happens that it is a standalone tool. It provides the GUI. For many Android applications, for debugging and analysis tools, just like one simulator, it is acting there. And it does not require any installation of the particular ID. Like as we discussed earlier that today we are executing. This is not necessary. So, you want only this simulator for the debugging purpose. And it generally has the tools like DDMS, TracerView, and HerachiViewer, Systress, TraceView, and PixelPerfect MagnificationViewer. These are some of the components which is embedded into this. Using these tools, generally these are called as the Android SDK tools. There are two types of tools. The standard SDK tools and platform tools. These are components of the Android SDK tools, which are generally used by the developer for many reasons. Then starting this Android device monitor is you have to just click on the Android device monitor tool icon from the menu one. Then you have to select the Android and then Android device monitor. And one more thing that if you have any problems, if you have any problems running this Android device monitor, you have to just need to take care of the updation process. You have to update your Android studio. Then as I said earlier that you have to take it. Add these tools and platform tools. Subdictionary is also there of the SDK to your path available. So, this is one overview. You can see there on the Android studio. There is one option there that is called the DDMS. You can click on the DDMS so that it should be open in the verbose mode. It is called as the verbose mode in which there is a device view on the left side, file explorer view. You can see the multiple files in the project. Then emulator control view is there to control the ongoing activities during the project execution. And the last one is the locket. That is the fourth one and which is at the bottom of the window. You can see there which are the application tag and test is performed there. You can attach the files also there. By this overview you can analyze and debug the project. So next one is the Android debug bridge. This is in short called as the ADB. And actually it is common line tool. Which is located in the platform tool dictionary. For this there are specific commands are there to perform the certain activities. That first one is the ADB shell to create any Linux shell. This command is generally used and after execution of this you can perform the operations like making a dictionary, running a file and installation of particular apps. Then there are multiple various commands for this purpose. And they are shown there just for making dictionary make there to push the file onto the device. Just like copy the file from the device that the command is there. We use keyboard. So there is one question for you guys that is what is DBA and what purpose it is used. So ADB is nothing but it provides the connection and communication with the device and emulators. Once it is connected developers can execute the commands which can be used to perform the activities like installation of apps, copying the files, reading and logs. Just as I said earlier. So next one is the toast messages. Toast message is nothing but one just message window. We can say it to window. It will just appear for a few seconds on the screen. And it does not let any activity. And toast examples are there. Just as a volume control. When you press the keys, hardware keys of the volume up and down. The certain message window is there which comes on the screen. But it does not hamper any execution of the ongoing activity. So when the view is shown to the user, it appears on the top of the screen. Generally one function is there to creation the for the app toast message. That format is nothing but the toast make toast make text. In that it generally requires the three parameters one. First one is the context. In what context you want to display it. And the second one is the resource ID. And the third one is the duration. Generally what happens that context always is this parameter is used. Means in that function only it is toast messages displayed. And second one is that you can use particular resources just like strings. You can use it and edit text. So whatever their information is there it is displayed on the toast message. Otherwise you can pass it manually the message whatever you want to show. And third one is the duration. Means for what time it should be displayed. So there is one example which is shown there. And that gravity is set there to make it middleware. Gravity.center is the parameter. And at the last sentence you can say that according to the x offset and y offset the midpoint is selected so that it should be center of the screen. And next one is the log class. Log class is generally used to log messages while running the application. Means whatever the activities are going on to it it is logged and shown to the user one. Generally there are a lot of many types of the logs are there. We have a look on that. That is the error message, warning message, informational message, and debugging message, verbose mode message. And what a terrible failure message. So for this kind of the logs if you want to display this kind of mainly these are the some categories of the logs. And if you want to display any message regarding this category then you have to use that functions. And generally it is used mainly two parameters that first one is the tag one. Whatever tag you want to assign to that message. And second one is the message. Tag parameter is used to indicate one category from which it belongs to. So that and it can be filtered also. So third parameter is also there. As we can see the tag and string message whatever there and third parameter is the throwable parameter. But it is not compulsory to use this parameter. And the lock cat utility is the same as I said earlier that it is just severity level by the tag and you can filter the messages according to the tags whatever assigned to it. You can access it by on clicking the Android icon there. And whatever the tools we are discussed that is the debugger, ADB and Android device monitor they can use this lock cat utility. So these are some references I used to make this video. Thank you.