logcat not displayed in jelly bean 4.1.1

[GoogleCodeExporter]

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

Original issue reported on code.google.com by lionello...@gmail.com on 22 Aug 2012 at 10:11

[GoogleCodeExporter]

if you have a solution i can apply to the app, please post it.

Original comment by jeffrey.blattman@gmail.com on 22 Aug 2012 at 10:44

[GoogleCodeExporter]

I personally do not know the solution but by googling around I've found
this link
http://code.google.com/p/acra/issues/detail?id=137

That refers to this official issue
http://code.google.com/p/android/issues/detail?id=34792

I hope that this helps,
Lionhe
Il giorno 23/ago/2012 00:44, <alogcat@googlecode.com> ha scritto:

Original comment by lionello...@gmail.com on 22 Aug 2012 at 11:07

[GoogleCodeExporter]

at the very least, moving to system/app allows alogcat to function in jb. so if 
no other workaround can be found, it'll just need to become a root application.

Original comment by chris.re...@live.com on 26 Aug 2012 at 3:17

[GoogleCodeExporter]

there's no solution in that thread. it notes that the app is able to get it's 
own logs, but that doesn't help with alogcat because the only reason for 
alogcat is to get the logs of other apps.

Original comment by jeffrey.blattman@gmail.com on 27 Aug 2012 at 10:51

[GoogleCodeExporter]

This thread seemed to help BetterBatteryStats dev chamonix with pulling logcats:

http://stackoverflow.com/questions/10648593/android-asynctask-process-logcat-doe
s-not-output-messages-on-emulator

Original comment by chris.re...@live.com on 2 Sep 2012 at 4:21

[GoogleCodeExporter]

After doing some reading and some testing, I've found three ways to make 
aLogcat work, all of which use root.

1. I haven't seen the source code, so I don't know how you're getting the 
logging info in the first place. However, supposing you're doing something 
equivalent to "exec alogcat", you can change it to "exec su -c 'alogcat'". I've 
tested this from the command line (it was the basis of my previous email) but 
of course I haven't tested it in your actual app.

2. Run a shell command to grant permission. I tested this from a shell on the 
phone (not via adb but directly on the phone). The following command works:
    su -c 'pm grant org.jtb.alogcat android.permission.READ_LOGS'
What's more, it only has to be run once, which makes it feasible to do it as a 
one-time setup step.

3. Use Titanium Backup or something similar to convert aLogcat to a system app. 
It seems that system apps have no trouble getting the requisite permission.

Of the options, it seems that option 2 would be a good choice to implement on 
Jelly Bean rooted phones. There might not be a good solution for non-root 
users, but root does indeed make it possible for aLogcat to function correctly.

By the way, here's the source that tipped me off: 
https://groups.google.com/forum/m/?fromgroups#!topic/android-developers/6U4A5irW
ang

Original comment by scott.se...@gmail.com on 3 Oct 2012 at 8:30

[GoogleCodeExporter]

And for all of us who support the developer...

su -c 'pm grant org.jtb.alogcat.donate android.permission.READ_LOGS'

Please remember to tip your devs!

Original comment by Scott3...@gmail.com on 30 Jul 2013 at 10:26