"It's a bingo!" I have isolated the problem - the reason is something to do with the Windows path.
I had a look for that DDMS program, by going to the logical place for it in Windows Explorer - <SDK path>/tools I did not run DDMS. This Explorer window was open in the background, that is all. I believe that adds the folder to some path in Windows (e.g. in DOS if you change drives, it will go to that folder). The I launched Eclipse and ran the program: ... [2010-05-12 19:33:57 - HelloAndroid] Launching a new emulator with Virtual Device 'AndroidLevel7Device' [2010-05-12 19:33:57 - HelloAndroid] New emulator found: emulator-5554 ... That second line was never happening before. Tip for others with this issue ==================== As soon as your emulator starts up (i.e. on Windows, you see 3 DOS boxes appear and disappear in succession) you should then get the "New emulator found" message. If not, you don't need to wait for the emulator to boot and unlock it etc. because something is wrong. Check your paths, or just leave <SDK path>/tools open in Windows Explorer (the only solution I have tried tonight but I am sure it is not permanently needed). Request for Developers / Google ======================= I have a lot of experience with Java but none with Android, and this issue set me back a few days. Could someone raise a bug report / ticket for this? If ADT cannot access whatever binary it needs in the <SDK path>/tools folder, it should throw an exception and error out on the console with a message saying what it needed. Thanks. -- 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
