whenever i start eclipse or android studio an emulator is constantly running in the background. when i try to turn it off it restarts again immediately. no matter if i work with a real device or an emulator i have created, this other emulator is not stoppable. in the android debug monitor this emulator is listed as emulator-5554 - Online - ? [2,3,4, debug] (Version API10). i never created or used this emulator, and there is no place to find and delete it.
actually i am able to work with eclipse or android studio with that annoying emulator, but it seems to slow down the performance and i would like to get ride of it.
Were you using BlueStacks back then by any chance?
It uses the port 5554, and that might have been your problem too!
It happened to me as well and found the solution in another question:
Eclipse Android Emulator-5554 is always displayed
Strange, but should be able to kill a "hidden" emulator instance from the command-line by connecting to its console, i.e.:
telnet localhost 5554
kill
Replace 5554 with your emulator instance's number.
I use AndroVM. For me its perfect.
Todo is:
install VirtualBox first
download AnroVM
file will open in VirtualBox
start the machine and set USB debug on (settings >> dev. options)
in commandprompt goto your "sdk\platform-tools" type adb connect 192.168.15.101
When it's ok you will see your device in Eclipse.
edit: When your Eclipse is not working well, just download a new bundle again
Related
Good afternoon! Not so long ago I began to develop an application for android. The application creates a database and write data through want Android Device Monitor pull database and view, but when you start, emulator-5554 switches to offline mode. I tried to solve the problem using the adb kill-server and adb start-server, to no avail. Prompt how to solve the problem? Used to develop Android Studio 2.3.
I have the same problem with u, but I found it work when I open the Android device monitor first.
1.close your emulator and android device monitor.
2.open your android device monitor.
3.open your emulator.
Then it work.I don't know why.
I had the same problem, the easiest working way is
First, Open Android Studio
Go to Tools -> Android -> AVD Manager - Find the emulator which has problem -> Right click on it and click COLD BOOT NOW .
This will restart the android system, it's just like you hold the power button of your Smartphone and choose Restart.
In my case I had to:
in build.gradle change dependency to classpath 'com.android.tools.build:gradle:2.2.3'
disconnect all connected devices
adb kill-server
adb start-server
then start Android Device Monitor
and at last launch emulator from Android Device Manager
Open Android SDK
Select Tab SDK Tools
Update Android Emulator and package related
I just found the solution to this problem. It was just a small thing.
You need to turn on your developer settings
Steps for this :
Go to Settings
Go to About Phone
Touch on build number for seven times(after this you become a developer).
Go back and go to developer options
Turn on the USB Debugging.
That is it . Your emulator will be online.
Happy coding!!
I am using emulator Nexus 5X got same issue. This emulator work perfectly before i rebooted my laptop. After my laptop rebooted this issue raise.
I solve this issue after enabling/activate Developer Options on the Emulator.
How to Activate Developer Options on Emulator
go to Settings
select About Emulated Device
Tap Build Number 7 times
Hope this could solve your problem or other readers. Thanks.
Try :
adb connect localhost:5555
You can start the Android Device Manager (ADM) by the command line script.
Go to the Android SDK tools folder %userprofile%\AppData\Local\Android\sdk\tools
Run monitor.bat
You can ignore its ddms error message when ADM starts. It does not affect to access the emulator.
I created a shortcut of monitor.bat on my Desktop. So I just double click the shortcut to start it when I need to run it.
For those who use Charles Proxy on their emulator, you need to enable USB debugging in Developer Options.
This fixed my problem.
There is a really simple solution to this problem:
run the command:
adb reconnect
this brings back the device online, you can check by running adb devices
I am unable to debug my app in Android Studio. It always keep showing this message
Warning: debug info can be unavailable. Please close other application using ADB: Monitor, DDMS, Eclipse
Restart ADB integration and try again
Waiting for process: com.#######
I can't debug by any method neither run time nor launching app in debug mode.
Did you turn it on the Android side? The option is hidden behind a backdoor now.
Then Windows need driver, Linux does not need driver, same might be but I don't know goes to Mac OS X. Windows driver for Nexuses are already included.
This method that I'm writing it works for windows :
1-You need to get your device's drivers using the manufacturer's website. (ADB Drivers).This is a must for debugging and it seems that it is where your problem is lying beneath. If you use a simulator like Genymotion, skip this step.
2-Enable USB debugging from developer options.
3-Connect your device.
As the error message is displaying
Warning: debug info can be unavailable. Please close other application using ADB: Monitor, DDMS, Eclipse
You have Eclipse program running which is using the ADB Connection. So first close the Eclipse Program and Try Debugging in Android Studio, if problem persist then restart Android Studio or restart machine
I am new to android development and was trying to use bluestacks to test my apps (as my pc won't run the emulator fast) but the bluestacks emulator is not being detected by android studio.
I started bluestacks and then ran my app. On the choose device dialog it doesn't show bluestacks.
I looked up in device monitor, but bluestacks wasn't detected there.
I also tried using adb kill-server, adb start-server, adb connect 127.0.0.1
but that didn't work as well. It says "connection could not be made as the target machine actively refused it".
All the solutions given in the other related stackoverflow post don't work. Android studio won't recognize bluestacks.
Please Help !!
Try in command prompt "netstat -anb" with administration privileges. Check if there is 127.0.0.1 5555 Estebalished.
If everything is OK then temporary disable firewall and type"adb connect 127.0.0.1:5555" should work.
i too have also gotten the error "connection could not be made as the target machine actively refused it" recently (when i tried to connect to adb using command prompt)
Trying with -> adb connect localhost:5555 or adb connect 127.0.0.1:5555 would not work. You need to identify your bluestack device ip address. You can identify the ip address using the preferences in your bluestack emulator setting. (where you enabled ADB in bluestack).
I did the following to resolve the error you had encountered and successfully connect Android studio to Bluestack. please try the following steps. (I am using windows 10, Android Studio 4.0.1, Bluestacks 4.200.)
find your android studio sdk platform tool folder. For me its is
custom installed in my D drive. for example->
D:\AppData\Local\Android\Sdk\platform-tools
right click on adb.exe
and run as administrator. (click on yes if a pop up ask if you would
like to make changes to your devices. After that you would only see
another pop up that suddenly disappear.)
open Bluestacks. Run your selected emulator (samsung/pixel etc). Ensure that
you have enable "Enable Android Debug Bridge (ADB) in the emulator
preferences.
open command prompt. cd to your platform tools folder path.
enter the following command->adb connect xxxxxxxxxxx where xxxxxx is your
device localhost ip. (see attach pic. My device ip is
127.0.0.1:xxxxx hence my command is ->adb connect 127.0.0.1:xxxxx
continue with the following command->adb devices you would see your bluestack
emulator device. same ip listed.
open your android studio. You would be able to see your bluestack emulator
[
i don't know if you fixed the issue or not but it's pretty simple to use bluestacks, if you see this screen when you open it like this all you have to do is run the app in android. it happens where android doesn't detect it because it wont see it as a device you either wait or try to get that screen (that sort of refreshs)
Just Need to do this!
Go to the SDK folder that you have got in your computer,then open the "platform-tools" folder,then open the "adb.exe" as administrator.
then try the BlueStack emulator.
if u got problem to connect with blue stack through android studio then follow following steps
in run(windows+R) put '%localappdata%\Android\Sdk\platform-tools' and check adb.exe is working correctly or not
If not then download file from
https://www.microsoft.com/en-us/download/confirmation.aspx?id=49093 which is
Update for Windows 7 for x64-based Systems (KB2999226) (related OS)
and install it.
allow adb.exe as exception in your virus scan software don't treat this exe as malware.
start your blue stack emulator.
go in setting of blue stack emulator go in preferences click checkbox 'Enable Android Debug Bridge'.
go to this location %localappdata%\Android\Sdk\platform-tools and run cmd through this location.
put command 'adb connect localhost:5555' press enter in command prompt.
start android studio then run project through play button popup will come with virtual device list, it will show your emulator's device.
...happy coding
I have no open emulator and no device connected to my computer but when I run my android project it shows me the following emulator. Why?
I have restarted my eclipse and my computer. nothing changed.
By any chance do you have an application installed called BlueStacks? If the answer is yes then this is because this is its self an Android emulator which listens on port 5554
I am running Android SDK 2.2 and am trying to get the adb to connect to the Google Nexus One phone. Its a new phone, shipped straight from Google - haven't installed any apps on it yet.
(I have Windows XP)
Here is what I have done so far:
Followed the instructions on setting up the device for development as given on the Android Developer's site:
http://developer.android.com/guide/developing/device.html
added android:debuggable="true" to my application manifest
USB debuggable is checked on the phone
downloaded the Device Drivers For Windows Revision 3 (this supports Nexus One phones)
Went through the Hardware Installation wizard to install the device - the device shows up as "Android Composite ADB Interface".
When I run adb devices on the shell, the device appears for a moment, then disappears.
On the Eclipse console, I get the following message:
[2010-11-13 11:54:42 - DeviceMonitor]Failed to start monitoring
I have rebooted the pc several times, uninstalled and reinstalled the drivers several times, but I get the same error each time. As I was researching this problem, someone had recommended rebooting the phone. I am a bit confused by that - is that a soft or hard reboot? Do I just power the phone off/on and is there something more complex involved? Do I have to hard reboot it to reset to factory version - even though its brand new?
Has anyone run into a similar problem? Any help on this would be great.
I can't test my application on the device if the adb cannot view the device. Thanks so much in advance.
I had this same problem. To get it working, do the following:
Close Eclipse
Open Task Manager and kill the adb.exe program.
Re-open Eclipse (Eclipse will automatically restart the adb.exe service)
Run adb devices from a command prompt and you should see something like the following:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
Of course, I'm assuming you have your phone plugged into your computer.
It sounds like something is killing the service as soon as it starts. Try disabling any anti-virus and running adb devices again. You can also check your system logs for errors - run compmgmt.msc and check the Event Viewer's logs.
When I run adb devices on the shell, the device appears for a moment, then disappears
Do you mean Windows' command shell cmd.exe? The output of 'adb devices' doesn't update itself, it should just print out what's currently connected then terminate.
Nothing here worked for me. And you know what? I plugged it to my USB 3.0 port.
Just plug it to regular USB 2.0 and it'll work.
Hi you jst need upgrade your usb driver, follow this ref link, after upgrading you need to uncheck USB debugging, disconnect cable from device and then check USB debugging and connect cable to device again. this'll solve your problem..
link text
I had this same problem. Do the following:
Plug your phone into your computer and:
Run the command prompt.
Go to the tools location of the android sdk.
run 'adb kill-server'
then run 'adb start-server'.
Turn off COMODO Firewall and Defense+ module
I got my Nexus One on Windows 7 64 bit going by following these instructions:
http://developer.android.com/sdk/win-usb.html
Note that the directory has changed to /extras/google/usb_driver.
You know that you need to do this if you go to control panel->devices and printers and show properties on the device, and there's no driver shown.
Open the task manager by Ctrl+Shift+Esc
In the Processes select adb.exe and Click the End process Button.
Now close the eclipse and restart it again.
This worked for me. Hope this would work for you as well.