If you receive an error or warning message at the top of the dialog, click the link to correct the problem or to get more information. If you don't have this file, enter the following command in a terminal window:. While the emulator is running, you can run Android Studio projects and choose the emulator as the target device. You can also drag one or more APKs onto the emulator to install them, and then run them.
Run the Android Emulator directly in Android Studio to conserve screen real estate, to navigate quickly between the emulator and the editor window using hotkeys, and to organize your IDE and emulator workflow in a single application window. To run the emulator in Android Studio, make sure you're using Android Studio 4. Currently, you can't use the emulator's extended controls when it's running in a tool window. If your development workflow depends heavily on the extended controls, continue to use the Android Emulator as a standalone application.
In addition, certain virtual devices—such as Android TV and foldable devices—can't be run in Android Studio because they have specialized UI requirements or important functions in the extended controls.
An APK Installer dialog appears. When the installation completes, you can view the app in your apps list. To add a file to the emulated device, drag the file onto the emulator screen. You can view the file from Android Studio using the Device File Explorer , or find it from the device using the Downloads or Files app, depending on the device version. A snapshot is a stored image of an AVD Android Virtual Device that preserves the entire state of the device at the time that it was saved — including OS settings, application state, and user data.
You can return to a saved system state by loading a snapshot whenever you choose, saving you the time of waiting for the operating system and applications on the virtual device to restart, as well as saving you the effort of bringing your app back to the state at which you want to resume your testing.
Starting a virtual device by loading a snapshot is much like waking a physical device from a sleep state, as opposed to booting it from a powered-off state. The simplest way to take advantage of snapshots is to use Quick Boot snapshots: By default, each AVD is set to automatically save a Quick Boot snapshot on exit and load from a Quick Boot snapshot on start. The first time that an AVD starts, it must perform a cold boot , just like powering on a device. If Quick Boot is enabled, all subsequent starts load from the specified snapshot, and the system is restored to the state saved in that snapshot.
Snapshots are valid for the system image, AVD configuration, and emulator features with which they are saved. When you make a change in any of these areas, all snapshots of the affected AVD become invalid.
Most controls for saving, loading, and managing snapshots are in the Snapshots and Settings tabs in the Snapshots pane in the emulator's Extended controls window. You can also control the Quick Boot options when starting the emulator from the command line. When you close an AVD, you can specify whether the emulator automatically saves a snapshot when you close.
To control this behavior, proceed as follows:. Use the Auto-save current state to Quickboot drop-down menu to select one of the following options:. Yes : Always save an AVD snapshot when you close the emulator. This is the default. Your selection applies only to the AVD that is currently open.
To save a general snapshot, open the emulator's Extended controls window, select the Snapshots category, and click the Take snapshot button in the lower-right corner of the window. To edit the name and description of the selected snapshot, click the edit button at the bottom of the window. To manually delete a snapshot, open the emulator's Extended controls window, select the Snapshots category, select the snapshot, and click the delete button at the bottom of the window.
You can also specify whether you would like the emulator to automatically delete snapshots when they become invalid, such as when the AVD settings or emulator version change. By default, the emulator will ask you if you'd like for it to delete invalid snapshots. You can change this setting with the Delete invalid snapshots menu in the Settings tab of the Snapshots pane.
To load a snapshot at any time, open the emulator's Extended controls window, select the Snapshots category, choose a snapshot, and click the load button at the bottom of the window. In Android Studio 3. Use your computer mouse pointer to mimic your finger on the touchscreen; select menu items and input fields; and click buttons and controls.
Use your computer keyboard to type characters and enter emulator shortcuts. To perform common actions with the emulator, use the panel on the right side, as described in table 2. You can use keyboard shortcuts to perform many common actions in the emulator. To pan in zoom mode, hold Control Command on Mac while pressing the arrow keys on the keyboard.
The screen recording controls are in the Screen record tab of the Extended Controls window. To begin screen recording, click the Start recording button in the Screen record tab. To stop recording, click Stop recording. Controls for playing and saving the recorded video are at the bottom of the Screen record tab. You can also record and save a screen recording from the emulator using the following command on the command line:.
To take a screenshot of the virtual device, click the Take screenshot button. By default, the screenshot is saved on your computer desktop. To change the location to which screenshots are saved, use the Screenshot save location control in the Settings category in the emulator's Extended controls window. The emulator supports the use of basic camera functionality on your virtual device for earlier Android versions.
Android 11 and higher supports the following additional Android Emulator camera capabilities:. You can use the virtual scene camera in a virtual environment to experiment with augmented reality AR apps made with ARCore. For information on using the virtual scene camera in the emulator, see Run AR apps in Android Emulator.
This feature can be used to import custom images such as QR codes for use with any camera-based app. For more information, see Add Augmented Images to the scene. You can greatly reduce the time it takes to test common AR actions by using the preset macros in the emulator.
For example, you can use a macro to reset all the device's sensors to their default state. Before using macros, follow the steps in Run AR apps in Android Emulator to set up the virtual scene camera for your app, run your app on the emulator, and update ARCore.
Then, follow these steps to use emulator macros:. Use the extended controls to send data, change device properties, control apps, and more. To open the Extended controls window, click More in the emulator panel. You can use keyboard shortcuts to perform many of these tasks.
The emulator lets you simulate "my location" information: the location where the emulated device is currently located. For example, if you click My Location in Google Maps and then send a location, the map shows it.
Controls for the device's location information are organized under two tabs: Single points and Routes. In the Single points tab, you can use the Google Maps webview to search for points of interest, just as you would when using Google Maps on a phone or in a browser. When you search for or click on a location in the map, you can save the location by selecting Save point near the bottom of the map. All of your saved locations are listed on the right side of the Extended controls window.
To set the emulators location to the location you have selected on the map, click the Set location button near the bottom right of the Extended controls window. Similar to the Single points tab, the Routes tab provides a Google Maps webview that you can use to create a route between two or more locations. Crafting Educational Materials.
Running in the Browser. Setting up Continuous Integration. Testing on physical devices. Troubleshooting Proxies. Using ClojureScript. Using Styled Components. Native Firebase. Sharing preview releases. Expo Accounts Account Types. Two-Factor Authentication. Programmatic Access. Working Together. Bare Workflow Up and Running.
Installing Expo modules. Installing expo-updates. Supported APIs. More about the APK Analyzer. More about the emulator. More about the editor. More about the build tools. More about the profilers. Chrome OS For information on recommended devices and specifications, as well as Android Emulator support, visit chromeos. Thank you for downloading Android Studio!
Download Android Studio Introduction 1. Accepting this License Agreement 2. If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity. SDK License from Google 3. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose.
Google reserves all rights not expressly granted to you. Except to the extent required by applicable third party licenses, you may not copy except for backup purposes , modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK. You agree that Google may stop permanently or temporarily providing the SDK or any features within the SDK to you or to users generally at Google's sole discretion, without prior notice to you.
Use of the SDK by You 4. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. Install and run your apps faster than with a physical device and simulate different configurations and features, including ARCore, Google's platform for building augmented reality experiences.
Powered by Gradle, Android Studio's build system allows you to customize your build to generate multiple build variants for different devices from a single project. The built-in profiling tools provide realtime statistics for your app's CPU, memory, and network activity.
0コメント