Status Update
No update yet.
Comments
im...@gmail.com
mo...@gmail.com
vl...@gmail.com
adb connect
failed to connect to '
na...@dekaresearch.com
re...@gmail.com
any expected fix ?
am...@gmail.com
[Deleted User] <[Deleted User]>
The workaround does work but slows me down because I keep forgetting.
cm...@gmail.com
So I can not connect device via wifi to debug.
e....@gmail.com
1a. Linux: Put this in your ~/.bashrc
function adbc() {
adb connect $1:5555
}
1b. Windows: Put this in adbc.bat anywhere in your PATH
@echo off
adb connect %1:5555
2. Run like adbc <IP>.
3. Profit.
en...@google.com
en...@google.com
en...@google.com
e....@gmail.com
ha...@icloud.com
I'm getting the same issue with version 1.0.41 on Rapsbian
pi@homebridge:~ $ adb --version
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
pi@homebridge:~ $ adb connect 10.0.0.16
* daemon not running; starting now at tcp:5037
* daemon started successfully
missing port in specification: tcp:10.0.0.16
en...@google.com
that's the debian version, not ours...
Version 28.0.2-debian
you'll need to talk to them about that.
it's also a very very old version.
you can download our current supported version from
ma...@gmail.com
vi...@gmail.com
Using Ubuntu 22.04.1 LTS, and downloading the latest ADB version:
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip && unzip platform-tools-latest-linux.zip
It's still asking for port specification:
$ ./adb version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
Installed as /home/user/Downloads/platform-tools/adb
$ ./adb connect 192.168.0.0
missing port in specification: tcp:192.168.0.0
en...@google.com
d'oh, looks like you're right... i think
shaju: want to fix parse_tcp_socket_spec() and add the missing tests to socket_spec_test.cpp (for both textual and numeric ip addresses)?
sh...@google.com
e....@gmail.com
is this linux only?
C:\Users\█\Downloads>adb connect 192.168.1.99
connected to 192.168.1.99:5555
C:\Users\█\Downloads>adb version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
Installed as C:\Android\Sdk\platform-tools\adb.exe
sh...@google.com
en...@google.com
yeah, actually, despite the code looking weird (and the lack of tests), both "1.2.3.4" and "1.2.3.4:1234" work for me on unix too. so although we can clean that code up (and add the missing tests so we're not confused in future), i don't think that's vitprado's problem...
vitprado: try adb kill-server and try again?
vi...@gmail.com
./adb version was running the downloaded version (33.0.3), but ./adb connect 192.168.0.x without adb kill-server was running the Ubuntu version (28.0.2).
I fixed it by replacing the Ubuntu binary with the downloaded binary. So to fix it on Ubuntu 22.04 (for now):
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip && unzip platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/lib/android-sdk/platform-tools/adb
Thank you!
Description
- Ubuntu 18.10
- Android Platform-Tools 28.0.2-5303910
- ADB 1.0.40
Steps to reproduce:
- Connect to a device with ADB over TCP, without specifying a port number e.g. "adb connect 192.168.1.20"
Expected behaviour:
- Connect to the device using the default port of 5555
Actual behaviour:
- Receive an error message: "missing port in specification: tcp:192.168.1.20"
Workaround:
- Specify the device port number e.g. "adb connect
Additional information:
I believe this relates to recent changes to this else statement in socket_spec.cpp (