I don't think there's much you can do. You will have to allow for a long boot time or upgrade your hardware. I've heard complaints about boot times being 20-30 minutes, but that may have been just the first boot.
On Apr 6, 6:41 am, Jakob Bjerre Jensen <[EMAIL PROTECTED]> wrote: > Hello Digit, > > Thanks for your answer, and you are right: I ran on a CPU with 1 GHz > and 500 MB RAM. > However I fail to find any system requirements related to CPU and RAM > in the documentation > "System and Software Requirements". I only complied to the Windows XP > requirement. Perhaps > it would be an idea to state hardware requirements as well? > > Anything I can do to run the emulator on a 1 GHz CPU with 500 MB RAM? > Allow longer first-boot time? > > Best regards, > Jakob Bjerre Jensen > > On Apr 6, 1:52 am, Digit <[EMAIL PROTECTED]> wrote: > > > for the record, Eclipse and the plugin are totally un-necessary for > > developing Android applications. they just provide a better environment but > > you should be able to use all the tools available in $SDK/tools from the > > command-line to package run and debug your Android applications. I do that > > routinely when benchmarking emulator binaries on different PCs. > > > now, the very first time you launch the emulator on a "clean PC", the boot > > sequence will be longer because the system will build various caches. any > > boot after than should be faster. > > > the "Application not responding" dialog you see is just a symptom of having > > a very long boot sequence (at the moment, the Application Manager is not too > > sharp and considers that the Home application is not responding because the > > CPU was taken by other processes during the long boot sequence). > > > now, why the boot sequence is long on your machine can be from two things: > > > - you're running on a "low-end" CPU (by today's standards of course, i.e. > > anything < 2 real GHz or with < 1MB L1 cache would qualify) > > > - there are probably some bad dependency / race conditions in our boot > > sequence that make the system_server crash in a loop during the boot on some > > machines. it's unfortunately something we could not reproduce. > > > On Sun, Apr 6, 2008 at 1:10 AM, Jakob Bjerre Jensen < > > > [EMAIL PROTECTED]> wrote: > > > > Hello, > > > > I have problems running the emulator on a completely "clean" PC only with > > > the following installed: > > > > 1. extract android-sdk_m5-rc15_windows.zip into a folder. > > > 2. navigate to the tools folder and execute "emulator". > > > > I.e. no Elipse Plug-in etc. installed. First the emulator screen appears > > > as normal, then however it > > > "hangs" for five minutes or so, finally the following error occurs: > > > > Application Not Responding. > > > The application com.google.android.phone is not responding. > > > > I have done quite a lot of coding on a Windows Vista without any > > > problems. The problem > > > occurs on a Windows XP Home Edition (if that makes any difference). > > > > Are there other tasks necessary to do (e.g. installing Eclipse + ADT) in > > > order to run the emulator? > > > > Best regards, > > > Jakob Bjerre Jensen- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
