Atyachin / Android-Emulator-on-AWS-EC2.txt. We run ARM emulation on x86 instance. We must use ARM ABI, since x86 requires KVM and EC2 instance doesn't support HW virtualization. We must disable GUI (-no-window) and audio (-no-audio) when running the emulator. We must specify '-gpu swiftshaderindirect' when running the emulator to.
- Timezone and Clock wrong for Android Emulator. When launching the emulator either from Run As - Run Configurations - Targets. Selecting the emulator (in my case GalaxyS44.2.2): made from recommendations on Samsung's developer site. I am passing Additional Emulator Command Line Options: -timezone 'America/NewYork'.
- Android Studio Emulator If you don't have an Android device available to test with, we recommend using the default emulator that comes with Android Studio. If you run into any problems setting it up, follow the steps in this guide.
This article describes the most common warning messages and issuesthat occur while configuring and running the Android Emulator. Inaddition, it describes solutions for resolving these errors as well asvarious troubleshooting tips to help you diagnose emulator problems.
Deployment issues on Windows
Some error messages may be displayed by the emulator when you deployyour app. The most common errors and solutions are explained here.
Deployment errors
If you see an error about a failure to install the APK on the emulatoror a failure to run the Android Debug Bridge (adb), verify that theAndroid SDK can connect to your emulator. To verify emulatorconnectivity, use the following steps:
Launch the emulator from the Android Device Manager (selectyour virtual device and click Start).
Open a command prompt and go to the folder where adb isinstalled. If the Android SDK is installed at its default location,adb is located atC:Program Files (x86)Androidandroid-sdkplatform-toolsadb.exe;if not, modify this path for the location of the Android SDK on yourcomputer.
Type the following command:
If the emulator is accessible from the Android SDK, the emulatorshould appear in the list of attached devices. For example:
If the emulator does not appear in this list, start the AndroidSDK Manager, apply all updates, then try launching theemulator again.
MMIO access error
If the message An MMIO access error has occurred is displayed,restart the emulator.
Missing Google Play Services
If the virtual device you are running in the emulator does not haveGoogle Play Services or Google Play Store installed, this condition isoften caused by creating a virtual device without including thesepackages. When you create a virtual device (seeManaging Virtual Devices with the Android Device Manager),be sure to select one or both of the following options:
- Google APIs – includes Google Play Services in the virtual device.
- Google Play Store – includes Google Play Store in the virtual device.
For example, this virtual device will include Google Play Services and Google Play Store:
Note
Google Play Store images are available only for some base device types suchas Pixel, Pixel 2, Nexus 5, and Nexus 5X.
Performance issues
Performance issues are typically caused by one of the following problems:
The emulator is running without hardware acceleration.
The virtual device running in the emulator is not using an x86-based system image.
The following sections cover these scenarios in more detail.
Hardware acceleration is not enabled
If hardware acceleration is not enabled, starting a virtual device fromthe Device Manager will produce a dialog with an error messageindicating that the Windows Hypervisor Platform (WHPX) is notconfigured properly:
If this error message is displayed, seeHardware acceleration issues below for steps youcan take to verify and enable hardware acceleration.
Acceleration is enabled but the emulator runs too slowly
A common cause for this problem is not using an x86-based image in yourvirtual device (AVD). When you create a virtual device (seeManaging Virtual Devices with the Android Device Manager),be sure to select an x86-based system image:
Hardware acceleration issues
Whether you are using Hyper-V or HAXM for hardware acceleration, youmay run into configuration problems or conflicts with other software onyour computer. You can verify that hardware acceleration is enabled(and which acceleration method the emulator is using) by opening acommand prompt and entering the following command:
This command assumes that the Android SDK is installed at the defaultlocation of C:Program Files (x86)Androidandroid-sdk; if not,modify the above path for the location of the Android SDK on yourcomputer.
Hardware acceleration not available
If Hyper-V is available, a message like the following example will bereturned from the emulator-check.exe accel command:
If HAXM is available, a message like the following example will bereturned:
If hardware acceleration is not available, a message like the followingexample will be displayed (the emulator looks for HAXM if it is unableto find Hyper-V):
If hardware acceleration is not available, seeAccelerating with Hyper-Vto learn how to enable hardware acceleration on your computer.
Incorrect BIOS settings
If the BIOS has not been configured properly to support hardwareacceleration, a message similar to the following example will bedisplayed when you run the emulator-check.exe accel command:
To correct this problem, reboot into your computer's BIOS and enable thefollowing options:
- Virtualization Technology (may have a different label depending on motherboard manufacturer).
- Hardware Enforced Data Execution Prevention.
If hardware acceleration is enabled and the BIOS is configuredproperly, the emulator should run successfully with hardware acceleration.However, problems may still result due to issues that are specific toHyper-V and HAXM, as explained next.
Hyper-V issues
In some cases, enabling both Hyper-V and Windows HypervisorPlatform in the Turn Windows features on or off dialog may notproperly enable Hyper-V. To verify that Hyper-V is enabled, use thefollowing steps:
Enter powershell in the Windows search box.
Right-click Windows PowerShell in the search results and selectRun as administrator.
In the PowerShell console, enter the following command:
If Hyper-V is not enabled, a message similar to the following example will bedisplayed to indicate that the state of Hyper-V is Disabled:
In the PowerShell console, enter the following command:
If the Hypervisor is not enabled, a message similar to the following example will bedisplayed to indicate that the state of HypervisorPlatform is Disabled:
If Hyper-V and/or HypervisorPlatform are not enabled, use the followingPowerShell commands to enable them:
After these commands complete, reboot.
For more information about enabling Hyper-V (including techniques forenabling Hyper-V using the Deployment Image Servicing and Managementtool), seeInstall Hyper-V.
HAXM issues
HAXM issues are often the result of conflicts with other virtualizationtechnologies, incorrect settings, or an out-of-date HAXM driver.
HAXM process is not running
If HAXM is installed, you can verify that the HAXM process is runningby opening a command prompt and entering the following command:
If the HAXM process is running, you should see output similarto the following result:
If STATE is not set to RUNNING, seeHow to Use the Intel Hardware Accelerated Execution Manager to resolve the problem.
HAXM virtualization conflicts
HAXM can conflict with other technologies that use virtualization,such as Hyper-V, Windows Device Guard, and some antivirus software:
Hyper-V – If you are using a version of Windows before theWindows 10 April 2018 update (build 1803) and Hyper-V is enabled,follow the steps in Disabling Hyper-V so thatHAXM can be enabled.
Device Guard – Device Guard and Credential Guard canprevent Hyper-V from being disabled on Windows machines. To disableDevice Guard and Credential Guard, seeDisabling Device Guard.
Antivirus Software – If you are running antivirus softwarethat uses hardware-assisted virtualization (such as Avast), disableor uninstall this software, reboot, and retry the Androidemulator.
Incorrect BIOS settings
If you are using HAXM on a Windows PC, HAXM will not work unlessvirtualization technology (Intel VT-x) is enabled in the BIOS. If VT-xis disabled, you will get an error similar to the following when youattempt to start the Android Emulator:
This computer meets the requirements for HAXM, but IntelVirtualization Technology (VT-x) is not turned on.
To correct this error, boot the computer into the BIOS, enable bothVT-x and SLAT (Second-Level Address Translation), then restart thecomputer back into Windows.
Disabling Hyper-V
If you are using a version of Windows before the Windows 10April 2018 Update (build 1803) and Hyper-V is enabled, you must disableHyper-V and reboot your computer to install and use HAXM. If youare using Windows 10 April 2018 Update (build 1803) or later, AndroidEmulator version 27.2.7 or later can use Hyper-V (instead of HAXM) forhardware acceleration, so it is not necessary to disable Hyper-V.
You can disable Hyper-V from the Control Panel by following thesesteps:
Enter windows features in the Windowssearch box and select Turn Windows features on or off inthe search results.
Uncheck Hyper-V:
Restart the computer.
Alternately, you can use the following PowerShell command to disablethe Hyper-V Hypervisor:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
Intel HAXM and Microsoft Hyper-V cannot both be active at the sametime. Unfortunately, there is no way to switch between Hyper-Vand HAXM without restarting your computer.
In some cases, using the above steps will not succeed in disablingHyper-V if Device Guard and Credential Guard are enabled. If you areunable to disable Hyper-V (or it seems to be disabled but HAXMinstallation still fails), use the steps in the next section to disableDevice Guard and Credential Guard.
Disabling Device Guard
Device Guard and Credential Guard can prevent Hyper-V from beingdisabled on Windows machines. This situation is often a problem fordomain-joined machines that are configured and controlled by an owningorganization. On Windows 10, use the following steps to see if DeviceGuard is running:
Enter System info in the Windows search box and selectSystem Information in the search results.
In the System Summary, look to see if Device GuardVirtualization based security is present and is in the Runningstate:
If Device Guard is enabled, use the following steps to disable it:
Ensure that Hyper-V is disabled (under Turn Windows Featureson or off) as described in the previous section.
In the Windows Search Box, enter gpedit.msc and select the Editgroup policy search result. These steps launch the Local GroupPolicy Editor.
In the Local Group Policy Editor, navigate to ComputerConfiguration > Administrative Templates > System > Device Guard:
Change Turn On Virtualization Based Security to Disabled (asshown above) and exit the Local Group Policy Editor.
In the Windows Search Box, enter cmd. When Command Prompt appearsin the search results, right-click Command Prompt and selectRun as Administrator.
Copy and paste the following commands into the command prompt window(if drive Z: is in use, pick an unused drive letter to useinstead):
Restart your computer. On the boot screen, you should see a prompt similar tothe following message:
Do you want to disable Credential Guard?
Press the indicated key to disable Credential Guard as prompted.
After the computer reboots, check again to ensure that Hyper-V isdisabled (as described in the previous steps).
If Hyper-V is still not disabled, the policies of your domain-joinedcomputer may prevent you from disabling Device Guard or CredentialGuard. In this case, you can request an exemption from your domainadministrator to allow you to opt out of Credential Guard. Alternately,you can use a computer that is not domain-joined if you must use HAXM.
Additional troubleshooting tips
Android Emulator Time Wrong Location
The following suggestions are often helpful in diagnosing Androidemulator issues.
Starting the emulator from the command line
If the emulator is not already running, you can start it from thecommand line (rather than from within Visual Studio) to view itsoutput. Typically, Android emulator AVD images are stored at thefollowing location (replace username with your Windows user name):
C:Usersusername.androidavd
You can launch the emulator with an AVD image from this location bypassing in the folder name of the AVD. For example, this command launchesan AVD named Pixel_API_27:
This example assumes that the Android SDK is installed at the defaultlocation of C:Program Files (x86)Androidandroid-sdk; if not,modify the above path for the location of the Android SDK on yourcomputer.
When you run this command, it will produce many lines of output whilethe emulator starts up. In particular, lines such as the followingexample will be printed if hardware acceleration is enabled and workingproperly (in this example, HAXM is used for hardware acceleration):
Viewing Device Manager logs
Often you can diagnose emulator problems by viewing the Device Managerlogs. These logs are written to the following location:
C:UsersusernameAppDataLocalXamarinLogs16.0
You can view each DeviceManager.log file by using a texteditor such as Notepad. The following example log entry indicates thatHAXM was not found on the computer:
Deployment issues on macOS
Some error messages may be displayed by the emulator when you deployyour app. The most common errors and solutions are explained below.
Deployment errors
If you see an error about a failure to install the APK on the emulatoror a failure to run the Android Debug Bridge (adb), verify that theAndroid SDK can connect to your emulator. To verify connectivity, usethe following steps:
Launch the emulator from the Android Device Manager (selectyour virtual device and click Start).
Open a command prompt and go to the folder where adb isinstalled. If the Android SDK is installed at its default location,adb is located at~/Library/Developer/Xamarin/android-sdk-macosx/platform-tools/adb;if not, modify this path for the location of the Android SDK on yourcomputer.
Type the following command:
If the emulator is accessible from the Android SDK, the emulatorshould appear in the list of attached devices. For example:
If the emulator does not appear in this list, start the AndroidSDK Manager, apply all updates, then try launching theemulator again.
MMIO access error
If An MMIO access error has occurred is displayed,restart the emulator.
Missing Google Play Services
If the virtual device you are running in the emulator does not haveGoogle Play Services or Google Play Store installed, this condition isusually caused by creating a virtual device without including thesepackages. When you create a virtual device (seeManaging Virtual Devices with the Android Device Manager),be sure to select one or both of the following:
- Google APIs – includes Google Play Services in the virtual device.
- Google Play Store – includes Google Play Store in the virtual device.
For example, this virtual device will include Google Play Services and Google Play Store:
Note
Google Play Store images are available only for some base device types suchas Pixel, Pixel 2, Nexus 5, and Nexus 5X.
Performance issues
Performance issues are typically caused by one of the following problems:
The emulator is running without hardware acceleration.
The virtual device running in the emulator is not using an x86-based system image.
The following sections cover these scenarios in more detail.
Hardware acceleration is not enabled
If hardware acceleration is not enabled, a dialog may pop up with amessage such as device will run unaccelerated when you deploy yourapp to the Android emulator. If you are not certain whether hardwareacceleration is enabled on your computer (or you would like to knowwhich technology is providing the acceleration), seeHardware acceleration issues below for steps you cantake to verify and enable hardware acceleration.
Acceleration is enabled but the emulator runs too slowly
A common cause for this problem is not using an x86-based image in yourvirtual device. When you create virtual device (seeManaging Virtual Devices with the Android Device Manager),be sure to select an x86-based system image:
Hardware acceleration issues
Whether you are using the Hypervisor Framework or HAXM for hardwareacceleration of the emulator, you may run into problems caused byinstallation issues or an out-of-date version of macOS. The followingsections can help you resolve this issue.
Hypervisor Framework issues
If you are using macOS 10.10 or later on a newer Mac, the Androidemulator will automatically use the Hypervisor Framework for hardwareacceleration. However, some older Macs or Macs running a version ofmacOS earlier than 10.10 may not provide Hypervisor Framework support.
To determine whether or not your Mac supports the Hypervisor Framework,open a Terminal and enter the following command:
If your Mac supports the Hypervisor Framework, the above command willreturn the following result:
If the Hypervisor Framework is not available on your Mac, you canfollow the steps in Accelerating with HAXMto use HAXM for acceleration instead.
HAXM issues
If the Android Emulator does not start properly, this problem is oftencaused by problems with HAXM. HAXM issues are often the result ofconflicts with other virtualization technologies, incorrect settings,or an out-of-date HAXM driver. Try reinstalling the HAXM driver, usingthe steps detailed inInstalling HAXM.
Additional troubleshooting tips
The following suggestions are often helpful in diagnosing Androidemulator issues.
Starting the emulator from the command line
If the emulator is not already running, you can start it from thecommand line (rather than from within Visual Studio for Mac) to viewits output. Typically, Android emulator AVD images are stored at thefollowing location:
~/.android/avd
You can launch the emulator with an AVD image from this location bypassing in the folder name of the AVD. For example, this commandlaunches an AVD named Pixel_2_API_28:
If the Android SDK is installed at its default location, the emulatoris located in the~/Library/Developer/Xamarin/android-sdk-macosx/emulator directory;if not, modify this path for the location of the Android SDK on yourMac.
When you run this command, it will produce many lines of output whilethe emulator starts up. In particular, lines such as the followingexample will be printed if hardware acceleration is enabled and workingproperly (in this example, Hypervisor Framework is used for hardwareacceleration):
Viewing Device Manager logs
Often you can diagnose emulator problems by viewing the Device Managerlogs. These logs are written to the following location:
~/Library/Logs/XamarinDeviceManager
You can view each Android Devices.log file by double-clicking it toopen it in the Console app. The following example log entry indicatesthat HAXM was not found:
Android emulator is very famous for its performance. It’s very, very, very notoriously… slow. If you debug your app with Android emulator, it get more extremely slower. This performance problem stems from the fact that Android OS is written for ARM processor (not for Intel/AMD processor or let’s say not for computer processor). Therefore when we get our apps run on Android emulator (which is running on Intel/AMD processor), every assembly code row has to be emulated. A run-time binary translation will happen to translate every assembly code of development machine to device machine. And that point slows down everything.
Even that we can use our real devices for debugging and developing which promise a better performance and save us a lot of time, we’ll face the problem again when we want to test our apps with different resolutions and screen sizes devices. Testing on multiple real devices is definitely a ‘must’ when writing apps for Android, but if the emulator is good enough, we can test it with many test cases in emulator before pushing to the test apartment.
The Android emulator is shipped in Android SDK as default. You can find it under folder ‘tools’ of SDK (%USERPROFILE%android-sdkstools). With the emulator, you have an opportunity to write apps without owning a real device. However, if you start the emulator, you’ll recognize something wrong here. It can take up to 5 minutes just for starting an AVD (Android Virtual Device) and when you debug your apps, you’ll see how slow it is to jump from current code row to next code row.
Because of annoyed problem, in this post, I would like to give you a tip to speed up your emulator.
1. Prerequisites
The tip works only if you’re using a computer with Intel processor having Intel Virtualization Technology. You need to check in your BIOS settings if Intel Virtualization Technology is enabled. Enable it, if it’s in off mode.
2. Install Intel Hardware Accelerated Execution Manager
The Intel Hardware Accelerated Execution Manager (Intel® HAXM) is a hardware-assisted virtualization engine (hypervisor) that uses Intel Virtualization Technology (Intel® VT) to speed up Android app emulation on a host machine. In combination with Android x86 emulator images provided by Intel and the official Android SDK Manager, HAXM allows for faster Android emulation on Intel VT enabled systems (From Intel)
Android Emulator Time Wrong Get
Let’s follow this URL
http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager
choose installation for your OS and install it.
I let everything as default during the installation. That means 2GB RAM for Intel HAXM, you can adjust the amount of RAM according to your resources. Please note that reserving a large memory for Intel HAXM can cause the other processes run slowly.
After installation finishes, you can check if installation works by giving in console the following command sc query intelhaxm. If you see the STATE is RUNNING, that means installation is successful.
3. Install Intel Atom x86 Image
– Start Android SDK Manager (from your IDE or directly under %USERPROFILE%android-sdksSDK Manager.exe)
– Be sure that under Extras, the Intel x86 Emulator Accelerator (HAXM) is installed
– Be sure that under Android x.x.x (API xx) (the Android version which you want your AVD running on), the Intel x86 Atom System Image is installed.
– For example, in my case, I would like to have an AVD with Android 4.0.3, my settings should be like following image.
4. Create AVD
– Start AVD Manager (from your IDE or directly under %USERPROFILE%android-sdksAVD Manager.exe)
– The recommended settings for AVD are in image below. Important is the CPU/ABI should be set as Intel Atom (x86) and the option Use Host GPU is checked for speeding up rendering process.
– When you start your AVD, if you see the message HAX is working and emulator runs in fast virt mode, that means you have all settings correct.
Now start your AVD and enjoy a ‘fast’ Android emulator ever seen. :).
5. Updates
5.1 15.07.2014
If you get this error during installation of Intel Hardware Accelerated Execution Manager
This computer does not support Intel Virtualization Technology (VT-x). HAXM cannot be installed. Please refer to the Intel HAXM documentation for more information
Microsoft Hyper V can be the cause of error. If you have Microsoft Hyper V enabled, Intel HAXM can’t be installed on your computer. So if you don’t use Microsoft Hyper V and want to use Intel HAXM for speeding up Android emulator. You can disable Microsoft Hyper V by this command with administrator role
Wait for a moment until this command finishes. Restart computer and then you can install Intel HAXM