Develop Reference

Android Studio - Virtual Device takes too much disk space even with default settings (4x more space than normal)

When I create a Virtual Device in Android Studio, it takes 4+ GB of disk space when freshly created with the default settings. It normally takes between 500MB and 1.5GB as I could see on some other questions related to Virtual Devices and the screenshots of the official Android documentation.
Here's a screenshot of my devices when freshly created with default settings:
My Virtual Devices
As you see, the Pixel phone is taking 4.5GB of space and the Nexus 5X is taking 4.3GB.
Also, we did exact same process with a colleague and here's a screenshot of her freshly created Virtual Devices:
My colleague's Virtual Devices
As you can see, in her case, the Pixel phone is taking 503MB and the Nexus 5X is taking 1.1GB.
We both used the same default settings as you can see here:
Virtual Devices settings 1
Virtual Devices settings 2
We both have the same platforms:
MacOS High Sierra 10.13.6
Android Studio 3.1.3
Does anyone have idea of what is generating this oversizing on my Virtual Devices?
Thanks for your help.

Today i accidentally solved the issue. I needed to perform some updates on the Android Studio while installing some libraries and i updated:
Android Platform SDK 28 (which was the one i was using for my Virtual Devices) to Revision 6 and the Google APIs Intel x86 Atom System Image for that SDK to Revison 5.
I also updated the Android SDK Platform Tools to 28.0.1, the Android SDK Tools to 26.1.1 and the Intel x86 Emulator Accelelator (HAXM Installer) to 7.3.0.
Then, i needed to test on another Virtual Device and it was created and ran starting at 1.0 GB. So i decided to delete my current devices and create them again after this update. I created once again the two Virtual Devices that are show above on the question and the results were the following:
Pixel phone -> Now starts at 1.0 GB
Nexus 5X phone -> Now starts at 1.1 GB
Which is four times less than before the update.
So, basically, the solution and recommendation is to try to keep everything up to date! :)

Android O (API 26) Preview Emulator doesn't start

I downloaded the Android Studio 3.0 Canary 1 preview and used the AVD manager to download the Android O x86 system image. When I set up an AVD with the wizard, using the Pixel phone as the hardware. When I start the emulator, it just hangs on the boot screen forever.

I had the same problem. Make sure to create a new virtual device instead of editing an existing one.

My OS is Debian 9. I have the same problem for API 26, but I can launch the emulator with API 25 without a problem thanks to this link: https://stackoverflow.com/a/42903352/6603006
If you have any problem with API 25 on AVD Manager, you can use Genymotion application. It's fast and stable.

I was facing a similar issue, i did the following steps to fix it
1) Updated Haxm and emulator from the SDK manager to the latest version
2) Delete the existing AVD with android 26 and create a new one
3) Tried emulating a phone with a lower resolution (like nexus 4). Pixel and pixel XL have high resolutions and run very slowly, so unless you HAVE to use the pixel device, I would recommend a lower res device which will put less strain on your machine. When I tried running API 26 on an emulated pixel it took hours to boot up.

1.Delete all existing AVDs.
2.Invalidate Caches and restart
3.Clean and rebuild project
4.Create new AVD.
And make sure you have the latest version of emulator and HAXM installed from SDk Manager.
hope this helps.

Look at bellow page. it has explained with details:
https://www.andreszsogon.com/using-android-8-and-9-emulators-without-android-studio/
briefly I did these steps to solved the problem:
Update Android SDK Emulator to a higher version
install higher System Image (for API 26)
install or update HXAM
delete old AVD machines
create new AVD machine with this configuration: ( RAM: 2048 , VM Heap: 256 )

Developing an Android App. But cannot run emulator nor real device (Windows 7)

