Greg, Apart of the emulators being extremely slow (as others have mentioned) their configuration can be a bit buggy. For example, if you try to allocate too much RAM, it may not start up correctly. I've found you can fix this by manually fixing the configuration file. I don't remember the details any more since I stopped using them some time ago but I think you had to manually add or remove "M" or "MB" to the end or the RAM setting. The config tool would actually set this wrong. Of course that bug may have been fixed by now but who knows.
In general then, you may want to look up problems people are having with the emulator itself. If you can get one to start up independently of eclipse it should be fine after that. Just be sure to use the snapshot option that will save its state so you don't have to wait 10 minutes for it to boot ever time. David "If we can hit that bullseye, the rest of the dominoes will fall like a house of cards... checkmate!" -Zapp Brannigan, Futurama On 26 April 2014 17:49, Greg Keogh <[email protected]> wrote: > This is way off topic in here (the forum might have a meltdown). Has > anyone here managed to get the ADT (Android Developer Tools) and an Eclipse > project running in an emulated device? I installed the whole ADT and latest > JDK, generated a hello world project according to the steps > here<http://developer.android.com/training/basics/firstapp/creating-project.html>, > but when I "Run as Android Application" the Nexus 5 emulator appears and it > stalls at this line with no explanation: > > Waiting for HOME ('android.process.acore') to be launched... > > The Eclipse experience differs enough from Visual Studio to drive you > batty. > > *Greg K* >
