The avdmanager is a command line tool that allows you to create and manageAndroid Virtual Devices (AVDs) from the command line. An AVD lets you define thecharacteristics of an Android handset, Wear OS watch, or Android TV devicethat you want to simulate in the Android Emulator.

• Virtual Device Manager
• Android Virtual Devices Download

If you're using Android Studio, then you do not need to use this tool and youcan insteadcreate and manage AVDs from the IDE.

After typing cordova run android in terminal, I'm getting this error:Waiting for emulator to start.PANIC: Broken AVD system path. Check your ANDROIDSDKROOT value /Users/username/Library. Mac-os-x avd-manager. Improve this question. Follow edited Nov 28 '19 at 10:07. Asked Nov 22 '19 at 10:14. Mars Robertson Mars Robertson.

The avdmanager tool is provided in the Android SDK Tools package (25.3.0 andhigher) and is located in android_sdk/tools/bin/.

Syntax

Global options

Global option	Description
-s	Silent mode: only errors are printed out
-h	Usage help
-v	Verbose mode: errors, warnings and informational messages are printed.

Virtual Device Manager

Commands and command options

Command and options	Description
create avd -n name -k 'sdk_id' [-c {path|size}] [-f] [-p path]	Create a new AVD. You must provide a name for the AVD and specify the ID of the SDK package to use for the AVD using sdk_id wrapped in quotes. For example, the following command creates an AVD named test using the x86 system image for API level 25: The following describes the usages for the other options: -c {path|size}: The path to the SD card image for this AVD or the size of a new SD card image to create for this AVD, in KB or MB, denoted with K or M. For example, -c path/to/sdcard/ or -c 1000M. -f: Force creation of the AVD. Use this option if you need to overwrite an existing AVD with a new AVD using the same name. -p path: Path to the location where the directory for this AVD's files will be created. If you do not specify a path, the AVD will be created in ~/.android/avd/.
delete avd -n name	Delete an AVD. You must specify the AVD with name.
move avd -n name [-p path] [-r new-name]	Move and/or rename an AVD. You must specify the AVD with name. The following describes the usages for the other options: -p path: The absolute path to the location at which to create the directory where this AVD's files will be moved. If you do not include this argument, the AVD will not be moved. You might choose not to include this argument if you want to rename the AVD in place. -r new-name: The new name of the AVD if you want to rename it.
list [target|device|avd] [-c]	List all available targets, device definitions, or AVDs. If you do not specify target, device, or avd, avdmanager lists all three. Include the -c argument to receive a compact output, suitable for scripts. The -c argument is not available when listing all three options together.

Once you install Android Studio, it's easy to keep the Android Studio IDEand Android SDK tools up to date with automatic updatesand the Android SDK Manager.

Update your IDE and change channels

Android Studio notifies you with a small bubble dialog when anupdate is available for the IDE, but you can manuallycheck for updates byclicking Help > Check for Update (on Mac, AndroidStudio > Check for Updates).

Updates for Android Studio are available from the followingrelease channels:

• Canary channel: These are bleeding-edgereleases, updated roughly weekly, and available for download atdeveloper.android.com/studio/preview.

  In addition to receiving canary versions of Android Studio, you will also receive previewversions of other SDK tools, including the Android Emulator.

  Although these builds are subject to morebugs, they do get tested and we want to offer them so you can try newfeatures and provide feedback. This channel is not recommended forproduction development.

• Dev channel: These are hand-picked canary builds thatsurvived a full round of internal testing.
• Beta channel: These are release candidates based on stablecanary builds, released to get feedback before going into thestable channel.
• Stable channel: The official stable release that isavailable for download atdeveloper.android.com/studio.

If you'd like to try one of the preview channels (Canary, Dev, or Beta)while still using the Stable build for your production Android projects, youcan install both side by side.

To change the update channel for an existing install, proceed as follows:

1. Open the Preferences window by clickingFile > Settings (on Mac, Android Studio >Preferences).
2. In the left panel, click Appearance & Behavior >System Settings > Updates.
3. Be sure that Automatically check for updates is checked, then select a channel from the drop-down list (see figure 1).
4. Click Apply or OK.

Figure 1. The Android Studio Updatespreferences.

Delete unused Android Studio directories

When you run a major version of Android Studio for the first time, it looks for directories containing caches, settings, indices, and logs for versions of Android Studio for which a corresponding installation can’t be found. The Delete Unused Android Studio Directories dialog then displays locations, sizes, and last-modified times of these unused directories and provides an option to delete them.

The directories Android Studio considers for deletion are listed below:

• Linux: ~/.AndroidStudio[Preview]_version_
• Mac: ~/Library/{Preferences, Caches, Logs, Application Support}/AndroidStudio[Preview]_version_
• Windows: %USER%.AndroidStudio[Preview]_version_

Update your tools with the SDK Manager

The Android SDK Manager helps you download the SDK tools, platforms, andother components you need to develop your apps. Once downloaded, you can findeach package in the directory indicated as the Android SDK Location,shown in figure 2.

To open the SDK Manager from Android Studio, click Tools >SDK Manager or click SDK Managerin the toolbar. If you're not using Android Studio, you can download toolsusing the sdkmanager command-line tool.

Android Virtual Devices Download

When an update is available for a package you already have, a dash appears in the check box next to the package.

• To update an item or install a new one, click the check boxso it shows a checkmark.
• To uninstall a package, click to clear the check box.

Pending updates are indicated in the left column with a download icon. Pending removals areindicated with a red cross .

To update the selected packages,click Apply or OK, then agree to anylicense agreements.

Figure 2. The Android SDK Manager.

Recommended packages

You should give special consideration to the following toolsin the SDK Tools tab:

Android SDK Build-Tools

Required. Includes tools to build Android apps. See the SDK Build Tools release notes.

Android SDK Platform-Tools

Required. Includes various tools required by theAndroid platform, including the adb tool.

Android SDK Tools

Required. Includes essential tools such as ProGuard. See the SDK Tools Release Notes.

Android Emulator

Recommended. A QEMU-based device-emulation tool that you can use to debug and test your applications in an actual Android runtime environment. See the Android Emulator release notes.

Note: Most API libraries that were previously provided by theSupport Repository packages (such as the Android Support Library, Constraint Layout,Google Play services, and Firebase) are now instead available from Google's Maven repository.Projects created with Android Studio 3.0 and higher automatically include this repository in thebuild configuration. If you're using an older project, you must manually add Google's Maven repository to yourbuild.gradle file.

In the SDK Platforms tab, you must also install at least oneversion of the Android platform. Each version provides several differentpackages. To download only those that are required, click the check box nextto the version name.

To see all available packages for each Android platform, clickShow Package Details at the bottom of the window.Within each platform version, you'll find the following packages:

Android SDK Platform

Required.At least one platform is required inyour environment so you're able to compile your application. In order toprovide the best user experience on the latest devices, use the latest platformversion as your build target. You'll still be able to run your app on olderversions, but you must build against the latest version in order to use newfeatures when running on devices with the latest version of Android.

Intel or ARM System Images

Recommended. The system image is required in order to run the Android Emulator. Each platform versioncontains the supported system images. You can also download system images laterwhen creating Android Virtual Devices (AVDs) in the AVD Manager. Select either Intelor ARM based on your development computer's processor.

Note: If you plan to use APIs fromGoogle Playservices (including Firebase), you must use either the Google APIs system imageor the Google Play system image (the latter includes the Play Store app).

The above list is not comprehensive and you can add other sites to download additional packagesfrom third parties.

In some cases, an SDK package may require a specific minimum revision ofanother tool. If so, the SDK Manager notifies you with a warning and addsthe dependencies to your list of downloads.

Tip: You can also customize thebuild.gradle file so each project uses a specific build chain andcompilation options. For more information see, Configuring Gradle Builds.

Edit or add SDK tool sites

To manage which SDK sites Android Studio checks forAndroid tools and third party tool updates, click the SDK Update Sitestab. You can add other sites thathost their own tools, then download the packages from thosesites.

For example, a mobile carrier or device manufacturer might offer additionalAPI libraries that are supported by their own Android-powered devices. Todevelop using their libraries, you can install their Android SDK packageby adding their SDK tools URL to the SDK Manager in theSDK Update Sites.

If a carrier or device manufacturer has hosted an SDK add-on repository fileon their website, follow these steps to add their site to the Android SDKManager:

1. Click the SDK Update Sites tab.
2. Click Add at the bottom of the window.
3. Enter the name and URL of the third party site, then click OK.
4. Make sure the checkbox is selected in the Enabledcolumn.
5. Click Apply or OK .

Any SDK packages available from the site now appearin the SDK Platforms or SDK Tools tabs,as appropriate.

Auto-download missing packages with Gradle

When you run a build from the command line, or when using Android Studio 3.3 or later, Gradle can automatically download missing SDK packages that a project depends on, as long as the corresponding SDK license agreements have already been accepted using the SDK Manager.

When you accept the license agreements using the SDK Manager, Android Studio creates a licenses directory inside the SDK home directory. This licenses directory is necessary for Gradle to auto-download missing packages.

Note: Accepting the license agreements using the android command line tool does not create this licenses directory. You must first accept the agreements using the SDK Manager to be able to use this feature.

If you have accepted the license agreements on one workstation, but wish to build your projects on a different one, you can export your licenses by copying over the accepted licenses directory. To copy the licenses to another machine, follow these steps:

1. On a machine with Android Studio installed, click Tools > Android > SDK Manager. At the top of the window, note the Android SDK Location.
2. Navigate to that directory and locate the licenses/ directory inside it. (If you do not see a licenses/ directory, return to Android Studio and update your SDK tools, making sure to accept the license agreements. When you return to the Android SDK home directory, you should now see the directory.)
3. Copy the entire licenses/ directory and paste it into the Android SDK home directory on the machine where you wish to build your projects.

Gradle will now be able to automatically download missing packages your project depends on.

Note that this feature is automatically disabled for builds you run from Android Studio, as the SDK manager handles downloading missing packages for the IDE. You can also manually disable this feature by setting android.builder.sdkDownload=false in the gradle.properties file for your project.