Until when? How long should the user continue to wait before he can conclude that something really has gone wrong? Remember: he said the message "waiting for Home android.process.acore" was STILL displaying on the screen. Can we count on this message to be accurate?
Sure, I know that the emulator takes a LONG time, even on a fast machine. But sometimes the launch really does fail, and the user needs a way to tell. My own experience has been: 1) it takes a very long time, and paints the word 'Android' on the screen in two different fonts 2) sometimes, but not all the time, I have to unlock the menu 3) sometimes, but not all the time, execution passes directly to the application, sometimes I have to launch it myself. I don't remember what was displaying in the console window in all these cases: that is why I ask which messages we can really count on in that window. It seems pretty random which I get in 2 and 3. But computers are deterministic finite state machines! They are not supposed to do things like this! On Jan 13, 6:17 pm, CT <yeu...@gmail.com> wrote: > continue waiting ! > > On Jan 7, 4:22 pm, Jonathan <jonathan.gord...@gmail.com> wrote: > > > Hey all, so I just completed the hello world tutorial but it won't > > seem to run. I waited for a long time at the Android screen with the > > blinking underscore, then finally I moved onto a screen with a fancy > > font Android and its kinda flashing silver. The console in eclipse > > still says waiting for Home anroid.process.acore... How long does it > > usually take to load?? Am I doing something wrong?? Thanks
-- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en