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
Related
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?
I want to test an application, but I got a problem with my device. I have a Samsung Galaxy S3 which version is 4.1 (Jelly Bean), and a S. Galaxy Note 8.0 and this is what I have done:
I have activated the developer mode.
I have activated the USB debugging.
I have installed the ADB on my computer.
And the problem is that when I connect the phone (or the tablet) to the computer through USB port, the device start in multimedia mode and the debugging mode doesn't active.
I hope that you can help me, thanks.
You need to download sansung driver for windows 7. Try this http://www.usb-drivers.org/samsung-android-usb-device-driver.html
I have a Samsung Galaxy S4 that I would like to deploy my app to using eclipse. However the device simply does not appear on the list of devices to deploy to.
I am using Windows 7 64-bit.
The phone appears as a drive when plugged in, allowing me to transfer files to and from the device.
The phone has developer mode and USB debugging switched on.
In the Android SDK Manager, the Google USB Driver appears as installed.
I have manually installed the usb driver located at \extras\google\usb_driver\.
This same device has been recognised and deployed to on other computers.
I have tried restarting the adb server in command prompt using adb kill-server and then typing adb start-server.
I have tried restarting both the phone and the computer.
My deployment screen simply thinks there is no android device:
Any ideas? Is there perhaps something I am missing here that is required for my android device to be properly recognised by eclipse?
First, is your device id showing up when you use adb devices
If it is, it's just a matter of restarting eclipse. Another cause could be that you're using the Google USB driver, whereas you should be using Samsung's Android USB driver, which can be found here:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Get the drivers for your Galaxy S4 here:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
P.S. ya better got Nexus 5
You should install Samsung KIES, that have included some USB Drivers and something more, then you will able the possibility to eclipse sdk recognize your Phone, i was with the same problem, after i installed KIES everything worked fine, trust me.
KIES Download:
http://www.samsung.com/us/kies/
I use two devices to develop my Android apps:
a Samsung tablet Galaxy tab 10.1 (Android 3.1)
a Samsung S2 (Android 4.0.3)
I develop on Mac OSX Lion.
My problem is that my Samusung S2 is not recognized by Eclipse (everything is ok with my tablet!!). To be more accurate, my S2 appears something like 1 second every 1 minute in DDMS or the "Android Device Chooser" (the window which appears when you launch the app in Eclipse and where you can choose between a physical device or emulator) and then disappears !!! This is driving me crazy.
I tried absolutely everything I found on forums:
update all modules via the SDK Manager
update of Eclipse via Help => check for updates
tried 3 different USB cables...
tried to reset adb either via DDMS or in command line (adb kill-server and then adb start-server)
I checked that USB debugging is set on my S2
Can the rubbish Samsung app "Kies" induce some issues? (not the case with my tablet) Other idea?
Can anybody help me ???!!!
Thanks !!
Finally, I had a physical problem with the micro-USB connection on my Samsung S2... I returned it to Samsung and they repaired it ! it seems that the micro-USB connection on S2 are very fragile...especially when you connect/disconnect very often your device !! Hope this helps...
Use Kies to force a reinstall of the drivers.
In Kies (Version 2.3.2.12054_20):
Tools > Troubleshoot connection error.
Follow the wizard (there is a "Reinstall device driver" stage).
I don't have a special confidence this will fix your problem. I offer it as something to try.
I have tried installing the Samsung Captivate Drivers, but ADB does not see them. I have got the google adb drivers in sdk directory but everytime i try to install this driver it says that Windows think I have the best driver for the device. It keeps the MTB driver. I have tried uninstalling but MTB driver keeps coming back. I am trying to get the debug bridge to work to a Samsung Captivate. adb devices shows nothing.
try to use Samsung Kies. It has samsung drivers with in.
you can find it here :
http://www.samsung.com/uk/support/main/supportMain.do
works fine for me with the Samsung i5700 on Win7 x64
Installing Samsung New PC Studio worked for my Samsung Fascinate. You get a bit more than just drivers, but it worked.
It is just a matter of installing the Samsung Captivate Drivers. (Some people have to reinstall them several times) and then just making sure that USB is definitely set for debugging. This should work. The Android application itself needs also to be enabled for debugging android:debuggable="true" in the Android-Manifest. This is what it needs. Note this is how to get ADB working so that if you type adb devices you will see the Samsung device. Kies is an option for file sharing.