Why can't OSX detect android Galaxy S for USB debugging?

StackOverflow https://stackoverflow.com/questions/8606478

Question

I searched for similar questions on this issue but found none related to Mac OSX.

Situation:
Trying to test android apps on a Galaxy S (Details below) but Mac is not detecting the device. Tried all the things below and have wondered whether this might be a driver issue (which I've heard things about for Samsung USB debugging).

Questions:
1) Are samsung drivers required for android USB debugging?
2) And are they available for Mac OSX? 3) Any other reasons OSX might not detect device for usb debugging?

Things I tried:

  • Enabled USB Debugging @ Settings >> Applications >> Development >> USB Debugging
  • Enabled Tethering @ Settings >> Wireless and network >> Tethering >> USB Tethering
  • Set Tethered mode @ Settings >> USB connection >> Tethered mode
  • Attempt to detect devices via ./adb devices (from platform tools dir)
  • Verified that "Unknown Sources" is checked @ Settings >> Applications >> Unknown Sources
  • Verified that device is connected to Mac
  • Restarted phone
  • Restarted mac
  • Added various device / product ids to adb_usb.ini
  • Did ./android update adb (which does adb kill-server / start-server)

Using:
Samsung Galaxy S (4G) with Sprint
Mac OSX 10.6.8
Eclipse Classic 3.7.1

Was it helpful?

Solution

Have you tried connecting the phone using a powered USB hub? I haven't tried it yet but found this blog post that suggests it may help for Samsung Galaxy devices.

http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/

OTHER TIPS

make sure that you plugin your device in the usb ports on the mac itself, not on the keyboard usb-ports.

Go to Tethering select and then deselct USB Tethering and you are done. this worked like a charm.

Well I tried all kind of stuff for a phone that was working yesterday but not today. Finally replacing the cable between the phone and my mac solved the issue.

USB driver problems happens under Windows.

For MacOS, I had nothing to do : ADB found my device.

You don't need tethering : it's for sharing an Internet connection.

USB Debugging is needed. Also make sure you authorize your Galaxy to use Unknown sources (@ Applications -> Unknown sources (it's a check box)).

Go to

  1. Settings
  2. Wireless and Networks
  3. USB Utilities
  4. Detach the USB cable
  5. Select Connect Storage To PC
  6. Reconnect your USB cable to your phone.

Source: Galaxy S II Forums - Help, Mac won't recognize my galaxy S 2

This happens all the time with lots of phones. Two things that have worked for me are (1) type "adb kill-server" at the command line, or (2) try another cable.

This is what worked for me on Samsung Duos:

  1. Go to settings > More > About device(at the bottom)

  2. On that about device screen go to bottom and touch 6 times on the "Build number" (un till it doesn't display any notice)

  3. Then visit again to settings > More and it will display developer options before the about device. Click on developer options and tweak options as you need.

Now on the mac, click on run button in android studio, it will display the connected device.

Resource: http://www.geekygadgetworld.com/3303/enable-developer-option-samsung-galaxy-grand-duos

This may sound crazy, but I tried every suggestion on this page except what finally worked:

Use the Samsung USB cable that comes with the S7 (my S6 cable worked too)

Every other USB cable I tried did not work. I don't know exactly why (USB 2 vs 3?), but that is what worked for me.

Of course, make sure USB debugging is turned on, and yada yada yada, but I did all that and still NOTHING. The moment I plugged in the USB cable that came with my S7 I got the RSA fingerprint message, and confirmed USB debugging, and the device showed up in Android Studio when I clicked Run.

HTH --jsp

I spent a night fighting this problem with my Doogee DG350, which runs the Chinese MTK chipset which has issues with USB on OS X. I found the solution was to run ADB in TCP/IP mode and then connect wirelessly:

adb tcpip 5555

adb connect 192.168.1.10:5555

adb devices

it's actually a bonus, cos you can dispense with the USB cable and debug wirelessly. Not looking back

The connection via tcpip has a potential to work. However, the port 5555 is probably not available. I know this can work because I have an app on my Android called "Synctunes Wireless" which syncs' my itunes on my desktop wirelessly via tcpip and using port 4444. So I used the ip address and this port showing on this app and I can see this device in my Eclipse. Only thing is that the device type is unknown so the "OK" button is still disabled. So this has potential to work. Just have to find the right port number or maybe something else that is missing.

None of these things worked for me. I'm running 4.4.2 on an LG VS450PP, trying to connect to a Mac laptop running OS X 10.10.5. Neither MTP nor PTP worked at all, even after following all the suggestions listed here and elsewhere on SO. I only got the RSA message when I chose the Internet option from the USB settings (and then I chose Ethernet).

After that, it was golden.

If anyone still has this problem and looking for a solution, what helped me is to install Smart Switch app. After that my Samsung device finally showed up

So i did some research because the same thing happened to me. If the simple solution doesn't work you should check if you installed knox when you first launch your phone. If you did install knox the only way for you to activate usb debugging would be to reset your phone back to factory config in order to deactivate knox (aka not installing it again), apparently you don't have the option to unistall knox on recent phones.

I know it is ridiculous but do make sure your phone's got a SIM card!

To activate the USB debugging on Samsung Galaxy S go to Menu -> Settings -> Applications -> Development -> Check "USB debugging".

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top