Tanarif

Essentially I have the code to a project, it loads in eclipse and I have everything installed and experience with working in eclipse. But lately the emulator just refuses to load the project. Usually I get a forced close message, or a disconnection etc. If anyone could perhaps get onto a live chat with me, or teamviewer, and help me out - I will gladly pay you $20 per hour of your time as I need this done asap.

This is what I get when I run the the project, if you wish to help out for free then that is also much appreciated.

[2012-02-08 20:46:46 - GoalManager] ------------------------------
[2012-02-08 20:46:46 - GoalManager] Android Launch!
[2012-02-08 20:46:46 - GoalManager] adb is running normally.
[2012-02-08 20:46:46 - GoalManager] Performing com.android.sample.goalmanager.LoginActivity activity launch
[2012-02-08 20:46:46 - GoalManager] Automatic Target Mode: launching new emulator with compatible AVD 'droidX2'
[2012-02-08 20:46:46 - GoalManager] Launching a new emulator with Virtual Device 'droidX2'
[2012-02-08 20:46:50 - Emulator] emulator: emulator window was out of view and was recentered
[2012-02-08 20:46:50 - Emulator]
[2012-02-08 20:46:50 - GoalManager] New emulator found: emulator-5554
[2012-02-08 20:46:50 - GoalManager] Waiting for HOME ('android.process.acore') to be launched...
[2012-02-08 20:46:51 - GoalManager] emulator-5554 disconnected! Cancelling 'com.android.sample.goalmanager.LoginActivity activity launch'!

Snedd

Try using Window/AVD Manager to start an emulator manually, probably you should also tick the wipe user data option. Wait for the emulator to fully boot so that the home screen is displayed. Then try launching your app.

__________________
Roller Toaster - a game for android involving a rolling ball, lots of donuts, and no monkeys.

Tanarif

Thanks a ton for the response - tried but no luck unfortunately, it just got stuck on '[2012-02-09 00:53:36 - GoalManager] Starting activity com.android.sample.goalmanager.LoginActivity on device emulator-5554' and eventually had to close.

Snedd

Hmmm

Make sure you have the devices & logcat tabs on: window/show view/other/android. Is the emulator definitely showing up in the devices tab as online. If it is, you should get more detailed messages in logcat than in the console that should give some indication why it is failing. If it isn't showing as online, try stopping and starting adb:

adb kill-server
adb devices

Last edited by Snedd; February 8th, 2012 at 08:41 PM.