Android Error – The Emulator Disconnects and Doesn’t Launch the App
Does Eclipse show "Emulator-XXXX disconnected" even though the Android emulator works fine? Find out why it happens and how to fix it quickly.
When you try to run the emulator from Eclipse, you may get the following error on screen even though the emulator works perfectly:
Emulator-XXXX disconnected! Cancelling ‘actividadEjecutora activity launch’!
This error can happen for several reasons. One of the best known is that the computer running the emulator is not very powerful, so the emulator takes so long to load that Eclipse loses the connection to it; it can also happen after several successful launches on the emulator.
Solution
There’s nothing else to do but close the disconnected emulator and restart it. When you launch the app again, the emulator usually starts up once more.
“Android Error – The Emulator Disconnects and Doesn’t Launch the App” by Ramón Invarato at jarroba.com, licensed under Creative Commons Attribution-NonCommercial-ShareAlike 3.0. Registered at Safe Creative.

You may also like
Android Error – The Log Shows Nothing
Is your Android Log empty even though the emulator or device is connected? Learn how to fix this common Eclipse error with a quick restart.
Android Error – The Connection to adb Is Down and a Severe Error Has Occurred
Getting the Eclipse error "The connection to adb is down, and a severe error has occured"? Here are two simple ways to restart adb and fix it.
Android Error – Eclipse Throws an Error That Doesn’t Exist Anywhere
Eclipse shows a red X on your Android project but no error anywhere? Follow these step-by-step solutions to fix the phantom error and the R.java problem.
Android Error – Eclipse Doesn’t Show the Android Buttons After Installing the ADT and the SDK
Eclipse doesn't show the Android SDK Manager and AVD Manager buttons after installing the ADT and SDK? Here's how to bring them back in a few steps.


Leave a comment