I have a HP Slate 21 that is connected to my Windows box using a USB cable. USB debugging is enabled on the device. After adding the proper %SingleAdbInterface%
and %CompositeAdbInterface%
entries to the android_winusb.inf
file, I now see "Android ADB Interface" in my Device Manager. However, running adb devices
at the command-line does not show the device.
I have another HP slate 7 that shows up just fine under adb devices
.
The only difference I see from Device Manager is that the one that works is named "Android Composite ADB Interface" and the other one is named "Android ADB Interface."
There is yet another subtle difference. In the winusb.inf file, for Slate 7 I have two %CompositeAdbInterface%
entries defined but for Slate 21, there is just one %CompositeAdbInterface%
entry defined.
What could be wrong with my setup?
Have you ever reset the adb after you installed the new device?
Or from command line:
adb kill-server
adb start-server
adb devices
againDisable and re-enable "use debug mode" on your telephone
Same as other android devices, a new Yuntab also requires going to settings > about and tapping on the build number to enable developer status.
While many of these solutions have worked for me in the past, they all failed me today on a Mac with a Samsung S7. After trying a few cables, someone suggested that the ADB connection requires an official Samsung cable to work. Indeed, when I used the Samsung cable, ADB worked just fine. I hope this helps someone else!
Tried off/on developer/usb options, but turns out swopping for another cable worked. Just in case someone waste time trying everything software.
Toggling USB debugging off and then back on did the trick for me.