Apps AVD not displaying Hello World for over an hour

[GTbrewer]

I've been trying for days to get the AVD up and running just to get started with the
Hello World example from the Android developer site
(Hello, World | Android Developers). After a
reboot last night, with only Mozilla running, I started Eclipse again, and deleted
and re-did the Hello World example, following it to the letter, as before, except,
per advice I read somewhere, using 1.5 as the platform instead of 2.1 or 2.2.

Whereas before, the emulator consistently became disconnected and each run
was aborted, this time, the emulator came up, and started going through its boot
process. That was about 10:10 PM local. Over an hour later, I gave up on it and
killed the emulator (had to use Task Manager to do so). I reset both the Eclipse
project and the AVD to 2.2, and ran it again....and promptly fell asleep. When I
woke up, it'd been 1:20 (yes, one hour and twenty minutes), and the console
said (as with 1.5 before that) that it was still waiting for the HOME app to run.

I understand that it takes a few minutes to start up, but how many hours fit into
those "few minutes" that it takes to start up? Seriously, I know that its
taking that long cannot be normal. My system is several years old, and a laptop
at that (my desktop ate itself...won't stay on for more than a minute), and my
FreeBSD system, which does have Eclipse and JDK in the ports section, is
only a 650MHz Pentium class (dmesg output:
CPU: AMD Athlon(tm) Processor (650.03-MHz 686-class CPU)

So I doubt it would do much better....

Does anyone know what the problem might be? I've tried and read everything I
can find, so even a pointer to the appropriate FM to read would help.....

Thanks

EDIT: this morning, I left it running while I went to a D'r's appointment. By the time
I got home, it'd been running (and still waiting) for 2.5 hours. No error messages on
the console, just waiting.

 

[GTbrewer]

Ok, I read a suggestion to run adb to debug the AVD, and did so. Here is an excerpt from
the log output that I was able to capture:

-----------------------------------------------------------------------------------------------

5:android.process.acore/10000}
I/Process ( 161): Sending signal. PID: 205 SIG: 9
I/ActivityManager( 161): System now ready
I/SystemServer( 161): Making services ready
I/ActivityManager( 161): Config changed: { scale=1.0 imsi=0/0 loc=ld_US touch=3
keys=2/1/2 nav=3/1 orien=1 layout=35 uiMode=17 seq=2}
W/SurfaceFlinger( 161): closeGlobalTransaction timed out!
W/SharedBufferStack( 172): waitForCondition(DequeueCondition) timed out (identi
ty=0, status=0). CPU may be pegged. trying again.
D
-----------------------------------------------------------------------------------------------

Note the last line ("W/SharedBufferStack......CPU may be pegged, trying again.")

I checked in task manager, and the CPU was, in fact, at 100%.
That was only one of many of the same line repeated throughout what I captured.

What could I be doing wrong that would cause that?

Thanks.....

 

[GTbrewer]

Well, I guess I don't NEED the AVD as much now, as I've just learned how to install my own apps for testing,
etc., on my phone from my PC (on a Motorola Bravo, where that's normally blocked).

FWIW, the instructions I found are at
http://theandroidsite.com/2010/03/11/how-to-install-non-market-apps-on-your-motorola-backflip/