Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
BOOK: Professional Android 2 Application Development
This is the forum to discuss the Wrox book Professional Android 2 Application Development, 2nd Edition by Reto Meier; ISBN: 978-0-470-56552-0
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional Android 2 Application Development section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old January 28th, 2011, 06:18 PM
Registered User
Join Date: Jan 2011
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Basic problem debugging first app?

Really newbie problem here.

I'm working thru Chapter 2 - basically just the hello android app.

The problem is that whenever I do run->configuration or debug->configuration, the AVD emulator starts, but all that happens is that the word "ANDROID", in block letters, appears on the emulated display. Hello World does not.

I even tried creating a new project using the sample apps that come with the SDK, and debug into one of those, and the same thing happens.

What appears in the eclipse console is:

2011-01-28 14:06:35 - hello_android3] Android Launch!
[2011-01-28 14:06:35 - hello_android3] adb is running normally.
[2011-01-28 14:06:35 - hello_android3] Performing com.example.android.notepad.NotesList activity launch
[2011-01-28 14:06:35 - hello_android3] Automatic Target Mode: Preferred AVD 'android2.3.1-basic-wvga800' is not available. Launching new emulator.
[2011-01-28 14:06:35 - hello_android3] Launching a new emulator with Virtual Device 'android2.3.1-basic-wvga800'
[2011-01-28 14:06:40 - hello_android] New emulator found: emulator-5554
[2011-01-28 14:06:40 - hello_android] Waiting for HOME ('android.process.acore') to be launched...
[2011-01-28 14:06:53 - hello_android] emulator-5554 disconnected! Cancelling 'com.test.hello_android.hello_android_activity activity launch'!

the last line about emulator disconnected appears after I kill the emulator task in windows. None of the controls in the emulator are responsive.

Appreciate any help!

Old January 30th, 2011, 01:13 AM
Registered User
Join Date: Jan 2011
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts

The emulator always takes a looong time to boot. If it takes more than 10 mins, then kill it and try again. However, once it initially boots, it is much faster. So once you run your app, don't close it. Leave it up for the next app you run.
Old February 17th, 2011, 03:45 PM
Registered User
Join Date: Feb 2011
Location: Ottawa, Ontario, Canada
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts

I have found that on slow hardware you may have to "unlock" the emulator, and click "Wait" on some of the tasks that appear to be hanging to dismiss the dialog about processes being slow to start. Once you have done that your emulator will run fine.. for the most part. At least I have found this on my Ubuntu Netbook Remix powered Dell Mini 9 Netbook.


Similar Threads
Thread Thread Starter Forum Replies Last Post
problem in debugging chandanbhakuni .NET Framework 2.0 4 September 22nd, 2006 04:37 PM
problem debugging smart tag, please help Medes Visual Studio 2005 0 April 15th, 2006 03:09 PM
Problem debugging client-script on WindowsXP Dmitriy General .NET 0 October 11th, 2005 03:54 PM
.Net Remote Debugging problem - Please help!! peterdoherty VS.NET 2002/2003 3 August 16th, 2004 07:21 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.