问题描述
我整个下午都陷入困境，试图在Android Studio中再次运行我的小型Android/Kotlin应用程序.粘贴在这个问题主题上的消息突然让我失望.
I am stuck a whole afternoon trying to run again my small Android/Kotlin application in Android Studio. The message pasted on this question topic suddenly nocked me down.
我已经完成了这些尝试:
I have done these tentatives:
1-冷启动(在虚拟设备"屏幕>操作">立即冷启动"上
1 - cold boot (On Virtual Devices screen > Actions > Cold Boot Now)
2-我删除了以前的虚拟设备，并下载了一个新设备(Nexus One)
2 - I deleted my previous Virtual Device and I downloaded a new one (Nexus One)
3-我遵循了其他stackoverflow答案
3.1
cd C:\Users\Jimis\AppData\Local\Android\Sdk\platform-tool
adb kill-server
adb.exe start-server
adb devices -l
3.2
删除了平台工具，并从 SDK平台
deleted plataform-tool and redownlowaded it from SDK Plataform
3.3
重启计算机
我完全被困住了.
引起我注意的是:为什么要向端口5037分配那么多的PID.下面是波纹管，最初启动Androdi Studio时我只有3个，而在尝试调试应用程序后，我得到了更多.
Something called my attention: why so many PIDs to port 5037. See bellow that initially when I started Androdi Studio I had only 3 and after I tried debug my application I got a lot more.
Microsoft Windows [versão 10.0.18363.836]
(c) 2019 Microsoft Corporation. Todos os direitos reservados.
C:\Users\Jimis>netstat -ano -p tcp |find "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 11492
TCP 127.0.0.1:5037 127.0.0.1:50582 ESTABLISHED 11492
TCP 127.0.0.1:50582 127.0.0.1:5037 ESTABLISHED 10052
C:\Users\Jimis>netstat -ano -p tcp |find "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 11492
TCP 127.0.0.1:5037 127.0.0.1:50582 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50714 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50731 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50734 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50736 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50737 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50738 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50739 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50740 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50741 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50742 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50743 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50744 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50745 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50746 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50747 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50748 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50749 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50750 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50751 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50752 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50753 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50754 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50755 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50756 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50757 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50758 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50759 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50760 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50761 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50762 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50763 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50764 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50765 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50766 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50767 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50768 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50769 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50770 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50771 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50772 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50773 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50779 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50780 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50781 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50782 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50783 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50784 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50785 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50786 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50787 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50788 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50789 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50790 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50791 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50792 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50793 ESTABLISHED 11492
TCP 127.0.0.1:5037 127.0.0.1:50794 ESTABLISHED 11492
TCP 127.0.0.1:50582 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50714 127.0.0.1:5037 ESTABLISHED 792
TCP 127.0.0.1:50717 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:50719 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:50722 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:50729 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:50731 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50734 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50736 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50738 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50739 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50740 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50741 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50742 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50743 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50744 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50745 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50746 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50747 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50748 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50749 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50750 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50751 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50752 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50753 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50754 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50755 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50756 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50757 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50758 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50760 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50761 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50762 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50763 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50764 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50765 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50766 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50767 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50768 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50770 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50771 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50772 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50773 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50791 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50793 127.0.0.1:5037 ESTABLISHED 10052
TCP 127.0.0.1:50794 127.0.0.1:5037 ESTABLISHED 10052
C:\Users\Jimis>
试图用"netstat -a -b"找出为什么有很多建立到相同端口5037的连接的问题，我到达了此列表，但在使用Android Studio和仿真器时是否正常这不是为什么
Trying to figure out with "netstat -a -b" why so many established connections to same port 5037 I reached this list but I don't if it is normal when using Android Studio and Emulator
...
TCP 127.0.0.1:5037 SPANOT149:0 LISTENING
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50582 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50714 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50731 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50734 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50736 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50738 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50739 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50740 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50741 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50742 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50744 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50745 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50746 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50747 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50748 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50750 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50751 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50753 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50756 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50757 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50760 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50761 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50762 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50763 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50764 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50765 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50766 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50767 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50768 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50770 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50772 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50773 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50793 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50797 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:50955 ESTABLISHED
[adb.exe]
TCP 127.0.0.1:5037 orionhost:51276 ESTABLISHED
[adb.exe]
我的应用程序build.gradle
My app build.gradle
apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-android-extensions'
apply plugin: 'com.google.gms.google-services'
android {
compileSdkVersion 29
buildToolsVersion "29.0.3"
android {
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
}
defaultConfig {
applicationId "com.mycomp.appfirestore"
minSdkVersion 16
targetSdkVersion 29
versionCode 1
versionName "1.0"
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.3.72"
implementation 'androidx.appcompat:appcompat:1.1.0'
implementation 'androidx.core:core-ktx:1.2.0'
implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
testImplementation 'junit:junit:4.13'
androidTestImplementation 'androidx.test.ext:junit:1.1.1'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'
// Firebase Libraries
implementation 'com.google.firebase:firebase-core:17.4.2'
implementation 'com.google.firebase:firebase-auth:19.3.1'
implementation 'com.google.firebase:firebase-database:19.3.0'
implementation 'com.google.firebase:firebase-storage:19.1.1'
implementation 'com.squareup.retrofit2:retrofit:2.9.0'
implementation 'com.squareup.retrofit2:converter-gson:2.9.0'
implementation 'com.squareup.okhttp3:logging-interceptor:4.7.2'
}
项目build.gradle
Project build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
ext.kotlin_version = '1.3.71'
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.6.3'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
classpath 'com.google.gms:google-services:4.3.3'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
***添加了
在相关的情况下，我刚刚更新到Android Studio 4.0和相同的问题.
in case it is relevant I just aupdated to Android Studio 4.0 and same issue.
Android Studio 4.0
Build #AI-193.6911.18.40.6514223, built on May 20, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1237M
Cores: 8
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins:
我在stackoverflow上读了很多书，达到了这个其他问题
Reading a lot on stackoverflow I reached this other issue
我尝试使用
Vulkan = off
GLDirectMem = on
我不知道我到底做了什么，但是无论如何我都尝试过，但仍然遇到同样的问题.在同一stackoverflow讨论中，我注意到有人在谈论hyper-V.
I don't know exactly what I did but I tried it anyway and I am still getting same issue. In this same stackoverflow discussion I noted someone talking about hyper-V.
如果有意义的话，前一段时间我在Windows 10中关闭了Hyper-V，因为我不得不出于其他原因(OpenShift/minishift)使用VirtualBox.我认为这与我的问题没有关系，因为直到2天前，端口5037都没有出现这种问题.顺便说一句，我很好奇:Android模拟器是否某种程度上依赖HyperV?
In case it is relevant, I have turned off Hyper-V some time ago in my Windows 10 because I had to use VirtualBox for other reasons (OpenShift/minishift). I don't think it has relathionship with my issue because until 2 days ago I had not such problem with port 5037. BTW, I am curious: does Androids Emulators depend on HyperV somehow?
***在雅各布发表评论后进行了编辑
*** edited after Jacob's comment
Microsoft Windows [版本10.0.18363.836](c)2019微软公司. Todos os direitos储备库.
Microsoft Windows [versão 10.0.18363.836](c) 2019 Microsoft Corporation. Todos os direitos reservados.
1)在启动Android Studio之前，我没有按预期连接到5037
1) Before I started Android Studio I had no connection to 5037 as expected
C:\ Users> netstat -ano | findstr"5037"
C:\Users>netstat -ano | findstr "5037"
2)然后，我启动了Android Studio，并看到至少三个与端口5037的连接.
2) Then I started Android Studio and I see at least three connections to port 5037.
C:\Users\Cast>netstat -ano | findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 11880
TCP 127.0.0.1:5037 127.0.0.1:54602 ESTABLISHED 11880
TCP 127.0.0.1:54602 127.0.0.1:5037 ESTABLISHED 348
3)然后，当我单击调试"应用程序(shift + F9)时，在Android Studio的左下角出现两条消息错误
3) And when I click on Debug app (shift + F9) I get two messages errors on left bottom side of Android Studio
Emulator: emulator: ERROR: AdbHostServer.cpp:102: Unable to connect to adb daemon on port: 5037
Emulator: socketTcpLoopbackClientFor: error: fd 56668 above FD_SETSIZE (32768)
以及与大量TIME WAIT的大量连接.对我来说似乎很奇怪.
and a lot of connections with numerous TIME WAIT. It seems so weird to me.
C:\Users>netstat -ano | findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 11880
TCP 127.0.0.1:5037 127.0.0.1:54602 ESTABLISHED 11880
TCP 127.0.0.1:5037 127.0.0.1:54631 ESTABLISHED 11880
TCP 127.0.0.1:5037 127.0.0.1:54643 ESTABLISHED 11880
TCP 127.0.0.1:5037 127.0.0.1:54647 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54648 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54649 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54650 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54662 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54663 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54665 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54666 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54667 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54668 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54669 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54670 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54671 ESTABLISHED 11880
TCP 127.0.0.1:5037 127.0.0.1:54672 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54673 ESTABLISHED 11880
TCP 127.0.0.1:5037 127.0.0.1:54674 TIME_WAIT 0
TCP 127.0.0.1:54602 127.0.0.1:5037 ESTABLISHED 348
TCP 127.0.0.1:54631 127.0.0.1:5037 ESTABLISHED 5224
TCP 127.0.0.1:54634 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:54636 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:54639 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:54641 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:54643 127.0.0.1:5037 ESTABLISHED 348
TCP 127.0.0.1:54671 127.0.0.1:5037 ESTABLISHED 348
TCP 127.0.0.1:54673 127.0.0.1:5037 ESTABLISHED 348
C:\Users>
整个事件日志
01/06/2020
00:08 Gradle sync started
00:08 * daemon not running; starting now at tcp:5037
00:08 * daemon started successfully
00:08 Gradle sync finished in 2 s 418 ms (from cached state)
00:08 Executing tasks: [:app:assembleDebug] in project C:\WSs\FireStoreDemos\AppFirestore
00:08 Emulator: socketTcpLoopbackClientFor: error: fd 56296 above FD_SETSIZE (32768)
00:08 Emulator: socketTcpLoopbackClientFor: error: fd 56296 above FD_SETSIZE (32768)
00:08 Emulator: emulator: ERROR: AdbHostServer.cpp:102: Unable to connect to adb daemon on port: 5037
00:08 Emulator: socketTcpLoopbackClientFor: error: fd 56668 above FD_SETSIZE (32768)
00:08 Emulator: socketTcpLoopbackClientFor: error: fd 56668 above FD_SETSIZE (32768)
00:08 Emulator: socketTcpLoopbackClientFor: error: fd 56928 above FD_SETSIZE (32768)
00:08 Emulator: socketTcpLoopbackClientFor: error: fd 56928 above FD_SETSIZE (32768)
00:08 Gradle build finished in 19 s 659 ms
00:08 Install successfully finished in 584 ms.: App restart successful without requiring a re-install.
***更改ADB端口后进行了编辑
*** edited after changed ADB port
我在Windows环境中将ANDROID_ADB_SERVER_PORT更改为5038，然后重新启动Android Studio，仍然看到5037在等待连接.
I changed ANDROID_ADB_SERVER_PORT to 5038 in Windows Environment and restart Android Studio and I still see some 5037 waiting for connection.
在Windows中更改环境变量ANDROID_ADB_SERVER_PORT后
After changed Environemnt Variable ANDROID_ADB_SERVER_PORT in Windows
C:\Users\>netstat -ano | findstr "5037"
TCP 127.0.0.1:5037 127.0.0.1:54643 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54671 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:54673 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:55204 TIME_WAIT 0
TCP 127.0.0.1:54602 127.0.0.1:5037 TIME_WAIT 0
TCP 127.0.0.1:54631 127.0.0.1:5037 TIME_WAIT 0
C:\Users\>netstat -ano | findstr "5038"
TCP 127.0.0.1:5038 0.0.0.0:0 LISTENING 7912
TCP 127.0.0.1:5038 127.0.0.1:55238 ESTABLISHED 7912
TCP 127.0.0.1:55238 127.0.0.1:5038 ESTABLISHED 11368
推荐答案
这很可能是由于权限不足引起的.以管理员身份运行Android Studio或命令提示符(以您喜欢的方式为准)，这应该可以解决您的问题.
This is likely caused by insufficient permissions. Run Android Studio or your command prompt (whichever you prefer) as an administrator and that should solve your problem.
这篇关于模拟器:模拟器:错误:AdbHostServer.cpp:102:无法连接到端口5037上的adb守护程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！