Im having some weird issues setting up the SDK in eclipse, when i go to make a project i cant select anything in the build target. I have installed the eclipse plugin and the SDK but im not sure whats going on. Some help please, thanks!
You are not able to see the build target because you have not installed any Android virtual device in your AVD Manager.
AVD Manager is located at the same place where SDK Manager resides(in windows startmenu-programs-android SDK Tools)
Open AVD Manager with administrator privilege and install any build target you choose. Then try in the eclipse . It will work fine.
Related
While updating few latest packages in my Android Studio 2.1.1, two of the packages need me to 'Exit Android Studio and Launch Standalone SDK Manager' (see image link)
https://i.stack.imgur.com/9ueRW.png
How do I do that?
Also, Launch Standalone SDK Manager Option in the Tools> Android> SDKManager file doesn't work.
Please help!
You can try going to C:\Users\YourName\AppData\Local\Android\sdk from command prompt and launch SDK Manager.exe
You can open it from your sdk path which in my case is
C:\Users\Akshay\AppData\Local\Android\sdk
Double click on SDK Manager.exe and it will open standalone SDK manager, refer attached Screenshot.
It appears that you can no longer open the standalone SDK or AVD Manager in the later versions of Android Studio. At least, that appears to be the case for for Android Studio 3.0 beta versions. I did read a post where someone claimed that the standalone versions have been deprecated. Navigating to Android Studio SDK location and double clicking on either "SDK Manager" or "AVD Manager" doesn't bring up the standalone managers anymore. I believe that's the way its intended to work. I have read that some people have downloaded and installed the Android SDK independent of Android Studio and are able to bring up a standalone version. I've not tried this since I'm not exactly sure where one would get an official Android SDK. The official site has it bundled with android studio. They only reason I was trying to bring up a standalone version was that someone suggested that if it could be used to install the Oriel Google play x86 emulator, which apparently doesn't give the bogus "Emulator: qemu-system-i386.exe: goldfish_battery_read: Bad offset .. " errors. It's just a nuisance error message so I wasn't that interested in seeing this that would eliminate that bogus error message. I've installed that emulator using the SDK manager in Android Studio itself, but I'm not able to configure an emulator that uses it using the built in AVD Manager. Not sure why, but it is after all a beta version of Android Studio.
I'd installed HAXM emulator but am still getting the problem in Running AVD.
provide me a solution for this error?
your android SDK has an incomplete update , specifically the HAXM installer for running the emulator is corrupted some how.
You need to reinstall the required platforms and the system images for those platforms
Go to the local.properties and change the sdk path to the new sdk (if downloaded from scratch), otherwise it will work if the current sdk is updated perfectly.
I inadvertently accepted android studio's upgrade suggestion to 2.3 (canary), although I had always had it set to check for the developer channel, not canary, somehow that got switched. Now I no longer have a 'Launch Standalone SDK Manager' option in my 'SDK Manager' window.
I liked the standalone manager for various reasons, including that it suggested what needed to be downloaded and upgraded. The regular sdk manager lists a lot of things I expect I don't need like 'CMake', 'LLDB', 'Constraint Layout for Android', 'Solver for ConstraintLayout', 'Google Play APK Expansion Library' ('Google Play APK Expansion Library rev 3' is already installed, so do I need this too?), etc.
Is the standalone sdk manager unavailable for 2.3 canary 2, or is there something more I need to do to get it?
I also have updated to the Canary version 2.3 and I'm amazed that they took it away there.. but you can still start it via the SDK Manager.exe located in your sdk folder
C:\Users\You\AppData\Local\Android\sdk
Present:Today when i was trying to launch, the terminal says, The android command is no longer available.
For manual SDK and AVD management, please use Android Studio.
Past:
I also face the problem after updating to Canary version 2.3 on my mac.. On Mac or Linux, open a terminal and navigate to the tools/ directory in the location where the Android SDK is installed, then execute android sdk
or for only mac user go to folder located in
/Users/your mac account name/Library/Android/sdk/tools
and double click android to Launch Standalone SDK Manager
My Advice: Stop Searching for Launch Standalone SDK Manager and get use to be of android studio SDK manager and just choose the Show Package Details for more detailed description like Launch Standalone SDK Manager.
With the 2.3 Canary update, when using SDK Manager.exe or tools/android.bat, no manager is opened. However tools/android.bat give a pretty good answer to why it is not working:
The "android" command is no longer available.
For manual SDK and AVD management, please use Android Studio.
For command-line tools, use
tools\bin\sdkmanager.bat and tools\bin\avdmanager.bat
We can still use command-line tools, but no more standalone SDK manager.
Yes, "Launch Standalone SDK Manager" option in Android Studio V2.3 is not available, But you can still start it via SDK Manager.exe located in your sdk folder.
c:\Users\You_User_Account_Name\AppData\Local\Android\SDK Manager.exe
Enjoy Android Studio with new features.
I just received an official response from AOSP -
Project Member #1 uchid...#google.com
deprecated feature , please check latest stable version Android 2.3
The link is now gone, and it is intentional.
Yes the standalone sdk manager option is missing in Android Studio 2.3. Get yourself used to the sdk manager available in Android Studio settings.
Also if you are installing Android Studio from scratch, you will not be available to find Sdk Manager.exe from C:\Users\You\AppData\Local\Android\sdk or anywhere you install it.
Today, I decided to try Android Studio. When opening AVD Manager from the Tools > Android > AVD Manager menu on Android Studio, the list shows that the AVD named DroidBox fails because of "Unknown target android-16". I created that Virtual Device back when I used Eclipse for Android programming.
I have android-16 downloaded on my system (I know the path to the dir, and it has worked before), but apparently the location isn't being seen.
How can I tell AVD Manager where to find the directory?
you can set the path for same sdk that you were using with Eclipse. Just follow these steps:
File-> Project Structure->Android SDK location.
Under Android SDK location, browse for you sdk that you are using with eclipse. Yoy may need to re-start Android Studio to take effect! i m using A.S 0.8.6!
Even I had faced the same problem. Tools -> AVD Manager -> Create Virtual Device just adds the Virtual device. Underlying SDK (=~ Android OS selected while creating the Virtual device) should be separately installed.SDK can be installed from Tools -> SDK Manager.
Android Studio looks for different directories than Eclipse. From Android Studio, run the SDK Manager and verify that marks API 16 as installed. If not just install it and that should work
I'm running Eclipse Juno and have installed the SDK manager for Android for the Mac OS. Things seemed to be going fine, could import old projects as new Android app.
The problem is I can't find the AVD manager. I went to Windows-> and I do not see options for SDK manager or AVD manager.
I went to run a project and it asked me to create a device using the AVD manager, so it's installed, I used it. Is my set up incorrect? Does the latest version of Eclipse just not have it?
I was using the wrong version of Eclipse. You need to install Eclipse per usual, download the Android SDK, then use the one in the version in the adt-bundle-mac directory. That one is the one with the version of Eclipse with the Android plugins. Just answered this for anyone else who is having this problem.