alogcat is not reading logs- blank output

[GoogleCodeExporter]

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

Original issue reported on code.google.com by erk...@gmail.com on 8 Mar 2011 at 8:43

[GoogleCodeExporter]

if you connect via usb debugging, and do "adb logcat", what do you see? my 
question is if logging is working at all, or if there's an issue w/ alogcat.

Original comment by jeffrey.blattman@gmail.com on 8 Mar 2011 at 9:22

[GoogleCodeExporter]

First there was error:
"Unable to open log device '/dev/log/main': No such file or directory"

After I create these folder ( :)  yeah I know, it is not normal but) I have:

" logcat read: Is a directory"

so what is the issue?

Original comment by erk...@gmail.com on 8 Mar 2011 at 9:49

[GoogleCodeExporter]

i'm not sure about the issue. /dev/log/* are not real files, they are
virtual devices, so creating the folder there was the wrong thing. if
/dev/log is empty and you don't see the devices, i'm not sure what to say.
it is not an issue w/ alogcat.

Original comment by jeffrey.blattman@gmail.com on 9 Mar 2011 at 2:48

[GoogleCodeExporter]

i'm not sure about the issue. /dev/log/* are not real files, they are virtual 
devices, so creating the folder there was the wrong thing. if /dev/log is empty 
and you don't see the devices, i'm not sure what to say. it is not an issue w/ 
alogcat.

Original comment by jeffrey.blattman@gmail.com on 9 Mar 2011 at 2:48

[GoogleCodeExporter]

FYI: 
This usually happens if you use speedmod-kernel (i.e. k13 on SGS) which has 
logging disabled by default. To change this you gotta simply enter Recovery, 
navigate to "Advanced Speedmod ULK features" and enter "TWEAK options". There 
you choose "Enable Android Logger" to make our beloved alogcat work again :)
BTW,thx for this very nice app!

Original comment by dev.pr...@googlemail.com on 17 Mar 2011 at 10:50

[GoogleCodeExporter]

Original comment by jeffrey.blattman@gmail.com on 19 Mar 2011 at 6:30

• Changed state: Invalid

[GoogleCodeExporter]

I am having the exact same issue and did the exact same process as comment 
no.2. After finding this issue report, I deleted the main folder I created and 
rebooted into stock recovery and I didn't see any advanced options. I then went 
into CWR and didn't see anything like what was mentioned in comment no.5. Does 
anyone know what I can do to get this working. I am using a Droid Bionic with 
the Th3ory ROM. I have updated to the latest Motorola Kernel.

Original comment by Calla...@gmail.com on 14 Nov 2011 at 6:22