Android SDK AVD Error: null

Question

When I try to install the Android SDK on eclipse, I cannot create a new virtual device. I keep getting this error. [2011-05-28 12:05:16 - SDK Manager] Error: null. Is there any way I can fix this

How I fixed this problem deleted all the files in my workspace. Reset and it started to work.

Answer 1

same issue here in MAC OS X. Here is my configuration.

bigboy:platform-tools kaffein$ uname -a Darwin bigboy.home 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64 

Why

This is a problem with the resolution settings of your ~ / .android / avd. Since the settings and configurations of the virtual device emulator are written in this folder, SDK tools should be written in this directory (avd-manager in this case).

how

First check your permissions ~ / .android / avd with the ls Unix command (cd to your home directory):

 bigboy:~ kaffein$ ls -al .android/ drwxr-xr-x 5 kaffein staff 170 Jan 5 14:35 . drwxr-xr-x+ 53 kaffein staff 1802 Jan 5 21:22 .. -rw-r--r-- 1 root staff 123 Jan 5 14:08 adb_usb.ini -rw-r--r-- 1 root staff 131 Jan 5 14:35 androidwin.cfg drwxr-xr-x 2 root staff 68 Jan 5 12:48 avd 

The avd folder is owned by root. You can start by changing the owner of this folder yourself using the following command.

 bigboy:~ kaffein$ cd .android/ bigboy:.android kaffein$ sudo chown kaffein:staff * 

check again that you now own the folder using the following command:

 bigboy:.android kaffein$ ls -al total 16 drwxr-xr-x 5 kaffein staff 170 Jan 5 14:35 . drwxr-xr-x+ 53 kaffein staff 1802 Jan 5 21:22 .. -rw-r--r-- 1 kaffein staff 123 Jan 5 14:08 adb_usb.ini -rw-r--r-- 1 kaffein staff 131 Jan 5 14:35 androidwin.cfg drwxr-xr-x 2 kaffein staff 68 Jan 5 12:48 avd 

you should have an output like the one above (of course, kaffein should be your username)

Finally, you must change the permission settings in the avd / folder using the following command:

 bigboy:.android kaffein$ sudo chmod a+rw avd/ 

verify that you really changed the settings with the ls -al command.

 bigboy:.android kaffein$ ls -al total 16 drwxr-xr-x 5 kaffein staff 170 Jan 5 14:35 . drwxr-xr-x+ 53 kaffein staff 1802 Jan 5 21:22 .. -rw-r--r-- 1 kaffein staff 123 Jan 5 14:08 adb_usb.ini -rw-r--r-- 1 kaffein staff 131 Jan 5 14:35 androidwin.cfg drwxrwxrwx 2 kaffein staff 68 Jan 5 12:48 avd 

avd is now set to 777.

Final step

From your Eclipse IDE, open AVD Manager and try creating a virtual device. Taaadaaaa !!!! Everything should work ...

Hope this helps ...

Answer 2

Just for sharing, I got the error [2011-10-20 10:07:17 - SDK Manager] Error: null, and I solved the problem by setting the ANDROID_SDK_HOME environment variable on top of the control panel.

Start → Control Panel → System and Security → System → Advanced System Settings → Environment Variables → New

Variable name: ANDROID_SDK_HOME Variable value: (the path will be your preferred location of the .android folder, except for the last slash) For example: C: \ Users \ MyUserName

Hooray!

Answer 3

I had the same problem just now.

Running the android tool and trying to add AVD gave me the error "Allow rejection" in my ~ / .android folder (here Mac OS X).

I bet too much, but this solved the problem for me:

• Exit the android tool or Eclipse AVD Manager;
• Delete the .android directory;
• Launch the Android tool and try adding AVD.

Voila. With this, I was able to add new AVDs both using the tool (on first start) and in Eclipse.

I am sure that I somehow ruined the rights, and that the most correct solution to this problem is to fix the permissions of this directory.

Answer 4

If you still have this problem, I found a solution (on Windows 7). My console was giving me the same error, and Eclipse said that my Android sdk file was not in the right place, although it was - whenever I opened eclipse.

To fix this, right-click on your android-sdk folder, go to properties, security, and then in the "Group or usernames" list, make sure that each of them (especially the "trusted installer") has full permissions for the file - make sure all the "enable" boxes are checked. The next time you run the SDK Manager, you can download everything without a problem.

Answer 5

