Chrome DevTools detects device only when device is plugged out/disconnected

468 views Asked by At

Short summary:

Chrome DevTools doesn't detect my device (Google Pixel 7 Pro) when device is plugged in. The interesting thing is that the device is recognized when I disconnect it from the cable. When that happens, I am able to see pages opened in a browser on my device for a short period of time (5 seconds) before they disappear. Of course, in that scenario pages are not interactive, so If you click "Inspect" option before it dissapear nothing will happen.

Some useful information:

  • Chrome DevTools and device detection worked for me in the past. Therefore, I am not trying this for the very first time.
  • USB debugging is enabled on the phone
  • I tried setting USB preferences to "File transfer", "MIDI", "No data transfer", etc. It behaves the same for every mode.
  • I am able to see my device from File explorer. I can copy photos from the phone to laptop, etc.
  • When I run adb devices command my device is recognized (and it is not in the offline mode)
  • I followed the troubleshooting instructions from the official page. My device is connected to the machine directly, I tried unplugging the USB cable multiple times and USB cable definitely works.
  • I tried to install OEM USB driver manually, but I am not allowed to replace the driver. This happens after I choose a new driver location enter image description here
  • Chrome DevTools recognize a device from my college. So, the problem is probably somehow related to specific device model, not to machine settings. In my case the device is Google Pixel 7 Pro

Any ideas?

1

There are 1 answers

1
Josh McGee On

The following steps result in something usable for me but it's not clear to me yet why this particular sequence seems to work:

  1. turn off "USB debugging" in the Android settings
  2. run "Revoke USB Debugging Authorizations" in the Android settings
  3. turn on USB debugging
  4. switch to Chrome and accept the request
  5. run "Revoke USB Debugging Authorizations" again
  6. switch to Chrome and accept the request again