New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 648741 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Oct 2017
Cc:
█ lhchavez@chromium.org
elijahtaylor@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Chrome shell won't execute ADB connect correctly (appends extra port that causes connect failure)

Reported by swolf...@slack-corp.com, Sep 20 2016 
Chrome Version: Version 54.0.2840.24 dev
Chrome OS Version: Platform 8743.25.0 (Official Build) dev-channel veyron_minnie
ARC Version 3264590
Firmware Google_Veyron_Minnie.6588.197.0
Chrome OS Platform: Asus C100p
<b>Network info: <network, encryption type, router model (if known)></b>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) On a chromebook that has developer mode enabled and adb debugging enabled Go to wifi settings and grab the ip address of the chromebook
(2) open up a terminal (ctrl + alt + t)
(3) type 'shell' to start the adb shell 
(4) type adb connect <ip address>:22 as instructed in this document https://developer.android.com/topic/arc/index.html

Expected Result:
successfully connected to device

Actual Result:
(for ip address = 10.10.23.8) the result is unable to connect to 10.10.23.8:22:22 (an extra port gets appended, causing adb connect to fail)

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

Always
What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.
Screenshot 2016-09-20 at 2.10.25 PM.png
74.4 KB View Download

Comment 1 by dhadd...@chromium.org, Oct 11 2016

Cc: elijahtaylor@chromium.org lhchavez@chromium.org
Components: Platform>ARC

Comment 2 by uekawa@google.com, Oct 12 2016 

on 55.0.2882.0 8888.0.0 (today's canary) test image device on samus,
adb connect localhost:22 worked.
adb connect xx.xx.xx.xx:22 worked.

I'm guessing this is non-test image official dev image in developer mode?

Comment 3 by lhchavez@chromium.org, Oct 12 2016 

As a workaround, can you try connecting from a workstation? If it's not the non-test official theory, there might be something R54-specific about the adb binary.

Comment 4 by lhchavez@chromium.org, Oct 13 2016 

Tried this from a non-test M54 Pixel 2015 (R54-8743.57.0.0). Same as uekawa@, I can both connect with

adb connect localhost:22
adb connect 192.168.xx.xx:22

I was unable to reproduce this issue in any way, even disabling ADB support in Android, trying to block the port, and stop Android altogether caused adb connect to "succeed".

Another workaround you can try is to do

adb connect 192.168.254.2

(note the lack of port). That should directly connect to Android instead of going through sslh.

Now, to correctly diagnose this, we'd like to get more information. Can you send feedback when this is happening (Shift+Alt+I) and mention lhchavez@ in the description. Also post the output of `sudo ps aux | grep sslh`.
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 16 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment