Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. This topic contains information to help you resolve issues that you may experience when you're using the Visual Studio Emulator for Android.
When the emulator is installed, the setup program checks the prerequisites for running the software. It displays warnings if the prerequisites are not present, but it does not require them for installation.
Cannot connect to network destinations on a domain or corporate network. Cannot connect to network destinations when network settings require manual configuration. Emulator starts slowly, fails to start due to a timeout, or app deployment fails. Computer fails to boot after installing the Emulator.
Visual Studio gets stuck trying to deploy the app to the emulator or the emulator does not appear as a debug target in other IDEs. Emulator stops responding because it couldn't set up the UDP port. Emulator fails to run app that uses Google Play Services.
Drag and Drop of a file, APK, or flashable zip file does not work. Emulator does not respond to multi-touch gestures. If you don't have Hyper-V installed, you will see the following message when you try to install the emulator. You must have a machine that supports HyperV and it must be enabled. Windows 8. If you see this message, check the System requirements for the Visual Studio Emulator for Android to see whether you can run the emulator.
It is not joined to a Windows domain and it does not share domain or workgroup credentials with the host computer. If your network requires domain or workgroup authorization for basic network and Internet connectivity, contact your IT administrator for an exception. This exception allows your development computer to serve as a boundary machine and to accept connections from non-domain-joined network devices like the emulator.
If you can't access network or Internet resources from the emulator, check with your IT administrator to make sure that the emulator's MAC addresses have been authorized on your network. To connect to network destinations from the emulator, your network must meet the following requirements:. Automatically configured DNS and gateway settings.
It's not possible to configure DNS and gateway settings manually for the emulator. If your network requires manually configured settings, check with your IT administrator to determine how you can enable network connectivity for the emulator.
Under certain conditions, the emulator takes several minutes to start or fails to start due to a timeout. When the emulator fails to start, you see the following message: App deployment failed. Please try again. The following conditions can result in this error. This configuration is not supported. Not enough memory is available because of other running applications. Reduce the number of applications that are consuming memory or increase the amount of memory.
This feature enables x86 bit images for API levels 26 and lower to run with the headless build. Android Studio uses the kernel to select emulation engines. You can now run the emulator with previous binaries that use QEMU1 if the QEMU1 executables emulator[64]-[x86 arm etc] are placed in the emulator directory. Windows: Fixed an issue that could sometimes cause the emulator to fail to start with a "vCPU shutdown request" message.
Fixed an issue with an unnecessary pipeline barrier in emulated compressed textures in Vulkan. Fixed an error that occurred with http proxy requests when chunked transfer encoding was used. For more information, see the commit details. Multiple virtual hardware displays will be included in a future emulator system image update. Added a new command line option: -delay-adb.
This option suppresses processing of ADB packets until the guest has completed booting off a cold boot. This option helps resolve issues that could occur if you use the emulator in a CI environment that reboots the emulator and uses DDMS at the same time.
Fixed an error that occurred when snapshots are loaded where glIsRenderbuffer would return the incorrect value. Fixed some issues with stale state when the Android guest reboots. Known issues The Snapshots UI is disabled for Automotive system images because snapshots aren't currently supported for these system images. The following sections describe the Project Marble improvements that are included with this update: Improvements for host audio behavior Starting with version If you are using the command line, you can also enable host audio using the -allow-host-audio option, and you can use the following ADB commands to turn host audio data on or off, respectively: adb emu avd hostmicon adb emu avd hostmicoff Improvements for headless emulator builds Starting with version The system-dependent shared libraries that are not packaged with the emulator has been reduced to the following list: Linux-vdso.
To address issues with some Linux installs containing incompatible versions of some Qt dependent libraries, we now package libfreetype , libsoftokn , libsqlite3 , and libxkbcommon with the emulator.
In battery mode, background CPU usage is greatly reduced. Furthermore, this automatically provides the CPU usage mitigation described for hotword detection from the Tracking for RAM usage distinguishes between graphics usage and total resident memory. General Project Marble improvements This update also includes the following general improvements that are part of the Project Marble initiative: You can now immediately pause all vCPUs on the emulator via the following console commands: adb emu avd pause adb emu avd resume Greatly reduced overhead of OpenGL drawing.
This improvement reduces CPU usage while the emulator is playing animations. Restored support for mainline QEMU's e virtual network device. You can use this device to set up the emulator in a bridged network environment. In a bridged network environment, the emulator is shown on the host network and the host network is shown on the emulator. QEMU 2. Upgraded ffmpeg version to 3. Logcat buffer size increased to 2 MB to address issues with flaky unexpected EOF when running logcat with the emulator.
This change addresses crashes and incompatibility issues associated with running the emulator in different locales. This change helps fix issues where images and assets do not display because of improper format for readback.
Added more diagnostic info to the Bugreport UI. In addition, you can access bug reports from the console using the following commands: telnet localhost avd bugreport On Android Q system images, the emulator increases its minimum RAM size to 2 GB.
Added more logging and printing whenever OpenGL or the hypervisor fails to initialize. If the emulator cannot start a concurrent -read-only instance of an AVD, the emulator now attempts to relaunch the -read-only AVD 3 more times over 3 seconds. This change increases the likelihood that the emulator will be able to launch concurrent -read-only instances an AVD if other writable instances of that AVD are not done cleaning up stale files.
For upcoming system images, the emulator now supports Hardware Composer 2. This change should lower the driver overhead when running most animations. In the emulator extended controls UI, divider lines in the keyboard shortcuts table have been restored.
We use these metrics to enrich our data about emulator resource usage with different use cases from our users, which allows us to make the emulator more efficient and responsive.
General Project Marble fixes This update also includes the following general fixes that are part of the Project Marble initiative: Fixed issues with twitching and incorrect frames that were displayed on systems with Intel GPUs when using Android Q system images.
Fixed issues where a black screen was displayed when using Android Q system images with Pixel 2 XL skins or any skin that has a notch or rounded corners. Fixed an issue where the -partition-size command line option would not set the data partition size. Fixed an issue where pulseaudio on the Linx emulator would spin and take up an entire CPU core in some situations.
Fixed issues with out of bounds memory access when processing compressed textures. Fixed a display issue in Android Q system images with snapshots where the notification shade's geometry was rendered with an improper instance divisor setting. Fixed a few hard-to-reproduce crash and freeze issues on launch that happened due to Qt losing signals or having flaky, inconsistent states on startup. Fixed numerous concurrency issues. We are now able to build the Linux emulator with ThreadSanitizer TSAN , which can easily uncover bugs that are otherwise difficult to reproduce.
For Linux users: we have found that on certain host kernels, the guest Android kernel can error out and exit in KVM with a generic hardware error. The emulator will now abort when this happens in order to increase debuggability previously, the emulator just hung. Fixed a long-standing issue with the Windows emulator where sub-processes, such as ADB commands, failed to start if the username had spaces in it. This fix can possibly address some crashes and race conditions.
Fixed a crash that happened with certain patterns of saving and loading snapshots from the snapshots UI using recent Android Q system images. Fixed an issue where the virtual scene camera would be blank when the emulator was initialized from a snapshot if an AR macro was playing when that snapshot was saved.
Fixed an issue where some users with remote desktop setups got a black screen when launching the emulator on Linux. Fixed an issue where if emulator was set always on top, the extended controls window appeared every time the emulator was rotated. Hardware profiles for foldable devices The emulator now includes hardware profiles for foldable devices.
There are two foldable hardware profiles that you can use to create an AVD: 7. Our CI and remote desktop users have the following long-standing issues: Programmatically sending input commands to the emulator involves either running adb shell commands that can experience high overhead, or using the telnet console, which is faster, but might not work with certain network configurations.
CI users often run emulators headless, which can make it difficult to notice issues that require the screen to be visible or interactive. These commands help address the following issues: Input commands can be sent to the emulator with low overhead over HTTP. HTTP also enables commands to be sent in additional network configurations. Screenshot commands can be sent to query the current screen, even if the emulator is running headless.
For interactivity, input events can also be sent back to the emulator. Remote desktop users can run the emulator headless on the main display with GPU accelerated rendering while using gRPC to get screenshots and send input events in order to interact with the emulator. Currently, this includes the following samples: A Go-based service that can be used to query emulator states.
A React app that demonstrates remote interactivity via screenshot and input RPCs. This sample requires protobuf version 3. Fixed issues where black screen would display when using Android Q system images with Pixel 2 XL skins.
The latest BIOS binaries are now used to start up the emulator. This change can help reduce "vCPU shutdown request" errors that happen sometimes when launching the emulator on Windows.
Backported a fix for the "wrong display when resuming Android Q system images from a snapshot" issue. Users were experiencing "unauthorized" emulators issues due to an incompatible change in ADB in platform-tools You can now safely use ADB from platform-tools If you are experiencing problems with "unauthorized" emulators, do the following troubleshooting steps: Exit all emulators. Relaunch the emulator. To address this, we've made the following changes: Actual host audio data is now squelched by default.
When the guest uses the microphone, silence is passed over instead of the host's audio. Updates on CPU usage investigations During our Project Marble investigations, we've noticed that high CPU usage on the emulator generally falls into the following three categories: At idle: Automatic app updates in Play Store images We found that at random intervals, all apps installed get updated, even when the user is not logged in. Issue When using a mapped file as the RAM snapshot, the emulator now unmaps the file mapping explicitly on exit.
Fixed an issue on Windows that caused the emulator to crash when booting system images with CPU acceleration disabled. Fixed the pixelated emulator display issue. Downsampling should now be working. Fixed an issue on macOS Fixed an error in timezone calculation that could cause the emulator clock to sporadically change.
Fixed rendering errors in various cocos2d and Unreal engine apps. Added support in the emulator for Wi-Fi peer-to-peer. Two emulators can now talk to each other directly via Wi-Fi if using the latest Pie Play Store image. In addition, we have also improved resource usage in the following areas: Reduced emulator memory usage during long-running tests.
If you still experience issues with memory usage during long-running tests, please create an issue that describes your use case in Issue Tracker.
Reduced CPU usage when running apps with animations. File-backed guest RAM snapshots By pre-allocating and mapping guest RAM as a file, the emulator can now save Quickboot snapshots during runtime, instead of doing all of the work on exit. You can do this in the following ways: Use the -no-snapshot-save or -read-only flags when launching the emulator from the command line.
You will need to restart the emulator after selecting this option. If the emulator is set to auto-save, you can run the following command to set a checkpoint: adb emu avd snapshot remap 0 After you run this command, the emulator Quickboot snapshot will stay at that checkpoint.
Run the same command again to load the emulator from your checkpoint. Disk images: Image locking is added and enabled by default. Multiple QEMU processes cannot write to the same image as long as the host supports OFD or posix locking, unless options are specified otherwise. QCOW2 shrinking now supported in qemu and qemu-img. Accessibility Fixed issues with screen readers and added better support for these tools in the Screen Record and Snapshot UI.
Made the Quick Boot notification icons more accessible to users who are color blind. These issues could cause the emulator to crash on start, freeze, or be unusable on the default GPU setting. The emulator now automatically switches to the Swiftshader renderer if it detects that these GPUs are in use. Fixed an issue that caused the emulator to not post the correct framebuffer if FBO!
Fixed issue where the virtual Android display would only show up in the top left corner. We believe this was due to misconfigured Qt environment variables. The emulator now overrides all Qt scaling-related environment variables. Fixed an issue where the emulator crashed in some situations when loading GLES1 apps from a snapshot. Fixed concurrency issues in OpenGL and launching render threads that could result in double frees or corrupted data. If the emulator is launched from the command line using the -no-window flag, the default renderer is now Swiftshader.
Location The emulator can now update bearing along with latitude and longitude position. The magnetometer virtual sensor adjusts itself dynamically to magnetic north by inferring motion when playing back a GPX or KML file. Device speed can now be set on the Location page. Fixed an issue where the virtual GPS location would not be updated periodically unless the Extended Controls window was opened at least once.
Camera On Windows, more webcams are now supported because the emulator dynamically resizes the camera frames that are delivered from the webcam. General quality improvements and fixes Some users reported that the emulator has been running slow. We identified one possible cause where the temp directory for the emulator ends up with too many stale files inside. As a workaround, the emulator no longer stores ADB liveness check files in that directory.
However, it may also help to delete the contents of that folder. If you are on Windows and notice that there is RAM free, but you are still unable to start the emulator, the commit charge may have been exceeded. For help with this issue, see the emulator Troubleshooting page. The -sysdir command line option now properly overrides the inferred system image directory. Fixed various issues with memory leaks, memory corruption, and CPU usage. If you are experiencing crashes, memory leaks, or other high resource usage, please create an issue in Issue Tracker.
Fixed an issue that reappeared on macOS To prevent this, the emulator now avoids using Bluetooth audio when running on macOS.
Issue Fixed an issue on Windows where the emulator clock would not be in the correct timezone. Fixed emulator slowness and hangs on Linux systems with spinning harddrives HDDs. Fixed some compile warnings that could lead to stack corruption on macOS. Fixed issues that could result in misleading reports of hanging.
Fixed an issue with destroying thread pools that could cause a crash if one of the threads was not successfully created. Fixed an issue on macOS where timers would become unreliable, leading to hangs and other strange behavior. If you experience emulator hangs on macOS, please create an issue in Issue Tracker.
Fixed an issue where closing the emulator would disable the UI, but not actually close the emulator. Fixed an issue that caused the emulator to fail to start after the first time if ADB was terminated forcefully.
The MIPS build has been removed. Fixed an issue where ADB connections could become corrupt on snapshot load. Fixed an issue where the emulator window would have an afterimage or teleport offscreen when resuming a snapshot where the device orientation was different from the AVD's default orientation. Fixed issues involving crashes when saving snapshots.
On Linux, btrfs filesystems can cause extreme slowdowns because the emulator automatically saves snapshots and uses copy-on-write for its virtual disk devices. For example, Ubuntu Fixed an x86 instruction emulator bug that could lead to a host crash General fixes Fixed OpenGL errors that occur when loading a snapshot in the camera app. Snapshots You can now save multiple AVD snapshots for a given device configuration and choose which of the saved snapshots to load when you start the emulator.
You can edit the name and description of each saved snapshot. For details, see Snapshots. Virtual scene camera and ARCore Developing and testing augmented reality apps AR with ARCore is now even easier with the new virtual scene camera, which allows you to experiment with your AR experience within a virtual environment. The built-in profiling tools provide realtime statistics for your app's CPU, memory, and network activity.
Identify performance bottlenecks by recording method traces, inspecting the heap and allocations, and see incoming and outgoing network payloads. See the Android Studio release notes. More downloads are available in the download archives. For information on recommended devices and specifications, as well as Android Emulator support, visit chromeos. If you're new to Android development, check out the following resources to get started. Build your first app Start writing code in Android Studio by following the tutorial to Build your first app.
Learn Android with interactive video training in the Android Fundamentals Udacity course. For help installing Android Studio, see the Install guide. Android Studio. Download What's new User guide Preview. Android Developers. Android Studio Android Studio provides the fastest tools for building apps on every type of Android device.
Download Not Available Your current device is not supported. Download options Release notes. More about the layout editor. 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
0コメント