Hey Guys, Does anyone have this problem happen before? The emulator open and runs fine, but the app just doesn't get loaded? Try to find the solution with no luck, is it something to do with adb?

Hi Cyrus_8888, Does our Logcat or console say anything? LA

Hi LA, Nothing can be seen in logcat. In run configuration, I've tried to select either launch Default Activity / Launch by project.BT_activity_root. But nothing seems to work. My app just can't be found in the emulator. BTW, Google APIs, platform 2.2, API level 8 were selected. It's so weird. Cyrus

Hi Cyrus, When you run your app and it launches the emulator, there should be some output being written to the Console (Android, not DDMS). It'll tell you that the emulator is launching, the app is being uploaded, etc. Can you paste what's going on there so we can see what's happening? Thanks! Mark

Hi Mark/LA, The console display output in below when the emulator launches. Emulator seems to work fine, but it just couldn't get connected with my app. Have you guys seen this issue happen before? kind Regards, Cyrus Android Launch! [2012-12-29 18:45:42 - SteakAndroid] adb is running normally. [2012-12-29 18:45:42 - SteakAndroid] Performing com.steakandroid.BT_activity_root activity launch [2012-12-29 18:45:45 - SteakAndroid] Launching a new emulator with Virtual Device 'NexusS' [2012-12-29 18:45:49 - SteakAndroid] New emulator found: emulator-5554 [2012-12-29 18:45:49 - SteakAndroid] Waiting for HOME ('com.steakandroid.com') to be launched...

Is that as far as it gets? Because that's basically Eclipse saying it's waiting for the Emulator to come up, and I bet it eventually fails saying it can't connect. There's only so long that Eclipse waits for Home to come up so it can upload the app before it bails. If it is bailing, you may want to reboot your system and make sure nothing else is running when you try and run the app. These tend to be attributed to low memory problems on the computer. Mark

Hi Mark, Thanks, I found the solution on http://stackoverflow.com/questions/3073046/waiting-for-home-android-process-acore-to-be-launched Waiting for HOME ('android.process.acore') to be launched... Wait for few seconds and then right click on the project and click run as Android application once again. It bounds to existing emualtor, doesn't open new emulator. Cheers Cyrus

Hey Cyrus, Glad you got it going. I've had to do that also or sometimes when I fix the project properties, Google API's, the project doesn't rebuild. One time I had to do it 10 tens with rebooting to get it to rebuild for the correct API. LA

Hi LA, Yes, indeed. There are more to come. I'm solving the problem one by one. It's lot harder to build an Android one rather than in Xcode. But this just my opinion. Thanks once again! :) Cheers Cyrus