Where should I begin the hunt for the cause of crashes / reboots when logging apps do not work anymore?

  • 1
    Do you mean logcat? – minicookie Mar 19 '13 at 0:10
  • yes, for example... – Jens Piegsa Mar 19 '13 at 7:10
  • Maybe you should find out why it doesn't work! ^^ – minicookie Mar 19 '13 at 8:21
  • 1
    This I have already found out. For privacy reasons, applications may no longer read each others log files. – Jens Piegsa Mar 19 '13 at 13:26

As can be seen in this video from the Google I/O conference, in Jelly Bean applications can no longer read the system log for other applications, they can only read their own log. This has broken most (all?) system log readers, here's a blog post from a developer of such an application talking about how it has affected his application.

The only way to have an app read other apps system log entries when using Jelly Bean is to root the phone.

Although other apps can't read the log files it is apparently possible to do it from the PC, try giving LogShark a go.

  • Root is not necessary. I have created a utility to collect logs: gist.github.com/hrj/5983971 – HRJ Jul 16 '13 at 18:37
  • @HRJ That looks good, I'll add it into my answer. I do say "only way to have other apps" so the answer isn't incorrect but again, good work. – Peanut Jul 16 '13 at 18:57

The easiest most simple way that will give you definitive results is to remove all apps and install them one at a time until you install one that starts your problem.

If you just installed an app recently and think it may be questionable, uninstall it and see if your problem is gone. This in all honesty is a lengthy process.

  • 1
    The question asks about logging apps in general suggesting it's not one application causing the OP a problem. – Peanut Mar 28 '13 at 12:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.