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.
Related
The title pretty much says it all: I'm working on an Android Studio (3.5.2) project on my Windows 7 64-bit running laptop, I connect my Samsung J7 (2016) to the laptop through the original Samsung cable but Android Studio simply can't see the device. If I try to do the same on my desktop computer (same Android Studio version but on a Windows 10 64-bit OS) everything works just fine.
Here comes the funny thing: the "adb devices" command shows the device (and I'm 100% sure it's my smartphone since it's the only device connected). The Android Studio toolbar keeps showing "No devices" anyway.
I've spent 3 hours on this and couldn't find a solution. I already tried every suggested solution around the web (stackoverflow.com included), but I achieved nothing:
Disabling/Enabling USB Debug function in the Developer Settings of my smartphone (including revoking USB debugging authorizations)
Running Android Studio as admin (sometimes it solves strange stuff...)
Trying to USB connect through PdaNet+
Android Studio built-in troubleshooting service (re-scanning for devices actually makes me see my smartphone but it's treating it as if it can't be used as a debugging device; anyway the smartphone-computer connection is just fine: I can browse my files and all. Killing and restarting the ADB server does nothing)
Tried connecting both as PTP and MTP
Tried both the Google USB Drivers and the Windows Update drivers (those the computer gets when you first connect the device)
Thanks in advance :)
if you use linux as your PC OS. may be try to install adb will help you..
apt-get install adb
that's work for me.
I am trying to run an app that I have built on my phone. I have enabled USB-debugging mode on my LG G3, but my Linux Machine and Android Studio is saying that there are no connected devices.
How do I fix this? Have I forgotten something important?
I had the same connection problem.
Switching to "Send Images (PTP)" solved it for me.
I had similar problem with my Xperia S.
1) I installed android adb tools on Ubuntu. (Using: sudo apt-get install android-tools-adb android-tools-fastboot)
2) Selected MTP mode on my Xperia S. Disabled debugging. Disconnected the phone from system.
3) Enabled USB debugging, connected the phone again and tried the command "adb devices" from ubuntu terminal.
It then started the adb daemon and listed my device.
Once the device was listed there, I started the android studio again, and my phone was listed there.
Also, you might find this helpful : https://developer.android.com/tools/device.html
Hope it helps..
CD to your sdk platform-tools folder
Check if adb sees your device
./adb devices
If it displays 'List of devices attached' and a blank line below, then restart adb as follows:
./adb kill-server ./adb start-server
then re-run ./adb devices and see if it picks up the device, eg as follows:
List of devices attached xxxxxxxxxxx
There is a well-written and detailed step-by-step guide for connecting a phone with Android Studio when running Linux here:
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Changing in the USB Options on the phone to "Send Images (PTP)" worked to me as well (on a LG phone). Must be something with LG phones, because with other Android phones this wasn't needed.
After taking a few hours, I just solved a similar problem minutes ago with LG G3 on WINDOWS.
Maybe my experience can help you.
Firstly, do NOT enable USB debugging.
Secondly, install the OFFICIAL USB driver from LG (I have no idea whether this is available on Ubuntu). Please make sure the driver works normally by some LG software. BTW, I don't think LG is good at software.
Thirdly, enable USB debugging and go.
This has been asked a lot. I can't get my device running with ADB on MacOSX. I know this is a software problem, because I can connect via the Samsung application Kies.
see
1) adb not finding my device / phone (MacOS X)
2) Android device is not recognized in adb
3) Why won't Eclipse/adb detect my Samsung Galaxy Tab device on my Mac?
Possible solutions of which none worked for me.
start-server , kill-server
USB-Debugging on?
Add vendor ID to ./android/adb_usb.ini
usb cable defect?
add sdk path
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext (?)
Connect your device via USB hub instead of directly connecting to one of the usb ports on MAC.
details
OSX 10.8.0,
Eclipse Juno (4.2.1),
Android 4.0.3,
apropriate SDK #15
Edit: Tried on Windows 7 also. Update firmware. Nothing working.
So finally I got it. I thought I was in debugging mode, because Android has this weird greyed out checkbox. I could activate USB testing mode, and now it is working.
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.
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.