Eclipse android sounder freezes

Question

Sorry if this is a stupid question. im very new for development.

When I run the emulator on Android, instead of loading the home screen. it just stays on this screen:

I do not get any error codes or anything else, and it does not slow down my entire computer or eclipse, it just freezes the emulator and does not move on. I just need to press the button (x) to exit it. so I was wondering if anyone knows how to fix this and thanks!

change

I would also like to mention that after a very long time I get this screen

Answer 1

The best option is to use bluestacks android emulator . In my opinion, this is much faster than the Google Android emulator.

Here are the steps to configure:

1 - Install bluestacks emulator

2 - Open cmd

3 - Enter the command: set path="Android SDK\config\platform-tools" (you need to enter the full path where your adb.exe is located

4 - adb connect 127.0.0.1

Now you can run applications directly in the BlueStack emulator from your IDE.

Answer 2

what I found that helps me when a device goes offline is to go to the window ---> Show View ---> Devices (you may need to click "Other" and select it there, and then select " reset adb "

Sometimes a device goes offline for an unexplained (not explained to me anyway!) Reason

You can simply create another emulator with the same specifications. Have you tried this?

PS you may need to restart it again so that it is listed in the "Devices" window

Answer 3

On Windows, ARM system images are very slow; Intel x86 images faster, up to 4x; so you should try with the Intel image. Trying with a smaller screen should also help; especially if your memory settings are low. With such a large screen as shown above, it is possible that your emulator is simply running out of memory.

Answer 4

Get the x86 build from android-x86.org, install using VirtualBox (or something else, but virtual box, if it's free). Find the ip of your vm using ctrl + F1 (go to cli, ctrl + F7 to return to graphical mode) and netcfg . Then adb connect 192.168.1.5 (replace your vm ip).

then it should work.

Answer 5

I am having a problem with the recently updated SDK on the Ubuntu 12.xy desktop computer and WinXP. I thought it was strange because there were no problems with the 2.2 SDK with which I played on my Ubuntu 10.xx system last year or so. Following NH's suggestion, I used the SDK manager to install 2.2 (API 8) and created an emulator for this level, and this emulator also works on these desktop systems, like on a laptop. Since I was just studying, and the physical device is at 2.2, I am going to leave it that way until I need to move up.

Answer 6

Wipe user data before starting the emulator. This will reset the emulator and all applications, but at least you do not need to recreate or reconfigure it.

Make sure you clear this check box the next time you run the emulator.

Answer 7

Emulators are inherently slow because they must mimic all the hardware of your device (including the camera, Wi-Fi adapter, etc.) in the software.

However, you must set aside half a day for the emulator to boot for the first time (walk the dog or something else while you wait), and then every time after that it should be faster.

Choose an API below 14 (e.g. Gingerbread API 10, most devices run this) to improve emulator loading.

Then, after the emulator had, however, you need to download it for a long time, you can just click the run in eclipse, and your application should run it in the emulator. When you are done, don’t close the emulator, just go back to the eclipse, make changes to the code, and then run it again and it will automatically close the application, replace it with a new version and launch it.