android连接夜神模拟器出现daemon not running; starting now at tcp:5037问题解决
2020-05-10 04:14
3751 查看
连接夜神模拟器，进入Sdk/platform-tools目录运行
adb connect 127.0.0.1:62001
但是，今天在连接模拟器的时候出现如下情况
显然是5037端口被占用,用管理员打开cmd
netstat -ano | findstr "5037"
查看哪个进程占用了5037端口
杀死这个进程
taskkill /F /PID 19476
再次连接，成功
小松与蘑菇
原创文章 126获赞 414访问量 12万+
关注
私信
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- mac下* daemon not running.starting it now on port 5037 * 问题解决
- * daemon not running.starting it now on port 5037 * 问题解决
- * daemon not running.starting it now on port 5037 * 问题解决
- adb: CreateFileW 'nul' failed: 系统找不到指定的文件，* daemon not running; starting now at tcp:5037
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK .
- 最新Android 出现Please ensure that adb is correctly located at问题的解决方法
- Android 出现Please ensure that adb is correctly located at问题的解决方法
- adb命令安装apk，和安装问题daemon not running. starting it now on port 5037解决
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- daemon not running. starting it now on port 5037 ADB server didn't ACK 解决5037端口被其他进程所占用
- 最新Android 出现Please ensure that adb is correctly located at问题的解决方法
- android变异时报出daemon not running. starting it now on port 5037错误
- adb -连接不上- daemon not running. starting it now on port 5037 ADB server didn't ACK
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- 最新Android 出现Please ensure that adb is correctly located at问题的解决方法
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- Android adb shell:daemon not running. starting it now on port 5037错误
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK