I have bruised myself on this problem, using Eclipse Gandymede. I am using AVD 1.6 at the moment. In my case the "sad result" appears to be caused by exceptions from my own code, though i suppose one might argue that the tools should be more robust. I needed to read the Reference documentation carefully. For instance, I used wait() on a thread when i meant sleep(). In onPause(), onResume(): make sure to call super.onPause(), super.onResume()
Is there a quicker way to diagnose such errors? Please let me know. On Jan 2, 2:18 am, jimjenkins5 <[email protected]> wrote: > Hello all, > > I am having a problem with the emulator (orADB). I consistently lose > connection with the emulator andADBdoes not list it as a running > device. Eclipse will report back "sadresultfromadb!" after trying > to install the program. > > I am running Eclipse Galileo and most AVD's I've tried have been 1.6 > although I have tried 2.0, 1.5, 1.1 also. > > I've added an exception in my firewall, turned the firewall off, and > disabled antivirus applications. > > I've also tried completely uninstalling eclipse (i.e. deleting the > folder and redoenloading) and the Android SDK. > > So far nothing has worked and my development is at a standstill. The > only thing I can get to work is to create a new AVD each time I debug > the application which is time consuming and requires waiting 10 > minutes for the emulator to start up again for every change in code. > > Any ideas on what I may be able to do would be appreciated. I am very > frustrated at this point. > > Thanks, > Jim
-- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
