Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 558956]
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Use -gpu <mode> to override the mode of hardware OpenGL ES emulation
indicated by the AVD. Valid values for <mode> are:
on -> enable GPU emulation
off -> disable GPU emulation
auto -> use the setting from the AVD (default)
enabled -> same as 'on'
disabled -> same as 'off'
guest -> use guest-side OpenGL ES implementation
Note that enabling GPU emulation if the system image does not support it
will prevent the proper display of the emulated framebuffer.
You can always disable GPU emulation (i.e. '-gpu off'), and this will
force the virtual device to use the slow software renderer instead.
Note that OpenGLES 2.0 is _not_ supported by it.
The 'auto' mode is the default. In this mode, the hw.gpu.enabled setting
in the AVD's hardware-qemu.ini file will determine whether GPU emulation
is enabled.
Even if hardware GPU emulation is enabled, if the host-side OpenGL ES
emulation library cannot be initialized, the emulator will run with GPU
emulation disabled rather than failing to start.
--------------------------------------------------------------------------
DT gave me this info recently:
auto - Let the emulator choose hardware or software graphics acceleration based on your computer setup. (Equivalent to on.)
host - Use the GPU on your computer. This option is typically the fastest. However, some Windows drivers have issues with rendering OpenGL graphics, so you can't use the computer GPU.
swiftshader - Use SwiftShader to render graphics in software. It's slower than using the GPU, but normally yields good results.
mesa - Use the Mesa 3D software library to render graphics. This solution has been deprecated in favor of SwiftShader, which can be faster.
angle - Use Almost Native Graphics Layer Engine (ANGLE) and Microsoft DirectX on Windows to render graphics in software. ANGLE is fast and well-tested, but the rendering might be poorer than other solutions.
off - Don't use a GPU, either hardware or software-emulated, resulting in poor graphics rendering. This option can be useful (and faster) if your app doesn't use graphics, you want to test features that don't rely on graphics, or for snapshots. Snapshots aren't supported when graphics acceleration is enabled. (Equivalent to guest.)