novhy / alogcat Goto Github PK

user request black background. could be simple toggle between black and white 
backgrounds. i 
noticed that the blue (debug) text is a little dark on a black background.

Being able to toggle case sensitivity would be helpful.

What steps will reproduce the problem?
1. Launch alogcat
2. Press the "Menu Key" button on the phone (the label is 4 horizontal lines).
3. Note the menu options come up, and the below error gets logged.

What is the expected output? What do you see instead?
Error is logged, I don't think it should be. Note the error only happens the 
first time the menu is opened each time the app is launched.
W/KeyCharacterMap( 2831): Can't open keycharmap file
W/KeyCharacterMap( 2831): Error loading keycharmap file 
'/system/usr/keychars/qtouch-touchscreen.kcm.bin'. 
hw.keyboards.65538.devname='qtouch-touchscreen'
W/KeyCharacterMap( 2831): Using default keymap: 
/system/usr/keychars/qwerty.kcm.bin


What version of the product are you using? On what operating system?
2.1.6 on Motorola Droid OS v2.2.1

Please provide any additional information below.

What steps will reproduce the problem?
1. Start aLogcat
2. Exit aLogcat (eg. by pressing Back button)
3. Check with "adb shell ps" for running 'logcat' processes


What is the expected output? What do you see instead?
No logcat process started by aLogcat should be running.


What version of the product are you using? On what operating system?
1.3.4 on a HTC Hero (Android 1.5)

Please provide any additional information below.
As I understand aLogcat starts 'logcat' processes on the phone, to obtain
the log messages. 

For a clean shutdown it should either:
--------------------------------------
- kill the created processes itself (maybe in onPause() or on click to a
dedicated exit button?)

