I found the emulator to be unworkably slow, although Genymotion may fix that (I've never used it). What worked best for me was just plugging my phone in and developing straight on that.
Sent from my flux capacitor. Please excuse brevity and any odd autocorrect errors. On 26/04/2014 6:02 PM, "Nic Roche" <[email protected]> wrote: > Hi Greg, > > > Has anyone here managed to get the ADT (Android Developer Tools) and an > Eclipse project running in an emulated device? > > Yeah, it was pretty straightforward, compared with some of the toolchains. > Some of the commandline processes may give you more control (adb, ant...). > > I was running phonegap apps from eclipse. This may give extra details: > > > http://www.adobe.com/devnet/html5/articles/getting-started-with-phonegap-in-eclipse-for-android.html > > Searching the specific hangline might give you more precise direction: > > Waiting for HOME ('android.process.acore') to be launched. > > The ADT emulators are dead slow loading. Use Genymotion (for personal > use); load a android VM _before_ a run in eclipse and the adt finds it... > > Nic > > > > > ------------------------------ > Date: Sat, 26 Apr 2014 17:49:32 +1000 > Subject: [OT] Android Developer Tools > From: [email protected] > To: [email protected] > > 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* >
