This page contains guidance for troubleshooting common issues and configuration problems in Android Studio.
High density displays
As of version 1.5, Android Studio provides support for high density displays (like HiDPI and Retina monitors) on all platforms.
Scaling factor settings
Android Studio determines the scaling factor for your display as follows:
- For Retina displays, UI elements are scaled by a factor of 200% and images are rendered in high resolution. There should be no blurriness due to scaling, even in multi-monitor configurations. Note that there is no support for scaling factors other than 100% (for non-Retina displays) and 200% (for Retina displays).
- Android Studio uses the primary display's DPI settings to determine the scaling factor of UI elements. For images, if the scaling factor is less than 150%, normal resolution images are scaled up. If the scaling factor is greater than 150%, high resolution images are scaled appropriately.
- Android Studio determines the scaling factor by looking at the "Text Scaling Factor," then at the XWindow system DPI Setting.
A DPI setting of 96 corresponds to a scaling factor of 100% (no scaling), and a DPI setting of 192 corresponds to a scaling factor of 200% (the size of UI elements is doubled). Android Studio currently supports DPI settings between 96 (100% scaling) and 288 (300% scaling).
If Android Studio does not detect the correct system DPI on your Linux or
Windows machine, you can set it manually by setting the
property in the
ide.properties file as described in Customize your IDE
properties. Note that this property has no effect on Mac machines.
This property functions as follows:
- Sets the DPI to 192 (200% scaling), ignoring the system settings.
- Sets the DPI to 96 (100% scaling), ignoring the system settings.
Blurry or pixelated elements on high density displays
If one or more elements of Android Studio's UI appear blurry or pixelated on your high density display, you may be experiencing one of the following issues:
- If most of the Android Studio UI looks fine, but one particular icon is blurry or pixelated, or one particular UI element uses the wrong size font, that particular element probably has not yet been fully updated for HiDPI support. Please file a bug by clicking Help > Submit Feedback. Please include a screenshot and as much information as possible on your system configuration.
- If you are using a Windows or Linux machine and your display uses a scaling factor other than 100% or 200%, images may appear slightly blurred due to the scaling.
- If you are using a Windows machine and you have have changed the Windows font size in the Control Panel, you may experience blurred or pixelated font. You can resolve this issue by signing out of Windows and then signing back in.
- On a multi-monitor setup running Windows 8.1 or later, when you move a window from one display to another display with a different resolution or DPI, you may experience font or image problems (see bug 186007). There is no known workaround at this time.
- Older versions of the JRE 1.8 had an issue for blurry fonts (JRE 1.8.0_25-b18 amd64 in particular, see bug 192316.) As of version 2.2, Android studio includes a bunded version of the latest supported JDK, which includes the JDE. To resolve this issue, update Android Studio to version 2.2 or higher and switch to use the bundled JDK by clicking File > Project Structure > SDK Location and checking the Use embedded JDK checkbox.
Incorrectly-sized elements on high density displays
If the entire Android Studio UI is the wrong size on your high density display, see Scaling factor settings. If some elements of the Android Studio UI are the wrong size on your high density display, but others are correctly-sized, you may be experiencing one of the following issues:
- If you are using a custom editor scheme, the editor font may appear too small or too big compared to the rest of the UI elements on a high density display. To fix this issue, click File > Settings then click Editor > Colors and Fonts > Font and change the size of the editor font. Note that when the default scheme is active, the editor font size is scaled automatically (see bug 186920).
- If some UI elements of Android Studio are the right size, but others are too small or too big, you may be experiencing issue 186923. Please file a bug by clicking Help > Submit Feedback. Please include a screenshot and as much information as possible on your system configuration.
If you are running Android Studio on a 64-bit Linux machine, you may need to install some specific libraries, as follows.
If you are running a 64-bit version of Ubuntu, you need to install some 32-bit libraries with the following command:
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1 lib32bz2-1.0
If you are running 64-bit Fedora, the command is:
sudo yum install zlib.i686 ncurses-libs.i686 bzip2-libs.i686
Project sync issues
When attempting to sync your project, you may receive the following error
message: "Connection to the Internet denied. ('Permission denied: connect')".
You can resolve this error message by adding the system property
-Djava.net.preferIPv4Stack=true to your
gradle.properties file in Android Studio as follows:
- Open your
gradle.propertiesfile in Android Studio.
- Add the following line to the file:
org.gradle.jvmargs=-Djava.net.preferIPv4Stack=trueNote that if you have already added other Gradle JVM arguments to your
gradle.propertiesfile, you can add this property to the same line as shown in the following example:
org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true
- Restart Android Studio for your changes to take effect.
- Click Sync Project with Gradle Files to sync your project.
Problems updating the IDE on Windows
On Windows, files that are in use by a process cannot be deleted. When you attempt to use the built-in update mechanism in the IDE, it sometimes refuses to install the update, usually providing an error message like "Can't delete C:\some\path\file".
To work around this, open the task manager and attempt to kill processes that may be using the file, such as any Gradle daemons.
If you are using an obsolete version of the Android Support Libraries, you may receive an error message like the following:
:app:processDebugManifest app/src/main/AndroidManifest.xml:0:0 Error: uses-sdk:minSdkVersion 19 cannot be smaller than version L declared in library app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/21.0.0-rc1/AndroidManifest.xml Suggestion: use tools:overrideLibrary="android.support.v7.appcompat" to force usage
To resolve this issue, use the SDK manager to update to the latest (non-preview) versions of the Android Support Libraries. For more information about setting up the Support Libraries, see Support Library Setup.
Android Emulator runs slowly after an update
A number of external factors can cause the Android Emulator to begin running slowly after an update. To begin troubleshooting, we recommend the following steps:
- If you are running the Android Emulator on a Windows machine, check to see if you have installed Windows Updates KB4013429 and KB4015217. Some users reported improved Android Emulator performance after uninstalling these updates. Users also reported improved Emulator performance after installing Windows Update KB4015438.
- If you are running the Android Emulator on a Windows machine, ensure you have installed the latest version of HAXM (HAXM 6.1.1 or later). For more about how to determine what version of HAXM you have installed, see Configuring VM Acceleration.
- Some users have reported lags for Android Emulator associated with running Avast Antivirus. To address this issue, try uninstalling Avast Antivirus.
- If you have an Intel GPU (and in particular, the Intel HD 4000), ensure you have downloaded and installed the latest Intel graphics driver.
- If your machine has both an Intel HD 4000 GPU and a discrete GPU, disable the Intel HD 4000 GPU in Device Manager to ensure you are using the discrete GPU.
- Try running the emulator using the
-gpu swiftshader, or
-gpu guestmodes. For more information about configuring graphics acceleration options on the command line, see Configure Hardware Acceleration.
- Ensure that your router is not using IPv6 addresses if you do not have an IPv6 connection.
If you are still experiencing problems with the Android Emulator running slowly, Report a Bug, including the necessary Android Emulator Details so we can investigate.