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 am trying to run an application developed in Android Gingerbread (API 10) emulator in Android Studio 2.3.2.
When running, it shows the message,"waiting for target device to come online" and it stays on that even after the emulator has come online, and does not go beyond that point.
I tried to:
1. Update libraries
2. Restart the PC
3. Stop the emulator from AVD
However the application runs successfully on my mobile with Android Naught 7.1.1, but I want to test the app in Gingerbread environment which on the emulator I am not able to do.
I am not able to understand where exactly do I need to check for such error.
I had this problem too when using Gingerbread armeabi and armeabi-v7a images. Nothing helped. I fixed it by using x86 image.
If you don't see device in $ adb devices, try to run:
$ adb kill-server
$ adb start-server
I am not able to connect Android Wear Emulator with my device.I have HTC One device which has 4.4 (KitKat OS).
I follow below link :
Setting up Android Wear
But, when I execute the line adb -d forward tcp:5601 tcp:5601 through command prompt,nothing happens.Android Wear emulator does not show device connected.
Note : I am able to launch the Android Wear Preview app successfully in my device and Notifications settings is also enabled.
Any help will be appreciated.
#Lance Nanek basically helped me solved this problem. In case you had the similar problem, these steps might be helpful.
run 'adb devices' , you should see two devices, one is your
emulator, the other is your device with Android Wear Preview app
installed.
you might see your emulator offline, if so, kill the emulator. From avd, start it, carefully uncheck 'launch from snapshot' - this
is contrast to Android Wear Get started instruction: "Start the AVD
again, but select Launch from snapshot and deselect Save to
snapshot."
run 'adb devices' again, make sure you do see two
devices online
run command 'adb -d forward tcp:5601 tcp:5601'
from the android wear preview app, tape connect, you should be ready
to go.
On the newly updated Android Wear app (Aug 2014) there is a settings button top right when asked to choose a device connected via bluetooth. Pressing this button will connect to an emulator instead.
Enable adb debugging in the developer options on your watch.
Enable bluetooth debugging in the developer options on your watch.
Enable bluetooth debugging in the wear app on your phone. run in terminal:
adb forward tcp:4444 localabstract:/adb-hub; adb connect localhost:4444
See this training.
I think I also had luck with using the cradle plugged directly into the computer, but unable to confirm that now.
Android Wear using Genymotion
For people who does not have a phone with Android 4.3 or above, we can not try the Android Wear Preview. :'(
And here is a way you can try, use Genymotion Nexus 4 or any other emulator with Android 4.3 or Android 4.4 and it works!
Setup a Nexus 4 with Android 4.3 in Genymotion.
Start both the Nexus 4 and Android Wear emulator.
You should first install Google Play Services on the Nexus 4:
Download the zip file
Drag it into the Nexus 4
Reboot the device, and now you are able to install "Android Wear Preview" on Play Store
Open Terminal, use adb tools:
adb devices
you shoud see 2 devices,
adb -s [device name of Nexus 4] forward tcp:5601 tcp:5601
Done!
The trouble I was having, was that the pre-selected API level was set incorrectly. It should be set to the following values:
Using Host GPU is optional.
Stuck with the same a while ago. It appeared that Google updated their Android Wear app. After installing the new version I was able to connect successfully to wear through its interface (as long as I used device with android 4.3+ and adb -d forward tcp:5601 tcp:5601 command)
After some hours trying to find the solution... I've found it!
In my case, the problem was that I have two different SDKs (one from Eclipse and the other from Android Studio), so I was trying to execute the ADB commands in the wrong one.
So it is important that you check the path you are using in your IDE and execute the commands on the same.
I was getting suck on "Connecting to Emulator", but I fixed it by using an Android Wear ARM virtual device instead of an x86 one.
Run the adb -d forward tcp:5601 tcp:5601 command in super user mode
Eclipse is in another hard drive (e:). While avd are in c:/Users/Myname/Android.
Problem is that when I run as android application, nothing happens, though the emulator is running. The app is working on the physical phone. I've read several answers, all vague. Help?
I suspect the Android Debug Bridge (adb) isn't running or isn't correctly running. Try running
adb devices
If your emulator is not listed, try running
adb kill-server
adb devices
Note that adb is installed in the platform-tools subdirectory within your android sdk installation.
Here I have an application, which is supposed to be run on 4.0.3 AVD (as selected in properties).
But as soon as I run the app, it automatically starts in 2.2 AVD.
So, I've change the run option from "Run configurations", and set it to Always prompt to pick up device.
Now I have both 2.2 and 4.0.3 AVD running:
But as soon as I run the app, eclipse gives the list of online devices I have, and there is only 1 device (2.2) online:
How can I make my app run on 4.0.3 AVD?
Generally this problem is solved by two simple commands, I recommend you to run these two commands from your DOS prompt(In windows) or shell (in case of Linux)
adb kill-server
adb start-server