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

Issue 835326 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Android device not visible in DevTools

Reported by teo8...@gmail.com, Apr 20 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. Connect my phone via USB
2. Open a web page in Chrome on my phone
3. On the Computer, in Chrome, go to DevTools -> more Tools -> remote Devices

What is the expected behavior?
Should find my fucking phone listed and be able to inspect it

What went wrong?
my phone doesn't fucking show up

Did this work before? Yes no idea, but it used to

Chrome version: 65.0.3325.181  Channel: n/a
OS Version: 
Flash Version:
 
Screenshot from 2018-04-20 18-34-51.png
14.2 KB View Download

Comment 1 by teo8...@gmail.com, Apr 20 2018

I see, it's a bug in Android, not in Chrome.

For some reasons, USB debugging got disabled on its own (I had enabled it ages ago and never disabled it).
Not only that, but also the Developer Options disappeared from the Settings (I had to the click-7-times-on-build-bumber trick again).

However, even after reenabling the developer options, turning those on, and enabling USB Debugging, still nothing happens.
When I connect the phone to the computer, it's supposed to show me a notification icon that USB debugging is enabled. It doesn't.

I don't know where the fuck the Android bugtracker has ended up, so please somebody report that to the Android team.

Comment 2 by woxxom@gmail.com, Apr 20 2018

Try debugging over wifi connection by installing "WiFi ADB" android app. 
You can find many tutorials.

Comment 3 by teo8...@gmail.com, Apr 20 2018

> Try debugging over wifi connection by installing "WiFi ADB" android app. 
> You can find many tutorials.

Thank you for the workaround. Anyway, the issue still remains, USB debugging is supposed to work. (Who says there's a wifi network available, btw).

This seems to be an issue on the Android end, because I don't see the usual notification icon that used to appear as soon as I would connect the usb cable, indicating that USB debugging is enabled.
Labels: Needs-Triage-M65
Labels: -OS-Linux OS-Android
The issue seems to be related to OS-android. Hence, adding appropriate labels.

Thanks...!!
Labels: Needs-triage-Mobile
Cc: sandeepkumars@chromium.org
Labels: -Needs-Triage-M65 Triaged-Mobile Needs-Feedback
Tested the issue using #65.0.3325.181 on Mac 10.13.3, connected Pixel 2 device to Mac using USB cable. Device was detected and can see under remote devices.

@Reporter: Could you please try disable to enable USB debugging from developer tools and check if you still face the issue?

Thanks!!

Comment 8 by teo8...@gmail.com, Apr 24 2018

> @Reporter: Could you please try disable to enable USB debugging 
> from developer tools

You mean disable and reenable it on the Android phone?
I tried that a million times, didn't help.
As I said, from the phone it looks like usb debugging doesn't get enabled at all (when plugging the phone to the computer, I expect a debug icon to appear on the notification area right away, and it doesn't happen).

Or did you mean disable and reenable "discover USB devices" from Chrome on the computer? Tried that as well already, nothing changes.
Project Member

Comment 9 by sheriffbot@chromium.org, Apr 24 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Blink>USB
This seems to be a issue with USB debugging, hence adding related component for further triaging of the issue as this issue isn't reproducible form TE end.

Thanks!!
Cc: reillyg@chromium.org
Components: -Blink>USB
Labels: -OS-Android Needs-Feedback OS-Linux
Summary: Android device not visible in DevTools (was: Can't fucking debug a mobile device)
Please be mindful of the Chromium Code of Conduct and be respectful when communicating on issue reports: https://www.chromium.org/conduct

Since it appears you are on Linux please make sure that you have appropriate udev rules configured for having access to ADB devices. Instructions here: https://developer.android.com/studio/run/device

If USB debugging is enabled on your phone and yet you do not see the notification that USB debugging is active then you may be using a cable which only provides power and not data. Please run `lsusb` or check in chrome://device-log to check that your computer is detecting that the phone has been plugged in.
Please be mindful of the Chromium Code of Conduct and be respectful when using this issue tracker: https://www.chromium.org/conduct

If the phone is not displaying the USB debugging notification even through USB debugging is enabled then it probably not detecting the host. This may be because you are using a charge-only USB cable that does not properly connect the USB data pins. Please check the output of the `lsusb` command or chrome://device-log to ensure that the device is being detected by the host.

Comment 13 by teo8...@gmail.com, Apr 26 2018

> you may be using a cable which only provides power and not data

Nope, not the case. I use the very same cable to program an arduino.
Project Member

Comment 14 by sheriffbot@chromium.org, Apr 26 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
What about my other questions? Do you have the appropriate udev rules configured to give your user access to the device? Does this device appear in the output of the `lsusb` command? Does the device appear in chrome://device-log?
Status: WontFix (was: Unconfirmed)
As there is no action on this issue for long time closing this issue. Request you to update your Chrome to latest #66.0.3359.181 and verify. Feel free to file a new issue if the issue is still reproduced at your end.

Thanks!

Sign in to add a comment