@Mark Thanks for the hint about the MOTODEV forum. That seems worthwhile even though my poor test user has already downloaded and run more than 20 versions in helping me isolating offending code. I hope one additional barebones test won't push him over the edge. Who knows when I need him again.
@Prakash I spent some time on the DroidX forums and at there are many posts about random reboots even with the stock firmware. Small developers can't continue chasing issues that may come down to faulty firmware. My time is better spent getting ready for Android 3.0. But the Moto guys could do the same thing I did since it is all open source (google maps may not be open source, I forgot). But this debugging is a pain. Take 30,000 lines of code (in my case), make an educated guess as to which parts may be responsible, and strip them out (leaving 22,000 in my case). Then the app worked. Then I built 5 test versions, each of them putting an additional 2000 lines of code back in. My user reported at which point it crashed and the I built 5 new versions between the last non-crashing and the crashing version. However, we were fairly lucky in that it all seemed to work. Stuff like this rarely comes down to a null-pointer or something similar but are often due to some side-effects that only occur in certain conditions like low memory. So this type of debugging I just outlined is not necessarily consistent and the results may even be misleading. We got lucky. Of course, Moto has access to parts of the device I don't and I am sure they can make the device log survive the reboot, something that would have saved me a lot of time. -- 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
