Develop Reference

Android Studio: AVD options give the error "The skin directory does not point to a valid skin", but only when editing the virtual device

In Android Studio (Arctic Fox | 2020.3.1 Patch 1), the initial creation and subsequent launch of a new virtual device in the emulator completes without any issues and the device frame shows properly. However, when opting to edit the virtual device, an error pops up briefly at the bottom of the window saying, "The skin directory does not point to a valid skin," and the Enable Device Frame option becomes un-ticked. If you cancel out of the Android Device Configuration window, the skin will still load correctly. If you check the Enable Device Frame checkbox and select the Finish button, the emulator will load without a skin. Going back to the device's option page shows that the Enable Device Frame checkbox has once again become un-ticked. Is this a bug and/or is there a workaround to this? I want to boot from a particular snapshot each time the emulator loads, but cannot do that without accessing the option page (whereby the skin will disappear once I finalize my option selection.)

I had this problem, I discovered I didn't have the SDK version downloaded for the version I had selected in AVD.
To solve in Android Studio Select: Tools > SDK Manager
Then check you have downloaded the SDK for the android version you are trying to use in AVD

I had the same issue when creating a new AVD:
Click "Show Advanced Settings"
Set "Custom skin definition" to "No Skin"
Error is gone

I had the same issue.
Create a new device.
Compare the config.ini files between the two.
I found mine in C:\Users\USER\.android\avd\Pixel_4_API_30.avd\
Edit accordingly.
Restart.

Unable to turn on "Snapshot" in Android Studio AVD Manager & save it

Android Studio 2.1.3 on Windows 10 64 bit.
I go to Tools->Android->AVD Manager.
It shows me an error "Android Virtual Device" failed to load - click Details to see the error.
When I click Details, it does not show any error.
When I click on Edit & try to turn of "Host GPU" & turn on "Snapshot" option, the OK button remains grayed out - so I cannot save the Snapshot Option.
The emulator itself runs fine - however, how do I turn on the Snapshot option.

Try going to your SDK manager and making sure everything is updated. Your options are slightly different and I believe it's because you are using an older version.
They now have the Emulator Accelerator. You can also select to run off of your hardware and choose the number of Cores from your CPU to assign to the virtual device.

accroding to this image http://imgur.com/cWqmDgH you have not set skin ..so please choose skin option then you will be able to see ok button

Where did the Hardware Keyboard Present go in Android Studio 0.8.14 Virtual Device Configuration?

In the lastest version of Android Studio (0.8.14) it has a great new wizard for creating/configuring an AVD. However, two key things have been removed:
Hardware Keyboard Present
and the ability to choose some pre-existing/default skins
Does anyone know if this is a bug or what to do instead? I'd like to be able to type using my keyboard into the emulator.

Selecting New Hardware Profile when creating or editing your AVD will bring up a dialog box which has a check box titled Has Hardware Keyboard.
With regard to skins if you go to the Default Skin directory search and go to {Your Android SDK Location}\tools\lib\emulator\skins then you should be able to see a dynamic skin option.
Presumably this is the folder where you should be able to add new device skins, although I'm not sure exactly where the greater range of default skins are.

Android emulator doesn't scroll back UP

Trying to use the AVD in Eclipse Kepler on Windows 7 Pro.
Nexus 7 2012 with the Level 19 (4.4.2) APIs and the Intel Atom processor.
Every listview, once scrolled down, immediately scrolls to the bottom and stays there. I can start to drag the list back towards the top, but as soon as I let up on the mouse button, it bounces back to the bottom of the list. This is for ANY list - system settings, app listings, etc., as well as my custom coded HTML5 app.
Has anybody ever seen that before? A Google search turned up nothing useful...
-Paul-

To solve this issue follow the steps below:
Click on virtual device manager and then select the AVD that you are using.
Now, click on edit and choose CPU/ABI as ARM.
Click ok and and run your project again. The scroll view will work properly.

I had the same issue - solved it by changing the Virtual Device to use ARM CPU instead of Intel Atom
(Change under Run -> Run Configurations -> Target -> Your virtual device -> Manager.. -> Your device -> Edit... -> CPU/ABI: Change to ARM)

D'pad Is disabled in emulator

I am using android sdk 4.0.3 ,I have created an Emulator of it.
Now I have a problem that the emulator is showing the Disabled
DPAD Buttons .I have set up the Hardware keyboard present and display skin with buttons option in configuration.
So i just want to enable the Dpad Buttons on emulator

Every emulated device is based on a more or less real device, which you chose as '4.0" WVGA (480x800:hdpi)' this doesnt only concern the resolution of your emulated device bur also its hardware features. In the main screen of the avd-manager enter the tab that says device definitions. there you can edit your chosen device and you will find the dpad under input.

This sounds crazy, but it worked for me:
Launch a fresh emulator from the Android Virtual Device(AVD) Manager.
Note: "DO NOT START THE DEVICE".
Find the configuration file, something like: ~/.android/avd/XXXX.avd/config.ini
Notice that this directory has only one INI file.
Edit config.ini:
change hw.dPad=no to hw.dPad=yes
The AVD Manager will still show dPad=no when you click on Details. It appears to not catch on until the virtual device is started. (Clumsy? yes)
Start the device. It should show DPAD without the complaint about it not being there.
The DETAILS button in AVD Manager should also show hw.dPad=yes
I ran into this while trying to bring up the "Snake" demo. It failed to run, asking to press the UP key -- and the pad didn't respond! After getting DPAD set, the demo can be controlled through the pad.
This appears to be a bug in the AVD Manager. If you get dPad set to 'yes', it can be set to 'no' through the AVD Manager. But changing 'no' to 'yes' requires the above workaround.

The virtual device folder has a config file , just like my Mac OS X and a VM(A17) :
~/.android/avd/A17.avd/config.ini
change
hw.dPad=no
to
hw.dPad=yes

I found this solution in a different file. I am using SDK version revision 20.
Create a fresh AVD from you AVD manager.
There is no option in AVD manager to enable DPAD. I tried even by clicking Edit.
Go to C:\Users\%USERNAME%\.android\avd\YOUR_AVD_NAME folder
Open hardware-qemu.ini file. Here you will get all hw config details.
There you will find hw.dPad = no; Change it to hw.dPad = yes and save the file
Restart your AVD and Voila !!! DPAD is now enabled in Emulator.

Edit config.ini as
hw.dPad=no --> hw.dPad=yes
.
Clone Device Definitions with enable keyboard
Enable Input -> Keyboard.
For your previous AVD, So you wouldn't face this problem anymore in the future.

You have to uncheck the hardware keyboard present option. It would then be enabled. So the option would be
Display a skin with hardware controls - true
Hardware keyboard present - false