Develop Reference

Could not recognize my android device on mac

I am trying to connect my android device on mac to test application I developed.
First I installed USB driver, then I activated in my phone the developer option by tapping on Build Number and then tick USB debugging option.
Once I did all those steps when I connect my android mobile, my Mac still not recognize my device.
Any idea to solve it?

Maybe it's your USB cable, try another one.
There are two types of USB cables:
for supplying power only
for supplying power and data

I after few research and testing of existing solutions, I found mine, my issue was released while I have installed Android file Transfer for Mac

I experienced the same problem with a Moto X and my Macbook Pro. I tried many of the suggestions (installed Android File Transfer, tried different usb ports on my computer, Settings => Storage => USB computer connection => toggled between MTP and PTP, etc.). None of these other recommendations helped.
It finally worked when I tried a different micro-usb cable.
Bizarre. You definitely want to first enable Developer Options first by going to Settings => About Phone => tapping Build number 7 times to display Developer Options. From there, you want to enable USB debugging.

I found this solution to be helpful to resolve this problem
Connect your Android to your Mac via USB.
Unlock your Android's screen. ...
Swipe down to open the Android Notification Panel.
Tap the USB option in the Notification Panel.
Tap "File transfer" or "MTP."
Click the Go menu and select "Applications."
Double-click "Android File Transfer."
https://discussions.apple.com/thread/250023078

I had this problem. The only solution was to reboot my computer. Then it started working again.

Just to add my experience here. I had a similar problem with my mac book pro and my Google Pixel 1 device. For me when running adb devices locally, I was no longer showing my device on the list. I would see any emulators I had running, but not my physical device.
My solution and steps:
Go to the "Settings App"
Go to "Developer Options"
Revoke USB debugging Authorizations
Toggle Developer Options off / on
My device then prompted me to allow debugging from my computer and everything continued to work as expected. adb devices resulted in showing my connected device.
Hopefully, this will help someone else if the above does not.

Make sure to have debugging by usb enable on your device.
It is an option inside "Developer options"

I've recently (2018) started to have this issue, and have found the only way to get my device connected is to use a USB hub. I have not been able to track down a root cause but will edit this answer if I can find a solution rather than a workaround.

I connected my Android deceive with my mac:
1) If you use Android studio, you may update to latest version of 1.0.2 or 1.1 preview, because lower version have some problem with ADB connection.
2) You may restart your IDE once again.
3) You may go to settings -- storage -- three docs on the right up corner -- USB computer connection -- enable MTP

I have an HTC U11 and a MacBook Pro (2017). It used to work most of the time, but I experienced issues with it once or twice. Then a restart of the Mac solved the problem.
Recently I was not able to USB debug. adb devices gave nothing, even though my phone said I'm USB debugging (even asked if I wanted to).
After trying many things the solution was to connect my phone and run HTC Sync Manager (I also had to update it). Then it magically started to woek.
I hope it helps somebody.

check your android sdk tools, install your sdk-plateform-tools package.then it is ok

For me what fixed the problem is
i clicked on the notification "USB for file transfer" in the
notification panel on the phone
Clicked on "Transferring images"
Than I clicked on "Transferring files / Android Auto" and it was fixed.

Eclipse is not recognizing my Android tablet

I think I have done everything right but I cannot get Eclipse to recognize my plugged in running Samsung Tab-2. Below is what I have done. What have I done wrong?
1) I have instelled USB drivers and can move files from the tablet to the Windows XP computer.
2) I have enabled USB debugging on the phone
3) I have been debugging on a virtual device then sending the apd files over email to my tablet and phone. That works fine. Obviously, I have enabled that on the phone.
4) I set up Eclipse to always ask what device to debug on.
5) I plugged the tablet into the USB slot and it is recognized by Windows.
6) I read the instructions Here
7) I click debug and am faced with a blank list of devices under "Choosing a running Android Device". My tablet does not show up.
8) I find myself at wit's end (adventure reference).
9) I ask for help on Stackoverflow.

I think you should take a look at this answer. An identical issue was accepted at that post.
Hope it works to you!

Try a different MicroUSB cable, I have seen this affect the device showing up in Eclipse, even if the cable is working fine for everything else (even transferring files to/from that specific device).

If nothing works you can use adb over wifi by calling : adb connect "your ip adress". I am assuming the Tab runns Android ICS. You can enable Adb over wifi right under the USB debugging- menu point.

How many times have I called tech support and had them tell me to reboot windows? Well, the solution was to reboot windows. Nowhere in any of the installation instructions did I skip a step of rebooting but just thought I should try that.

Windows won't recognize Galaxy S2 at all

