Month or couple ago my emulator started to get close (maybe crash?) every time I press ctrl button on keyboard or when I click emulator's rightside buttons (take screenshot, rotate screen etc..).
It's very annoying, how to resolve it?
Solution.1
By setting the Graphics option on the Android Virtual Device to Software instead of Automatic or Hardware. Once you did that the emulator device started up great and everything worked.
Or
Go to Menu->Tools->Android and uncheck the option Enable ADB Integration Run the application. Now the emulator will be launched, but the app will not run. Once the emulator is fully launched, check the Enable ADB Integration option and re-run the app. Now the app will be launched in the already running emulator.
Solution.2
You might have forwarding enabled on adb. You can try this: Quit Android studio and launch terminal. Run these commands:
adb kill-server
adb forward --remove-all
adb start-server
Now you can launch the Android Studio and try again.
I hope one of the solution work for you.
Thank You!!!
i made oneother divice with lower sdk version and worked for me, latest version was 11, so i made the new device in emulator with sdk v10
Related
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!
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
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
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 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.