This is an odd one. When I'm at work I have my Macbook Pro plugged into a monitor, which has built-in USB ports. I plug the USB from the monitor into my laptop, and then plug Android phones or tablets into the monitor. This works great and there are no problems running or debugging using ADB.
However, if I plug devices directly into my laptop they will not be detected. They receive power but do not show up in ADB. I have tried the following:
Rebooted the laptop
Killed and restarted ADB
Installed Android Studio updates
Used all USB ports on the laptop
Used different USB cables
Used different USB devices, spanning all Android versions
What gives? I am running High Sierra 10.13.6. Any ideas? I can post more information if needed but I'm not sure what will be helpful.
Related
I'm finding I need to restart my computer in order for Android to recognize that it's connected to my computer. Sleeping the computer seems to require another restart even after resetting the NVRAM.
When Android won't connect to the computer, plugging the USB cable back in doesn't help. Neither does restarting the phone, changing the USB mode in Developer Settings from "Charging" to "PTP" or the other modes. Nor does killing adb and starting it again.
Specs:
Phone
Google Pixel 2
Android 8.0.0
Computer
MacBook Pro (Retina, USB Type-A ports)
macOS 10.13.1 High Sierra
adb 1.0.39 (rev. 3db08f2c6889-android)
Cable
AmazonBasics USB 3.1 Type-A to Type-C
I have found that it was the cable. Apparently some USB cables allow only charging but not file transfer.
After trying another cable, my Android File Transfer app detected it right away and I was
You have to enable the Developer Mode and USB Debugging first. See e.g. https://www.bestusefultips.com/enable-developer-mode-on-pixel-2-pixel-2-xl/
After this you should be able to see your device with adb devices -l shell command.
A while ago, I was able to connect my device and have it be detected on Android Studio. But now that's no longer the case. I've tried it with two separate phones and ADB is unable to detect either of them. After doing some research, I've tried a couple of things:
*Enabled USB debugging
*ADB kill-server/start-server
*Switching phone from MTP to PTP
*Switching USB ports/cables.
Is there anything else that might be useful to try that I haven't tried?
Thanks!
-T
Connect your device and select Connect to PC Software option. MTP and PTP won't work.
Edit:
If you are using a Samsung Galaxy device you might have to use a powered USB hub as suggested in this post
Is there any collision between Genymotion and hardware device on Android studio?? Yesterday, I tested my android phone as a debug machine on android studio. It worked perfectly. However, today, after installing genymotion and run my project on it, Android studio couldn't detect my phone....
I followed these steps :
check whether USB debugging is enabled
check sony xperia USB drive (I installed it from websites, and reinstalled it automatically after conneting my device)
reset Android device monitor
reboot my phone
reboot my computer
plug on/off usb cable
There is no collision between Genymotion and hardware devices. But Genymotion does come with its own copy of adb which introduces potential adb client/server mismatch possibility. So just delete the adb binary from the genymotion\tools folder (you may need to kill all running adb processes first) and you should be ok.
I have a htc device on android 4.1.1. I have installed htc drivers, but the device is not listed as plugged into a usb. The device starts charging when plugged into usb - the cable is fine. What else could be causing this issue?
If you are on windows try installing the android universal USB driver
If you are on MacOS you need android file transfer
If this doesn't work try changing USB port and make sure that your device is conected as Mass Storage.
I have a Wi-Fi Motorola Xoom that I am connecting via ADB for development. I am seeing an intermittent problem where the device (with ID number) shows up in the adb devices list, but will present as being offline.
The device and computer both show the tablet as being connected. I've tried a combination of rebooting each device and swapping USB ports, but the only thing that solves the issue is switching out the cable. Furthermore, a cable that I used yesterday doesn't work today -- I am having to use a previously non-functioning cable to connect.
Is this a driver issue? Device port issue? I have seen this issue with several versions of the Motorola drivers as well as the PdaNet drivers. I am currently using Motorola Mobile Drivers 4.7.1.
WARNING: this question referred to an older device and as such the answers may no longer be relevant to current ADB connection issues.
I met the same problems like yours, and I found out that the USB cable has mal-functions in the PIN of head USB. So I switch to the new USB cable, it just works fine and detect device as online.
I had the same problem, and switching from the USB port on the front of my machine to the port on the back made things work. It could be related to a difference in port power or USB type.
From XDA: nouvelle_adr http://forum.xda-developers.com/showthread.php?t=2247471
I downloaded the adb version and it worked.
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window"