Believe me, I know there are a TON of these posts in SO, but I've gone through most of them and have yet to find a solution. Some notes:
I'm running Mac OSX Yosemite
Both my devices are USB-debug-enabled (rooted HTC One X, and Motorola Moto G)
On both devices, I have successfully run the app via Eclipse before (in fact the HTC is my main testing device)
My usual method when the device fails to appear is to quit Eclipse, then run adb kill-server killall adb and then restart Eclipse.
This time that method didn't work. I've also tried restarting the phones, and restarting Eclipse multiple times.
Running adb devices shows the device there (the device's ID, and 'device')
I've checked the SDK Manager, just in case there were some magic Mac drivers that I could use. Nope, so such luck.
Anyone got any ideas for this?
Man, you guys are good. The device magically started working again.
If anyone else wants to try and reproduce the solution:
Attempt to debug on device for about an hour with no success.
Consider selling soul. Check craigslist for soul buyers.
Post issue on SO.
Play several rounds of Zuma. Plug in and out the device each time. Quit Eclipse each time.
Swear profusely as you see adb devices showing your device just fine, and even the friggin Logcat in Eclipse itself showing the device tittering away, but you just can't use the device.
Consider changing careers.
Call it a night.
Open Finder, poke through folder on phone (in my case it just had HTC's software installer).
Try again, because you hate yourself.
It works now.
Related
Don't mark this as a duplicate. Let me explain what's wrong and tell you what I've done. So here's my problem. When I open Android Studio, it gives me an error like so:
So then I went to my windows firewall settings. Here is what I have:
As you can see, Firewall is off. Then, I went to my antivirus security program and turned the settings off there:
As you can see here too, I disabled Smart Firewall. Then, I opened Android Studio again. I got the same error here too.
I pressed the OK button and moved on. Then, Android Studio loaded up and everything. After that, ADB started loading. This is where the real error occurs.
I have also tried it with Eclipse, but it also says ADB not responding. For the past month or so, Android Studio has been working fine. I have never gotten these error or warning messages with Android Studio before, so this is rather new to me.
Here is what I have tried:
In cmd, adb kill-server then I pressed the restart button on the ADB not responding message
Restarting computer
Turning USB Debugging on and off on my Nexus 5
So, I really can't find a solution to this. Any help regarding this problem would be extremely appreciated.
Sometimes it just gets into a mess. Close your ide then Go to processes and terminate all adb processes.
Then when you open up android studio it should kick off adb again fresh (or you could run something like 'adb devices' from command prompt before opening the ide if you're worried it gets in to a bad state while the ide is waiting for it to initialize)
If none of that works you could also reboot your device. I've very rarely found it necessary, but it has helped me in the past
Kill processes bas_deamon & bas_helper Then press restart for ADB and it will work.... this what I do in WIndows 7 when I face this issue.
You may want to make sure your phone is unplugged. When it is plugged in, I have noticed this happening and the solution for me (which may be Mac specific) is to unplug my phone from the computer.
I had the same error messages, but a different problem.
Port 5037 was not in use, but still adb couldn't start.
So after hours of trying I finally realized, that it was an installed VPN-client (Checkpoint Endpoint Security). Even though there was no connection (and I even killed the process) the connection didn't work. After uninstalling everything worked like a charm.
Maybe it helps someone who reads this question, because everywhere else you just read about the blocking port. And in addition, while the client was installed some other TCP-based Frameworks and even Windows-Remotedesktop stopped working too.
This happened to me as well. I solve it by terminating all process that is using port "5037" which is, by default, the port used by adb.
Sir,
Actually Sometimes our parent control software interfere with it. but after turning off its real time protection , we got this error. so basically you need to check the whether we are using 32 bit Android Studio or 64 bit. just try to av same bit operating system as of Android Studio , u ll get this error removed after that. :)
For Windows: add a system variable as following and then restart your Computer then try again - it will be OK
ANDROID_ADB_SERVER_PORT
10501
I had the same problem on Mac OS X. After some research I've found a bad entry in my /etc/hosts file for my localhost (192.168.99.100 localhost).
I removed the bad line and left the line 127.0.0.1 localhost for ipv4 and some entries for ipv6 in.
After a reboot the Android Studio was able to communicate with adb and found my connected Android device again.
I am a java beginner. I am going through a book right now actually called Java in 24 Hours sixth edition by Rogers Cadenhead learning java and android programming. Anyways, to my problem. I am using eclipse to make a simple app and I want to transfer it to my galaxy s 2. I am ready to debug it and pick my device.... except its not there. I have installed Kies, the drivers, made sure its in USB debug mode but it will not recognize it. Any suggestions? This is not a duplicate! It is different because even though its in debugging mode, even though Ive reinstalled kies twice, even though Ive made sure the USB port or cord is not a problem it still does not work! But whats strange is my My Touch will work perfectly with the app. What am I missing here? HELP PLEASE.
You are most likely having a problem with the adb in your platform-tools folder. It is the android device bridge. Go to the android-sdk folder and then go to platform-tools and inside you will see adb. Press shift + right click anywhere in an empty spot of that folder and click on 'open a command line here.' Type: adb devices. It should show you a list of usable devices. If that doesn't show your galaxy (it will be a big number/letter sequence like: 3ANIWRN42408) or anything than try adb kill-server then adb start-server. And then see if adb devices shows your device.
If that is hard to follow, check this out: adb/usb tutorial
I am using LG-P500. When I try to select it in the 'Android device chooser', Eclipse recognizes the phone but not the target. It says target "unknown". Because of this problem, I can't choose the phone as the Android device.
How can I get Eclipse to recognize the target?
Had the same problem with an LG phone. Rebooting it (phone) worked for me
One solution I am aware of is to just turn off and on USB Debugging on your phone. It also happens to solve a bunch of other device-not-recognized kinds of problems.
Follow these steps, if your device is recognised but the eclipse is stating it as unknown:
->open cmd
->go to the your android sdk directory --> Go to platform-tools
->adb kill-server
->adb start-server
this will definitely solve your problem :)
If you already installed USB driver and still your device showing as unknown then follow this solution. I had same problem with my MOTO G and this solution works fine for me
Check your device that
USB connected
and
USB debugging connected
or Check the following
The solution was to create a udev rule for the device. See http://developer.android.com/guide/developing/device.html#setting-up for how to setup a udev rule for your specific vendor device.
With the rule in place. Eclipse was able to launch and debug.
One simple trick works fine for me.
Disconnect device from PC
Tap revoke USB debugging authorization in phone setting
Reconnect device to PC
Tap OK for RSA authorization
The reason that my SCH-I535 device was not being targeted... is because I had the device plugged into a USB 3.0 port.
Once I plugged it into a 2.0, everything began to work properly.
Also try this, On your phone:
Go to "USB computer connection"
Select Connect as "Media Device (MTP)"
I tried these suggestions, but unfortunately, nothing worked.
What worked for me was:
close Eclipse
end the adb.exe process (using Windows Task Manager)
restart Eclipse (the device was now recognized in Android Device Chooser)
Go to Settings -> Storage -> Click on Top right menu button -> USB computer connection-> Check Media device(MTP) is enable or not
Do you have a driver for your phone installed on your computer, eclipse doesn't automaticly come with drivers for phones.
My problem solved by changing the cable. Nothing else worked for me.
For this problem I had tried disconnecting/reconnecting the USB cable, toggling on/off the USB debugging and relaunching Eclipse with no effect. Trying a different android device showed exactly the same eclipse errors, with two entries marked 'offline' and after disconnecting the USB connection it still showed one entry while nothing was connected.
My problem was solved by rebooting my computer and starting again. Probably ending the adb.exe programme (answer 4) would have done it too in my case.
GALAXY S5
I know this has been answered heaps of times already but if you have a Galaxy S5 then the turn off and turn on of USB debugging works to resolve this problem
When the phone is plugged in and the Eclipse window shows the "Unknown" icon...on the phone turn off USB Debugging then on again, it will then ask to allow that computer to connect, and you can say to always let it do so. Then it comes up OK.
create a udev rule for your development device.
I had this same issue, and I found this post, which fixed it for me.
Just download
http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip
unzip it and replace your "C:\Program Files (x86)\Android\android-sdk\platform-tools" directory with that
Credit goes to hack_on
Here is his post that helped me:
https://stackoverflow.com/a/15000565/342497
Thanks! :-)
If you cannot select the ok button when choosing a device it probably means you cant do things like adb logcat either in my experience.
I usually kill adb from Task Manager and it starts working. I noticed adb kill-server only sometimes works, and that there are often multiple processes called adb running... not sure if this is a bug or by design.
step 1 : rigth click on the project => properties => android => select api level that your device suport.
step 2 : restart your phone
work for me ...
Had the exact same problem. Working fine for over two years then all of a sudden this error pops up. The fix for me was running the SDK Manager.exe located here on my machine: C:\Program Files (x86)\Android\android-sdk
Turns out I did not have the ability to run on the device with Android operating system 4.2.2, only 4.0.2. After the SDK updated recognition worked perfectly. Turns out my phones operating system was updated and I forgot to update the SDK.
Had the same problem. Turns out I had changed my USB connection mode from MTP to MSC. Changing it back to MTP solved the problem. Thanx.
I used to debug w/o problems in my HTC One X, I broke the screen and until they repair it I managed to get an HTC One (M7 I think it's called internally).
I was unable to debug with this same problem, what actually happened is that besides having to follow a weird procedure to make Debug options appear (press 7 times in the firmware version in "About" menu) the phone was showing a message asking me to verify that the computer trying to debug on it was authorized.
I had not seen this behavior before in any the the phones I have used, not sure if this is a new functionality or simply it was not enforced on the other ones.
It is because that you didn't allow your phone to be debug by this computer.
Lock your screen, unplug and plug it then unlock screen click allow in the dialog.
KITKAT 4.4.2+ users, TRY to switch from ART to DALVIK or from DALVIK to ART. :) solved mine.
I tried different drivers, turning USB debugging on/off, rebuilding program with lower level API, killing ABD and restarting. Then I saw post on here regarding cable swap. Changed USB cable to Samsung USB cable and worked immediately.
you need to authorize the device to that computer. I was connecting the phone to my centos VM and kept getting this. I had to kill the adb server and then run it as root user. then you will get the prompt on the phone to authorize machine.
For me it worked by disabling and enabling the USB-Debugging option while ADB is running. Thanks for all the suggestions.
I had the same problem, restarting the PC worked for me.
(Debugging was already on, USB cable plugged in, fresh restart)
SOLUTION:
Switched USB connection from Media Device (MTP) to Camera (PTP).
When I did this it the PC installed device drivers, then phone gave me my computer's fingerprint and had a dialog concerning allow device to use USB Debugging. Accept. Device shows up in eclipse. All good.
(On Samsung Note II API 19)
Note: it's good habit to always try toggling the USB mode. I don't think it's the act of designating Camera (PTP), but the dialogs that are generated when doing so. Also, I had my phone replaced: I remember seeing this dialog before but not on this phone. Maybe there's an option somewhere to enable it per device?
I had the same problem. Turns out my device was prompting a dialog asking me whether I should allow connecting to my laptop or not. After clicking yes this problem went away.
The problem for me turned out to be insufficient rights of adb server.
I run Android Studio through remote desktop (used laptop to connect to a local, more powerful computer). Apparently i didn't have all the privileges when running through remote desktop.
After stopping adb server and restarting it with root privileges solved the problem.
sudo ./adb kill-server
sudo ./adb root
Edit:
Turns out i had to do this just the first time. Since the first time i don't have to do this anymore.
Hey Everyone,
I have had this working before, but all of the sudden it stopped working, I have reinstalled the drivers, restarted the adb server, restarted the phone and computer a few times, and it just won't work. The thing that is weird about it is that I had it working before, and it just stopped working, if I never had it working before, then I would assume I just didn't have something installed correctly, but it must be if it worked before. Any ideas for anything I can do to fix this, I am getting tired of using the crappy emulator :p
Thanks,
WWaldo
Edit: Editing the edit, because I am dumb and forgot I had the copy mode on...no new info on the issue then :(
It can be many things:
bad device drivers: try removing all usb drivers for the device and start from scratch
bad mb drivers preventing the recognition of any usb: look into the device manager for trouble
as EboMike said, bad cable: do you hear the sound when the device is plugged in?
phone not in debug mode: adb requires usb debug mode. Check the phone settings
bad ROM: you mention "the rom I am running": flash another one and check
I have seen this problem off and on while running the Eclipse (Galileo) under Fedora 11-13, whether the target is my device or an emulator. But now with my new device, the HTC T-Mobile G2 (Android 2.2), I see it much more frequently: I successfully download the app (complete with lots of Log.d() calls), the system successfully launches it, but the LogCat pane in the DDMS perspective is completely blank.
Sometimes, only sometimes, I seem to be able to kick it into action by clicking on the tool for Debug (the little bug one). But that doesn't even work all the time. Worse yet, it forces me to restart the whole program, which is very cumbersome.
And yes, I did remember to connect the device and make sure the device shows up under "adb devices", AND make sure that is the device the ADT downloaded to. I can even hit breakpoints in the code.
I suppose I could try relying only on the debugger, but I put a lot of work into writing those Log.d statements in the right place, it would be a giant leap backwards to do without them now. So any suggestions concerning what the problem might be, workarounds, or how to find relevant bugs logged against either ADT, SDK or the G2, would be welcome.
TIA
PS: Google searches such as "android ddms logcat" have not helped so far.
PS: I have also considered running ddms from the commandline, but the instructions on how to do this wtihout conflicting with the port already chosen by ADT for running DDMS are not clear enough to inspire confidence: so I always quit Eclipse before running the command line version of ddms. But then I lose the handy ability (provided by Eclipse) of navigating my source code while reading the log, so this too, is an inferior solution. Perhaps if someone can connect a few more of the dots in Google's instructions on this by explaining how to get the device and command-line DDMS to agree on a port while still running Eclipse, that would be a good solution.
Just to suggest the basics, when you click on the DDMS tab, is the device listed on the devices tab? (If devices isn't there, click Window->Show View->Devices) If it is listed, have you clicked on the device (on the name column). Sometimes if the device isn't clicked on it will not show the logcat.
If it is and you have selected the device - try clearing the log (the icon of a page with a red cross at the bottom right corener of it - located at the top right of the logcat panel) I find if I have had it running for a long time it sometimes fills up and stops displaying the log, although normally one line is shown.
It seems that ADT looses the connection with the device or is not re-connected when you reboot the device or emulator.
I've found that if you have more than one device or emulator you can click on the other one, click on the empty log window and the logs for this other device appear, then click the device that lost connection and will be re-connected.
Yes, sounds like black magic, but it's all we have...
It worked for me when I did following.
Remove the connection to the device (i.e. unplug the USB cable), then restart Eclipse. Next time it starts, you can see the LogCat is back on action writing logs.
Hope this helps.
I have experienced the same problem on and off.
Basically the logs were coming on console using "adb logcat" but not in the logcat view of eclipse. I've noticed that restarting the emulator , then restarting the eclipse and then relaunching the emulator from eclipse gets rid of this problem.