Shall we compare experiences? I regularly run the SDK and emulator not on Ubuntu, but Fedora, which is similar enough.
You say even 10 minutes later, you are still looking at boot animation: what I see that is so similar is: about 1 launch in 7 or 10, it gets stuck early on. I never let it go for 10 minutes though;) Instead, if it hasn't got to the home screen (even if it says I have to press Menu to unlock) within 3 minutes, I kill the emulator launch and start it over. I have never seen it fail twice in a row. Yes, it is annoying, but since it never fails twice in a row, I have never felt a very strong urge to debug it further. The workaround is good enough. So how does this differ from your situation? Are you getting the 10 minute failure every time you launch the emulator? Do you still get it after rebooting the machine? Or after rebooting only Eclipse? On May 27, 2:08 am, "Robert P. J. Day" <[email protected]> wrote: > (aside: my apologies for the regular posting of newbie-level > questions -- i'm just trying to stress test stuff as i learn it so > it's not surprising that i'll screw something up and need help to fix > it. also, hysterically, with what little i know so far, i've been > asked to give a beginner-level tutorial locally on how to get started > with android. the mind reels. anyway, onward if i might ...) > > curiously, since just yesterday when i ran the emulator on my ubuntu > 10.04 system and it worked relatively quickly, this morning, bringing > up a new AVD that i just created (nothing special about it) is taking > *forever* -- literally, it's been 10 minutes since i started the > emulator and i'm still looking at the boot animation screen. > > is there a way to debug what's going on? i've already verified that > not long after i start the emulator, "adb devices" sees it and i can > "adb shell" into it. some time after that, what i assume is the > "bootanimation" utility starts to run which produces the neat > "android" boot logo and ... much more time passes. > > during this time, i'm shelled into the emulator, "ps" works (i can > see the "bootanimation" utility running), "top" works, things are > clearly running but i have no idea why, just in the last several > hours, things are so much slower. this is an absolutely stock AVD (1G > SD card), no added apps, etc. it's the same thing i was testing > previously with no issues. > > given that i can shell into the emulator and poke around, is there > something i can check? at this point, i'm baffled. > > User 43%, System 32%, IOW 0%, IRQ 1% > User 85 + Nice 0 + Sys 64 + Idle 44 + IOW 0 + IRQ 3 + SIRQ 0 = 196 > > PID CPU% S #THR VSS RSS PCY UID Name > 186 54% S 18 122508K 24064K fg system system_server > 147 18% R 1 912K 396K fg root top > 196 9% S 4 12772K 5148K fg graphics /system/bin/bootanimation > 40 1% S 4 3388K 176K fg root /sbin/adbd > ... snip ... > > -- > > ======================================================================== > Robert P. J. Day Waterloo, Ontario, CANADA > > Linux Consulting, Training and Kernel Pedantry. > > Web page: http://crashcourse.ca > Twitter: http://twitter.com/rpjday > ======================================================================== -- 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 [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