I'm having an issue with my Galaxy S2. I typically leave it in Debug mode, up until a few days ago it has worked great. I've successfully loaded APK's for testing through eclipse previously.
I tried to load a prototype of a new app im working on and when I plugged in the S2 nothing happened, Windows didn't beep like usual and when I tried to view running devices it did not show up.
When I look at the device manager under universal serial bus controllers, it doesn't show any 'unknown devices'
I've tried reinstalling drivers through kies, and third party sources (as well as removing all drivers and letting windows install them again for me.
I've tried connecting as Mass Storage Device, with debug mode on and off.
I've restarted both my computer and phone many times.
When my phone is off and plugged in Windows will beep and say that a device was connected but not recognized (which is more then what I get when the phone is on)
And sometimes when I "troubleshoot connection issues" in Kies it will reinstall the drivers and after the process is complete windows will report "Drivers were not successfully installed"
I've tried plugging it into my Windows XP laptop and it will show up as "Unrecognized device" even after I installed Kies on the laptop, and tried the driver installation it with the same results.
Posting here is my last resort as I've spent close to 5 hours troubleshooting this issue, and searching for answers. My biggest concern is that when I do plug my phone in it will beep to say that it is charging, but windows 7 doesnt even see it!
I appreciate all suggestions & help!
EDIT: Also I installed the Samsung Android USB Driver for Windows and windows reports that the drivers were not successfully installed
Thanks
Jon

Try to key in dialer:
*#7284#
It has 4 options:
UART
MODEM
PDA
USB
MODEM
PDA
In USB section, select the PDA. If it already selected to PDA then reselect it by selecting MODEM and then PDA again.
Only change the USB setting and then press back and try reconnect to kies again.
Hope it helps..

I had the same problem and JUST as i was about to give up, i realized that I had replaced my usb cord with a generic one from the store. I happened to still have the old one around still and that ended up being my issue -.-; Hope this helps someone else!

This really sucks, I know I've had this happen a few times and it's really annoying to have to deal with. I had luck with this post where they suggest:
... they suggested removing battery from hero with usb pluged in and
then putting battery back in, so i did this thinking it wouldn't work
and hey presto, mounting option became available. I was then able to
follow your first set of intructions to install the drivers through
devices and sync is now working!
If that doesn't work there are a few suggestions and helpful driver websites on there for you to follow :-D
I know I would:
Uninstall all drivers related to your device
Restart Computer without connected
Pull battery on device, plug it in, and once detected put battery back in.
If driver doesn't install correctly, or "unknown device", go to the website on that forum to get the CORRECT driver for your device and Windows OS
Go to Control Panel->Device Manager->(unknown device)->Update Driver
Locate downloaded driver, install
Make sure that when connected, the device says "USB Connected" in it's notification area
Click "Turn on USB storage", or "USB Debugging -> USB debugging"
.. this will at least show you that you have the right drivers.
IF you did all of this and you still can't get it to debug through eclipse, you either have conflicting drivers somehow, or your eclipse IDE isn't setup properly. Maybe update Eclipse, and Android SDK and try again?
Sorry can't give you exact details but this problem could be ANYTHING lol

I had the same problem while using a generic cord.
Don't use for usb transfert
I think they are made only for charging.
Solve by using a stock cord not a generic one.

Okay, so after talking to Samsung they informed me that there is a small defect with the female usb connection, and that it can sometimes be loose.
Only solution, mail it to them...

This fix works on all my computers that "don't recognize" my rooted Samsung Android. Plug the phone into the computer and restart phone. When it comes up again, the computer recognizes it.

My method is KIES AIR.
Open Kies Air
Go to settings > Bluetooth off set.
More settings > Tethering and portable hot spot > Bluetooth tethering check true and portable Wi-Fi hotspot check true.
Now KIES air open on your device and start button click. copy IP address to browser
Your s2 is connected your computer.
Open browser, and copied ip then click paste.

I have two Win XP SP3 workstations that would not connect to my Galaxy. Finally fixed it by installing this particular Intel driver and installing Windows Media Player 11.

if you are running a custom kernel on your phone, you may want to check too if you have "force fast charge" turned on or not. I thought my phone and computer would never talk to each other again but it turned out I had fast charge enabled. Turning that off solved the problem for me.

It might be an issue with USB 3.0 ports. I was tormented by this issue too and I was at the point where I was so ready to burn this device to kingdom come. Before I did that, I decided to use my never-used 2.0 port and guess what, IT WORKED! If your PC doesn't have a 2.0, good luck with that.

punch in code *#7284#, (UART set to PDA) and (USB set to PDA)
solved my problem

Why won't Eclipse/adb detect my Samsung Galaxy Tab device on my Mac?

I've connected my Samsung Galaxy Tab device to my Mac. Yes, I've turned on debugging. When I go to run my application to test on the device the device is not listed on the Android Device Chooser menu. Running the ./adb devices shows no results.
NOTE: Posting this question for others to find. When looking for the solution earlier all I was able to locate were answers to broken links to device driver downloads for Windows.

Make sure you uncheck
Settings > Applications > Unknown Sources (Allow installation of non-Market applications)

Turn on USB Debugging inside Settings > Applications > Developers Settings

If you're trying to connect to a Mac, I had this issue with a Samsung Galaxy Tab 10.1 running Android 4.3. To enable developer options, open the Settings app, tap on "About device" under the "General" tab and then tap on the "Build number" repeatedly (it's grayed out but you can tap on it anyway). A small pop-up will appear showing the amount of additional taps you need to do to turn on these options.
Once enabled, just turn on USB Debugging and it'll show up in Eclipse just fine.

