1 GB is definitely not enough to run the Eclipse + the emulator. Your system is probably swapping all the way during the 4+ hours, and even when executing the emulated system.
On Tue, Feb 9, 2010 at 4:53 PM, DonFrench <[email protected]> wrote: > I have this problem on my W7 netbook, which only has 1G of memory. > But if I wait long enough (4+ hours), it eventually comes to life. > And in the meantime it is eating almost all of the machine cycles. So > my conclusion is that you need more than 1G of memory (or superhuman > patience) to run the emulator. And even when it does eventually come > to life, the performance is so bad as to make it virtually unusable. > > On Feb 9, 3:06 pm, jDev <[email protected]> wrote: > > I set up Eclipse as directed on the android development site, and ran > > the emulator after building one of the sample apps. The emulator comes > > up and just displays some text and doesn't function after that. The > > program doesn't even seem to run. > > > > I am following the steps on the site exactly (or at least I think I > > am), but no matter what program I try to run on the Emulator it never > > seems to function (just displaying that same message). > > > > Has anyone come across this before/know of the easy fix? > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
