It has more to do with how much memory you have than the speed of the processor. On my brand new 1G netbook it takes 4-5 hours!!! Check the Task Manager and I think that you will see that the emulator is eating up all the memory and CPU resources as it swaps memory to disk to make space for itself. Add another G or two of memory and you should be OK.
On Feb 11, 10:11 am, Dan S <[email protected]> wrote: > Sometimes you have to wait quite a long time for the Android OS inside > the VM to boot before your app starts up, depending on how fast your > machine is. I sometimes have to wait around a minute. > > Dan > > On Feb 10, 6:48 pm, Josh <[email protected]> wrote: > > > Hello Android Dev's > > > Short FYI: I am new to the Android development, I have the SDK (2.1) > > and I am running Eclipse. I tried writing the Hello Android basic > > application. I coped the same code the tutorial has but when I try > > running the application to see the final result, I am unable to get > > the Virtual Android to perform the same result as the tutorial. > > > I have created the default AVD that the tutorial explains at the > > beginning of the tutorial; the problem is the AVD is for Android 1.5, > > and since I am working with 2.1; Eclipse does not appear to work. I > > went through the AVD Manager and created a 2.1 virtual device with > > default settings. > > > The problem is, when I run, I get the emulator, however it just shows > > the default A N D R O I D screen. It does not show Hello Android like > > the tutorial explains. > > > Does anyone know what I am missing in order for my basic application > > to show up? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
