You could try using Logcat from http://code.google.com/p/android-random/. If you patch it, using this patch I submitted: http://code.google.com/p/android-random/issues/detail?id=4 , you can filter it and save the logcat output to /sdcard (Useful when a crash occurs).
On May 5, 1:24 pm, mathias axelsson <mathias.axels...@gmail.com> wrote: > Log Collector was great (esp since end-users also can use it). Ill prob take > a look at creating a su replacement as well since I sometimes need to kill > an app on the road. > > Thanks! > > On Fri, May 1, 2009 at 1:32 PM, Carter <ccjerni...@gmail.com> wrote: > > > You could also use Log Collector, which is available on the Android > > Market. > > > On May 1, 1:26 pm, fadden <fad...@android.com> wrote: > > > On May 1, 8:06 am, mathias axelsson <mathias.axels...@gmail.com> > > > wrote: > > > > > When running 'su', in terminal, I get 'uid XXXXX not allowed to su'. > > > > 'logcat' gives permission denied /dev/log/main. > > > > To avoid creating a situation where an app could run "su" and do > > > dastardly deeds, an explicit userid check was added to "su". You need > > > to be in an adb shell. > > > > If this is inconvenient, you can create an unrestricted "su" > > > replacement. One approach is to make a copy of the shell and chmod/ > > > chown it to setuid root. This creates a security hole -- something > > > could scan your phone for setuid binaries and speculatively execute > > > them looking for root shells -- but it's no worse than the previous > > > "su" binary. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
