AVD Manager on Android Studio 1.5.1 and installation in a custom place emulator will not work

Question

I installed Android Studio (1.5.1 - see image for assembly details).

During installation, I selected a custom option to set a specific path. I knew that my% SystemDrive% was located in a network location, and I wanted to install it on a local drive.

So this means that by default the application would install: \ networkPath \ Users \ MyUserName \ Android \ SDK

However, since I selected a custom installation, I chose the local path: C: \ Users \ MyUserName \ Android \ SDK

Creation and construction of the Fine project

Everything seemed fine, and I was able to create a new project and create it without any problems.

However, when I tried to run the built, and then basically failed silently. The emulator never appeared and no errors occurred. Android Monitor simply displays a message stating that No Connected Device is detected. AVD Manager

Fortunately, I knew a little about checking what happened to the emulator, and I opened AVD Manager. The specified device displays an error. I right-click on the device and select View Details. This is when the AVD manager showed that it was trying to read from the network path, although I changed it in a custom installation. \ networkPath \ Users \ MyUserName \ Windows.android \ AVD \ Nexus4.avd as well as \ networkPath \ Users \ MyUserName \ Windows.android \ AVD \ Nexus4.ini

Registry Editing

I closed Android Studio. Then I opened regedit and edited the values ​​at: HKLM \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Profile List which initially looked like this:

And change them so that they all point directly to the c: \ drive (instead of% systemdrive%)

Environment variable: ANDROID_SDK_HOME

I found that others mentioned the ANDROID_SDK_HOME environment variable, and I noticed that my machine does not have this value, so I added it and set it like this: C: \ Users \ MyUserName \ Android \ SDK

Then I launched Android Studio again and launched AVD Manager. There were no devices this time, but instead, AVD Manager asked me to create it with the following window:

Now I try to download one of the devices with the Google APIs, but every time I do this, they download and install successfully, but then disappear from the list. Note that in the following image, API level 15 or 16 APIs are not available for weapon architecture.

Please note that there is one specified for API level 17 with a handle. Now I will try to install it.

You can see that it has successfully downloaded and installed correctly. Now I click the [Finish] button. The item no longer appears in my list.

An API level 15 element is automatically selected. I guess, because that one was downloaded initially when I installed Android Studio.

Finally, if you uncheck the [] show box of downloadable system images, which is terribly confusing - and I assume that you show the ones you have already downloaded, then you will see that it shows only one Level 15 Virtual Appliance API.

This is terrible. Has anyone seen this problem? Could anyone else fix this?

I assume that I just need to go and perform a complete reinstall of Android Studio.

Answer 1

EDIT 2 with the final solution

Thanks to the warning and insight of SO post-er ( code-apprentice ), I was able to find a solution.

Here is what I had to do.

• create the idea.properties file and put it in the \ networkLocation \ myUserName \ .Android 1.5 \ folder
• put two lines in it that point to my local drive

idea.config.path = C: /Users/myUserName/.AndroidStudio1.5/config/ idea.system.path = C: /Users/myUserName/.AndroidStudio1.5/system/

Then I started up Android Studio again, and I tried to install a system image that included the Google APIs. It worked and it was added to the list:

However, it has not yet shown the other API levels that I installed earlier (15, 16, etc.).

Removed from disk

I noticed that they were located in a local folder at:% USERPROFILE% \ Android \ SDK \ add-on for any reason. I deleted all the folders under this path, and the original Google options APIs reappeared on my list. See Selected Item in Image.

SOLUTION Now that I install them, they appear in the list, and I can create new AVD based on them. Everything works.

EDIT I used a tool that I wrote to see where Android Studio wrote to disk, and I found a path that shows the problem:

Despite the fact that I have made significant changes to ensure the installation by fully installing my local drive, Android Studio will save some (a lot) of data along the way.

I did Google on: .AndroidStudio 1.5 \ config \ This led me to the following documentation: http://tools.android.com/tech-docs/configuration

There you will see that the installation should use% userprofile% to determine where it writes this data. My% userprofile% points to my local drive (c: \ users \ myUserName), but Android Studio still insists on writing data to the network.

Important information here: Windows:

%USERPROFILE%\.{FOLDER_NAME}\studio.exe.vmoptions and/or %USERPROFILE%\.{FOLDER_NAME}\studio64.exe.vmoptions %USERPROFILE%\.{FOLDER_NAME}\idea.properties 

I deleted the remote .Android Studio 1.5 directory and copied it to my% userprofile% (local) directory. Then I restarted Android Studio, and he thinks he needs to create all this again, because he wants to place it in the remote directory again.

The main problem :

Obviously it is not using% userprofile%

---

Is getting worse. I deleted the application and all the settings (presumably).

Then I installed everything again, and it looked as if it had chosen the correct default installation path:

But, when I started Studio, he opened the project that I created with the first installation.

Also, I still don't see the API image that I supposedly installed before. Only one image. Nothing more.

This is really not a great installation system. I am working on a book that helps Android Devs get started, but if they fall into this cycle of problems, there is no way to get them out of it with a good emulator.

Very unfortunate.

Answer 2

You should look in the idea.properties file in your project ( Android Studio path to various directories ). It looks like this is set to override system settings.

Answer 3

Download the appropriate SDK and API levels and Image Systems in the Android SDK Manager .

And then they will usually be displayed on the AVD .