I've a device connected via USB (Samsung SM-T385 - Type C Port) and I don't have any emulator created in my system.
OS : Ubuntu 16.04
ADB Version : Android Debug Bridge version 1.0.40 ; Version 28.0.2-5303910
Problem
Even though I haven't added any emulator, adb blinks with emulator-5554 [DISCONNECTED] like above. Sometimes even the real device is not getting detected, and shows just the blink text. This issue also occurred to one of my colleagues. He uses a Windows 10.
What worked?
Restarting the system solved this issue for an hour or less,then the issue rises again.
What didn't work?
adb kill-server
Kill adb from process list
Restarting Android Studio
Question
How do I fix this issue, without restarting the system ?
Change your port number in Android studio setting page
Here is the answer: Blinking option in Connected Devices list that won't let me debug any app
but basically the answer is it is videostream app... uninstall that and fixed!
I couldn't understand why my HTC Wildfire s doesn't recognize by adb. When I run I have this error insufficient permissions for device . My platform is ubuntu 12.04. So when I turn into another OS (like MaC os) it is working fine (device runs well enough). So when I turn it on ubuntu it doesn't work.
I read some posts where they said you have to kill you server and start it again. I did it too. but no result
Could anyone tell me what's going on here?
Unless you've manually changed your permissions around on your machine, you need to run your adb server as root to give it permissions to communicate with the Android device.
sudo adb start-server
See an article here how to automate it on machine startup.
When you try to connect to the android device, the Windows needs you to install the driver for the phone, Mac doesn't need you to do anything, Ubuntu needs you to configure a udev rules file.
This is the link and I think it may help you.
I have a simple camera app I'm trying to push to my phone, but HTC sync (Thunderbolt on Verizon) simply will not recognize the device. I believe this is the reason I can't get the phone to accept the APK. All my drivers, project, and sdk manager and plugin are updated and I reinstalled HTC sync just to be sure. I also enabled usb debugging and unknown sources
I believe the Thunderbolt connectivity issues also destabilize the eclipse plugin. I get hung randomly during Android functionality in eclipse (like simply loading DDMS or a Run Configuration).
As a result, I'm trying to find a way to work around having to use HTC sync to push my app there.
I developed with a HTC Desire some weeks ago and it worked without problems.
You shouldn't need HTC sync. Have you tried to use the google usb driver as described here?
Whats the output when you call adb devices from commandline? If everything worked correctly you should see the device id of your phone.
Sometimes the following can help if adb does not recognize your device:
adb kill-server to stop the adb process
Use the task manager to make sure no other adb process is running (stop them with the task manager)
restart adb server by calling adb devices
Try to install the app using adb install -r C:\path\to\app.apk
I use "adb devices" to get following result. Only one device is connected to PC by USB, but we get 8 lines of result.
Could anyone suggest the reason?
WH96TNE00361 offline
WH96TNE00361 offline
WH96TNE00361 offline
WH96TNE00361 offline
WH96TNE00361 offline
WH96TNE00361 offline
WH96TNE00361 offline
WH96TNE00361 offline
Try the following:
Unplug the usb and plug it back again.
Go to the Settings -> Applications -> Development of your device
and uncheck the USB debugging mode and then check it back again.
Restart the adb on your PC.
adb kill-server
and then
adb start-server
Restart your device and try again.
To complete the previous answers, another possible solution is to change the USB socket in which your cable is plugged in.
I had this problem (with the classical answer about using adb kill-server / start-server not working) and it solved it.
Actually, it took some time to find that because Windows was correctly recognizing the device in my first socket. But not ADB. As Windows was recognizing the device, I had no real need to test other USB physical sockets. I should have.
So you can try to plug the cable in all your USB physical sockets directly available on your computer. It did worked for me. Sometimes the USB sockets are not managed the same way by a computer.
Beginning from Android 4.2.2, you must confirm on your device that it is being attached to a trusted computer. It will work with adb version 1.0.31 and above.
adb kill-server
adb start-server
that solved my problem
I've had a similar issue with one of my phones.
I was unable to connect and use usb debugging on any of my computers.
In the end, I had to restart the usb debugging on the phone manually [doing so using the Developer menu was not enough].
There's only one command you have to run on your phone [I did it using Terminal Emulator app]:
adb usb
And that was it.
Hope this helps someone in the future.
You may also try downloading newest version of adb http://developer.android.com/tools/help/adb.html
Reboot the device. This always fixes it on Mac OS, whereas adb kill-server does not.
On my Galaxy Nexus with Android 4.2.2, I had the same problem initially, 'adb devices' was showing the device but with offline status (USB debugging was initially active on my device).
These are the steps I took to remedy the situation :
Disable USB debugging (Device not connected to PC)
Re enable USB debugging
Now connect to your PC, now a pop up on the device (not on PC) will ask you for authenticating the PC, Thats it...
adb devices now lists both device id and no offline.
I post here my question just in case is helpful for somebody else.
My problem was that my colleague was connected to the same device and I was not able to connect to the same device.
Note: I had this problem with Amazon Fire TV connecting over Wifi.
There are 2 solutions:
Easy to "drop" his connection (sorry buddy :)
Restart the device
adb kill-server
adb start-server
adb connect device-ip
A bit more difficult but two clients can use the same device (use different TCP ports)
Please look at this answer
For me with Android 4.1.1 only rebooting device works
Run SDk Manager and install Android SDK Tools and Android SDK Platform-tools updates. ADB must be updated to a new version for 4.2.x
I had the same issue and none of the other answers worked. It seems to occur frequently when you connect to the device using the wifi mode (running command 'adb tcpip 5555'). I found this solution, its sort of a workaround but it does work.
Disconnect the usb (or turn off devices wifi if your connected over wifi)
Close eclipse/other IDE
Check your running programs for adb.exe (Task manager in Windows). If its running, Terminate it.
Restart your android device
After your device restarts, connect it via USB and run 'adb devices'. This should start the adb daemon. And you should see your device online again.
This process is a little lengthy but its the only one that has worked everytime for me.
Had this on client's machine it turned out he had an out of date version of adb installed via website offering adb and fastboot. The client in question didn't want to install the whole SDK because of perceived bloat :S .
So if you're seeing offline make sure you've downloaded and using the latest adb. I ended up emailing him adb executable.
Also worth checking that the adb you are using is the correct one in the Path. i.e on Mac
$ which adb
/Users/me/dev/adt-bundle-mac-x86_64/sdk-macosx/platform-tools/adb
if non of the steps work from the above. my device still offline after connected through wifi. i did the following:
go to your device...
go to settings.
go to developer options.
Allow adb debugging in charge mode only.
repeat the steps as you always do . which is:
a. connet your usb on chargemode only.
b. open command write:
- adb tcpip 4455
- adb connect 192.168.1.11:4455
b. disconnect usb.
now everythings work for me .
make sure the device is set for usb debugging
Have the adb client running (e.g. via "adb usb" or adb start-server"
LEAVE the device connected via usb!!!
AND THEN reboot the device.
This always brings my Motorola MB525 "online" again, after adb complains it would be "offline". I'm using OSX btw.
I made adb working on Android 4.4.2 with GT-N8010 (Samsung tablet) after setting device in authorized mode once upgraded adb to SDK version.
~/local/opt/Android/Sdk/platform-tools/adb
Android Debug Bridge version 1.0.32
While It did not work using :
adb version
Android Debug Bridge version 1.0.31
Shiped in Ubuntu LTS version :
apt-cache show android-tools-adb | grep Version
Version: 4.2.2+git20130218-3ubuntu23
This link may help then
Can't connect Nexus 4 to adb: unauthorized
After wasting hours on it, I have updated my version of adb and now adb devices shows my device online and I can run the app on it again.
also make sure adb isn't running in your processes automatically. If it's there right click open file location, figure out what is starting it, kill it with fire. Run the updated adb from an updated android sdk platform tools. This was the issue with mine, hope it helps someone.
What did me in is was that multiple unrelated software packages just happened to install adb.exe -- in particular for me (on Windoze), the phone OEM driver installation package "helpfully" also installed adb.exe into C:\windows, and this directory appears in %PATH% long before the platform-tools directory of my android SDK. Unsurprisingly, the adb.exe included in the phone OEM driver package is MUCH older than the one in the updated android sdk.
So adb worked just fine for me until one day something caused me to update the windows drivers for my phone. Once I did that, absolutely NOTHING would make my phone status change from "offline" -- but the problem had nothing to do with the driver. It was simply that the driver package had installed a different adb.exe - and a MUCH older one - into a directory with higher precedence.
To fix my installation I simply altered the PATH environment variable to make the sdk's adb.exe have priority.
A quick check suggested to me that "lots" of different packages include adb.exe, so be careful not to insert an older one into your toolchain unintentionally.
I must really be getting old: I don't ever remember such a stupid issue taking so endlessly long to uncover.
Check that the ADB version that you are running is newer than the version of the OS on the connected devices. For me, updating the ADB helped to get the device online.
if i start an emulator using the android SDK r12 it does not show up in the adb devices list
win7 64 // android 2.2 (not an actual hardware device - just the emulator)
what could be the problem?
You can also try to :
adb kill-server
adb start-server
to restart the adb server. Maybe something went wrong with the adb-server. This happens a lot, and many such issues can be solved by restarting the server.
Make sure that you are at the path and give command.
android-sdk_r12-windows\android-sdk-windows\platform-tools>adb devices
I am also using win7 64 It is working for me. If you are getting any error. Mention it.
Also make sure that USB debugging is enabled in your device.
Settings>Applications>Development>USB debugging
Can you able to see device in eclipse?
If not then close your emulator and open it again.
Sometimes even adb itself bugs, for me always works good old pkill:
pkill -9 adb