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.
Related
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 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.
After developing and testing for months my android application both on the emulator and on a phone, I suddenly can not connect any more to the phone in one of the two PCs I use for development.
One PCs runs Windows XP 32bits. Here everything is ok. But my main development machine is a Windows 7 32bits: Both of them run Eclipse Galileo. I can not get connected to the Samsung Galaxy S GT-I9000T phone from there. Two Sundays ago I updated my application last version to the phone. Went on vacations. After returning I upgraded the Samsung Kies suite to the new version 2. It is supposed it installs USB drivers for Windows. I also upgraded to Android SDK 9 and ADT 9 but I'm not sure it was after the problem appeared. Then I realized can not connect to the phone. My first suspect was Samsung Kies. But I made all these intallations on the xp PC and the connection works OK. Then I returned to the Windows 7. There is another driver called "USB Driver for Windows" which I have installed from Android's SDK "SDK and AVD Manager"/"Available Components"/"Android Repository" I tried to reinstall it. I deleted the package despite the warning it can not be undone. Then I tried to find it on the "Available Packages" but it was no more there.
I reinstaled Samsung Kies, Eclipse, Android SDK but the problem remains the same:
Another fact: with USB debugging active, Samsung Kies can not connect to the phone. It detects something is connected but it stays forever trying to connect.But it occurs also on the XP machine.
In summary:
I can not get listed the "USB Driver for Windows" in the "SDK and AVD Manager"/"Available Components" for installation, even after reinstalling all the development environment
I can not get the development environment to connect to the phone for debugging.
How to fix this?
Any hint is welcomed.
Thanks in advance.
Sammy
I finally found the origin of the problem. I hope it will be useful to someone else.
Device Manager showed "ADB Interface" / "SAMSUNG Android Composite ADB Interface" with a warning sign. The device was not running 'cause some inconsistencies in the registry.
I deleted both the "ADB Interface" / "SAMSUNG Android Composite ADB Interface" and "Universal Serial Bus Controllers" / "SAMSUNG Android USB Composite Device" and reinstalled them from Windows Update. This time I didn't used Samsung Kies Tools / Install Driver menu.
Thanks for your time.
Sammy
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.
Mac OSX 10.6.4
Nexus One Android 2.2
The command adb devices will list my emulators and also my Droid Eris (Android 2.2) but nothing shows for the Nexus One
I have searched extensively and failed to find any answer or suggestions, any help most welcome
Power cycle and reboot everything including the phone.