aLogcat market barcode
There are several “log view” applications on the market. All of them provide a means to send your log file contents, typically via email. This is one good approach, but it doesn’t handle the use case where you don’t have immediate access to a PC email client to view the results. aLogcat is an Android application that allows you to view your Android device log from the device itself. It provides a scrolling, color-coded log that is filterable by keyword and log level. It also supports output in various log formats. aLogcat also covers the send log use case by allowing a snapshot of the log to be sent off to another device.
This is mainly an app for developers, but it is also useful for power users that are willing to get involved with developers to help them find problems in their applications. Most Android developers are small scale hobbyists and can’t devote full-time effort and money to rigorous testing across multiple devices. I hope this app lowers the barrier for involvement of the average user in the development cycle.
aLogcat
Zero Credibility 
Stopped working after playing with it for a bit, caught this stacktrace:
DALVIK THREADS:
“main” prio=5 tid=3 RUNNABLE
| group=”main” sCount=1 dsCount=0 s=Y obj=0x4001e250 self=0xbc48
| sysTid=5790 nice=0 sched=0/0 cgrp=default handle=-1344001236
at android.app.ApplicationContext.getResources(ApplicationContext.java:~225)
at android.content.ContextWrapper.getResources(ContextWrapper.java:80)
at android.view.View.(View.java:1773)
at android.view.View.(View.java:1817)
at android.widget.TextView.(TextView.java:326)
at android.widget.TextView.(TextView.java:320)
at android.widget.TextView.(TextView.java:315)
at org.jtb.alogcat.LogActivity.cat(LogActivity.java:102)
at org.jtb.alogcat.LogActivity.access$0(LogActivity.java:97)
at org.jtb.alogcat.LogActivity$1.handleMessage(LogActivity.java:81)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4203)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
at dalvik.system.NativeStart.main(Native Method)
“Binder Thread #3″ prio=5 tid=19 NATIVE
| group=”main” sCount=1 dsCount=0 s=N obj=0x43b2af18 self=0x2a2cf8
| sysTid=5801 nice=0 sched=0/0 cgrp=default handle=2952336
at dalvik.system.NativeStart.run(Native Method)
“java.lang.ProcessManager” daemon prio=5 tid=17 NATIVE
| group=”main” sCount=1 dsCount=0 s=N obj=0x43a439e8 self=0x10e928
| sysTid=5798 nice=0 sched=0/0 cgrp=default handle=1108560
at java.lang.ProcessManager.watchChildren(Native Method)
at java.lang.ProcessManager$1.run(ProcessManager.java:87)
“Thread-9″ prio=5 tid=15 VMWAIT
| group=”main” sCount=1 dsCount=0 s=N obj=0x43a46258 self=0x2a1190
| sysTid=5797 nice=0 sched=0/0 cgrp=default handle=2753584
at android.os.Message.obtain(Message.java:~90)
at android.os.Message.obtain(Message.java:150)
at org.jtb.alogcat.Logcat.cat(Logcat.java:105)
at org.jtb.alogcat.Logcat.start(Logcat.java:68)
at org.jtb.alogcat.LogActivity$3.run(LogActivity.java:152)
at java.lang.Thread.run(Thread.java:1096)
Right, it doesn’t crash or so, just uses 100% cpu seemingly forever and is unusable. Says “Reading log data”, but gui never wakes up again.
how long did it run before you have this problem? how can i reproduce?
Joe,
I new to Android and am having problems downloading the alogcat through the Market on an HTC Hero phone.
Any suggestions would be appreciated.
The download seems to hang. I’ve stopped and restarted but it’s taking longer than an hour each time.
sorry, i don’t have any good suggestions. there are a lot of reasons why your download might not be going through … poor network connection, out of memory of your phone … aLogcat is hosted no differently that any other app, so i can assure you it’s not specific. i would suggest you perhaps visit forums for your phone and see what you can find.
Is it safe to send the log file to a developer? Couldn’t there be personal info in there?
there is nothing to prevent a developer of an arbitrary app from writing personal info to the log. that being said, as a rule developers should and do not do that. i have never seen personal info written by any application.
Does anybody know which type of video recordsdata are supported? I bear in mind the Instinct only may dl 3gp utilizing opera mini. I downloaded the twist ap, possibly that is the issue? How can I watch movies from sites other than youtube? Which file varieties? Often I’m given the choice of 3gp or mpeg4. Cannot get either to work. Thank you for your time! Rattling I wish I used to be eligible for the upgrade to EVO!
MIME-type of the SEND Intent is incorrect. It is “plain/text” instead of “text/plain”.
At least my application (http://www.appbrain.com/app/ru.gelin.android.sendtosd) crashes.
The intent is sent by Send menu command.
there is no such mime type “plain/text”.
the format of a mime type is /. “plain” is not a type. refer to this page for details,
http://en.wikipedia.org/wiki/MIME
interested to understand your problem though.
This is what I say. “plain/text” is not a correct MIME-type.
But when you choose Menu -> Send in the aLogcat, the Intent is sent. The Intent action is SEND. The Intent EXTRA_TEXT contains the log. But the Intent type is “plain/text”. Yes “plain/text” instead of “text/plain”. And this is the error.
sorry. i misunderstood. i filed a bug, and hope to get to it soon,
http://code.google.com/p/alogcat/issues/detail?id=10
Ok. Thank you.
Oh! The aLogcat is “googlecoded”! If I knew it, I would create an issue directly in googlecode. Could you please set the home page in Market description directly to http://code.google.com/p/alogcat/ ?