Android emulator in Android Studio 3.2 supports AMD processors on Windows 10

Android Emulator 27.3.6 was recently released on Canary and Dev channels alongside the Android Studio release, bringing a long-awaited feature for AMD users on Windows 10. This new version has finally supported running emulator with hardware acceleration on machines with AMD processors.

Previously, AMD users on Windows 10 were unable to run the Android emulator with hardware acceleration, which resulted in slow, inefficient, and generally frustrating to use compared to the experience on the platform. -Intel form.

It changes with the New versionwhich also brings other changes such as:

  • Fixed crashes after the initial snapshot load when loading color stamps from the snapshot.
  • Fixed potential memory corruption when saving snapshots of OpenGL shader program info logs.
  • Fixed potential memory corruption when checking host system CPUID.
  • On AMD machines running the latest version of Windows 10 and on which the Windows hypervisor platform can be successfully enabled, the emulator can now boot API level 26+ x86/x86_64 AVDs in accelerated mode.
    • Warning: We have found that enabling Hyper-V or the Windows hypervisor platform on many AMD Ryzen machines, especially laptops with Vega GPUs, can prevent Windows from booting. We recommend trying only if your AMD system is already working successfully with the Windows Hypervisor platform enabled.
    • To fix: If Windows can no longer boot due to Windows Hypervisor Platform activation, disable virtualization in your system BIOS and reboot, which should allow you to disable the feature.

Credits: Reddit user /u/Ssunde2

Android Studio Emulator Developer /u/lfy_google also clarified that hardware acceleration should also work on Windows 10 Home systems, although the latter does not have a “Hyper-V” option. Simply enabling the “Windows Hypervisor Platform” option in Windows Optional Features should do the trick. Also, support for API 25 and below is not yet included; users can expect this to be fixed in the next version of Canary.


Via: Reddit

Comments are closed.