brendankirby / alogcat Goto Github PK

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

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.

What steps will reproduce the problem?
1. It doesn't seem possible for another app to start alogcat and instruct it to 
filter based on criteria the app specifies

What is the expected output? What do you see instead?
It would be nice if alogcat could be started with an Intent that would 
communicate the filter

I am using Samsung galaxy 3 (I5801). I am not able to play any media file. When 
I try t play .mp3 files, I get the following error "Sorry, the player does not 
support this type of file." 
I have attached the logcat for reference. Also my youtube & video player is not 
working.

My phone is rooted but I am using the stock rom build number FROYO.DDJP4

Please help me

Regards
Vishal Bibra

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

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

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

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.

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.

READ_LOGS permission on Jelly Beans (Android 4.1) will not be granted anymore 
to normal apps.

Apps are only allow to read their own logs.

See for more information 
https://groups.google.com/group/android-developers/browse_thread/thread/e94e00e6
2ad66a78

You could try to implement a function to grant yourself READ_LOGS permission 
with for users with rooted devices.

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

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

Many times I get quirky behavior from my Defy with CM7, and when weird stuff 
happens I go to alogcat and save the log, vowing to look at it later.  

Well, I've got 53 logs on my SD card now, and I have no idea what the weird 
behavior was or why I saved it.

It would be great to allow the user to enter a really quick summary of what was 
going on, that could be placed at the beginning of the file.  Because people 
perhaps parse these logs with other tools, maybe the entry itself could obey 
the same rules as other log entries:

03-13 16:31:01.063 I/aLogCat(xxxx): Here is the user comment regarding this log 
file.

The comment would ideally be the first line in the log.

I planned to work on this sometime in the future, let me know what you think.

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

Can you please let me know how to keep this app running even in standby or 
sleep mode? I want to check what is still running even in standby mode. Am 
getting only 24hours battery in stand-by mode.

Thanks a lot in advance,

What steps will reproduce the problem?
0. Write an app *without* the READ_LOGS permission
1. Have the app send a 'start logging' intent to aLogCat
2. Have the app send a 'save to the sdcard' intent to aLogCat
3. Have the app read the log from the sdcard

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

The expected result if you don't have permission to read logs is that you 
shouldn't be able to read the logs.  Instead, it appears you're able to read 
the logs by getting aLogCat to read them for you and then leave them where they 
can be read by anyone.

Please provide any additional information below.

This is not the first bug of this kind found.  See 
http://arstechnica.com/tech-policy/news/2011/11/researchers-find-big-leaks-in-pr
e-installed-android-apps.ars for similar security holes.

Potential solutions:
  i) Have an option to turn on and off those intent receivers in aLogCat.
  ii) Have a new permission required to send those intents.  Better still, require the app sending the intents to have the READ_LOGS permission to send the intents - that way you don't have to worry about dealing with new permissions.  See http://developer.android.com/guide/topics/security/security.html#manifest
  iii) An option that combines i) and ii): Have an option in aLogCat that allows you to specify who can send the events.  Anyone, apps with log viewing permissions, or no-one.  This is more complex than ii), or even i) and ii) together, as it requires turning on and off the required permissions programatically with Context.registerReceiver() rather than just adding a line to manifest as option ii) would.

Please consider adding an option to keep the screen on / prevent the device 
from going into standby.

I might be missing something, but it makes sense for me that the device keeps 
running while you are looking at the log output.

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

Being able to toggle case sensitivity would be helpful.

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

While alogcat uses only 488KB of internal memory, it would be nice to have it 
movable to the SD card.

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

alogcat is 2.6.1

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;
  }
}

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.

Please consider providing a way of donating that doesn't require me installing 
proprietary software (i.e. the Google Market) on my phone.

What steps will reproduce the problem
1. start the application
2.the logcat window is almost empty
3.

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

the usual logcat output is expected

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

jelly bean 4.1.1 jelly belly 1.0.0
Please provide any additional information below.
This bug has been solved in the library acra on August 16th
it concerns all applications that display the logcat

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

What steps will reproduce the problem?
1. Start aLogcat
2. Wait for some log messages to appear
3. Scroll

What is the expected output? What do you see instead?
I do see the expected output.
But aLogcat also shows a lot of these logs:

11-22 10:53:49.232: DEBUG/dalvikvm(353): GC_EXTERNAL_ALLOC freed 39K, 56% free 
2708K/6151K, external 3584K/3600K, paused 39ms

This makes it hard to follow the other logs.

What version of the product are you using? On what operating system?
aLogcat v2.3.2
Android v2.3.3
Desire/AndroidEmulator

Please provide any additional information below.

What steps will reproduce the problem?
1.Enable hourly auto-log
2.Log something
3.Watch the timestamps in the logs written. Some lines, already appearing in a 
previous log, are replicated in the next

What is the expected output? What do you see instead?
No replication, next log should start with the next line following the line 
written in the previous log

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

Please provide any additional information below.

What steps will reproduce the problem?
1. Start aLogcat.
2. Save the log.
3. Browse phone storage over ADB.

What is the expected output? What do you see instead?
I would expect the new log file in the aLogcat folder, but it is missing. If I 
trigger a media scan (using Android's Developer Tools) and refresh the folder 
on the computer, the new log is there.

What version of the product are you using? On what operating system?
Version 2.6.1 (downloaded from F-Droid), on Cyanogenmod 11.0m11.

Please provide any additional information below.
This only affects MTP devices. My old Nexus S (which exposed its file system as 
USB mass storage) did not have this issue. I reported this as a bug in 
Cyanogenmod and was told that apps are expected to call 
MediaScannerConnection#scanFile 
http://developer.android.com/reference/android/media/MediaScannerConnection.html
#scanFile(java.lang.String, java.lang.String) after creating a new file. 
Apparently aLogcat is not doing this.

What steps will reproduce the problem?
1.connect USB to another computer
2.alogcat <menu> <save> (to file)


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

Files are not saved due to sdcard being unavailable.  
However alogcat behavior is oblivious, even reporting name of nonexistent file.
User should be made aware that save can't complete.


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

Downloaded yesterday; Droid X running stock 2.2.1 (never rooted)

Please provide any additional information below.

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.

I'd like to suggest that the search button be used as a shortcut for 
menu>filter.

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"/>

some (many) strings are not localizable. [email protected] has 
requested this be fixed so the app may be localized to hebrew.

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.

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.

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.

Hi, not an issue but I couldn't find anywhere else to make suggestions.
A widget would be a really useful addition to this app.
Cheers, thanks for your work.

As the title suggests...

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.

Sometimes I forget that I have a filter loaded, so I would like the Toast 
notification to show the filter contents if there are any.  I've created and 
tested a patch to do this, I'm attaching it.

Maybe the same sort of method could be used to change the application title 
from aLogcat to "aLogcat [filter contents]"

Thanks for this indispensable app.

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

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. 

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.

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