3 ms·
Note that you have to enable GPU Emulation for any given AVD first! A lot of people seem (understandably) confused that their emulator wasn't suddenly much fast
by mdwrigh2 15y ago
Note that you have to enable GPU Emulation for any given AVD first! A lot of people seem (understandably) confused that their emulator wasn't suddenly much faster with this update.
Quick Start Guide to Getting GPU Emulation Working:
* Open up the settings for your AVD (either by creating a new one or editing a current one)
* Go to Hardware (near the bottom), and hit new on the far right
* Select GPU emulation from the drop down list and hit okay
* Find GPU emulation in the list of properties under hardware, click on the value column and set it to "yes"
See here[1] for more ways on how to speed up your emulator.
[1]: http://developer.android.com/guide/developing/devices/emulator.html#accel-vm http://developer.android.com/guide/developing/devices/emulat...
- robot 15y agoI am wondering about the opposite case: how do they emulate graphics when there is no GPU support? Do they emulate the GPU device, or use a software library? Which library if it is done in software?
- mdwrigh2 15y agoEssentially all of the commands on the device are translated into native OpenGL calls, so I suspect if you don't have a GPU you just get the default OpenGL software renderer.
- huggyface 15y agoTo add an anecdote about this new functionality, I have been unsuccessful using the GPU acceleration (x64 Windows 7 with an nvidia GTX 560 w/latest drivers). With the emulation on the AVD GPFs with emulator-arm.exe has stopped working (invalid access). Anyone have success?
- blinkingled 15y agoMe neither - Win 7 x64 Sandy Bridge GPU.
- biafra 15y agoI did as you suggested but in the logcat output I see the following message: "Emulator without GPU emulation detected." Is it accelerated anyway?
- biafra 15y agoIt seems to be working if I start the emulator on the command line via: emulator -avd 403_r2 -gpu on