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
Related
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
I am using Android studio 3.4.1, In which my projects are not running in real device. but not having any problem in emulator.
After connecting the usb and i have run the app. then getting this error. after that device is not even listed in the available devices.
error got in logs:
Installation did not succeed.
The application could not be installed.
Installation failed due to: 'device '711KPMZ0603459' not found'
Retry
Retry also not working.
I also tried in Android studio Beta 1 and Beta 3. same problem happening.
can any one help me in this?
FYKI:
1. USB debugging enabled.
Tried USB option for File Transfer, USB tethering, No data transfer.
Tried with different cable as well.
Problem identified only after updating 3.4.1 android studio. Also facing in 3.5 Beta 1 and Beta 3.
Same kind of problem already added in Issue Tracker. https://issuetracker.google.com/issues/122892907
Kill and Restart the adb manually through Terminal using below comments. use cd to go inside platform-tools under Android sdk folder.
./adb kill-server
./adb start-server
PS: Before posting this questing here, i already tried quitting the adb in Activity Monitor (which can be opened from spot light)
Activate USB-Debugging in Developer Options and set your USB options from Charge phone to transmit Data.
Well the mark of your phone is important because in my case i use LG G5 and i could not see my device even after turning on developer mode and enabling debugger options.
I don't know the type of phone you use but you can try my solution.
After turning on USB debugging, go to tethering under the networks sections and turn on USB tethering then try again.
Hope It helps!
I'm trying to run an ionic app on my mobile phone (Android 4.4.2).
USB-Debugging is activated.
When i run the command "ionic emulate android" everything works fine and the app is opend in the emulator.
But when I run the commad "ionic run android" I get following warning:
WARNING : No target specified, deploying to emulator
and the app is started on the virtual device...
Shouldn't the app run on my mobile phone? What am I doing wrong?
How can I specify the target?
P.S.: When I copy the .apk file to the phone I can run the app.
I had another developer tool opened (Chrome Inspect) and it "ate" the connection. In my case, just closing the Chrome Inspect panel and running ionic run android worked.
I solved the problem.
Here is what I did:
I typed into the command line: adb devices (located in the "platform-tools" folder in the Android SDK) which returned me an empty list.
So I installed my phone's drivers, which I downloaded from the vendors homepage.
Now the list contains my device and the app is started on my mobile phone.
I had a different problem, with a very simple solution.
When plugging in your Android device for the first time, it'll ask you to trust the computer's certificate. That popup screen disappeared on me, as I was just getting a call.
Simply unplugging/replugging your phone and accepting your computer's certificate should do the trick!
Once you've enabled your device for debugging, make sure to turn on usb tethering on the device;
Settings > Tethering & Networks > USB tethering
This fixed the problem for me.
In my case I had Android 5.1.1, and below are the steps I took:
Please check that your PC recognizes your phone (you can access the files like in a USB flash drive). If not please install the drivers from google here.
Please check that the USB debugging options is checked on your phone, then:
1- Go to Setting -> General -> '{} Developer options'
2- Look for the 'USB debugging' option
3- If the 'USB debugging' option is disabled then turn off 'Developer options' and turn it back on. Now you should be able to check the 'USB debugging' option.
None of these worked for me on android 6.0 on a mac.
I found this article: http://trendblog.net/android-file-transfer-not-working/
quoting from it:
Enable Developer Mode by going to Settings > About Phone (at the very bottom usually) > press on Build Number repeatedly until the pop-up appears
Go to Settings > Developer Options
Enable USB debugging
I'm on a Mac.
What worked for me was to heed the warning on the device that said no program on the Mac was available that could connect to the device, such as Android File Transfer.
I installed that. Unplugged and replugged the USB cable. And voila.
I had two problems (Ubuntu OS):
I had a connection open with chrome//inspect - close that (simply close the tab)
I missed the dialog that appears when you connect your device through USB cable. You must trust the computer.
Now run the command cordova run android and look at your device there another dialog will be appeared click ok, now you are done! In the terminal you will see LAUNCH SUCCESS. By the way I removed the old app from my device too.
No target specified and no devices found, deploying to emulator
When this message appears, you have to click START, and activate your emulator before.
If your app is already installed in your device and your device debuging is already enabled.
Then uninstall the previous app and install the fresh apk
sudo ionic cordova run android
Once you are remove the USB plugin from the computer means it will not work. Already open the Chrome inspect in your PC means close that tab and run.
In my case, just closing the Chrome Inspect panel and running ionic cordova run android worked.
Thats all. Enjoy your coding
I got the solution by removing the Android emulator and re-create the emulator from AVD Manager of Android Studio.
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
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.