I have searched but not found any queries or answers for my specific circumstance. I have a fast new machine with plenty of memory running Windows 7. I'm using the latest Eclipse and Android SDK.
我搜索过，但是没有找到任何关于我具体情况的查询或答案。我有一台运行Windows 7的内存容量很大的新机器。我正在使用最新的Eclipse和Android SDK。
When I run an app the emulator takes about 45 seconds to start (blazingly fast for the emulator!) from run initiation to running my app.
当我运行一个应用程序时，从运行启动到运行我的应用程序，仿真器的启动时间大约为45秒(对于仿真器来说，速度非常快!)
If I then change the app and re-run it on the still-running emulator, the time increases to 70+ seconds! As opposed to all other complaints people have, in my case restarting the emulator is faster than using the existing instance. I don't like that.
如果我更改应用程序并在仍在运行的模拟器上重新运行它，时间将增加到70秒以上!与所有其他人的抱怨相反，在我的例子中，重启模拟器比使用现有实例要快。我不喜欢这样。
Here are the times:
这里是《纽约时报》:
2011-09-29 13:07:13 - hello Uploading hello.apk onto device 'emulator-5554'
2011-09-29 13:07:18 - hello Installing hello.apk...
2011-09-29 13:07:37 - hello Success!
on rerunning after changing the app to get it to reload:
修改app后重新运行，使其重新加载:
2011-09-29 13:08:18 - hello Uploading hello.apk onto device 'emulator-5554'
2011-09-29 13:09:16 - hello Installing hello.apk...
2011-09-29 13:09:24 - hello Success!
As you can see, the upload to the emulator takes a mere 5 seconds when the emulator is freshly started. It takes nearly a minute with a running emulator! This is the cause of the extended re-running time. This doesn't change even when I uninstall the app on the emulator before re-running it.
如您所见，当模拟器刚刚启动时，向模拟器上载只需5秒。使用一个正在运行的模拟器需要近一分钟!这就是延长重新运行时间的原因。即使我在重新运行之前卸载模拟器上的应用程序，这也不会改变。
Any ideas on what I could try to solve this? It appears to be some kind of communication problem, possibly with adb.
有什么办法可以解决这个问题吗?这似乎是某种沟通问题，可能与亚行有关。
18 个解决方案
#1
30
As others have posted, just clicking around in the emulator while uploading drastically improves the upload speed. I had the same problem and Googled for an answer, and trying out this trick helped me. I'm running a 2.3.3 AVD.
就像其他人发布的那样，只要在模拟器中点击一下，上传速度就会大大提高。我遇到了同样的问题，用谷歌搜索了一个答案，试着用这个方法帮助了我。我运行的是2。3。AVD。
#2
8
My new discovery is a small "hack" how you can make your upload faster. I realized that the cases when the upload was faster were caused by my interaction. So when I upload new app without active working with emulator, it is slow. But when I work with it (testing my application, exiting, opening applications list, etc.), the upload is MUCH faster - in my case approx. 15seconds instead nearly 2 minutes.
我的新发现是一个小“黑客”，你可以让你的上传速度更快。我意识到上传速度更快的情况是由我的互动造成的。所以当我上传新应用而不使用模拟器时，速度很慢。但当我使用它(测试我的应用程序、退出、打开应用程序列表等)时，上传速度要快得多——在我的案例中大约是这样。15秒，而不是2分钟。
So I think, that the problem is somehow in performance settings of the emulator. When I do nothing, it thinks no big performance is needed, emulator is switched to some economic state, so also my upload is slow.
我认为，问题在于模拟器的性能设置。当我什么都不做的时候，它认为不需要大的性能，模拟器被切换到一些经济状态，所以我的上传也很慢。
#3
6
A better solution:
Go to Run -> Run Configurations... -> Target Tab -> Additional Emulator Command Line Options. Add there:
运行->运行配置…->目标选项卡->额外的仿真程序命令行选项。添加:
-netspeed full -netdelay none
Now close the emulator and run it again.
现在关闭模拟器并再次运行它。
After doing this the time for uploading went from 2 minutes to 8 seconds.
这样做之后，上传的时间从2分钟增加到8秒。
Edit: I have also found that quitting Skype makes my emulator upload much faster.
编辑:我还发现退出Skype会让我的模拟器上传得更快。
#4
5
I have the same problem, I'm developing an android application which is like 4,6MB and it takes me like maybe 50-60 seconds to upload it on emulator and run it.I don't think this is a problem with the communication. The JVM is slow, that's why you need a time to upload your apk and run it.I don't think you can do anything about it, except you start testing your application on a device.
我也有同样的问题，我正在开发一个android应用程序，大概是46mb，我大概需要50-60秒在模拟器上上传并运行它。我不认为这是沟通的问题。JVM很慢，这就是为什么您需要时间上传apk并运行它。我不认为你能做什么，除了你开始在一个设备上测试你的应用。
#5
5
Play with the emulator while uploading your application. I totally agree with teepee. It reduced my waiting time from 4 minutes to 30 secs.
在上传应用程序时使用模拟器。我完全同意teepee的说法。我的等待时间从4分钟缩短到30秒。
#6
5
The fastest emulator you can get it's a VMWare machine with Android.
你能得到的最快的模拟器是一个带有Android的VMWare机器。
While developing my game, Elastic World, I was suffering from the same problem. After waiting minutes for the emulator to startup, the game was running at 20 FPS maximum. Even on low end android devices I could easily get 60 FPS. The upload speed was very slow.
在开发我的游戏时，我遇到了同样的问题。在等待模拟器启动数分钟后，游戏以最高20 FPS的速度运行。即使在低端安卓设备上，我也能轻松获得60个FPS。上传速度很慢。
So I moved to a VMWare Android machine, following the instructions from this site: http://www.android-x86.org/documents/installhowto/
所以我转到一个VMWare Android机器，按照这个网站的指示:http://www.android-x86.org/documents/installhowto/。
The same game loop now runs at 250 FPS. (it's not playable at this speed and I have the game limited to max 60 FPS, but overriding this limitation it gives 250 FPS)
同样的游戏循环现在以250帧/秒的速度运行。(在这个速度下不能玩，我的游戏限制为最多60帧/秒，但超过这个限制后，游戏限制为250帧/秒)
When Eclipse ends the build process I just have to wait 1 to 5 seconds for the game to appear on the virtual machine. And I'm running an old Core2Duo
当Eclipse结束构建过程时，我只需等待1到5秒，游戏就会出现在虚拟机上。我在运行一个旧的Core2Duo
#7
4
This is not an issue with the AVD, it's eclipse the problem and I don't know if there is a way to change it within what we could call the jungle of parameters.
这不是AVD的问题，而是eclipse的问题，我不知道是否有一种方法可以在参数堆中改变它。
To be brief you can launch an emulator all by yourself in a console command using the following :
简单地说，您可以使用以下命令在控制台命令中自己启动一个模拟器:
emulator.exe -avd MyAVDName -netspeed full -netdelay none
Nice the parameters, why isn't Eclipse using it? Some Eclipse coder should make it the default. Another solution is to switch to IntelliJ IDEA. It will gloriously replace your old clunky IDE with a fresh and better one.
很好的参数，为什么Eclipse不使用它呢?一些Eclipse编码器应该将其设置为默认值。另一个解决方案是转向IntelliJ的想法。它将光荣地取代你旧的笨重的IDE，一个新的，更好的。
#8
4
I know this is an old topic, but I think I actually have a solution to this issue.
我知道这是一个老话题，但我认为我确实有一个解决这个问题的办法。
First you need to boot the emulator without the netspeed arguments like follows:
首先，您需要引导仿真器，而不需要如下所示的netspeed参数:
emulator -avd <name>
Once it's started log in to the emulator using telnet. You can get the port from the top of the emulator window or by running adb devices and looking at the serial for the emulator which is in the form emulator-port (this is usually 5554 in most cases)
一旦它开始使用telnet登录到模拟器。您可以从仿真器窗口的顶部获取端口，或者运行adb设备并查看仿真器的串口(在大多数情况下通常是5554)
telnet localhost 5554
After you've logged in using telnet you need to issue the following command to force the emulator to use a very high network speed
在使用telnet登录之后，需要发出以下命令，以强制仿真器使用非常高的网络速度
network speed 500000
You can then check this setting in telnet using the following command
然后可以使用以下命令在telnet中检查此设置
network status
Which should return
它应该返回
Current network status:
download speed: 500000000 bits/s (61035.2 KB/s)
upload speed: 500000000 bits/s (61035.2 KB/s)
If you now try to install the APK you should find the performance is dramatically increased. In my case it went from 260s to 18s.
如果您现在尝试安装APK，您会发现性能显著提高。在我的例子中，它从260到18s。
#9
2
Just thinking out loud:
想大声说:
I don't know this for a fact, but I'm wondering if this slow down is because Android applications each have their own instance of the Dalvik VM and run as a separate user and process. When you "think" you have closed your application, Android may be keeping the process (definitely the VM) alive in case you restart the application. This is similar to the pre-fetch behavior in windows.
我不知道这是怎么回事，但我想知道这是否是因为Android应用程序都有自己的Dalvik虚拟机实例，并作为一个独立的用户和进程运行。当您“认为”您已经关闭了应用程序时，Android可能会在重新启动应用程序时使进程(肯定是VM)保持活动状态。这类似于windows中的预取行为。
When you re-run the application, after modifying the sources, Android perhaps has to destroy the cached instance. The additional delay you notice in the case of re-deployment in the same emulator instance may be because of the costs incurred in gracefully shutting down the VM and the application.
当您重新运行应用程序时，在修改源代码之后，Android可能必须销毁缓存的实例。在相同的仿真器实例中重新部署时，您会注意到额外的延迟，这可能是因为优雅地关闭VM和应用程序所产生的成本。
#10
1
I get the same problem, but I'm convinced it has something to do with the O.S., because I uploaded the same application using a MacBook Pro and a Dell laptop, which is more powerful, given the hardware spec, however the upload time is significantly lower on the Mac.
我也有同样的问题，但我相信这和O.S.有关因为我用MacBook Pro和戴尔的笔记本电脑上传了相同的应用程序，这比硬件规格更强大，不过Mac上的上传时间要低得多。
On this Dell laptop with Windows, however, uploads to actual Android devices are way, way faster.
不过，在这款搭载Windows操作系统的戴尔笔记本电脑上，上传至Android设备的速度要快得多。
I thought it might be related to the "Google USB Driver package", that I haven't installed before, but after installing it, nothing really changed.
我认为它可能与我之前没有安装的“谷歌USB驱动程序包”有关，但是在安装之后，并没有什么真正的改变。
#11
1
Try to set your emulator RAM to 1024.
尝试将模拟器RAM设置为1024。
#12
1
Elaborating on what teepee said in an earlier post, I've found that if I muck with the already-running AVD during the uploading phase, it finishes MUCH quicker (5 seconds vs 60 seconds) and I'm installed and running in a fraction of the time. This is with a 4.0.3 AVD. Haven't tried the others yet.
在之前的一篇文章中详细阐述了teepee说了什么，我发现，如果我在上传阶段把已经运行的AVD弄脏，它会更快地完成(5秒vs 60秒)，而我的安装和运行时间也只有一小部分。这是4。3 AVD。还没试过其他的。
#13
1
The alternative ways:
另一种方式:
Setting up a FTP server on your pc for hosting apk files, now you can download apk files by android emulator web browser and install app directly whitout using adb.
在您的pc上设置一个FTP服务器来托管apk文件，现在您可以通过android仿真器web浏览器下载apk文件，并使用adb直接安装应用程序。
or
或
Install a samba client on android emulator and share apk files on your pc, then copy apk files to emulator and install app directly whitout using adb.
在android仿真器上安装一个samba客户端并在您的pc上共享apk文件，然后将apk文件复制到仿真器中，并使用adb直接安装应用程序。
All of above ways are faster than adb install.
所有这些方法都比adb安装要快。
#14
0
Silly question - did you try it on several AVDs? It is possible your one AVD is messed up in some way.
愚蠢的问题——你在几个AVDs上试过吗?你的一个AVD可能在某些方面出了问题。
#15
0
Do as much interaction with emulator as you can while uploading the apk on emulator, if you press random buttons of emulator while uploading it will upload early, before it took 5-6 mins to upload but now it take only 15 - 20 secs.
在模拟器上上传apk时，尽可能多地与模拟器进行交互，如果你在上传的同时按下模拟器的随机按钮，将会提前上传，在上传之前需要5-6分钟，而现在只需要15 - 20秒。
#16
0
I have seen this too. Here is something that helped, assuming you've been using the same AVD. Wipe the user data on the AVD. After doing this, it would load the app much faster again, a couple of seconds.
我也见过。这里有一些有用的东西，假设你一直在使用相同的AVD。擦除AVD上的用户数据。这样做之后，它会再次以更快的速度加载应用程序，几秒钟。
#17
0
In a terminal/console I shell into the AVD with adb -e shell then go to the tmp directory where the apk is being uploaded cd /data/local/tmp then do ls -l to see the current file size. I've found that if I sit there and keep hitting up arrow then enter to quickly repeat the ls -l the upload speeds up dramatically. You can watch the progress as the file size increases.
在终端/控制台I shell中，使用adb -e shell将其放入AVD中，然后进入tmp目录，在该目录中，apk被上传cd /data/local/tmp，然后执行ls -l以查看当前文件大小。我发现，如果我坐在那里，不停地点击箭头，然后进入快速重复ls -l，上传速度会急剧上升。随着文件大小的增加，您可以查看进度。
This is probably similar to the effect of clicking around in the AVD others have mentioned.
这可能与别人提到的AVD中单击鼠标的效果类似。
I'm on a Mac. Not sure if it's the same on Windows or Linux.
我用的是Mac电脑，不知道Windows还是Linux都是一样的。
#18
0
This might work on windows,
这可能适用于windows，
start the Task manager --> processes tab--> look for emulator.exe,
启动任务管理器——>进程标签——>寻找模拟器。exe，
right click and set priority to high
右击并将优先级设置为high
dont forget to set it to normal after your work is done.
工作结束后，不要忘记把它设置为正常。
also closing unwanted applications which require a lot of memory like chrome and firefox can be closed when not needed.
同时关闭需要大量内存的不需要的应用程序，如chrome和firefox，在不需要的时候可以关闭。
#1
30
As others have posted, just clicking around in the emulator while uploading drastically improves the upload speed. I had the same problem and Googled for an answer, and trying out this trick helped me. I'm running a 2.3.3 AVD.
就像其他人发布的那样，只要在模拟器中点击一下，上传速度就会大大提高。我遇到了同样的问题，用谷歌搜索了一个答案，试着用这个方法帮助了我。我运行的是2。3。AVD。
#2
8
My new discovery is a small "hack" how you can make your upload faster. I realized that the cases when the upload was faster were caused by my interaction. So when I upload new app without active working with emulator, it is slow. But when I work with it (testing my application, exiting, opening applications list, etc.), the upload is MUCH faster - in my case approx. 15seconds instead nearly 2 minutes.
我的新发现是一个小“黑客”，你可以让你的上传速度更快。我意识到上传速度更快的情况是由我的互动造成的。所以当我上传新应用而不使用模拟器时，速度很慢。但当我使用它(测试我的应用程序、退出、打开应用程序列表等)时，上传速度要快得多——在我的案例中大约是这样。15秒，而不是2分钟。
So I think, that the problem is somehow in performance settings of the emulator. When I do nothing, it thinks no big performance is needed, emulator is switched to some economic state, so also my upload is slow.
我认为，问题在于模拟器的性能设置。当我什么都不做的时候，它认为不需要大的性能，模拟器被切换到一些经济状态，所以我的上传也很慢。
#3
6
A better solution:
Go to Run -> Run Configurations... -> Target Tab -> Additional Emulator Command Line Options. Add there:
运行->运行配置…->目标选项卡->额外的仿真程序命令行选项。添加:
-netspeed full -netdelay none
Now close the emulator and run it again.
现在关闭模拟器并再次运行它。
After doing this the time for uploading went from 2 minutes to 8 seconds.
这样做之后，上传的时间从2分钟增加到8秒。
Edit: I have also found that quitting Skype makes my emulator upload much faster.
编辑:我还发现退出Skype会让我的模拟器上传得更快。
#4
5
I have the same problem, I'm developing an android application which is like 4,6MB and it takes me like maybe 50-60 seconds to upload it on emulator and run it.I don't think this is a problem with the communication. The JVM is slow, that's why you need a time to upload your apk and run it.I don't think you can do anything about it, except you start testing your application on a device.
我也有同样的问题，我正在开发一个android应用程序，大概是46mb，我大概需要50-60秒在模拟器上上传并运行它。我不认为这是沟通的问题。JVM很慢，这就是为什么您需要时间上传apk并运行它。我不认为你能做什么，除了你开始在一个设备上测试你的应用。
#5
5
Play with the emulator while uploading your application. I totally agree with teepee. It reduced my waiting time from 4 minutes to 30 secs.
在上传应用程序时使用模拟器。我完全同意teepee的说法。我的等待时间从4分钟缩短到30秒。
#6
5
The fastest emulator you can get it's a VMWare machine with Android.
你能得到的最快的模拟器是一个带有Android的VMWare机器。
While developing my game, Elastic World, I was suffering from the same problem. After waiting minutes for the emulator to startup, the game was running at 20 FPS maximum. Even on low end android devices I could easily get 60 FPS. The upload speed was very slow.
在开发我的游戏时，我遇到了同样的问题。在等待模拟器启动数分钟后，游戏以最高20 FPS的速度运行。即使在低端安卓设备上，我也能轻松获得60个FPS。上传速度很慢。
So I moved to a VMWare Android machine, following the instructions from this site: http://www.android-x86.org/documents/installhowto/
所以我转到一个VMWare Android机器，按照这个网站的指示:http://www.android-x86.org/documents/installhowto/。
The same game loop now runs at 250 FPS. (it's not playable at this speed and I have the game limited to max 60 FPS, but overriding this limitation it gives 250 FPS)
同样的游戏循环现在以250帧/秒的速度运行。(在这个速度下不能玩，我的游戏限制为最多60帧/秒，但超过这个限制后，游戏限制为250帧/秒)
When Eclipse ends the build process I just have to wait 1 to 5 seconds for the game to appear on the virtual machine. And I'm running an old Core2Duo
当Eclipse结束构建过程时，我只需等待1到5秒，游戏就会出现在虚拟机上。我在运行一个旧的Core2Duo
#7
4
This is not an issue with the AVD, it's eclipse the problem and I don't know if there is a way to change it within what we could call the jungle of parameters.
这不是AVD的问题，而是eclipse的问题，我不知道是否有一种方法可以在参数堆中改变它。
To be brief you can launch an emulator all by yourself in a console command using the following :
简单地说，您可以使用以下命令在控制台命令中自己启动一个模拟器:
emulator.exe -avd MyAVDName -netspeed full -netdelay none
Nice the parameters, why isn't Eclipse using it? Some Eclipse coder should make it the default. Another solution is to switch to IntelliJ IDEA. It will gloriously replace your old clunky IDE with a fresh and better one.
很好的参数，为什么Eclipse不使用它呢?一些Eclipse编码器应该将其设置为默认值。另一个解决方案是转向IntelliJ的想法。它将光荣地取代你旧的笨重的IDE，一个新的，更好的。
#8
4
I know this is an old topic, but I think I actually have a solution to this issue.
我知道这是一个老话题，但我认为我确实有一个解决这个问题的办法。
First you need to boot the emulator without the netspeed arguments like follows:
首先，您需要引导仿真器，而不需要如下所示的netspeed参数:
emulator -avd <name>
Once it's started log in to the emulator using telnet. You can get the port from the top of the emulator window or by running adb devices and looking at the serial for the emulator which is in the form emulator-port (this is usually 5554 in most cases)
一旦它开始使用telnet登录到模拟器。您可以从仿真器窗口的顶部获取端口，或者运行adb设备并查看仿真器的串口(在大多数情况下通常是5554)
telnet localhost 5554
After you've logged in using telnet you need to issue the following command to force the emulator to use a very high network speed
在使用telnet登录之后，需要发出以下命令，以强制仿真器使用非常高的网络速度
network speed 500000
You can then check this setting in telnet using the following command
然后可以使用以下命令在telnet中检查此设置
network status
Which should return
它应该返回
Current network status:
download speed: 500000000 bits/s (61035.2 KB/s)
upload speed: 500000000 bits/s (61035.2 KB/s)
If you now try to install the APK you should find the performance is dramatically increased. In my case it went from 260s to 18s.
如果您现在尝试安装APK，您会发现性能显著提高。在我的例子中，它从260到18s。
#9
2
Just thinking out loud:
想大声说:
I don't know this for a fact, but I'm wondering if this slow down is because Android applications each have their own instance of the Dalvik VM and run as a separate user and process. When you "think" you have closed your application, Android may be keeping the process (definitely the VM) alive in case you restart the application. This is similar to the pre-fetch behavior in windows.
我不知道这是怎么回事，但我想知道这是否是因为Android应用程序都有自己的Dalvik虚拟机实例，并作为一个独立的用户和进程运行。当您“认为”您已经关闭了应用程序时，Android可能会在重新启动应用程序时使进程(肯定是VM)保持活动状态。这类似于windows中的预取行为。
When you re-run the application, after modifying the sources, Android perhaps has to destroy the cached instance. The additional delay you notice in the case of re-deployment in the same emulator instance may be because of the costs incurred in gracefully shutting down the VM and the application.
当您重新运行应用程序时，在修改源代码之后，Android可能必须销毁缓存的实例。在相同的仿真器实例中重新部署时，您会注意到额外的延迟，这可能是因为优雅地关闭VM和应用程序所产生的成本。
#10
1
I get the same problem, but I'm convinced it has something to do with the O.S., because I uploaded the same application using a MacBook Pro and a Dell laptop, which is more powerful, given the hardware spec, however the upload time is significantly lower on the Mac.
我也有同样的问题，但我相信这和O.S.有关因为我用MacBook Pro和戴尔的笔记本电脑上传了相同的应用程序，这比硬件规格更强大，不过Mac上的上传时间要低得多。
On this Dell laptop with Windows, however, uploads to actual Android devices are way, way faster.
不过，在这款搭载Windows操作系统的戴尔笔记本电脑上，上传至Android设备的速度要快得多。
I thought it might be related to the "Google USB Driver package", that I haven't installed before, but after installing it, nothing really changed.
我认为它可能与我之前没有安装的“谷歌USB驱动程序包”有关，但是在安装之后，并没有什么真正的改变。
#11
1
Try to set your emulator RAM to 1024.
尝试将模拟器RAM设置为1024。
#12
1
Elaborating on what teepee said in an earlier post, I've found that if I muck with the already-running AVD during the uploading phase, it finishes MUCH quicker (5 seconds vs 60 seconds) and I'm installed and running in a fraction of the time. This is with a 4.0.3 AVD. Haven't tried the others yet.
在之前的一篇文章中详细阐述了teepee说了什么，我发现，如果我在上传阶段把已经运行的AVD弄脏，它会更快地完成(5秒vs 60秒)，而我的安装和运行时间也只有一小部分。这是4。3 AVD。还没试过其他的。
#13
1
The alternative ways:
另一种方式:
Setting up a FTP server on your pc for hosting apk files, now you can download apk files by android emulator web browser and install app directly whitout using adb.
在您的pc上设置一个FTP服务器来托管apk文件，现在您可以通过android仿真器web浏览器下载apk文件，并使用adb直接安装应用程序。
or
或
Install a samba client on android emulator and share apk files on your pc, then copy apk files to emulator and install app directly whitout using adb.
在android仿真器上安装一个samba客户端并在您的pc上共享apk文件，然后将apk文件复制到仿真器中，并使用adb直接安装应用程序。
All of above ways are faster than adb install.
所有这些方法都比adb安装要快。
#14
0
Silly question - did you try it on several AVDs? It is possible your one AVD is messed up in some way.
愚蠢的问题——你在几个AVDs上试过吗?你的一个AVD可能在某些方面出了问题。
#15
0
Do as much interaction with emulator as you can while uploading the apk on emulator, if you press random buttons of emulator while uploading it will upload early, before it took 5-6 mins to upload but now it take only 15 - 20 secs.
在模拟器上上传apk时，尽可能多地与模拟器进行交互，如果你在上传的同时按下模拟器的随机按钮，将会提前上传，在上传之前需要5-6分钟，而现在只需要15 - 20秒。
#16
0
I have seen this too. Here is something that helped, assuming you've been using the same AVD. Wipe the user data on the AVD. After doing this, it would load the app much faster again, a couple of seconds.
我也见过。这里有一些有用的东西，假设你一直在使用相同的AVD。擦除AVD上的用户数据。这样做之后，它会再次以更快的速度加载应用程序，几秒钟。
#17
0
In a terminal/console I shell into the AVD with adb -e shell then go to the tmp directory where the apk is being uploaded cd /data/local/tmp then do ls -l to see the current file size. I've found that if I sit there and keep hitting up arrow then enter to quickly repeat the ls -l the upload speeds up dramatically. You can watch the progress as the file size increases.
在终端/控制台I shell中，使用adb -e shell将其放入AVD中，然后进入tmp目录，在该目录中，apk被上传cd /data/local/tmp，然后执行ls -l以查看当前文件大小。我发现，如果我坐在那里，不停地点击箭头，然后进入快速重复ls -l，上传速度会急剧上升。随着文件大小的增加，您可以查看进度。
This is probably similar to the effect of clicking around in the AVD others have mentioned.
这可能与别人提到的AVD中单击鼠标的效果类似。
I'm on a Mac. Not sure if it's the same on Windows or Linux.
我用的是Mac电脑，不知道Windows还是Linux都是一样的。
#18
0
This might work on windows,
这可能适用于windows，
start the Task manager --> processes tab--> look for emulator.exe,
启动任务管理器——>进程标签——>寻找模拟器。exe，
right click and set priority to high
右击并将优先级设置为high
dont forget to set it to normal after your work is done.
工作结束后，不要忘记把它设置为正常。
also closing unwanted applications which require a lot of memory like chrome and firefox can be closed when not needed.
同时关闭需要大量内存的不需要的应用程序，如chrome和firefox，在不需要的时候可以关闭。