bdliang / alogcat

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

Will not work on Android 4.1 Jelly Beans #41

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
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.

Original issue reported on code.google.com by domschuermann@gmail.com on 19 Jul 2012 at 5:46

GoogleCodeExporter commented 8 years ago
thanks. i guess we will see if a future version of android provides a way for 
users to manually allow this.

Original comment by jeffrey.blattman@gmail.com on 1 Aug 2012 at 10:12

GoogleCodeExporter commented 8 years ago
I used titanium backup to change to a system app and that seems to fix the 
problem. 

Original comment by mattbr...@gmail.com on 30 Aug 2012 at 5:45

GoogleCodeExporter commented 8 years ago
I followed the tip to use Titanium Backup and changed it to a system app. That 
also fixed the issue for me. Bummer I had to do this, but at least it works 
now! 

Original comment by sean.ait...@gmail.com on 3 Jun 2013 at 5:07

GoogleCodeExporter commented 8 years ago
You could do as in that app and request Root permissions for aLogCat: 
https://github.com/dschuermann/faster-gps/blob/master/FasterGPS/src/main/Android
Manifest.xml#L22

Original comment by azr...@googlemail.com on 25 Jul 2013 at 6:40

GoogleCodeExporter commented 8 years ago
You also have to use execute a Shell with su instead of the default sh. See 
https://github.com/nolanlawson/Catlog for a working logcat implementation with 
superuser access.

Original comment by domschuermann@gmail.com on 26 Jul 2013 at 8:04