I'm new to developing an Android App using Android Studio. I've been following this example app on their website: https://developer.android.com/training/basics/firstapp/running-app.html#RealDevice
The problem is, when I try to run using the emulator or my real device (Samsung S5) using the instructions on that link, I still couldn't find my device. I get an error when using the emulator that would take 10 minutes to load on my 2 GB RAM computer (only to fail).
emulator: WARNING: Crash service did not start
emulator: Classic qemu does not support SMP. The hw.cpu.ncore option from your config file is ignored.
Cannot set up guest memory 'android_arm': Invalid argument (in red text)
Other considerations:
1. My processor is AMD and not Intel, so the Intel x86 Emulator Accelerator (HAXM installer) doesn't work for me.
2. I used the Nexus 5 emulator device with API level 21. I tried it with Nexus 6 emulator device with API level 23. No luck on both.
3. I've placed my Samsung S5 device on Debugging Mode but it never showed up on the "connected device" area when running the app.
I've searched for other questions relating to it. But my luck has run out. The fact that I got a slow computer adds to the bad luck.

You might be experiencing these problems due to allocation of excessive amount of RAM for the virtual device which wont be available for the device.
set it to something like 1024MB or 768MB and try again.

Virtual device (AVD , Android 4.4) failed to run every-time ? why?

I am a new learner of android development .When I was creating an AVD then it said that "on windows emulating RAM greater than 768M may fail depending upon system load.Try progressively smaller values of RAM if the emulator fails to launch" . respective screen shots are as fallows :
warning
stuck:
I tried to decrease the RAM size after that and tried 400 instead of 1024 but it couldn't open the AVD home page .I waited more than one hour but all in vain .I am using Android 4.4 API level 19 .I don't know why this happening and stuck at this situation.I want to know that where is the problem ,why it's not running .My PC configuration is :
OS: Windows 7 RAM: 2 GB Processor : Core2Duo

AVD is quite slow at times. Tips to speed it up significantly:
Download the Intel x86 Atom System Image from your Android SDK Manager for API 19
Then download and install
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
If you have a graphics card I would try to enable Host GPU option
Example settings for your AVD:
- CPU/ABI: Intel Atom (x86)
- Emulation Options: Use Host GPU

android emulator forever launching

i want to set up an android emulator, i downloaded android 4.4 (kitkat), tools, and all the extra's
the emulator is loading forever, its already loading for 2 hours, the android startup boot logo is not laggy, so the emulator is not slow.
I rebooted multiple times, and tried different devices
my emulator:
device: 10.1" WGXA (tablet) (1280 x 800: mdpi)
Target: android 4.4 - API level 19
CPU: ARM (armeabi-v7a) <--- cant change this
Memory Options: RAM:768 VM Heap: 32
Internal storage: 4096
Emulation Options: use host GPU
Computer specs:
4.2GHz 8-core cpu
4GB ram
and lot more
if i look in task manager it is using 15%cpu, 470MB RAM and 0MB disk speed

when you're using the Windows OS, you have to set the RAM to 512Mb in order to get the AVD to run properly.
Hope this helps as 2 hours is an awful long time for the emulator to load.

Had the same problem, try starting the AVD on its own and wipe user data before trying your app.

you are running these settings
10.1" WGXA (tablet) (1280 x 800: mdpi)
CPU: ARM (armeabi-v7a)
use host GPU
you must have a SUPER COMPUTER.... try a lower resulion start with 800x400,
if you have an INTEL pc,
download the "INTEL" engine from the SDK-MANAGER.API19
then use "use the GPU" setting and choose the "engine: intel" setting when creating an emulator
if you have a non-intel, then im sorry, stick with 800x400 resolution

Open android sdk manager
Extras-> install Android Support library

I had a problem on Windows 8 64-bit, with fresh installation of Eclipse and Android SDK - Virtual device was starting "forever".
I found this thread http://gotoanswer.stanford.edu/?q=android+emulator+forever+launching and link to
Can having spaces in the android sdk path cause problems in eclipse?
Solution: I moved Android SDK from
C:\Program Files (x86)\Android\android-sdk
to
c:\android-sdk
Changed location in Eclipse, and this fixed a problem for me. Now AVD launches normally. I have not found any other comments on the reason or explanation.
I hope it will help someone else.