Remote debugging of Chrome (USB debugging), not working for Samsung Galaxy S3, running Android 4.3.

Ever since I upgraded my Samsung Galaxy S3 to android 4.3 (from 4.1.2), I canโ€™t use Chrome remote debugging for Android (more details here ).

I have developer options and USB debugging on my phone, and this works fine on android 4.1.2. Now, when I connect my phone to the computer, it simply connects as a storage device and is not detected as a USB device using chrome.

I fix any problems with chrome since I could debug USB using Google Nexus4, while also looking at a different stream (here and elsewhere) there seems to be a problem with updating Samsung 4.3.

Any pointers to make this work?

+79
google-chrome samsung-mobile android-4.3-jelly-bean usb-debugging
May 14 '14 at 7:30
source share
9 answers

Having examined a little more, I came across. Apparently, there is still no solution to this problem, but there is a workaround - a return to an outdated workflow .

The inherited workflow really worked for me, and the only additional thing I had to do was go to the platform tools folder from the Android SDK download, open the command window here and run the "adb devices" command. This made the RSA computer fingerprint panel appear on my mobile screen, and after granting permission, the device appeared on the Chrome Inspect page.

It turns out that this is not a problem caused by updating the mobile OS, but Chrome (I was discarded by the fact that it somehow worked on my Nexus4). In older versions of Chrome, there was no need to download 500 odd Android SDKs for Android, as it supported the ADB plugin. But with the latest version of Chrome, I think switching to inheritance is the only way to go.

+18
May 29 '14 at 8:10
source share

My devices stopped working because Chrome has now deactivated the disparate ADB plugin because it is now built into dev-tools.

I downloaded the SDK and followed the instructions in the Chrome Developers . Somehow I found that the instructions that Alphonso serves are not enough, and I did it like this on Windows 8:




  • Download the Android SDK here ("SDK Tools Only" only) and unzip the contents.
  • Run the SDK Manager.exe and install the Android SDK platform tools.
  • Open Command Prompt (just by clicking the Windows button and entering cmd.exe)
  • Enter the path using ex: cd c: / downloads / sdk / platform-tools
  • Open ADB by typing adb.exe
  • Run the following command by typing it and pressing enter: adb
  • Make sure you are prompted on your device if you still cannot see your phone in Inspect Devices to run the following commands one after another (except for ")" adb kill-server "" adb start-server "" adb devices "

I had serious problems and managed to get him to work with these steps. If you still have problems, follow the google manual Remote debugging on Android with Chrome and check for some drivers. I had problems with the Samsung Galaxy Nexus, which needed special drivers for compatibility with ADB.




Update

If you are using Windows 10 and could not find the download link for the Android SDK ; you can skip # 1 and # 2. All you need to do is activate the โ€œ Android Debug Bridge โ€. Go straight to No. 3 - No. 7 after downloading and executing the " platform-tools " ( https://developer.android.com/studio/releases/platform-tools.html )

+159
Jun 25 '14 at 2:03
source share

Trying to execute Valros.nu's answer, I found that sdk download was now completed using androind studio, in exe 840MB installer.

Since all you need for this particular program is adb, you can get it in the standalone installer from the xda guys:

http://forum.xda-developers.com/showthread.php?t=2317790

Please note that you do not need to enter adb.exe , just enter adb devices in the command line that starts after installation.

Also, I had to disconnect and reinstall my samsung s4 in order to receive a remote debugging prompt on the phone

+29
Apr 01 '15 at 10:39
source share

For me, there was a decision to download the Android SDK and run adb devices , which launched the adb daemon.

+4
May 6 '15 at
source share

I know this is an older question, but I thought I would also post my solution:

  • Update Chrome on your phone and on your PC.
  • Even if it says that you have the latest driver for your device inside Device Manager, you might need an alternative. Latest Samsung drivers and try updating drivers.
+2
Jan 24 '15 at 3:53 on
source share

For me, the Inspect Devices menu item was not available (not shown at all). But just looking through the chrome: // checking the / # devices, I showed me my device and I was able to use the port forward, etc. I have no idea why the menu item is not displayed.

Phone: Android Galaxy S4

OS: Mac OS X

+1
Aug 15 '16 at 15:10
source share

I have a Samsung Galaxy S3 and it didnโ€™t show up on the Remote Devices tab or in chrome: // check. However, the device showed in the Windows Device Manager as the GT-I9300. What worked for me:

  • Connect your mobile phone to the front USB port.
  • On my phone, click on a successful connection notification
  • Make sure the connection type is camera (PTP)
  • On my windows machine, download the installer from https://github.com/koush/UniversalAdbDriver
  • Run it :)
  • Open cmd.exe
  • cd "C:\Program Files (x86)\ClockworkMod\Universal Adb Driver"
  • adb devices
  • Open Chrome on both your mobile phone and Windows computer.
  • On a Windows machine, go to chrome: // check - there, after a while you will see the target phone :)

I'm not sure that it somehow influenced the whole stream, but at some point I installed and later removed the drivers from Samsung: http://www.samsung.com/us/support/downloads/ > Mobile phones> Phones> Galaxy S> S III> Unlocked> http://www.samsung.com/us/support/owners/product/galaxy-s-iii-unlocked#downloads

+1
Jun 12 '17 at 19:34 on
source share

I had success after using ade.exe as described above, plus using the latest version of Chrome Canary . It appears that your desktop version of Chrome should be higher than the version installed on your Android device.

0
01 Oct '15 at 23:08
source share

Those who upgraded their device to Android 4.2 Jelly Bean or higher, or with a device powered by 4.2 jB or higher, will not find Developer Options in the Settings menu. Developer options hide by default on 4.2 jelly versions of Bean and later versions of Android. Follow the steps below to uncover developer options.

  • Go to Settings โ†’ About (On most Android smartphones and tablets) OR

Go to Settings โ†’ Advanced / General tabs โ†’ About (on Samsung Galaxy S3, Galaxy S4, Galaxy Note 8.0, Galaxy Tab 3 and another galaxy. Smartphone and tablet with Android 4.2 / 4.3 Jelly Bean) OR

Go to Settings โ†’ General โ†’ About (On Samsung Galaxy Note 2, Galaxy Note 3 and some other Galaxy devices with Android 4.3 Jelly Bean or 4.4 KitKat) OR

Go to Settings> About> Software Information> Advanced (on HTC One or other HTC devices with Android 4.2 Jelly Bean or higher) 2. Now scroll to the assembly page and tap it 7 times. A message appears stating that u is now a developer.

  • Return to the previous menu to see the developer option.

Credit at www.androidofficer.com

-6
May 20 '14 at 16:01
source share



All Articles