Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have had the same issue with the latest Android SDK. I simply deactivated the checkbox "Use Host GPU" within the settings of the virtual device and it started working again.</p> <p>The "Use Host GPU" does only work for me with Android 4.2 as "Target".</p> <p><strong>Update 26.02.2014:</strong></p> <p>There a two hints in the <a href="http://developer.android.com/tools/devices/emulator.html#accel-graphics" rel="nofollow noreferrer">Configuring Graphics Acceleration</a> chapter from developer.android.com.</p> <blockquote> <p>Caution: As of SDK Tools Revision 17, the graphics acceleration feature for the emulator is experimental; be alert for incompatibilities and errors when using this feature.</p> </blockquote> <p>and</p> <blockquote> <p>Start the AVD Manager and create a new AVD with the Target value of Android 4.0.3 (API Level 15), revision 3 or higher.</p> </blockquote> <p>So Android 4.0.3 (API Level 15) seems to be the minimum requirement for graphics acceleration.</p> <p><strong>Update 25.07.2018:</strong></p> <p>The latest Android Studio version does not have this option anymore. If the problem persists try to switch between the values of the "Emulated Performance" dropdown in the <a href="https://developer.android.com/studio/run/managing-avds#verifyconfigpage" rel="nofollow noreferrer">Verify Configuration</a> dialogue (if available) or refer to the <a href="https://developer.android.com/studio/run/emulator-acceleration" rel="nofollow noreferrer">Configure Emulator graphics rendering and hardware acceleration</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload