Launch the Android Emulator without first running an app. To start the emulator: Open the AVD Manager. Double-click an AVD, or click Run. The Android Emulator appears. While the emulator is running, you can run Android Studio projects and choose the emulator as the target device.
Well, Android Studio needs HAXM to run the emulator. HAXM drivers do not support the beta version of Mac Os High Serria yet. The driver works but with a little bit of additional command. First, you need to disable the Security Protection on kext. The drivers do not sign for this version. From:.
Get into Recovery Mode by restarting and holding down ⌘+ R until Apple logo appears. In the top menu click: Utilities Terminal. In the Terminal window type and press ↵ Enter: csrutil enable -without kext. Then restart the Mac. Then you can install HAXM from: Download the driver from here and unzip it.
Open a terminal and go to the directory of the driver: $ cd Downloads/haxm-macosxv620 edit the file and look for 10.12 $ nano silentinstall.sh CTRL + W 10.12 Add 10.13 after 10.12, and save the file ( CTRL+ X, Y, ↵ Enter) Run it: $./silentinstall.sh To be sure it works: $ sudo kextload -bundle-id com.intel.kext.intelhaxm Now you emulator should work!
Visual Studio Android Emulator crashes within five minutes. This is a Apache Cordova (TACO) project. The project type is not important since you can replicate the issue by simply launching an emulator from Visual Studio Emulator for Android interface. Tried the following emulators (all failed). 5.1' Marshmallow (6.0.0) XXHDPI Phone. 5.1' Lollipop (5.1.1) XXHDPI Phone. 7' KitKat (4.4) XHDPI Tablet.
5' KitKat (4.4) XXHDPI Phone I can run other Virtual Machines (all Windows so far) on Hyper-V just fine. I can also run Google Android Emulator as well as debug directly on Android device with USB debugging.
There are no error logs since it crashes the entire system in an instant (no blue screen). It looks like a compatibility issue between VS Android Emulators and the newly released AMD Ryzen Processors.
Ryzen is known to have a bug where certain FMA3 instructions can crash the system. I am running the latest BIOS with the AMD patch for this issue. System:. CPU: Ryzen 1800X - SVM Enabled (cannot run emulators with SVM disabled). Motherboard: ASUS Crosshair VI Hero - 083 BIOS with AGESA 1.0.0.4a.
Memory: G.Skill DDR4 (F4-3200C14D-32GB-GTZ x 2) = 16GB x 4 = 64GB at 18-14-14-34-2T timings. GPU: ASUS ROG 1080 OC Strix.
OS: Windows 10 64-bit Enterprise Edition with Power Options set to High Performance Mode. IDE: Visual Studio 2017 Enterprise Edition. Project Type: Apache Cordova / Visual Studio Tools for Apache Cordova (TACO).
Cordova Version: 6.3.1 Repro Steps:. Launch Visual Studio 2017 IDE with no solution loaded. Open Tools Visual Studio Emulator for Android.
Install an emulator profile (if you haven't already). Run emulator directly from the interface.
Click around the emulator for about five minutes (sometimes crashes before even getting to the lock screen) I can run the exact same solution with same emulator on my previous system based on Intel processor. I have stress tested the system under a variety of workloads with no stability issues. Same problem with my Ryzen 3 1200, Crosshair VI Hero(BIOS v.3502), Vengeance 8gigs 2400 (stable), Strix RX 560 4gigs. My problem is little different, like I tried Windows Phone 10 (UWP) emulator. I think all the emulators works in a same way and I get stuck + freeze the whole PC in 'Starting OS.' Until reset physically. But my little Surface Pro 3's i3 1.4Ghz, 4gigs 1600 DDR3 working very well with that emulator.
I also took my SSD where the both OS and VS17/Emulator installed to my friend's build who is using Ryzen 5 1600 for a test. At the first run the whole PC get freezes, after that it goes to normal, I can do what ever I want in the emulator, no problem at all, and I think its an architectural problem in ZEN series. Hope for the early fixes from both AMD and Microsoft soon.
It seems that I have found a workaround for this issue. As you may know these android emulators in Visual Studio are nothing more than a virtual machines hosted within HYPER-V. It turned out that the only thing you have to do to make those emulators stable on AMD Ryzen systems is to enable the ' Migrate to a physical computer with a different processor version' compatibility option in the Virtual Machine settings for processor using HYPER-V Manager. I have attached an image showing where the mentioned setting is located. After enabling that setting and launching the emulator I did not face any stability issues. Moreover I did not face any performance drops and I was finally able to start Android 5.1.1 emulator - previously it was hanging on 'Starting OS' message.
So it seems that the Android Emulator blocker for AMD Ryzen systems is solved. EDIT: I have discovered that this solution is not working in every case. From my own testing on Gigabyte AB350 Gaming 3 motherboard I can tell that it is working fine only if I have F10 bios version or newer installed. For other motherboard vendors it seems that it is not always working even with newest bioses. I am not microsoft staff but I know why this happens: The android emulator of visual studio uses intel HAXM; which only runs/install if you have a 'genuineintel' chip; if you have AMD chip, the emulator will not be stable and it will crash; technically, there is no reason why it should not work, but it is intel, they do all these things to keep the market.