Dear Jean-Baptiste Queru, Thank you for answer, however the problem is more complicated. In case of the application crash there framework or VM related exceptions' information, that I have no way to catch. In order to analyze what is the reason of the system crash I need this information, that's why I need the system log data to be available for me even if the device was turned off by the user after the application crash.
On Mar 2, 4:12 pm, Jean-Baptiste Queru <[email protected]> wrote: > How about writing your log data to your own file, probably somewhere > on the sd card? > > JBQ > > > > On Sun, Mar 1, 2009 at 6:11 AM,AGA<[email protected]> wrote: > > > Dear Group, > > The problem is still here... > > The "logcat -f" can give only partial solution. After the device is > > turned off, the "logcat -f" has to be > > executed again. If I need constantly enough log information from the > > system 64K is not enough. > > I've tried to execute "logcat -f" on start up - without success (just > > an empty file is created). > > I think this is a crucial issue for the application stability test to > > have the control over the log severity and size. Please help how I can > > get the log data !!!??? > > > Thanks in advance, > > AGA > > -- > Jean-Baptiste M. "JBQ" Queru > Android Engineer, Google. > > Questions sent directly to me are likely to get forwarded to a public > forum with no further warning. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
