I have been developing in Android for approximately two months now. Yesterday, my eclipse starting giving me the error:
The connection to adb is down, and a severe error has occured.
You must restart adb and Eclipse.
Please ensure that adb is correctly located at 'C:\android-sdks\platform-tools\adb.exe' and can be executed.
So I followed the steps for restarting adb located here.
Eclipse now gives me:
Android Launch!
adb is running normally.
My phones, however, are not being detected. I have a Galaxy S2 running Android 2.3.4 stock, and a S2 rooted running 4.0.3. Neither are being detected. On my home pc, both work fine in eclipse.
I have tried restarting my laptop, and even tried killing adb and eclipse and retrying the steps above. But it still won't detect my phones. My emulators are working fine. It is worth noting that the severe error has occurred seems to come back when I restart my laptop.
Install the Device driver provided by samsung in your laptop.
You can install Samsung kies it also installs the device driver
Install driver for your device if you already have driver means try to update your driver manually.
Are you using the samsung usb cable? try to use a non-Samsung one, I had a very similar issue and it worked for me.
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'm trying to connect my phone to Android Studio to follow up with some app development. I am currently struggling with connecting my phone to the computer properly, as ADB never seems to connect to the device.
When attempting to boot the app on the device, this is what Android Studio tells me in the run console
com.android.ddmlib.AdbCommandRejectedException: device still connecting
Error while Installing APK
Which leads me to think that this is a problem with ADB. So when I run adb devices I get this log:
List of devices attached
5210a780f48b44c5 connecting
It stays in the "connecting" state no matter how long I wait. I accepted USB debugging and file transfer.
When in Android studio, the device is listed as
I'm out of ideas as to how to fix this. I recently updated my phone (Samsung A5) to Android 8.0. This phone connects and debugs fine on my work computer. I tried updating Android Studio, rebooting my computer, installing Samsung drivers, rebooting my phone, revoking debug access, to no avail. I was able to work on this computer a while back but I don't know what changed.
How can I fix this problem so I can debug on my device?
[EDIT]
adb version shows this
Android Debug Bridge version 1.0.40
Version 4797878
Installed as C:\Users\Frederic\AppData\Local\Android\sdk\platform-tools\adb.exe
A friend told me to try to swap ports to a USB 2.0 instead of USB 3.0. After doing so it worked instantly as expected.
[EDIT]
It appears that this has more to do with the capabilities of the motherboard than the version of USB the port is. The opposite might be true for you, or just any other port.
I had the same problem and found that the issue was solved by switching off USB debugging on the device, then switching it on again.
I am working on my very first android app (yay), and I wanted to connect my Samsung Galaxy Note II to Eclipse to try out my app there. However, although my device seems to be detected, Eclipse won't recognize my device, making me unable to select it to run the app on. I can run it fine on the emulators though.
I have tried:
going into developer mode and enabling USB debugging on my phone
installing Samsung Kies
going into Samsung's site and downloading the USB driver that I found under my phone's model
restarting the adb stuff with command prompt (adb kill-server then adb start-server) then starting up Eclipse again
killing the adb stuff from Task Manager then starting up Eclipse again
...and I think that's it, and it's still not working!
If it helps, I am running on Windows 8, min API 8, target API 21, compile with API 21, and my phone is running API 20 (I think). Anyone know what I can do to fix this? Thanks!
Select at your device option "Connect as camera". After you connected your phone, on your device will appear a message asking for "trust your pc".
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.