When I launch eclipse and launch the Android project, it opens a new emulator every time,

Question

Eclipse Android Emulator takes an average of 7 minutes to start its activity, its quite a long time. Once the emulator is installed, other projects can run in one emulator, which takes less time. Sometimes, when I launch eclipse and launch an Android project, it opens a new emulator each time instead of installing the project in the same emulator.

I was looking for this problem, I found the only good reason, Connection rejected for sensor ports is a common problem. . I'm not sure. This is the real reason.

I use Eclipse for Windows, not Mac or Linux, and the previous activity was correctly set before starting the next project

Help me figure out what could be causing this problem and how I can make it normal.

Answer 1

If you start Eclipse with an ADT connection, then what usually happens is (1) you start a project (2), it asks you to select an Android device (3) if the device is not available, for example. a valid emulator, it will ask you to create it.

If Eclipse asks you to create a new emulator every time it is like this (1), you did not select an option in the pop-up window indicating that you would like to always run the project in a specific list of instances your emulator (2) is actually not compatible emulator.

If the emulator is created but not found (as I suspect this is happening), you need to update your ADT plug-in to connect to this emulator. You can do this from within the eclipse by going to the device viewing mode (window → show view → other → androids → devices) by selecting the triangle pointing down, to the right and selecting "reset adb". This will restart the bridge of the Android device, aka, which will connect eclipse to your emulator and allow it to recognize this instance again. After that, you can run your project on this emulator.

Answer 2

You can not start the emulator automatically by going to

run → run configuration → target . Then select “ Always request a device. ” Run the project after that and select another emulator device.

Here is a screenshot:

Answer 3

Not sure if this is the solution, but I noticed that clearing the memory on the emulator helped me several times. Also, I had a problem when I did not notice that the console stated that my emulator was running on the lower API requested by the application, so it opened the next best emulator instance.