I am familiar with using LOGCAT via my local TERMINAL Session.. But
you are suggesting that LOGCAT runs on the Device and can be
accessed?
Do I need to enable Logging in my app?
Will the LOGCAT show *all* activities from everything that's running
(i.e. not just MY app) ?
On Aug 30, 9:33 am,
So LOGCAT operate on the device as well??
Do I need to ENABLE anything in my app?
Does the LOGCAT have all of the device's activities in it, including
those NOT from my app?
Does the device automagically wrap the logcat (it can't grow
forever) ?
On Aug 30, 9:33 am, Kostya Vasilyev
30.08.2010 18:44, tony obrien пишет:
So LOGCAT operate on the device as well??
Do I need to ENABLE anything in my app?
Does the LOGCAT have all of the device's activities in it, including
those NOT from my app?
Logcat doesn't have to be specifically enabled. It does show info from
every
A good log app is called (strangely enough) Sendlog - it's fairly
lightweight and just asks the user to enter an e-mail address. Select
detailed logs for the best result.
As for adding logging statements all over the place. That's a very
good idea with one caveat. Add a logging variable like
Yes, Logcat appears to run independently of adb or your local
debugging connection, and has logcat output from *all* applications that
use Android log.* methods and the Android system itself.
Note that if you start logcat from the console of your development
machine (adb logcat) it first
Logcat just dumps the logs that are constantly generated on the
device.
Do I need to enable Logging in my app?
If you want to follow program logic that doesn't involve blowing up,
then most likely, yes.
Will the LOGCAT show *all* activities from everything that's running
(i.e. not just MY
6 matches
Mail list logo