I had this problem on my Mac and after 30 minutes tried switching USB ports and it finally started working on the second port.

I fixed it by reboot the device (Samsung Galaxy Tab2 7.0)

Update your driver for samsung. It can be found here: http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Connecting your phone after development mode is on, and USB debugging is on.
At connecting to the PC the phone asks to trust this location. Finally.
This fixed my problem while all other tips were incomplete.

It does not answer your question of how to get ADB to see the device - I could not get that working. But what I did to install an APK I needed to test was to put it in Dropbox on my computer, then install it from there on the device.

Connect your device via USB hub instead of directly connecting to one of the usb ports on MAC. It worked that way for me. Please give a try.

There's also a pop-up that comes up at times requesting the currently connected computer to have access to your device(not to be confused with the Linux not supported pop-up; it lies ; ] ). I continued to receive Target:Unknown in Eclipse until I managed to catch it and accept. This is on a Samsung Note 8", which I believe is registered as a Tab 10.1 in my Arch Linux udev rules.

It may also happen that USB debugging is not checked on your device. Please go to developper options in your device and check it is enabled.
By the way, for devices with android Jelly Beam (4.2) and later versions, you will find out that this option is hidden. To activate it, click 7 times on the compilation number, and the option will be activated.

Tried everything, nothing helped. Including
USB debugging enabled
MTP/PTP
ADB restarted
Device/PC restarted
Tried Samsung's USB driver
By tricking/modifying driver installer, installed Google OEM Usb drivers for Galaxy Tab.
All software up-to-date
The only thing that helped is installing Kies3 + setting PTP on device, instantly authorization pops out in device. Everything OK now.
Kies3 download here: http://www.samsung.com/uk/support/usefulsoftware/KIES/

Enable USB Debugging mode solve the problem!
For those who don't know how to enable it (it's very hidden on Android 4.3 onward), see this.

In my case, this solved the problem:
unchecked the Settings->Security->Unknown Sources,
clicked on the upper left corner and changed USB mode from MTP to PTP,
unplugged/plugged the device, and
clicked OK on the USB debugging prompt.

Had this problem last year, never solved it. Again, after googling high and low, I could not find a cure for the USB debugging flakiness. Now for the good news:
1) Root your device. 2) Install adbWireless widget from Play (I am in no way associated with the author).
You are now good to go. After starting adbWireless and following its directions, you can now debug through adb wirelessly to your device, in my case, the original 7" Galaxy Tab.

USB Debugging setting keeps "unchecking"

I'm doing Android development with Eclipse 3.6.2, OS X 10.6.7 and a Samsung Galaxy Tab.
Everything is working great, except every 15 or 20 minutes, the Settings | Applications | Development | USB debugging checkbox "unchecks" itself. Which means I need to unplug the USB cable and go back into the setting, re-select the checkbox, plug the cable back in and I'm good to go.
What I would like to know is if there is some way to make that checkbox "sticky" (I asssume it probably is supposed to be - but I haven't been able to figure out under what circumstances cause the "uncheck" to occur). I've tried a number of variations of USB / sdcard / Development settings and haven't found the "sticky bit" yet.
I'm new to Android, so I'm hoping there is some "you forgot to also do X" here...
EDIT:
Maybe it has to do with a USB Mass Storage message that pops up after 10 min or so? I just noticed a message "USB Connected: You have connected your phone to your computer via USB. Select Mount if you want to copy files between your computer and your phones SD card".

I have a Galaxy Tab and have not experienced this behavior. Nor have I encountered this on any other Android device, and I have used quite a few for development purposes.
From what I can tell, this state cannot be toggled via SDK applications, but only via the firmware. My guess is that there is something flaky in your setup that is triggering something in the Tab's firmware to do this.
Sorry that I don't have a silver bullet for you.
UPDATE
Maybe it has to do with a USB Mass Storage message that pops up after 10 min or so? I just noticed a message "USB Connected: You have connected your phone to your computer via USB. Select Mount if you want to copy files between your computer and your phones SD card".
That further suggests there is something strange going on between your development machine and the Tab. That should appear when you first plug in the cable, then remain there until you unplug the cable. I would not expect it to be toggling the USB debugging checkbox, but I am really starting to think you have one screwed-up Tab.

Had the same problem on Huawei P20. Upon activating developer options, what I did was :
On the smartphone, open System Settings -> Developer options -> Enable USB debugging
Connect the smartphone to the computer
When the prompt shows on the smartphone select "File Transfer"
Uncheck and check USB debbuging (smartphone is still connected to computer)
The prompt for USB debugging finally appears
Hope it helps.

verizon has something running in the background making this happen and having the same problem on my samsung fascinate after upgrading to fro yo. I think they're trying to block usb tethering

My Galaxy Tab 7" does this all the time. I would be in the middle of something and it would just drop. Over & over.
The solution that I found that works great for me is to just use adbWireless. This allows you to run ADB over wifi instead of USB. adbWireless can be found on the Android Market. It does require you to ROOT your phone, but since you are developing for it, you will want to do that anyway.

THis seems to have gone away in 2.3 for DroidX. But it was quite frustrating when I was using DroidX w/ 2.2 on OS X to debug.