Remote debugging using USB debugging is not woking I'm trying to remotely debug Chrome on my Samsung Galaxy Note 4, but I can't seem to get it working.

Note - to eliminate a device problem I have also tried to use an HTC One M8, but that also would not work.

Having reviewed the requirements from the Chrome remote debugging page -https://developer.chrome.com/devtools/docs/remote-debugging - I believe I meet all of the requirements -


Mobile device - Chrome 42.0.2311.111 (Lollipop 5.0.1)
Device used for debugging - Chrome Canery 44.0.2394.3 (Windows 7)
USB Drivers - Downloaded and installed from the Samsung website


Both devices are connecting to my laptop without issue, and I can transfer files between the two, however USB debugging is not working.

According to the above guide I should see a notification entitled Allow USB debugging?  However, this notification is no where to be seen, and consequently the device inspector (chrome://inspect/#devices) is reporting no devices detected.

I've found many similar questions that advise the user to focus upon the USB driver, however I have ensured that I have my manufacturers latest version installed and I have had no success.

Is anyone able to advise on what I may try next?



Edit - I forgot to mention that I have also looked in to downloading the Google USB driver - http://developer.android.com/sdk/win-usb.html#download

However, I'm running Windows 7 x64, and it appears that these drivers are only suitable for x86 installations.

I've now also downloaded the Universal Windows ADB Driver Universal Windows ADB Driver as recommended on this site, but still no joy - USB Debugging is not showing in ADB devices

I have also installed the ADB plugin for Chrome Canery, but once installed the plugin notifies you that it is no longer required.
I found the missing pieces of the puzzle were installing the Java SDK &amp; Android SDK.

I came across this because I couldn't connect to the "adb interface" - the Android remote debugging instruction page never mentioned installing an SDK, so I Googled "how to set up adb interface", and I found this page on How To Geek.

After installing the Java SDK &amp; Android SDK, I was able to detect the device using "adb detect", and then Chrome was able to detect the device on chrome://inspect.

Prior to installing the Java SDK &amp; Android SDK, chrome://inspect would not detect the device.

The version of Chrome Canary I was using was 48.0.2547.0 (64-bit).

The fact that the Java SDK &amp; Android SDK install fixed the problem contradicts Google's own advice here:


  You no longer need to configure ADB or the ADB plugin to debug remote
  browser tabs and WebViews. Remote debugging for Android is now part of
  the standard Chrome DevTools.