« Oldie but a goodie :-)
JOTD: 1/4/2010 »

Hello, Android (or… not.)

UPDATE: Wanted to put this update here. It works fine. The emulator takes a DOG’S age to boot up. This is going to be a painful development process.

I’m trying to get a Hello Android application up and running, per the dev website. But something seems to be missing.

I have:
- JDK 6 17
- Eclipse 3.5
- The ADT installed. (Apparently fine. tough to tell.)
- the android sdk platforms installed (1.1-2.0.1)
- a default avd created

The source for the hello world example is pretty solidly “hello world” and I’ve double-checked it and done a straight copy-paste.

But when I run the example in eclipse, an emulator comes up but the application doesn’t appear to kick off.

Any thoughts on troubleshooting that? There aren’t any compile errors. The status messages in Eclipse all look pretty straightforward, it’s just not doing anything.

[2010-01-04 19:18:43 - HelloAndroid]Android Launch!
[2010-01-04 19:18:43 - HelloAndroid]adb is running normally.
[2010-01-04 19:18:43 - HelloAndroid]Performing com.mpwilson.helloandroid.HelloAndroid activity launch
[2010-01-04 19:18:43 - HelloAndroid]Automatic Target Mode: launching new emulator with compatible AVD ‘my_avd’
[2010-01-04 19:18:43 - HelloAndroid]Launching a new emulator with Virtual Device ‘my_avd’
[2010-01-04 19:18:44 - HelloAndroid]New emulator found: emulator-5554
[2010-01-04 19:18:44 - HelloAndroid]Waiting for HOME (’android.process.acore’) to be launched…

UPDATE: Ick, sorry. That dump of the messages is nasty, but if you drop it in emacs or something it’ll straighten out.

Tags: , , ,

This entry was posted on Monday, January 4th, 2010 at 8:20 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “Hello, Android (or… not.)”

  1. Tom Smith Says:
    May 28th, 2010 at 4:51 pm

    Same happened to me, that’s why I found this post.
    It did eventually load and all was well!

    It was genuinely waiting - one thing that may make it super slow first time is that the AVD instructions do not say to set up a target API level, this is reported on the the console output and reports that it has used Level 7, the AVD Manager then shows API Level 7 for my-avd.

  2. Tom Smith Says:
    May 28th, 2010 at 4:57 pm

    Ignore post, you had already updated at the top of the blog.
    Oops :-)

Leave a Reply