:app:assembleDebug UP-TO-DATE
:app:installDebug
05:53:18 E/adb: error: could not install *smartsocket* listener: Address already in use
05:53:18 E/adb: ADB server didn't ACK
05:53:18 E/adb: * failed to start daemon *
05:53:18 E/adb: error: cannot connect to daemon
05:53:18 E/ddms: '/Users/bjhl/Library/Android/sdk/platform-tools/adb,start-server' failed -- run manually if necessary
:app:installDebug FAILED
the simulator i used is genymotion
i had solved this problem; when i check my system path , i found two android sdk paths; delete one of them, then it works well
@node-rookie i have:
export PATH=$PATH:/usr/local/android-sdk-linux/
export PATH=$PATH:/usr/local/android-sdk-linux/tools
export PATH=$PATH:/usr/local/android-sdk-linux/platform-tools
export PATH=$PATH:/usr/local/android-sdk-linux/build-tools
in ~/.bashrc
when i removed the last 3 i still get the error
I cannot find a solution too. Setting ADB path in Genymotion to Android SDK has no effect.
I have exactly the same problem. Happened to me after using my pixel. I spent over three hours now!
I have the same problem, and it not work for me
Guys, I might have found the solution, are you all using Android Studio IDE?
I had solved that. Just set the host 127.0.0.1 localhost, then it runs ok. Actually, I also close my proxy, the network maybe a case.
Just check whether your path is correct set or not
I had the same issue and just did
ps -ef | grep 5037
505 11809 1 0 4:44PM ?? 0:07.17 adb -P 5037 fork-server server --reply-fd 4
Got another adb process already running but not sure why it was started
Just did a kill -9 11809 and started adb server and its working fine now
@Sinapse87 Yes, the problem began once I installed Android Studio IDE
I have the same problem. It also started when I updated to a newer Android Studio IDE
Can you post here your log what is problem you facing?
I had another process running on the same port as adb. I killed it and it worked fine.
Also, if there is anyone still having this problem, take a look at the response of this guy https://stackoverflow.com/a/45456154/6115334 for me that solved the problem. I had an adb old version that was being found first in my path variable, It was not the version I was expecting to be executed, this old version is the one the always was having the port taken.
Same issue windows 7 without the Android SDK installed; using the genymotion adb.
All i did to fix was add the ‘C:Program FilesGenymobileGenymotiontools’ to the system path.. Presto..
the adb version on your system is different from the adb version on the android sdk platform-tools
link
it works for me
1 check sys adb version
# adb version
Android Debug Bridge version 1.0.39
2 check sdk adb version
# cd /Users/wan-mac/Library/Android/sdk/platform-tools
# ./adb version
Android Debug Bridge version 1.0.32
3 copy
# sudo cp /Users/wan-mac/Library/Android/sdk/platform-tools/adb /usr/local/bin
that’s all
arthurdenner, vanmart, dpnthanh, yingliangzhang, JasonMannon, syumai, bslayerw, ribamarsantos, and Vitiell0 reacted with hooray emoji
arthurdenner, pedrobertao, vanmart, techview51, v7, yingliangzhang, stoichoandreev, damianlajara, JasonMannon, rexlow, and 5 more reacted with heart emoji
Thank you very much, @wikieswan. Your solution worked for me.
I’m using Genymotion’s adb, and needed to add it to my PATH environment variable. eg. in Mac/Linux’s ~/.bash_profile:
export PATH=$PATH:/Applications/Genymotion.app/Contents/MacOS/tools
Then confirm it’s available with:
source ~/.bash_profile
which adb
@wikieswan thank you, works now
it sucks when this happened to you close to a deadline 😞
I think this will solve your problem
write cmd: ps -ef | grep 5037
great’s job @wikieswan i resolved my problem trough your solution. thx
@wikieswan I get this on my SDK adb version and sys adb version both.
Android Debug Bridge version 1.0.36
Revision 1:7.0.0+r33-2
And have set to Use custom Android SDK tools in Genymotion.
But when I run start Genymotion and run adb devices to check. This is what I’m getting.
List of devices attached
adb server version (39) doesn't match this client (36); killing...
error: could not install *smartsocket* listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Is there anyway to fix this ?
1.Genymotion settings=> ADB=>use customer Android tools
2.close Android Studio
3.yarn start
facebook
locked as resolved and limited conversation to collaborators
Jun 26, 2018
I am getting this error since two days ago when I updated my Android Studio to the latest stable version 2.3; the full error message I am getting from Gradle Console is:
07:59:59 E/adb: error: could not install *smartsocket* listener: Address already in use
07:59:59 E/adb: ADB server didn't ACK
07:59:59 E/adb: * failed to start daemon *
07:59:59 E/adb: error: cannot connect to daemon
07:59:59 E/ddms: '/Users/USER_NAME/Library/Android/sdk/platform-tools/adb start
server' failed -- run manually if necessary
My attempts to solve the issue:
-
kill all
adbprocesses and make sure no process is holding port 5037,adb kill-server(says* server not running *even in cases when adb is running), close Android Studio, delete~/.androiddirectory, runadb start-server(says* daemon not running. starting it now at tcp:5037 *; * daemon started successfully *, start Android Studio and run application, MAC throws erroradb quit unexpectedlyand gradle console shows same the error I posted above. -
uninstalled and deleted all Android Studio stuff (except for projects directory), restarted MAC, installed fresh and latest android studio.
-
increased gradle vm ram
org.gradle.jvmargs=-Xmx1536Min projectgradle.properties -
uninstalled antivirus and restarted the mac
Environment:
- OS: MacOS Sierra 10.12.3
- Android Studio: 2.3
- buildToolsVersion: ‘25.0.0’
- Android Debug Bridge version: 1.0.39
kennytm
504k104 gold badges1068 silver badges996 bronze badges
asked Mar 27, 2017 at 0:18
2
Address already in use means you have another instance of adb running.
Check your system variable $PATH and $ANDROID_HOME and local.properties file (of your project) and your .bash_profile . Make sure that all of these has same android sdk path. Then try restarting the adb server.
adb kill-server and adb start-server.
answered Apr 5, 2017 at 6:30
JIthinJIthin
1,4171 gold badge13 silver badges29 bronze badges
1
I usually find this issue occurring when I have two instances of ADB working, i.e when I have my Eclipse and Android studio running at the same time AND when they point to different SDK Manager(platform-tools folder) on the system. Try to search for what other IDE is using ADB, kill it in the Activity Monitor and run only one instance. Or my work around was to have only one SDK Manager and point both my IDEs to one platform-tools folder.
Hope that helps.
answered Apr 3, 2017 at 22:20
NehaNeha
171 silver badge2 bronze badges
In my case, I had an old version of adb installed using brew cask. And while I updated my Android Studio to the latest, the adb was still pointing to the brew installed older version.
So after updating that version, using:
brew cask install android-platform-tools
And making sure that the adb itself was pointing to the new version, the errors went away.
answered Sep 19, 2019 at 0:40
Edward TanEdward Tan
9249 silver badges17 bronze badges
Just write down platform-tools path (/Users/USER_NAME/Library/Android/sdk/platform-tools)
In the .bash_profile file, located at (/Users/USER_NAME/.bash_profile), like this :
export PATH=»$PATH:/Users/USER_NAME/Library/Android/sdk/platform-tools»
answered Aug 2, 2019 at 15:47
1
I executed cmd adb devices from terminal but instead of getting list of connected devices, I observed below error:
List of devices attached
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
How can I get list of connected device?
asked Jul 15, 2016 at 13:07
0
Faced this issue on Mac:
I have tried different solution, But below works for me —
- Uninstall «Vysor» plugin if you have installed for Chrome
- Under Home folder > find .Android folder and move to trash
- Goto, Android sdk > delete/move to trash platform-tools folder
- Again install/download from Android SDK Manager
- Open terminal —
adb kill-serveradb start-server
- Check
adb devices, It will work and display you all connected devices.
Hope it helps !
answered Jul 21, 2016 at 9:59
I had the same issue. I realized that I updated all my packages in the SDK manager recently. And having a second look I saw that I had the Android SDK platform tools installed twice (24.0.1 and 23.0.3). After deinstalling the 23.0.3 version everything worked more stable again including Vysor.
answered Aug 22, 2016 at 10:59
0
If you are using Genymotion, go into Settings>> ADB, and instead of letting Genymotion use its custom adb, directly point it to android sdk on your system.
ALso besides genymotion, there are other applications that use adb that would cause this conflict problem. You will have to check your app list.
answered Jul 17, 2016 at 18:17
3
Are you using Vysor? You may have installed it as a Chrome plugin. Please uninstall it because it also uses the Android SDK
answered Jul 19, 2016 at 7:55
2
I finally solved this issue by uninstalling HTC Sync.
The issue is caused by multiple running or older versions of adb.exe.
Open task manager and locate adb.exe, right click -> Open file location, in my case it showed C:Program Files (x86)HTCHTC Sync ManagerHTC Syncadb.exe.
answered Sep 11, 2016 at 19:56
1
I have GapDebug running pretty much 24/7 and I have found that it sometimes interferes with ADB. So I exit GapDebug, then start ADB, then restart GapDebug and all is well.
answered Sep 2, 2016 at 16:24
1
I have a slighlty different error message when starting adb on Android SDK
adb server version (32) doesn't match this client (36); killing...
error: could not install *smartsocket* listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If you somehow have SyncMate application installed on Mac OS X, SyncMate has and use their own adb to connect to Android devices using TCP/IP port 5037. Therefore, SyncMate adb causes port conflict with Android SDK adb default listen port.
Removing SyncMate application or change Android SDK adb port to other port than 5037 will solve this issue
answered Nov 21, 2016 at 23:33
AryoAryo
1011 bronze badge
1

