40

i am trying to start the android emulator from eclipse classic (juno) and it keeps giving me this error:

ERROR: unknown skin name 'WVGA800'

I developed my software using eclipse indigo, but since I installed eclipse juno and imported the same project it started to give me this error. any idea why? and how to resolve this issue?

Waqleh
  • 9,741
  • 8
  • 65
  • 103

12 Answers12

42

My solution was to create a new custom virtual device from the android virtual device manager and use that.

Dale Wilson
  • 9,166
  • 3
  • 34
  • 52
Waqleh
  • 9,741
  • 8
  • 65
  • 103
  • 1
    You created a new custom skin? or what? – LarsH Nov 13 '13 at 14:23
  • i created a new custom virtual device – Waqleh Nov 14 '13 at 18:10
  • 9
    For anyone that's not a constant Android-SDK user, such as myself (I mostly do Cordova), that's wondering how to create your new virtual device: Try `android avd` from the command line, or if you're managing Android SDKs via Eclipse, Window > Android Virtual Device Manager. – Adam Tuttle Mar 21 '14 at 13:16
  • 1
    For Android Studio users, it's under Tools > Android > AVD Manager. – TMN Jul 16 '14 at 20:19
  • There wasn't any default skin in my default AVD. So I just choose one – barak Aug 05 '15 at 13:10
  • @TMN or you can click that icon with the purple screen and green droid at the bottom right in the toolbar. OR on Mac (not sure of shortcut on Windows) you can click (Command + Shift + A and type AVD) Just a couple of extra options. – technoplato Feb 03 '16 at 18:43
  • @Waqleh I think since there are solutions that don't involve creating a new device that this particular solution isn't optimal. The error can be resolved by simply toggling the skin in the advanced settings of the ADV in question. – technoplato Feb 03 '16 at 18:44
18

For me on Mac OS X this error went away when I selected the skin in advanced setting it was saying is unknown. enter image description here

PUG
  • 4,301
  • 13
  • 73
  • 115
  • 2
    I did this.... Selected the Pixel_2 skin that I had error, clicked the ... button and then just selected open on the files that where there. – Recycled Steel Jun 11 '19 at 14:36
10

I had the problem and fixed it... Here the main idea of the issue is that the emulator can't find your android-sdk base directory.. so what is the fix? here I will explain..

  1. Find where you have installed your sdk. To do so go to Start->All Programs->Android SDK Tools->SDK Manager.. You will see that the path is written on the top of the window.. copy it somewhere so we need it later.. call it "SDK Path"
  2. Go to Start and Right Click on Computer and select "Properties".. Then select the last option on the left menu which is "Advanced System Settings".. Go to the "Advanced" tab and click on the "Environment Variables.." on the first list see if there is a variable called "ANDROID_SDK_ROOT".. If it's there then check if the value is the same as the "SDK Path" we copied in the step 1.. if they are not the same then change the value of it to the SDK Path...and check if your problem is solved. if not then go to step 3..
  3. If the "ANDROID_SDK_ROOT" matches the SDK Path or your problem didn't solve in step 2 then the problem is probably caused by your username.. This was my actual problem. my username had special characters in it like ( !,@,#,... ) or even spaces in some times. Speaking technically as I am myself a programmer, when the emulator program was trying to open the path, it was giving out an error because it couldn't open it because of the special characters..Guessing that the SDK is installed in your Local App Data folder ( Users\\AppData\Local ) as mine was, you should access it with another Enviroment Variable called "LOCALAPPDATA" which links to your Local App Data folder.. So in your SDK Path change the "drive:\Users\\AppData\Local" to "%localappdata" and your problem will be solved .. For example mine was "C:\Users\MiNuS !3\AppData\Local\Android\android-sdk" and I changed it to "%localappdata%\Android\android-sdk"... (without the double quotations)..

The same problem is present in some other java programs. I had the problem with the Zend Studio too...

Hope it will solve your problem, Good Luck

Miro Markaravanes
  • 3,285
  • 25
  • 32
5

I bumped into the same problem in Android Studio on Mac OS X 10.6.8 and there it helped to create a new AVD with target API Level 17 (the only one available after the standard setup it seems). None of the pre-existing AVDs work, however, only the new one (the old ones all use target APIs lower than 17).

Elias Mossholm
  • 150
  • 1
  • 11
4

The path to where it looks for the skin is in the ~/.android/avd/$deivce-name$.avd/config.ini

My issue like this occured because I had copied an avd to a different computer and the path was incorrect on that new computer.

grgrssll
  • 121
  • 1
  • 3
  • for me, an update to the android-emulator package moved the skins from `/opt/android-studio/plugins/android/resources` to `/opt/android-studio/plugins/android/lib`. `cd /opt/android-studio; find -name '*your_skin_name*'`... then A manual update of the paths in the avd's `config.ini` helped. – kubi Jan 05 '22 at 16:42
4

One solution, if you're happy to do this, is to not use a skin. To do this:

1> Tools/AVD Manager

2> Select the device

3> Click the pen icon in the "Actions" Column

4> Uncheck "Enable Device Frame"

Alternatively, if you want to select a preexisting skin, you can click on "Advanced Settings" and scroll down to the "Custom skin definition" drop down box.

And to see instructions on how to create a custom skin, you can click on "Advanced Settings" and scroll down to "How do I create a custom hardware skin", which links to here: https://developer.android.com/studio/run/managing-avds#skins

narco
  • 830
  • 8
  • 21
2

I had the same issue as I moved my avd files between systems and as in your case you have moved the relevant files. So the solution as to go to the .android folder and make changes to the files with .ini of conf in their names. In there you will see that the paths to various resources are different as a result of the move you made. So put in the correct path values.

That was how I solved mine.

George Udosen
  • 906
  • 1
  • 13
  • 28
1

You may need to update your AVD manager. WVGA800 is the default skin for the emulator. You might try to update your software

BlackHatSamurai
  • 23,275
  • 22
  • 95
  • 156
1

As you upgrade your Android Studio, the skin.path value can become no longer valid. The best approach is to copy the set of screens to your own folder path. This way the screens are in more permanent folders.

For example for Macbook:

  1. Find ~/Applications/Android Studio 1.5.1.0.app/Contents/plugins/android/lib/device-art-resources
  2. Copy device-art-resources folder to a place like ~/dev/device-art-resources
  3. For each config.ini in each of your avd folder, change skin.path value to point to the screen of your choice
david m lee
  • 2,547
  • 26
  • 14
1

For SDK-only installed

For who has not installed Android Studio but has only the SDK, to add a new device, or change a skin to an old device is

$ANDROID_HOME/tools/android avd
Ivan Buttinoni
  • 4,110
  • 1
  • 24
  • 44
1

My solution was to change the skin to nexus 5x !!

Paul Razvan Berg
  • 16,949
  • 9
  • 76
  • 114
0

I solved by uninstalling and reinstall the emulator.

In Android Studio, go to: Tools -> SDK Manager Appearance & Behavior -> System Settings -> Android SDK SDK Tools tab Uncheck the Android Emulator check box, and hit the Apply button. Do the same, checking the Android Emulator check box.

jon
  • 3,202
  • 3
  • 23
  • 35