gersugar.blogg.se

To find out what's really going on with the emulator, launch it directly from the ~/Android/Sdk/tools/emulator: In the terminal where Android Studio was launched, there may be vague messages about timeout reached. Make sure /dev/kvm is set to mode 660 and root:kvm, as described in the pre-installation section.Īndroid Studio itself may only give cryptic information or may act as though the emulator is launching but never launch it. See the pre-installation section above and make sure that the system supports KVM at the bios and processor level, that KVM is enabled correctly in the kernel, and that qemu and pulseaudio are correctly installed and working. Then click on Create New Virtual Device and follow the instructions from Android Studio. Create an AVD by clicking on the green play button underneath the Run menu. Make sure an actual Android Virtual Device (AVD) has been created. Then click on the SDK Tools tab and make sure that the box next to Android Emulator is checked as well as the boxes next to Android SDK Platform-Tools, and Android SDK Tools. This can be checked by going to Tools -> Android -> SDK Manager. Make sure the proper SDK tools and the Emulator are installed. User $ export _JAVA_AWT_WM_NONREPARENTING=1 Emulator will not launch

Show all groups on the system to check if kvm was added: QEMU should automatically create a new kvm group on the system and there should now be a /dev/kvm device. See QEMU article for information on how to set up KVM and install qemu. To have a fully functioning Emulator, it is required to have KVM enabled in the kernel (which means that the CPU and BIOS must support KVM), qemu installed, and pulseaudio installed.

The package will still install and partially work without these steps, but the Emulator will either not launch, or may seem to be working but will give a cryptic message about "waiting for target to come online". These pre-installation steps are required for the Android Studio Emulator to work.