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!
Related
The virtual device seems to be running but its status is stuck on booting so I can't install GApps (which I need to test some app) also it doesn't appear in the list of devices in Android studio.
I found this workaround to manually connect adb to Genymotion, but I still have an issue with GApps how can I install them?
I have had this same issue previously. However, what I did was that I closed Genymotion, reopen it and restarted the device.Then went to Android Studio and run the app. You should then see the device under 'Connected Devices'. You should be able to see your design on the emulated device.
I was having the same problem, what worked for me was running:
adb devices
If that doesn't work, try running
adb kill-server
adb start-server
I am using Redmi Note 5 Pro as a physical device to connect to the android studio. A night before everything was working fine and I was able to install apps from android studio to my physical device and view Logs with ease but Now apparently it's not working and showing the device as NULL. Please help.
I tried the post method but it is not working for me.
PS: The only thing I did was update a system update MIUI 9.5.14.0 in between but I suppose that should not be the reason for this.
OS: Ubuntu 16.04 LTS
As pointed out in the post
~/Android/Sdk/platform-tools> ./adb devices
Then restart the adb despite it shows device by
~/Android/Sdk/platform-tools$> ./adb kill-server
~/Android/Sdk/platform-tools$> sudo ./adb devices
This worked for me. Since it showed the device as against the answer in post prior to killing the adb server.
A more permanent solution instead of restarting the adb service every time you can add a udev rule so that you can always access the device.
See: https://stackoverflow.com/a/51554826/5815054
When I try to Run (or Debug) my project in eclipse, the AVD emulator emulator boots normally but eclipse doesn't recognise it. On DDMS, the Devices tab does not find the AVD emulator and thus I see no traffic in the LogCat.
On the other hand, when I plug my phone and choose Run (or Debug) project, eclipse connects to the phone and works just fine (I see it on DDMS on LogCat shows traffic). Any thoughts on this one?
I'm using Eclipse_Galileo_5.2 and Google APIs (API level 12, Platform 3.1). I was working with the same setup before the problem appeared without any problems.
I highly appreciate all the help...
Simply run from command line adb kill-server and then adb start-server. ADB will reattach to the running emulator and will be able to work with it. Do not exit the emulator as bashu suggests as the problem is likely to appear again if you have a slower computer.
Lots of time it happens to me also.
What i do is, I first Exit the Emulator. Then kill adb using
adb kill-server after that i clean the project.
and then adb start-server
and finally run the application and it works fine for me.
Thanks.
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
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