I am following the google android developer guide on adb here: https://developer.android.com/tools/help/adb.html#wireless
After all the steps, I and I run adb connect MY_IP, it says that connected to MY_IP:5555. However, when I unplug my phone from my computer, running adb devices shows that no devices are connected, and in Android Studio, it says no devices also. How can I fix this?
I am using a macbook pro running Yosemite, and an HTC One m7 running android 4.4.2
Any help would be greatly appreciated
Edit:
I just tested on an LG G3, and it worked. However, I need it to work on my HTC, because the LG isn't my phone. Why doesn't my HTC work?
Related
I'm experiencing an issue with my Nexus 5 and Nexus 10 devices.
I'm running Ubuntu 14.04 on VMware Workstation 9, and ADB only occasionally recognizes my devices. I find if I unplug and re-plug the devices, it'll eventually work, but it's annoying to have to go through this process everytime I disconnect my device.
Has anyone else experienced this/know of a workaround?
I don't have a real answer, but it happens to me occasionally on various devices. I find that the best thing to do is to root the device and connect to adb over wifi. You can use an app such as "ADB Konnect" to enable wireless debugging.
I would like to use my Sony Ericsson Xperia SO-03C phone running Android 2.3.4 for debugging my app. I have connected it to my Macbook Air via the USB port, and it seems Eclipse fails to recognize it (although I can charge the device).
I have already enabled "USB debugging" on the phone. I have also tried "adb devices" and it does not show my phone. I've also tried stopping and starting the server to no avail (adb kill-server/adb start-server). I'm out of ideas on what to try next.
Any help or suggestions is greatly appreciated.
Did you install the device driver for the phone?
This issue indeed was the cable I was using. It did not support data transmission. This issue clued me in.
I recently got a Macbook Pro. I had an old Macbook and developed Android apps on there with no problem. I have a Samsung Galaxy S2. I have installed the Android SDK and Eclipse along with the ADT plugin. Whenever I connect my device, it says "USB Debugging Enabled" in Android (v4.0.1), but when I run android-sdk/platform-tools/adb devices I get the output 0123456789ABCDEF Offline. When I unplug my phone and run this, it shows nothing.
I found this thread: Why is Eclipse and ADB not recognizing my Android Device?
but it is for Linux. I tried the "Second" steps in the answer from that thread to no avail. Does anyone know why my phone is showing up like this in adb?
edit: I just plugged in an old Droid 2 Global and adb connects fine. Must just be my GS2.
I found that I had to both switch to a Powered USB hub AND change cables. (This was for a Pantech phone connected to a new MacBookPro.)
It turned out to by the ROM I was using (CM9). I upgraded to CM10 and it works now.
I just run "adbd" in android device in /data/misc/adb this solved the ofline problem.
of all my devices i test to using eclipse..
my Samsung galaxy nexus is the only one that does not seem to connect to my mac..
i tried installing the android file transfer software but this did not help..
when i check in adb for devices it does not show up either..
USB debugging is enabled.
my cable was fine.. needed a better flashed ROM.. bumped up to Vicious-JellyBean-V5
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.