Windows 7上的模拟器非常慢 [英] Emulator awfully slow on Windows 7

问题描述

这不是怒，也不是永远的为什么Android模拟器这么慢"问题的副本.因此，直到几周(也许是几个月)之前，在我的Win7 64位系统上模拟Android设备至少是可以接受的(x86模拟相当快就可以使用).但是，尝试使用最新版本的SDK，平台工具等创建任何(快速"新""2.0")仿真器实例，只是几天来令人沮丧和痛苦的原因.我想了解这是否是我的问题，或者人们可以在Windows 7上实际使用最新SDK中包含的最新版本的Android模拟器.

This is not a rant, and also not a duplicate of the forever "why is Android emulator so slow" problem. So, until a few weeks (maybe months) ago, emulating Android devices on my Win7 64-bit system was at the very least acceptable (x86 emulation was decently fast to be usable). However, trying to create any ("fast" "new" "2.0") emulator instances using the latest version of the SDK, platform tools, etc., is only a source of frustration and pain for several days now. I'm trying to understand if it's an issue on my side or people can actually use the latest version of the Android emulator included in the latest SDK, on Windows 7.

我的PC配置:Win7 x64/Intel Core 2 Quad @ 3.8 GHz/6 GB RAM/足够的HDD空间/专用GPU

My PC config: Win7 x64 / Intel Core 2 Quad @3.8 GHz / 6 GB RAM / plenty of HDD space / dedicated GPU

尝试使用x86或x86_64的任何API级别启动仿真器时会发生什么:

What happens when trying to start an emulator with any API level, with either x86 or x86_64:

• 版本1)仿真器启动，出现Android标志，发光了一段时间，仅此而已.它永远不会到达主屏幕.仿真器日志绝对没有显示错误.尝试使用adb进行连接会冻结Android Studio，直到我杀死模拟器进程为止.

• version 1) emulator starts, Android logo appears, glows for a bit, and that's it. It never reaches the Home screen. Emulator log shows absolutely no errors. Trying to connect using adb freezes Android Studio until I kill the emulator process.

版本2)与版本1相同，但是在这种情况下，我什至无法杀死qemu-system-i386进程(是的，甚至没有完整的管理员权限).我必须重新启动Windows.进程仍然是僵尸，使用1 GB的RAM.

version 2) Same like version 1, but in this case I can't even kill the qemu-system-i386 process (yes, not even with full admin rights). I have to actually restart Windows. Process remains a zombie, using 1 GB of RAM.

版本3)如果我很幸运，有时它会到达主屏幕，但变得完全无法使用.有时我可以单击某些东西(可能是2-3次单击)，然后变得完全无响应.偶然的启动器已停止"/系统已停止"消息随机出现在模拟器的主屏幕中...

version 3) If I'm lucky, sometimes it reaches the Home screen, but becomes completely unusable. Sometimes I can click on things (maybe 2-3 clicks), and then becomes completely unresponsive. Occasional "Launcher has stopped" / "System has stopped" messages appear randomly in the emulator's home screen...

我已经安装了最新的Intel HAXM 6.0.3版本(由Android SDK管理器下载).在BIOS中启用了虚拟化.

I've installed the latest Intel HAXM 6.0.3 version (the one downloaded by the Android SDK manager). Virtualization is enabled in BIOS.

我尝试了各种仿真器选项(或多或少的RAM，硬件与软件GPU，x86/x86_64).每次几乎都是相同的结果.

I've tried all kinds of emulator options (more or less RAM, hardware vs software GPU, x86 / x86_64). Almost same result every time.

我已经完全删除并重新安装了整个Android SDK和Android Studio.

I've completely deleted and reinstalled the entire Android SDK and Android Studio.

不是问题-仿真器运行时它没有处于负载状态.

CPU is not the issue - it's not under load while emulator runs.

可用内存不是问题-模拟器运行时没有充分利用

Free RAM is not the issue - it's not fully used while emulator runs,

硬盘不是问题-我什至对其进行了碎片整理，并且在模拟器运行时它看起来没有任何负载.

HDD is not the issue - I even defragmented it, and it's not looking like it's under any sort of load while emulator is running.

所以，我的问题很简单:有人在使用Windows 7的人，只要通过一个简单的2-3次点击过程，就可以真正启动一个棉花糖x86模拟器，并使其真正到达主屏幕?还是新的，更快的"仿真器实际上需要某种我似乎不再拥有的超强大机器?唯一明显改变的是HAXM驱动程序.但这说明它已经初始化好了，所以我不知道.哦，VirtualBox运行得很好.相比之下，GenyMotion只能飞.但是我想让正式的Android模拟器处于工作状态，还是我要求太多?

So, my question is very simple: is anyone out there using Windows 7, who can actually start up, let's say, a Marshmallow x86 emulator just by a simple 2-3 clicks process, and actually have it reach the home screen? Or does the "new, faster" emulator actually need some sort of super-powerful machine which I don't seem to possess anymore? The only thing that apparently changed was the HAXM driver. But it's stating that it has initialized just fine, so I don't know. Oh, and VirtualBox runs just fine. GenyMotion, by contrast, just flies. But I'd like to have the official Android emulator in a working state, or am I asking for too much?

推荐答案

阿德里安(Adrian)，我很难过:是的，您将需要功能强大的处理器，甚至需要多一点RAM.以xxxhdpi分辨率运行api 24仿真的几乎可以接受的方案是具有8 ram的i7.

