Hi, It can really be anything. Modded Rom, bad implementation by a few manufacturer of some of the apis.
As Treking told you, in those case your best bet is to use your uncaught exception mecanism to send yourself internal logs that you generate for yourself. Not only the stacktrace but a detailed log of whats happening in your app and that you can customise. Store every action your user does, everything your app does in an Array. Using a "16:29:12 Before action X", "16:29:15 During action X", "16:30 After action x" protocol. And when your app crashes, send this array in your report. You'll then see the chronology of events and maybe you'll catch the culprit that kills your app. My two cents : Most "not in my code" bugs are generated on objects creation (eg. AudioBuffer audioB = new AudioBuffer(); ). So be sure to put a log line just before and a log line just after any of those. Long and tedious...Yes...Efficient...Yes :D Yahel -- 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
