Hi, Thank you for the reply.
We are taking apples and oranges. Kostya is a developer who reported an issue to the Android development team. He gave them a detailed stack trace and copy of his app. The exception was then analyzed by a professional development support team. As an aside, it doesn't look like the Android development team is done analyzing Kostya's issue. Nathan, your "issue" is based on reports from "end users". My conjecture is, there is a substantive difference between "end user" reporting and developer to developer reporting. A test/development team provides detail precise measurements. Are you end user reports, detailed and precise? (that's not how you indicated their reports in the original post). You don't know for certain whether it's an application defect, an OS defect , a hardware defect. That's OK :). My point is, you are speculating :) When a developer says "my application is error free and needs no code review', I'm not taking that bet :) Nothing personal, but we would not have things like unit testing, test groups, bug reporting systems, debuggers, etc. , etc., if most application releases are "error free and no need for code review" :) My final recommendation is, it's unlikely your code has no defects. Thus, before assuming there is an error in the OS, hardware, application language etc, I would post a little bit more about your application. For example, does it connect anything that might block? Again, thanks for the reply. I not going to speculate further on code that I haven't reviewed :) Good Luck :) Waving good bye :) Jason On Monday, January 7, 2013 5:21:55 PM UTC-6, Nathan wrote: > > > > On Monday, January 7, 2013 1:52:12 PM UTC-8, jason_gates wrote: >> >> Hi, >> >> No problem :) >> >> >> 1) Collection of an event log. I'm quoting the original post: >> >> >> "I have very little to go on in these reports. After a full reboot, there >> is little chance the logcat still has useful information. Since 4.1, we >> can't use any external programs to collect the log. I aim for prevention >> instead.". >> >> >> Thus, persist your own log. Your own application can write out a simple >> text file and later (after the reboot) read it. >> > > It could help, but I am having doubts that: > -There was any useful information in the log prior to the reboot either. > -That information was put there by my own code (not system messages). I'm > guessing system messages are more likely to be helpful. > -I know what log statements to put in there to make it useful - I'd have > to have some inkling of what the problem is. That's kind of why I posted > this thread. Hoping some of you would would have some idea of what *could* > cause a hard freeze. > An unhandled exception is unlikely based on the review jason suggested. > A respected person has already commented to the effect that my app > *can't* cause a system freeze without some underlying system issue. Which > is of little comfort to a user who does experience said freeze. > > But it might help. > > >> 2) If the issue is related to a vendor's key map, wouldn't that key map >> effect all applications on the device? Not just the poster's application? >> > Yes, it might. But your app will be probably blamed anyway. It's > perfectly possible for a device to have an issue that a particular user can > only reproduce in your app. > > >> To summarize, the original post describes a the challenge of identifying >> an issue. Where does it state the issue known to occur when key >> combinations are invoked? >> > I have no evidence it does or does not relate to key combinations. I can't > reproduce it, after all. Any suggestion is helpful at this point. The HTC > Droid Incredible "reboot if you update a notification" didn't ever make > sense and still doesn't. > > | Wouldn't that just a be an issue of reporting a bug to a vendor? > > Admire the optimism, though not sure about the "just" part. > > Nathan > > Nathan > > -- 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
