Took 28 seconds to go from pressing "Launch" to the "Press Menu to unlock" screen on Windows here, when I timed it just now. 24 when I killed it and ran it again. Tested using an Android 1.5 emulator image with a 64MB SD card image on a 2.8GHz Core 2 Duo laptop with an SSD running Windows 7. The Android 1.5 emulator gets better frame rate in OpenGL than newer Android versions, so I tend to use that, if I have to use an emulator instead of a device. What speed computer are you using that it takes 15 minutes? I didn't even kill Eclipse, which is sucking up massive amounts of memory like usual. -Lance
On Sep 17, 8:28 pm, DanH <danhi...@ieee.org> wrote: > Of course, keep in mind that it takes longer than 5 minutes (something > like 15) to cold-start the Android emulator on straight windows. > > On Sep 17, 11:11 am, Ahmad Musa <bzu.ah...@gmail.com> wrote: > > > hi all, > > > I am using windows XP, and my android development environment is > > on ubuntu installed inside vmware. > > all java applications I write on eclipse are running just fine, when > > it comes to an android app, the simulator is just > > killing me, it takes about 5 minutes to start my app. > > > please respond to me by email. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