I also ran into this problem on Linux, I found that this is a resolution problem, I solved the problem by adding write permission to the eclipse user, you can also solve this problem by changing the file owner to the eclipse user, I hope you will benefit from this.

Answer 6

Nothing was suggested for me, I was still getting an error on my CentOS 7 server.

After some additional copying, I found out that the problem is with the creation of the SDCard:

 $ avdmanager -v create avd --force --name avd_5568 --package 'system-images;android-25;google_apis;x86' --sdcard 256M --abi google_apis/x86 --device "4in WVGA (Nexus S)" Warning: Failed to create the SD card. Warning: Failed to create sdcard in the AVD folder. Error: AVD not created. null 

And after a few more searches, I realized that I needed to establish some required dependency.

Essential libraries for 64-bit GNU / Linux machines :
If you are using the 64-bit version of Ubuntu, you need to install the 32-bit libraries with the following command:

 sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1 libbz2-1.0:i386 

If you are using 64-bit Fedora, the command:

 sudo yum install zlib.i686 ncurses-libs.i686 bzip2-libs.i686 

Answer 7

Not sure if this is your problem, but I saw how this happens when the SDK manager looks for the wrong directory for Android Virtual Devices. I would double check this and make sure that it is correct, you will see it at the top of the Android SDK and AVD Manager.

Answer 8

I think your problem is that you cannot create a virtul device correctly?

The easiest way to create an AVD is to use the graphical AVD manager, which you launch from Eclipse by clicking Window> Android SDK and AVD Manager.


You can also launch AVD Manager from the command line by calling the android tool in the Android SDK.for tool directory of the guide / developing / tools / emulator.html commands, you should see this video and then -android-emulator-managing-android-virtual-devices -avd

Answer 9

Did you solve the problem? I had a similar problem on my Mac, but I solved it last night. I did not record access to my disk with a user account, which made it impossible to start the virtual machine. So I changed my read / write permission, which solved the problem.

Answer 10

I have the same problem. I downloaded the SDK (for Windows 64bits) from the Android developer website, when I created the AVD, I got an error: "[2013-03-14 ... SDK manager] error: null".

Run Eclipse.exe as administrator, then it works, I can create AVD.

Answer 11

I had the same problem. Check steps:

• The Sdk manager itself may be corrupted, so it is recommended that you save the backup and use it to check if there is a problem with the SDK manager

• Remove .android / avd from user / profile

• Remove metadata from your workplace. Make sure you take a backup.

• change workplace

• check .android privileges, you should be able to read records, if not, give the option to read records

Answer 12

The fastest way I found: Ubuntu 12.04 1. Go to the home folder 2. Ctrl + H (show hidden file and folders) 3. Right-click → Open in terminal

  // shows ownership for the android hidden folder your-machine:~$ ls -l .android/ // change ownership to you your-machine:~$ sudo chown yourUserName.yourUserName -R .android/ 

& try to create a new AVD

Answer 13

If you cannot create an AVD device:

• Check the .android folder and cross-checking if you have all the files that should be there ( adbkey , androidtool.cfg , ddms.cfg , debug.keystore , default.keyset ). Make sure adbkey.pub and debug.keystore .
• Go to your eclipse and run it as admin OR
• Go to the SDK folder and right-click. → go to properties → security
• Now click on each category of users in the list of group name lists and click "Edit."
• Make sure that they all have absolute permission or, rather, full control. (all flags should be checked)
• Now go back to sdkmanager.exe and right click -> properties -> security and repeat with 5.

Answer 14

This happened to me when I updated a few weeks ago.

Try this in Eclipse:

For Mac OS X

Window> Configure Vista ... (you will see that Android and AVD Manager are disabled)

now click on the "Command Group Availability" tab> Android and AVD Manager> check

Toolbar visibility> Android and AVD Manager> check

Now you can see the AVD Manager item in the Eclipse toolbar.

Hooray!!

Answer 15

I have one solution for those who can not create avd after changing the .android \ file to another disk, no permissions are needed.

do the following: after moving the .android file to another drive folder, for example

1: go to sdk folder → tools

2: Now double-click the android.bat file - sdk manager will start

3: Now go to the "Tools" tab and select "Manage AVD" - now the launch of the avd manager will begin

4: now create avd-avd in your folder with a specific outline.

5: restart the eclipse if you don’t start or run eclipse,

Now you can create avd in the specified drive folder.