View Single Post
Old 06-27-2011, 09:38 PM   #1
Logseman
じゃんぬねっ
Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.Logseman ought to be getting tired of karma fortunes by now.
 
Logseman's Avatar
 
Posts: 1,939
Karma: 1027561
Join Date: Feb 2010
Location: Tenerife
Device: bq Cervantes Touch Light
Helping developers: an introduction to Android debugging (Logcat)

The fact that Android is based on an open-source kernel and that it is an open ecosystem which allows running apps not only from its preferred market, but from alternative ones and even from simple executable files (.apk) implies that application development is more accessible than in other platforms. This implies that more amateur or small-time programmers will develop for Android, and this implies as well that they may not have the ressources for extensive testing. So this is a guide meant for users who want to help developers by debugging Android applications.

Mainly, we are going to cover three subjects: the installation of ADB (Android Debug Bridge), adding the folder where adb is located to your PATH variable in order to be able to run it in your terminal easily and the use of adb logcat. ADB (Android Debug Bridge) is, as its name states, the plaform which allows communication between the computer of a developer (or tester, as is our case) and the debugged device. What we want to do is to install it, then modify the PATH variable so that we only need to type "adb" for adb related commands anywhere we want, instead of having to access the folder where we installed ADB, and lastly a small guide on how to actually debug the applications. You'll notice that the deployment part is MUCH longer than the actual usage.
Logseman is offline   Reply With Quote