Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialIan Baylis
5,744 PointsIf you can't get your emulator working and you aren't working on an Intel Processor computer. Haxm doesn't work.
This is the closest I found to an answer, but it makes me more confused. This has worked for me, but is this the same as the X86?
Won't I need it to be X86?
1 Answer
kent1
5,437 PointsThat quora article told you to switch to using an ARM image which as you mentioned is not "x86". However, that's not a problem since the emulator is able to fully emulate the ARM hardware. Unfortunately that has substantial overhead and is thus significantly slower. Using an x86 image instead can potentially be hardware accelerated by taking advantage of the virtual machine extensions in modern processors. Both Intel and AMD CPUs are "x86" compatible but they have different virtual machine extension implementations and, as you discovered, Haxm only works with the Intel implementation, VT-x. However, the Android Emulator section concerning acceleration mentions the following as a acceleration requirement: "AMD processor on Windows: Android Studio 3.2 or higher and Windows 10 April 2018 release or higher for Windows Hypervisor Platform (WHPX) functionality". So maybe there's hope for you to be able to run in hardware accelerated mode if you run the latest Android Studio and are on an up-to-date Windows 10 OS (or if you run on Linux).