Added adb section to troubleshooting doc

inclement · inclement · commit 418f14f928ea · 2015-07-16T00:38:39.000+01:00
diff --git a/doc/source/troubleshooting.rst b/doc/source/troubleshooting.rst
@@ -16,6 +16,28 @@ If you find a bug, you can also post an issue on the
 `python-for-android Github page
 <https://github.com/kivy/python-for-android>`_.
 
+Debugging on Android
+--------------------
+
+When a python-for-android APK doesn't work, often the only indication
+that you get is that it closes. It is important to be able to find out
+what went wrong.
+
+python-for-android redirects Python's stdout and stderr to the Android
+logcat stream. You can see this by enabling developer mode on your
+Android device, enabling adb on the device, connecting it to your PC
+(you should see a notification that USB debugging is connected) and
+running ``adb logcat``. If adb is not in your PATH, you can find it at
+``/path/to/Android/SDK/platform-tools/adb``.
+
+Running this command gives a lot of information about what Android is
+doing. You can usually see important lines by using logcat's built in
+functionality to see only lines with the ``python`` tag (or just
+grepping this).
+
+When your app crashes, you'll see the normal Python traceback here, as
+well as the output of any print statements etc. that your app
+runs. Use these to diagnose the problem just as normal.
 
 Common errors
 -------------
