Can't find AVD Manager in Mac OS - android

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.

Related

Android studio is not properly installed

extra android m2 repository,extra google m2 repository and 2 more sdk components were not installed.
This message was displaying after the installation of Android studio.
Some components as Android sdk manager and AVD are not working properly.
Please guide me how to fix the problem.
Try to open Android SDK Manager and Select Android SDK Tools and Android SDK Platform-tools and update and then restart Android SDK Manager you will find Extras now install Android Support Repository inside Extras.If this doesn't help i guess you have to Re-install the software while reinstalling keep your internet connection on it may download packages and files form internet.
See to it that you have downloaded Android SDK properly without any issue.
I hope this answer helps..

Android studio 2.3 canary missing 'Launch Standalone SDK Manager' option in 'SDK Manager'

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.

Android Unknown Command 'crunch'

I just installed Eclipse and Android SDK in Mac OS X.
I imported the project to Eclipse and i get the Unknown command 'crunch' error while running the project.
How should I solve this issue.
Please help me
I just update
"Android SDK Platform-Tool" to 8 Rev and "Android Asset Packaging Tool"
from android sdk manager,
and then it works.
Have a try!
After updating to ADT r14, go to Window -> SDK Manager (in Eclipse)
Check on 'repository', uncheck "installed"
Wait for packages to load, then select all support packages, accept all and install them
Restart Eclipse
Run your apps on new ADT r14, without 'crunch' errors
Worked for me :)
Updating Android SDK Tools to r14 and Android SDK Platform-tools to r8 also solved this problem for me.
I had to check 'Installed' in the SDK Manager in order for the updates to be listed (even though I had the previous versions already installed). Checking only the New/Updates box meant they wouldn't show up in the list.
Go to Window -> Andriod SDK Manager (in Eclipse)
Check on 'repository', uncheck "installed"
Wait for packages to load, then select all support packages, accept
all and install them
Restart Eclipse
I had the same issue.
To fix it :
- Uninstall the current sdk tools (Android SDK Tools and Android SDK Platform-tools) in the Android SDK Manager
- Reinstall them at their last version (r14).
I encountered this kind of problem also, when updating SDK,
The solution was to re-enter the SDK folder path to the Eclipse.
(For some reason, the new SDK was instaslltion was in a diffrent folder from the original one)
For me, what worked was a combination of what Androgeek and tinyau said.
Summing up. I needed to update both my Android SDK Tool and Support Tools and restart eclipse.

Android SDK setup help

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.

Android:Android SDK and AVD Manager doesn't launch after did SDK upgrade?

I have Android development eclipse setup on Mac OS X. I recently did Android SDK upgrade from 1.5 to available versions such as 1.6, 2.0.1 and 2.1 and docs. After did upgrade, automatically restarted my Macbook and installed all new versions. After this, when i try to launch "Windows->Android SDK and AVD Manager", it doesn't launch at all. What might be the reason? Does anyone has the solution?
The reason why i'm trying to launch Android SDK and AVD Manager is, i need to add new Android virtual device(avd) target for 2.0.1 and 2.1 versions, for that i'm trying to launch Android SDK and AVD Manager.
Thank you in advance.
It seems the latest version of the Android SDK AVD Manager requires that there be a few directories (empty) before the AVD Manager will launch.
In the SDK install directory, there must be sibling directories to tools for "platforms" and "add-ons".
Create those directories, restart Eclipse, then launch AVD Manager.
And that should do it.
Then You can Update All and get platforms.
Well this is actually caused by the fact that android is installed on c:\program files folder (the commands executed by android consider that the called folder is c:\program which is a non existent folder and this issue is due to the space in the name of this folder).
So the solution is to reinstall your program under a folder with non spaced name (for example c:\Android) and it should be fine.
Note: this problem can also be related to a problem of jre problem so make sure you have the appropriate version for android sdk.
Have you tried launching Eclipse with the -clean option?
The clean option clears any cached data Eclipse might be using, so it may resolve the SDK/AVD Manager issue you are encountering.
Here is a more in-depth explanation:
http://www.eclipsezone.com/eclipse/forums/t61566.html
Here is one example of launching Eclipse from a command line (Terminal) in OSX with the -clean option:
http://www.brooksandrus.com/blog/2007/06/30/run-eclipse-from-the-command-line-on-os-x/
You might have to update your "SDK tools" as well as downloading the Android v2.1 SDK itself. I had the problem where after downloading v2.1, suddenly nothing worked as I got the message I needed to update to SDK tools rev5 - that update doens't happen automatically when you go to the AVD manager and download the "available packages". I don't know if it's the same on a Mac, but on the PC it was as simple as going to "Help -> Check for Updates" in Eclipse.
the newer version of the SDK tools is probably in a different folder than the old version, so update
Window -> Preferences -> SDK Location.
Paul
Check the install is ok by running the commands from the tools directory manually to check it's not an issue with the install
I had a similar problem and traced it to a faulty swt.jar file in the folder
[adroid_sdk]\tools\lib[platform]
Downloaded a new one from http://www.eclipse.org/swt/ and put all the files into the above directory. For me [platform] was "x86", but it might be different for you, though I only had 3 folders to choose from and I dont think it will hurt if you put the files in all of them.

Categories

Resources