Just began working on a new 2011 Macbook Pro only to find ADB cannot see any of my devices. This occurs under Eclipse in DDMS and when I run ./adb devices.
I have found some discussion of this saying there are intermittent issues in OS X 10.6.6 with problems seeing Android devices but this seems to be different as all of my devices are mountable via USB.
I see the exact same behavior running Windows 7 in Virtualbox, Apple support on this issue is non existent as they insist it is Android's problem.
The devices I have encountered this problem with include:
Sony Xperia mini X10
Motorola Droid
HTC Droid Eris
Samsung Galaxy Tab
Could this be a hardware problem on my new Macbook or am I dealing with something related to OS X?
Either way I may have to trade for a Windows laptop :-(
**updated March 27 2011
Have now tried a full Bootcamp installation of Windows 7 complete with all the Apple provided drivers - same result
resorting to powered USB hub didn't help either
The device appears as Android Phone under System Profiler but remains invisible to ADB, mounting works fine.
Finally found a solution, seems the tethering software I had installed on the macbook was interfering with ADB:
http://www.intohand.com/blog/?p=116
Applying the fix made it "just work" again:
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext
Related
The title pretty much says it all: I'm working on an Android Studio (3.5.2) project on my Windows 7 64-bit running laptop, I connect my Samsung J7 (2016) to the laptop through the original Samsung cable but Android Studio simply can't see the device. If I try to do the same on my desktop computer (same Android Studio version but on a Windows 10 64-bit OS) everything works just fine.
Here comes the funny thing: the "adb devices" command shows the device (and I'm 100% sure it's my smartphone since it's the only device connected). The Android Studio toolbar keeps showing "No devices" anyway.
I've spent 3 hours on this and couldn't find a solution. I already tried every suggested solution around the web (stackoverflow.com included), but I achieved nothing:
Disabling/Enabling USB Debug function in the Developer Settings of my smartphone (including revoking USB debugging authorizations)
Running Android Studio as admin (sometimes it solves strange stuff...)
Trying to USB connect through PdaNet+
Android Studio built-in troubleshooting service (re-scanning for devices actually makes me see my smartphone but it's treating it as if it can't be used as a debugging device; anyway the smartphone-computer connection is just fine: I can browse my files and all. Killing and restarting the ADB server does nothing)
Tried connecting both as PTP and MTP
Tried both the Google USB Drivers and the Windows Update drivers (those the computer gets when you first connect the device)
Thanks in advance :)
if you use linux as your PC OS. may be try to install adb will help you..
apt-get install adb
that's work for me.
I have this error using Android Studio on linux Mint with my Nexus 7 2013 model.
I have tried running ADB fro terminal and there are no devices listed. Also lsusb does not list the Nexus either. I have followed the advice on http://developer.android.com/tools/device.html and http://forum.xda-developers.com/showthread.php?t=2302780 but still no joy. Can anyone please help. It doesn't work with MTP or PTP setting.
SOLVED Having tried many things it turns out the USB cable that came with my Nexus 7 2013 was faulty. Changing the cable for another bog standard one has fixed it. It works now in Linux Mint and Windows 7 too.
I'm trying to test an Android Application on my Galaxy Nexus (from Google). I use Windows 7 Home Premium 64 bit and Eclipse Java EE IDE for Web Developers.
My device doesn't show in Eclipse DDMS view. My device also doesn't show when I run adb devices in cmd.
I have USB debugging enabled.
When I try to install the USB driver as shown here I get a message that my device software is up to date.
I also tried killing the adb server and starting it again.
Give the Universal Naked Driver a try? Be sure to follow the steps in the forum post.
Nexus devices require the Google USB Drivers, you can get them through the SDK Manager.
If you have them installed and the device still is not detected try the following:
Use a different USB port (for me the USB 3.0 port is always making problems)
Restart the device and the computer
Restart ADB
Also take a look here, which explains how to install drivers for the Nexus S.
I had a similar problem. I could not get my device to show up in my Eclipse devices window. When I typed adb devices, no devices were discovered. Fortunately, I discovered this website. It basically had me install a generic driver for my Motorola (Android 2). It had other drivers for Samsung and other manufacturers. After the install, my Motorola phone became visible with ADB.
I am developing an android app and am now ready to publish it to my device (HTC Desire). The only thing is I am using ubuntu and I am having trouble doing so. I have found some help on the internet regarding installing the drivers, only I need something called "adb devices", however in the latest android sdk it has been moved and now I can't find it. The SDK is up to date. Has anyone else had trouble getting linux to recognize their HTC device?
Cheers!
HTC devices work quite nicely under Linux, without any drivers whatsoever. I've used a HTC wildfire under ubuntu with no problems.
adb is an executable file. You can find it in the platform-tools subdirectory of the SDK. "devices" just a parameter to that command (adb devices lists all devices connected).
I just bought the Nexus S with the android version 2.3.3, which I update it to 2.3.4. I use to develop my android apps in my Mac but when i tried to connect my new Nexus S with the ADB it wasn't recognized. Though the ADB worked pretty well with pass android devices.
Moreover, I connected my Nexus S with the ADB under my Linux machine and then worked as a charm.
Any suggestions on how to make the nexus s be recognized to the ADB of my Mac?
Thx in advance!
As far as I know, the "Usb Driver Package" is for Windows only.
Did you tried to download and use the newest SDK/ADB from http://developer.android.com ?
I had some problems too these days, but after rebooting my phone and reenabling the debug mode ADB worked again.