Android studio

This article Article description::contains instructions for installing Android Studio.

Pre-Installation
These pre-installation steps are required for the Android Studio Emulator to work. 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".

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.

KVM and QEMU
See QEMU article for information on how to set up KVM and install qemu.

QEMU should automatically create a new  group on the system and there should now be a  device.

Show all groups on the system to check if  was added:

Add the user account which will be using Android Studio to the  group (in the example, the username is  ):

To check that the user was added to the  group:

Log out then back in, if already connected with this account.

Make sure is set to the correct ownership and mode permissions:

The desired permissions are mode  and the desired ownership should be. This should already be set, if not, set the ownership and permission mode with the following commands:

Pulseaudio
See pulseAudio article for information on how to install pulseaudio.

Files

 * - the SDK lives here
 * - projects created in Android Studio are found here

Invocation
Launch Android Studio with the command:

Emulator will not launch
Make sure the proper SDK tools and the Emulator are installed. This can be checked by going to. Then click on the tab and make sure that the box next to  is checked as well as the boxes next to, and.

Make sure an actual Android Virtual Device (AVD) has been created. Create an AVD by clicking on the green play button underneath the menu. Then click on and follow the instructions from Android Studio.

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. Make sure is set to mode   and , as described in the pre-installation section.

Android Studio itself may only give cryptic information or may act as though the emulator is launching but never launch it. In the terminal where Android Studio was launched, there may be vague messages about timeout reached.

To find out what's really going on with the emulator, launch it directly from the :

Then get a list of installed AVDs (Android Virtual Devices) with the command:

Try launching an AVD:

Where  is an example AVD name.

Pay attention to the terminal and see if it lists any error messages about missing libraries or other information.

Check in Android Studio Event Log, particularly for something like:. In this case, go to or  and move to some backup location the  files from there. Now the emulator will try to work with the system libraries. Optionally, make symbolic link to the system, for example:

Running Intel x86 Atom images on processors without ssse3 support may also give the warning, but images up to API 22 are known to work despite of it (newer doesn't). For Intel x86 Atom_64 images, the warning is:.

A system reboot might fix the issue so it's worth a shot if all else fails. Another thing to try is removing the emulator and the SDK and then reinstalling them. Also double check that all the pre-installation was followed correctly.