Hi, I have 2 suggestions :) First, I would review my code and make sure I've implemented try/catch/finally. You get inconsistent results if your application is not handling exceptions :) E.G. an attempt to use a value. Explicitly validate the value is not null. Place the block within a try/catch (and finally if apropos).
Next, I would consider implementing my own event log. Is there some reason why you are restricted to "Logcat"? Wouldn't writing out your own event log help you diagnose your issue? Hope that helps :) Good Luck Jason On Monday, January 7, 2013 12:52:59 PM UTC-6, Nathan wrote: > > Well, lo and behold, I have a Galaxy Nexus right next to me that is > completely frozen this very minute. > > I thought reproducing a hard freeze on a device available to me would be a > huge breakthrough. But no, nothing. The debugger detached without telling > me anything. The logcat gives out with no useful clues. The device is just > here frozen until I pull out the battery after which all evidence will be > destroyed. > > No Force Close dialog came up at anytime. No evidence in the log that one > was trying. > > Now this device has done some weird things lately. Like saying it is > charging when not connected to anything. And the battery got hot and ran > out too quickly for no apparent reason. > > Nathan > -- 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
