Arunkarthicknallasami / alogcat

Automatically exported from code.google.com/p/alogcat
1 stars 0 forks source link

Not tracking all logs. #32

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Does not track logs which show the beginning of an Intent (or) logs whose 
tag is "ActivityManager" and whose message fiels start with "Starting activity"
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by vij...@gmail.com on 11 Aug 2011 at 2:38

GoogleCodeExporter commented 8 years ago
please provide detailed steps on how to reproduce.

Original comment by jeffrey.blattman@gmail.com on 11 Aug 2011 at 4:51

GoogleCodeExporter commented 8 years ago
Whenever you start a new activity, you see a log which looks like this in the 
ADB Logcat,

08-10 16:02:48.875: INFO/ActivityManager(114): Starting activity: Intent { 
cmp=com.google.android.gm/.HtmlConversationActivity (has extras) }

These logs which have a tag of "ActivityManager" and their message field starts 
with text "Starting activity"(which basically signifies the beginning of an 
intent) do not show up in the list shown by the application.

Original comment by vij...@gmail.com on 11 Aug 2011 at 5:38

GoogleCodeExporter commented 8 years ago
I was noticing this bug too in how I wanted to use this app. The issue seems to 
be with setting the buffer flag sent to logcat. For some reason, logcat does 
not display the "Starting activity..." messages in either the main, radio, or 
events buffer. However, if you take out this flag completely, then it shows up 
in the logs. 

The current build doesn't let you do this though. Attached are some quick 
changes to make this happen. You'll need to select "None" under the 
"Preferences->Buffer" after the change and compiling this (I didn't make it the 
default).

Original comment by May...@gmail.com on 5 Sep 2011 at 2:01

Attachments:

GoogleCodeExporter commented 8 years ago
in stead of adding a "none" option, would it be simpler to just modify the code 
to not send the buffer argument if it's the default buffer (main)?

thanks for your help.

Original comment by jeffrey.blattman@gmail.com on 7 Sep 2011 at 4:07

GoogleCodeExporter commented 8 years ago
I hadn't looked into the logcat buffers much until the other day, but I think 
you're right that it's probably simpler to just leave out the buffer argument 
if "main" is selected. It should be the default buffer, not sure why the 
argument would cause the "Starting activity" messages to be dropped, but that's 
the only difference I saw between sending the argument for main or leaving it 
out completely.

Original comment by May...@gmail.com on 7 Sep 2011 at 5:08

GoogleCodeExporter commented 8 years ago
fixed in 2.4.

Original comment by jeffrey.blattman@gmail.com on 29 Dec 2011 at 3:43