Easy Fix for Logcat Blues on Jelly Bean Ports
Jelly Bean seems to be on everyone’s mind, as of late. The latest and greatest to come out of Google’s sweet treat factory is ravaging the site with its popularity and feature-packed nature. As such, ports are flying left, right, and center onto most devices (old and new) on the site. However, as is the case with most new OS versions, there are also complications and issues that need to be overcome in order to make the best out of the new release.
One of the bugs (not really a bug per se) that has plagued a few devices, including the Motorola Defy, is the fact that logcat apps are blocked by the OS itself, as Google seems to have added an extra set of permissions that these apps do not normally need in order to function. This is particularly important for ROM devs and people who need to know exactly what went wrong and what triggered it.
XDA Forum Member rtk217 found a simple way of granting said permissions via terminal emulator. Needless to say, your device must be rooted to do this, since you will be requesting superuser permissions through the terminal. This is a permission issue, which means that if you use more than one application for logging purposes, you will need to repeat the process for every app. The system must grant the app the required permission to work.
Please take this for a spin and get your apps working again. After all, we all need to provide a logcat from time to time.
so as you may noticed catlog /logcat/ alogcat and such are not working properly or at all.
that is because google added a new permission request from programs which they dont usually request.
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer.
[Thanks WhammyDroid for the tip!]