- or take care that the Android kernel's internal lowmemory killer can kill
the processes by setting the oom_adj value of the process accordingly (as
per default the processes get an oom_adj value of 0 which is the same as
FOREGROUND_APP so the lowmemory killer never will kill these processes.


For both options you need to know the PID of the spawn child processes.
It's possible to retrieve iT on Android by using reflection:


// start child process
java.lang.Process process = Runtime.getRuntime().exec( ... );

// try to get PID of child logcat process (for later killing)
int childPid = -1;
if (android.os.Process.supportsProcesses() &&
process.getClass().getName().equals("java.lang.ProcessManager$ProcessImpl")) {
  try {
    Field f = process.getClass().getDeclaredField("id");
    f.setAccessible(true);
    childPid = f.getInt(process);
  } catch (Throwable e) {
    childPid = -1;
  }
}

log filter input always caps the first word. this is because we changed the 
android:inputType to "textCaps*". this limits the input to a single line which 
was another issue, but we should probably use one of the other input types, 
like "text".  need to test though if this limits to single line as expected.

What steps will reproduce the problem?
1. open filter settings
2. input "line1" <return> "line2"

What is the expected output? What do you see instead?
The filter settings text input only shows the last line of text. And visually 
it looks like only a single line of text can be entered (i.e. no line break 
character). Please either don't accept line break as input or use a control 
which looks like a multi line input. The current implementation does not match 
common user experience.

What version of the product are you using? On what operating system?
alogcat 1.4
Android 2.1
HTC Legend

Hi, Sir:

Currently, alogcat only supports one type of Buffer, such as main, events or 
radio? Is it possible to log those buffers at the same time. From my 
experience, sometimes it is helpful for some developers.

Thanks,

Jungo

It would be nice to add logging to a SD card in the background.
Every minute or so app could append new log entries to some file on sd,
which would make logs permanent and allow debugging long time after
something happened

What steps will reproduce the problem?
1.open alogcat
2.wait logs 

==>>>   nothing shows-no log is showing


Expected to see any log. But output remains empty. Chainging filters or other 
options does not help.

last alogcat free from market on Froyo 2.2.1

What steps will reproduce the problem?
1. can't save all logs for 10 hours.
2.
3.

What is the expected output? What do you see instead?
xxx.2010.10.08.10:30_1.log
xxx.2010.10.08.10:35_1.log
xxx.2010.10.08.10:40_1.log
xxx
xx
x

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

Please provide any additional information below.

no reason to do this. it is not a blocking call. calling in a thread leaves 
open the possibility that the subsequent start thread is executed first, 
resulting in us immediately stopping the new Logcat we just started.

What steps will reproduce the problem?
1. Press Menu -> Save
2. The message about file creation appears.
3. The log record:
java.io.IOException: Parent directory of file is not writable: /sdcard/alogcat
appears.
4. No file is created.

What is the expected output? What do you see instead?
The file should be created. No error messages in logs should appear.

What version of the product are you using? On what operating system?
aLogcat v.1.5.1 on Android 2.1 on HTC Hero.

Please provide any additional information below.
I suppose the AndroidManifest.xml contains some wrong information:

1. You changed the minSdkVersion from 3 to 4 in the r18.
The correct tag should be:
<uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4"/>

2. Since SDK version 4 you should add a permission to write to SD card. Please 
add:
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

What steps will reproduce the problem?
1. Open aLogcat, scroll up to where problem is.
2. Loss place as app scrolls down, remove auto scroll in settings.
3. Get tired while scrolling down from top.

What would be nice is a menu option to go to bottom.
Also a setting to scroll to bottom on start (perhaps default, or perhaps not 
even a setting. I don't know a use case for people to look at the oldest 
messages first)


What version of the product are you using? On what operating system?
2.1.4 on Cyanogen Nightly 11082010.

Please provide any additional information below.
Would you mind providing commit log messages in subversion? It would make it 
eaiser to understand the work that has been done as well as relate revisions 
and release versions.

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

Please provide any additional information below.

Request for enhancement:
Add support for "-v threadtime" formatting

request from user is to increase log buffer size, to capture events that happen 
further in the past. 

alogcat has a static number of events it will display. i think this is 
necessary for performance. if it is set to display all log events in the 
buffer, this could be arbitrarily large and bring the app to a grinding halt.

therefore, i think the best solution is the following ... 

first, when alogcat sends or saves a log, it should capture all log events in 
the buffer, not just the ones being displayed. actually, allowing this for send 
might be questionable. will have to see how it performs.

second, allow the user to set the log file size. this can be done by invoking 
logcat with the -r, -n, and -f options. it should probably give some fixed 
values to keep the user from setting something arbitrarily large. perhaps 16, 
64, 256, and 1024k. 

with this, although the user won't be allows to view an arbitrarily large log, 
they can send it in email (maybe), or dump it to the SD card.

implementation wise this is pretty simple. we need to add a size option to the 
menu, and modify the implementation of send and save to exec logcat and capture 
the output instead of looking at the events being displayed.

optionally format the email as HTML. this would allow it to be color-coded as 
in the log viewer, adding to readability.

mime type for send email is set as "plain/text". it should be "text/plain". 
this is causing some mail clients to crash.

Current filter option appears to be a simple text box that's either blank 
(disabled) or filled out with filter criteria. I'd like to have the option to 
add several filters and enable/disable each without having to delete them.

I have added some "Slog.v or Slog.i" lines in the android source code. These 
modifications can be seen in another log app, but alogcat did not display my 
added information.

Are there any items I should pay attention to?

I am using CyanogenMod 6.2, nexous one.

What steps will reproduce the problem?
1. Start aLogCat & Wait for logs to be read
2. "Pause" log
3. Screen goes dark while I'm reading
4. sweep screen or/and unlock
5. aLogCat restarted capturing and i need to pause/scroll up again

What is the expected output? What do you see instead?
aLogCat stays paused

What version of the product are you using? On what operating system?
aLogCat 2.1.4, Samsung Galaxy S I9000, Android 2.2 / Doc Froyo 7.6.2

Currently the filter only permits a single substring search.

There have been multiple occasions where I have wanted to filter on multiple 
items.

I'm not certain how this might be best implemented. Either as multiple filters 
or a defined separator character such as a pipe. Adding separator character 
style would be a quick hack. 

I really like this App. Clean and simple interface. 

I like the auto-scroll feature as well, but often I scroll upwards in the list 
of entries, just to check something out. And when I forget to "pause" the 
playback first, it jacks me down to the bottom again when new entries arrive. 

It got a bit frustrating, so I download the source code and made the following 
changes:

private void cat(String s) {
   ...
   mLogEntryAdapter.add(entry);
   if (mPrefs.isAutoScroll() && isAtBottomOfLog()) {
      mLogList.post(new Runnable() {
         public void run() {
            mLogList.setSelection(mLogEntryAdapter.getCount() - 1);
         }
      });
}

private boolean isAtBottomOfLog() {
   // Add one to getLastVisiblePosition to account 
   // for the new entry just added and not yet scrolled
   return mLogList.getLastVisiblePosition() == -1 ||
     mLogList.getLastVisiblePosition() +1 == mLogList.getCount() -1; 
}

Now it only auto-scrolls if I'm already at the bottom of the list.

Your welcome to use the the above as you see fit, or to disregard it. Thanks 
for a great tool.

/Nicolai

The Top/Bottom items in the option menu are very useful, but it takes a lot of 
clicks to access them.

I downloaded the code an added the menu items to the context menu also, i.e. 
the menu that appear when you long-click the ListView. The menu items are bit 
more accessible from there, I think.

To get it to work, I added android:longClickable="true" to the entry.xml, 
registered an OnCreateContextMenuListener on the ListView in the onResume() 
method and unregistered it in the onPause() method.

Again, thanks for a great App.

/Nicolai

It would be great to have an option to submit the alogcat output to a 
pastebin site!