Develop Reference

Multiple devices issue in tcpip

I'm using termux in Android
I connect my using tcpip
I can't excute command reason show multiple devices connected
adb devices
List of devices attached
emulator-5554 device

adb allows multiple devices to be connected which will not allow to run the shell
you can try restarting the server using the following command and try again
adb kill-server
adb start-server
it worked for me some one already mentioned about the -s Serial number ( phone / emulator id )
adb -s SERIAL shell
so that will also be a good option to try
you can also try command line to connect with the target using
adb connect xxx.xxx.xxx.xxx:port
you may also try
adb disconnect
and retry
Good luck

ADB Connection refused from Mac to Android

I am trying to sideload a build to my phone, Alcatel Android 7. I have been able to sideload to it before but it's stopped working when I switched to a new network. I am running it from MacOS terminal.
Courtneys-MacBook-Pro-3:~ courtneytaniguchi$ adb connect 10.0.0.216
failed to connect to '10.0.0.216:5555': Connection refused
Courtneys-MacBook-Pro-3:~ courtneytaniguchi$
This phone is developer enabled, I have allowed installation of apps from unknown sources turned on in security, and USB debugging is on too. Yes, I am on the same network.

I had a similar problem failed to connect to '192.168.31.84:5555': Connection refused, final worked by:
kill and restart adb
adb kill-server
adb start-server
makesure USB wired connected
adb devices can see your device id
re-config to tcpip mode: adb tcpip 5555
Note: for multiple USB connected devices, should specify device serial id:
adb -s device_serial_id tcpip 5555
connect to you device via WiFi: adb connect your_android_phone_ip:5555
Full log for your refer:
 adb kill-server
 adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
 adb devices
List of devices attached
2e2a0cb1 device
orga4pmzee4ts47t device
 adb tcpip 5555
error: more than one device/emulator
 adb -s 2e2a0cb1 tcpip 5555
restarting in TCP mode port: 5555
 adb connect 192.168.31.84:5555
connected to 192.168.31.84:5555

Based on the commands you are entering it seems you are trying to do adb over wifi.
The following may help:
Rebooting the phone
Ensuring the phone is listening over TCP/IP by connecting to it via the USB and entering adb tcpip 5555
Turning USB debugging off and on again

I had the same error. Solved by following extra steps mentioned here which is connecting the device via USB and then executing the following command after finding device id :
./adb -s <device id> tcpip 5555

If you are stuck in the sideloading process, you can always e-mail the .apk file to yourself at an e-mail address which is configured on the phone, download the attachment, then go to 'downloads' app, and click on the .apk file, it should ask if you are sure you want to install the app, just say yes. You have to make sure that you have already selected 'Allow' in the Unknown Sources section in Settings/Development.

Same happened with me. Always rejected, I have two devices used to connect over wifi for some Android Project, im always rejected to 5555 on my Huawei Device. But there is one workaround i know that works.
➜ ~ adb connect 192.168.8.108:5555
failed to connect to '192.168.8.108:5555': Connection refused
➜ ~ adb connect 192.168.8.108:7612
connected to 192.168.8.108:7612
Try port 7612
Thanks!

Eclipse - How to add a specific driver (.ko file) as a module in Android

I'm runnig Eclipse Android v3.8 with Ubuntu, and I need to add a specific driver in the emulated system.
The driver is cp210x.ko, to connect an Arduino.
I have seen this post (for USB device), but the device is not reconize yet.
I have already builded this module with this source of Android (it works in a real system), but I don't know how to add it in Eclipse.
How can I do this?
Edit:
I don't know if it's possible. I have try the command lsmod to see what driver was already runnig:
~$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~$ adb devices
List of devices attached
emulator-5554 device
~$ adb shell
root#generic:/ # lsmod
/proc/modules: No such file or directory
So it's not the good method...

Adb install apk failure

my problem is about android and the adb commands. I'm working on a Nexus 5 and i want to install and apk with adb commands. So i start with adb devices, my mobile is detected by the computer so i go to the repertory where the apk is located and i launch adb install name.apk
It returns :
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
- waiting for device -
The Nexus 5 is rooted, and usb debug is activated
adb devices give me some sort of serial number of the mobile

If adb devices gives you a list of devices, then you could try to take serial number of your device and call adb -s <serialNumber> install name.apk. Here is more options you could try.

If you are using Ubuntu try restarting the adb server by giving sudo permission.cd > adb location and do sudo ./adb kill-server and sudo ./adb start-server.

Changing default port (i.e. 5037) on which adb server runs

I am a budding android developer and if there is no easy way of configuring the adb server to run on another port then the inflexibility of the tools will force me to quit android app development.
A web search did not return any solutions.
I also searched for '5037' in all files in android sdk directory but did not find a setting there.

Use the environment variable ANDROID_ADB_SERVER_PORT to select the port.
The following works under bash:
$ export ANDROID_ADB_SERVER_PORT=12345
$ adb start-server
* daemon not running. starting it now on port 12345 *
* daemon started successfully *
$ adb devices
List of devices attached
TA2070M5O6 device
$ ANDROID_ADB_SERVER_PORT=6789 adb devices
* daemon not running. starting it now on port 6789 *
* daemon started successfully *
List of devices attached
In another terminal I ran:
$ ANDROID_ADB_SERVER_PORT=6789 emulator ...
Back to original terminal:
$ ANDROID_ADB_SERVER_PORT=6789 adb devices
List of devices attached
emulator-5554 device
$ adb devices # ANDROID_ADB_SERVER_PORT was exported as 12345
List of devices attached
TA2070M5O6 device
I found this via the Jenkins Android Emulator Plugin as I noticed it was running adb on a different port.

With the latest adb version,
Use option -P (Note: Caps P)to start adb server in a specific port.
For Example, Try
$adb -P 5038 start-server
It will list the devices attached to this specific adb server. If the adb server is not running then it will start a new adb server with the given port number.
Hope it helps someone reading this post.
Thanks.

In Windows, go to Environment Variables – Add a new one called ANDROID_ADB_SERVER_PORT
and set it to whatever you want, I've set to 5038.
Should look like this:
Solved it for me.

There is another variable that supports this for connecting to a different machine's adb:
ADB_SERVER_SOCKET=tcp:some.other.host:1234 adb devices
To use it, you need to start adb on the other host with -a and probably background it too:
( adb -a -P 1234 nodaemon server & ) &