Adrian, in my sad opinion: yes, you would need a powerfull processor, even a litle bit more of ram. The almost-aceptable scenario for you to run api 24 emulation in xxxhdpi resolution is an i7 with 8 of ram.

但这是硬件和软件制造商想要您实现的目标:升级，升级，升级.对于您来说，这不一定是正确的，或者对于今天来说不是必须的.也许明天...

But this is what hard and software manufacturers want you for: upgrade, upgrade, upgrade. And it's not necessairilly true for you, or not obligatory for today. Maybe tomorrow...

这也是我的情况.我有第二代i5，内存为6 ram，有足够的磁盘.也有一个不错的geforce gpu.以及如何使模拟器运行，或者如何在win7中进行模拟?首先:从Windows卸载所有最近(大约30个)非安全系统更新(！是的，它们使您的系统非常沉重，与微软希望我们继续在系统上使用的各种分布式c ++包相同)即使我们一年或更短的时间使用它-请转到控制面板并关闭ripp'em！仅保留最新的c ++软件包-如果以后需要，请再次更新).实际上，我什至正在研究还有哪些更新"可以从系统中删除，以使其再次可用，然后再次进行挖掘.微软...

It's my case too. I have a second generation i5 with 6 of ram and plenty of disk. Have a good geforce gpu too. And what I do to have my emulators running, or, how do I emulate in my win7? First of all: unninstalled all the last (about 30) non-security system updates from windows (! yes..., they make your system very heavy, the same with the various distributed c++ packages microsoft want us to carry on with our systems even if we use it once a year, or less - go to control panel and ripp'em off! Keep only the most recent c++ package - if you need it later, update again). Actually I'm even investigating what else "updates" I can delete from my system to have it usable again, mine again. Microsoft...

第二:仅在测试时间内，在android studio(菜单文件)上启用省电模式"似乎可以使事情变得更快.

Second: enabling "power save mode" on your android studio (menu file), only in testing times, seems to make things faster.

第三:在具有低" API的模拟器上进行大量测试，例如android 4或5.并模拟具有小屏幕或分辨率为5 pol的设备.最高720点(水平)如果可能，请使用_x86 64仿真.

Third: do heavy tests on emulators with "low" apis, like android 4 or 5 at max. And emulate devices with small screens or resolution, 5 pol. with 720 points (hor.), at max. If possible use _x86 64 emulation.

有了这个，您就可以实现.仿真器的加载和打开速度很慢，但是在运行时，它的运行速度相当不错.要做的第一件事:在两个地方输入开发人员选项并"force gpu".这将指导您的PC利用专用的GPU系统.

With this you can make it happen. The emulator is slow to load and open, but when running it works in a fairly good speed. First thing to do there: enter developer options and "force gpu" on both places. This will instruct your pc to take advantage of your dedicated gpu system.

对不起，请勿尝试同时打开两个或多个仿真器.

Do not try to open two or more emulators at the same time, sorry.

完成90％的调试后(我在运行低于5的android版本的模拟器中进行调试，通常为4.0或4.1-480x800屏幕)，则您需要付出代价来加载大屏幕，大dpi的android 5 6或N).装入时，冲泡咖啡并使用浴缸.

When 90% of your debug is done (i do it in an emulator running android version lower than 5, normally 4.0 or 4.1 - 480x800 screen), then you pay the price to load a big screen, big dpi android 5, 6 or N). While it loads, make a coffee and use the bath.

加载美女(野兽?)后，然后对所有等待这个特殊时刻的应用进行最终测试.我维护我所有的应用程序.当我加载大" e时，我会利用这种机会进行所有我需要的测试-因为这不是一个简单的任务，每次我都想打开它.

When the beauty (beast?) is loaded, then do the final tests with all your apps that stayed waiting for this special moment. I maintain all my apps waiting for it. When I load the "big" emu I use this oportunity to do all tests I was needing - because it's not a simple task open this everytime I want.

如前所述:i7、8ram，强大的gpu以及非常重要的一点:一个好的SSD驱动器(直到快10倍)才能将该死的讨厌的硬盘扔进垃圾桶. :)最好.

In the future, as said: i7, 8ram, powerfull gpu and, very important: a good SSD drive (until 10x faster) to throw up damn nasty harddisk to the garbage. :) Best.

当您使用最新的API创建AVD图像时，Android Studio会定义用于仿真的内存和磁盘空间值，我认为这些值太大且太难于人质计算机处理.第一点:您的测试应用永远不会需要所有这些资源.二:您的电脑很难处理从此处到此处的非常零碎的Gb数据.第三:随着使用的增加，在硬盘上创建的虚拟映像会越来越大.因此:1-从您的avd图像，内存和磁盘大小中降低默认值； 2-在avd启动窗口对话框中，每次启动前都要编辑每个图像的选项和rip信息或/和3-不需要时从emu卸载应用程序.

when you create an AVD image with the latests APIs, Android Studio defines the ram and disk space values for the emulation and, in my opinions, these values are too big and too hard for the hostage computer to deal with. First point: your testing app never will demand all those resources. Two: your pc suffers hard to deal with a very fragmented Gb data from here to there, and there to here. Three: the virtual image created on your hard disk gets bigger with the use. So: 1 - lower the default values from your avd images, ram and disk sizes; 2 - on the avd launching window dialog, edit the options of each image and rip information everytime before start the emulation OR/AND 3 - uninstall your apps from the emu when not needed.

这篇关于Windows 7上的模拟器非常慢的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！