I have downloaded the latest Android Studio and when I run studio64.exe it opens Android Studio as a standalone application, however I would like to install it to my system.
The website says there is an installation wizard however I get taken straight to the Android Studio start screen. Is there still a way to install it on a Windows machine?
Turns out that Android Studio is now portable - like Eclipse. In other words, there is no installing, you just get the zip file, which contains everything you need, such as the executables that run Android Studio. You'll need to store this folder somewhere relevant and create a shortcut to the studio(64).exe file to run it from desktop/start menu.
The SDK is also no longer bundled with Android Studio, so that will need to be downloaded separately.
As of this post the Android Studio installation instructions by Google are out of date.
you can get the sdk manager as stand alone installer.once installed you need to run it as "administrator", than only it will be able to download and install packages and api's. follow the given below link:
http://dl.google.com/android/installer_r23.0.2-windows.exe
Check if its in compatible mode with your OS version of your machine. Right click on the downloaded bundle > Move to properties> Compatibility tab> Select Compatibility tab> Tick the check-box- Run in Compatibility mode> Select your OS version from the drop down.
You will get the set up wizard :)
Worked for me :)
I am following a basic MyFirstApp tutorial for creating an Android App, but am having trouble getting the emulator to work. I am using Eclipse (on OS X) and was told to go to the Android Virtual Device Manager and select an AVD name, select Nexus 7 (2012) (7.0", 800 x 1280: tvdpi) as the Device name, and select Android 4.2.2 (API 17) as the device target. Problem is, even though 4.2.2 has been installed, it is not showing up on the list.
The only target option I currently have available is Android 4.4W - API Level 20. In addition to that, the CPU/ABI option is greyed out, saying "No system images installed for this project." The OK button is also greyed out. According to the SDK manager, though, everything necessary for 4.2.2 and 4.4W has been successfully installed.
I have Eclipse and Android Studio installed, and have used both (though not successfully when it comes to emulators). Could that have caused an issue?
I am new to this and would appreciate any help in getting the emulator working. I've tried everything I can think of and every search I can think of, so now I need someone to help me out. Thank you!
try either :
restart eclipse
install ARM EABI v7a System Image under the Android 4.2 section from the SKD manager
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
I have installed Android Studio on my Windows 7 PC. But I cannot create the virtual devices on the studio as the button for AVD and SDK is disabled by default. How ca I enable them?
I haven't seen this error myself, but try going to
File -> Project Structure -> SDKs and make sure you have a listing for the Android SDK and that the home path is pointing to the correct location.
Well I found the problem. The gradle was not installed as my internet connection was not active. Make sure the Android Studio installs the gradle when you first start and create a project.
Go to the android-studio\sdk\tools\lib and search for AVD Manager and SDK Manager. If they are present, try running them.
While I do not know the actual reason for the disabled buttons, but this might just help in troubleshooting the problem.
I've to develop a simple Android app using the Cordova API(PhoneGap) and it requires Android 4.0.3 or higher versions (API Level 15 or above) to build the app on the emulator correctly.
But, when I give a build for the coded app, I happen to see that I get this below error message,
[2012-07-02 13:10:29 - SDK Manager] Unable to find a 'userdata.img' file for ABI armeabi to copy into the AVD folder.
On googling this problem, I came to know that I need to install the arm-eabi v7a system image onto my machine for this to run smoothly.
But the issue is that, unlike API 14, this is not appearing for API 15!
Below image shows the same:
Now, can anyone explain me how to fix this up, please? This is very peculiar to look at and re-installing the Manager/SDK/API Levels again and again was of no use.
Reference: Android SDK Manager is not showing ARM EABI v7a System Image option
Help is much appreciated!
Ideally this should not be the case.
For e.g. one does see the ARM EABI v7a System Image (API level 15) in the SDK Manager window.
You could try a few things:
Reinstall the SDK.
Alternatively, delete the ANDROID_SDK_INSTALL_FOLDER\system-images\android-15 folder and then install the SDK again and try.
What I have done is:
From the Android SDK Manager, I have installed the following options:
Platform SDK
ARM EABI V7A System Image
For the API to work you need to do the following steps:
close eclipse
Go to folder: ..\sdk\system-images
Open the folder for the system image you use. I can inside a folder called "default" and in "armeabi-v7a" only have to cut and move "armeabi-v7a" where the "default" and then "delete" default.
open eclipse