android - Reading ActivityManager-logs on a Jelly Bean device? -
jelly bean has removed ability read logs of other apps (according this i/o talk), sensible security improvement. however, need read activitymanager
-logs app work (to see app starting). this, using
private static final string clearlogcat = "logcat -c"; private static final string logcatcommand = "logcat activitymanager:i *:s"; //...
which no longer works, can read own application's logs in jelly bean. there alternative solution finding out when app starting (apart root)? understand why shouldn't able read other applications' logs (kind of - should other developers' resposibility make sure no personal information logged, not mine being prevented reading log), don't understand why activitymanager
, framework class, included in policy...
thanks,
nick
there extensive discussion of issue going on here. unfortunately, it's "expected behavior" , such won't fixed. current solution (for reading logs within application on jb , above) manually grant permission app through adb:
adb shell pm grant <pkg> android.permission.read_logs
a such-granted permission:
- survives reboots
- survives application updates (i.e. "adb install -r")
- does not survive if application uninstalled , installed again
it's obvious isn't normal user can expected do. gui-solution (where users can grant permission settings
menu of device) promised android team, unfortunately functionality removed before "fix" implemented.
Comments
Post a Comment