16

I tried to use the remote debugging tool of Google Chrome for my Samsung Galaxy S4 (https://developers.google.com/chrome-developer-tools/docs/remote-debugging?hl=nl). But my Chrome does not found my device after i used about:inspect. The list stays empty.

I already install the newest driver on my computer and both devices running Chrome version 32. On my phone the USB debugging checkbox is checked.

Does someone know what i can do to view my phone trough Chrome debugging?

JelleP
  • 976
  • 7
  • 20
  • 39
  • Do you see your device attached to the machine as a Media device? If not then there is a chance the cable you are using is a power only cable and not a data cable. – Kinlan Feb 04 '14 at 19:25
  • Same issue with a Galaxy Tab 2 10.1, everything up-to-date and connected as a media device. I'll post an answer as soon as I figure this one out. – Bart Feb 26 '14 at 09:13

3 Answers3

45

Do you have ADT (Android Development Toolkit) installed? If so, you may have to restart the ADB server. Follow these steps: (from this answer).

  1. Open a command prompt (Win+R, "cmd.exe", Enter)

  2. Go to the platform-tools directory of your locally installed ADT. In my case:

    cd /d D:\apps\adt-bundle-windows-x86_64-20131030\sdk\platform-tools

  3. Restart the ADT server by running the following commands:

    adb.exe kill-server
adb.exe start-server

  4. Now observe that your tablet will ask for remote debugging permission (by checking a fingerprint) upon connection.

  5. The device should now be found if you open chrome://inspect.
Community
  • 1
  • 1
Bart
  • 2,062
  • 15
  • 19
  • 1
    restarting server helped also in Samsung Galaxy Core so I suppose it will help on any device. It's hard to find that solution so many thanks for that! – Rob Mar 04 '14 at 13:57
  • in my case path was: C:\Users\YOUR_USERNAME\AppData\Local\Android\sdk\platform-tools device: SM-T520 – Rajab Shakirov Oct 26 '17 at 15:11
16

workaround if you don't have ADT (Android Development Toolkit) installed:

Managed to detect android based Samsung Galaxy phone after downloading andorid SDK platform-tools.zip and running the following command: "adb devices". It started some deamon, found attached device, and I was also able to see it in chrome canary inspect tab.

previously I also installed "Universal ADB driver" but not sure if this was required

Juri
  • 3,389
  • 1
  • 20
  • 16
  • 5
    Thank you! This was driving me crazy. Nothing to install too - just extract the folder, go to folder in command prompt and run "adb devices". The connection prompt popped up straight away on my S5 Mini and I was up and running. – Stephen Blair Jun 19 '15 at 16:23
  • This is working. You rock! (No need to Unversal ADB driver) – Naourass Derouichi Nov 14 '15 at 23:10
2

I stumbled over this exact problem. The solution above work's like a charm for me. But I'm lazy as hell, so I created a .bat file:

@ECHO OFF 
cmd.exe /K "cd C:\Users\YOUR_USERNAME\AppData\Local\Android\sdk\platform-tools && C: & adb.exe kill-server & adb.exe start-server"

The directory depends on your installation of your ADT.

Save as killstart_adb.bat and run this. Works for me.

Emanuel Malacarne
  • 45
  • 6