Android emulator for perpetual launch

Question

I want to configure the Android emulator, I downloaded Android 4.4 (kitkat), tools and all additional

the emulator loads forever, it has already been loaded for 2 hours, the boot logo to launch Android does not lag behind, so the emulator does not work slowly.

I rebooted several times and tried different devices

my emulator: device: 10.1 "WGXA (tablet) (1280 x 800: mdpi) Purpose: android 4.4 - API level 19 CPU: ARM (armeabi-v7a) <--- can not change this Memory options: RAM: 768 VM heap: 32 Internal storage: 4096 Emulation options: use the host GPU

Computer specifications: 4.2 GHz octa-core processor 4 GB of RAM and much more

if I look in the task manager, it uses a 15% processor, 470 MB of RAM and 0 MB of disk speed

Answer 1

when you use Windows, you must install RAM at 512 MB for the AVD to work correctly. Hope this helps, since 2 hours is a terrible time to download the emulator.

Answer 2

If you have the same problem, try starting AVD yourself and erasing user data before trying your application.

Answer 3

you use these settings 10.1 "WGXA (tablet) (1280 x 800: mdpi) CPU: ARM (armeabi-v7a) use the host GPU

you must have SUPER COMPUTER .... try a lower start from 800x400, if you have an INTEL computer, download the "INTEL" engine from SDK-MANAGER.API19 then use the "use the GPU" setting and select the "engine: intel "when creating an emulator

If you have non-intelligent, then I'm sorry, stick to 800x400 resolution

Answer 4

Open sdk manager for Android.

Advanced → install Android support library

Answer 5

I had a problem with the 64-bit version of Windows 8, with a new installation of Eclipse and the Android SDK - the virtual device started "forever." I found this topic http://gotoanswer.stanford.edu/?q=android+emulator+forever+launching and a link to
Can spaces in the sdk android path cause problems in eclipse?

Solution: I transferred the Android SDK from

C:\Program Files (x86)\Android\android-sdk

to

c:\android-sdk

The location in Eclipse was changed, and this fixed the problem for me. Now AVD starts normally. I did not find any other comments for a reason or explanation.

I hope this helps someone else.