flushWindowSurfaceColorBuffer 模拟器启动问题
来源:互联网 发布:阅读mobi的软件 编辑:程序博客网 时间:2024/06/06 03:37
[2014-09-09 14:42:16 - ListView1] Android Launch!
[2014-09-09 14:42:16 - ListView1] adb is running normally.
[2014-09-09 14:42:16 - ListView1] Performing cn.ac.siat.listview1.ListView1Activity activity launch
[2014-09-09 14:42:16 - ListView1] Automatic Target Mode: launching new emulator with compatible AVD 'Android14'
[2014-09-09 14:42:16 - ListView1] Launching a new emulator with Virtual Device 'Android14'
[2014-09-09 14:42:27 - Emulator] emulator: warning: opening audio input failed
[2014-09-09 14:42:27 - Emulator]
[2014-09-09 14:42:27 - Emulator] creating window 28 27 320 480
[2014-09-09 14:42:27 - ListView1] New emulator found: emulator-5554
[2014-09-09 14:42:27 - ListView1] Waiting for HOME ('android.process.acore') to be launched...
[2014-09-09 14:42:38 - Emulator] FB::flushWindowSurfaceColorBuffer: window handle 0x4 not found
[2014-09-09 14:42:38 - Emulator] FB: closeColorBuffer cb handle 0x3 not found
[2014-09-09 14:42:42 - Emulator] FB::flushWindowSurfaceColorBuffer: window handle 0x8 not found
[2014-09-09 14:42:42 - Emulator] FB: closeColorBuffer cb handle 0x7 not found
[2014-09-09 14:42:47 - Emulator] FB::flushWindowSurfaceColorBuffer: window handle 0xc not found
[2014-09-09 14:42:47 - Emulator] FB: closeColorBuffer cb handle 0xb not found
[2014-09-09 14:42:52 - Emulator] FB::flushWindowSurfaceColorBuffer: window handle 0x10 not found
[2014-09-09 14:42:52 - Emulator] FB: closeColorBuffer cb handle 0xf not found
Here's the deal. Host GPU is only supported for AVD devices that are using API 15 or later. You also have to have Android SDK Tools 17 or later installed. Also Host GPU is experimental. All of this is in the emulation documentation: http://developer.android.com/tools/devices/emulator.html
Also your machine has to support OpenGL (most do) and you will get better results if your machine has a separate GPU even though it will work with integrated graphic chipsets as well.
If you cannot take advantage of Host GPU then use the Snapshot option instead to gain some performance boost. This will take a snapshot of the ram on the initial start of the emulated device and then reuse it on initial boot start ups of the device. (Snapshot and Host GPU are actually mutually exclusive even though the ADV allows you to check both.)
- flushWindowSurfaceColorBuffer 模拟器启动问题
- flushWindowSurfaceColorBuffer 模拟器启动问题
- android模拟器启动问题
- Android 模拟器的启动问题
- Eclipse无法启动模拟器问题
- AndroidStudio无法启动模拟器问题
- android 1.5 SDK 模拟器无法启动问题
- Android启动多个模拟器问题概述
- 启动模拟器出现问题的解决
- 关于genymotion模拟器无法启动的问题
- 问题:运行项目时会启动另一个模拟器
- Android Studio启动模拟器出现的问题
- 解决Android Studio启动模拟器的问题
- eclipse中Android模拟器启动过一段时间DDMS假死问题
- Android 安装路径问题 -- 导致无法启动模拟器
- AndroidSDK安装路径导致模拟器不能成功启动问题
- 解决android 1920x1080模拟器无法启动问题
- Android: 亲测解决模拟器启动慢的问题
- 实例恢复
- Swap Nodes in Pairs
- Unity3D优化之Optimizing the Size of the Built iOS Player
- LeetCode 150 Median of Two Sorted Arrays
- Ubuntu 14.04 (32位)上搭建Hadoop 2.5.1单机和伪分布式环境
- flushWindowSurfaceColorBuffer 模拟器启动问题
- ios--pushnotification学习与总结(推送机制)
- 分享产品发布的10条经验
- POJ1987——Distance Statistics
- Eclipse 生成android程序apk文件
- File not found
- 颜色表
- Struts2自定义拦截器—Session超时的处理
- 设计模式-受限制的多例模式