The contents of the files are all about emulator, and there is emulator-arm.exe in the emulator directory.įrom the above analysis, it is known that the emulator folder and the tools file are similar, except that the latest emulator tool is in the emulator folder, then you only need to replace the emulator folder with the tools folder.įinally, the test arm virtual machine can start normally. Go to the android sdk directory and you can see the tools directory and the emulator directory. In Android Studio > Tools > AVD Manager > Create Virtual Device when prompted to Select a system image select the Other images tab and pick an arm-based image those images will run VERY slowly. Another option (does not answer your question directly) is to actually use an ARM image instead of X86. You can know that the emulator is in the android sdk/tools directory. Standard Android emulator with an ARM image. Pay attention to the commands executed in the lower left corner when turning on the virtual machine: The x86 virtual machine can be turned on, indicating that the virtual machine is okay, but the arm virtual machine cannot be used, which may be the problem of the emulator. Instead, use the x86 Android virtual machine but it will not go wrong. PANIC: Missing emulator engine program for 'arm' CPU. When using the android studio virtual machine, the arm virtual machine cannot be turned on, and an error is prompted:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |