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 scrolls, displaying the information that
has already been accumulated before you typed the command.
I suggest starting with one of those apps, since it would be just so
easy for you and your user to take first step.
+1 to what John Coryat is saying.
I actually do this in my app, have my own logging facility, controlled
by a simple boolean static variable. This way it's easy to make a custom
build for those users who are having problems.
-- Kostya
30.08.2010 17:48, tony obrien пишет:
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, Kostya Vasilyev<kmans...@gmail.com> wrote:
30.08.2010 16:48, tony obrien пишет:> I am loathe to start adding all kinds of
"log output" turning this
into a bloatware science experiment (but will if forced.)
Before you start doing that, I'd ask the user to download and install
one of the many applications that can display logcat output, run it, and
email the log to you.
You might see something interesting that's worth fixing.
--
Kostya Vasilyev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com
--
Kostya Vasilyev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
