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
Related
In android studio 3.6.3
This error indicates when I click on the Run button to install the program on the emulator.
Installation did not succeed. The application could not be installed.
Installation failed due to: 'device offline'
After a lot of searching, I found out that the adb had a problem and the emulator was turned off incorrectly.
I entered these commands in the cmd and the above error was fixed.
adb kill-server
adb start-server
adb connect [192.168.162.101]:5555
adb devices
List of devices attached [192.168.162.101]:5555 device
NOTE
This IP is 192.168.162.101, which has an emulator itself. If you want to run the emulator manually, you must get your emulator IP and replace it with 192.168.162.101, otherwise it should automatically follow. Implement the first two commands of the emulator on the adb
I was using the emulator. I just close the Android Studio and then opened it again. The issue was resolved.
Disconnect your phone and connect again. This was worked for me.
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!
Hey guys I am facing Some problem I am using gionee elife e 7 mini android phone I have tried almost everything to connect it with eclipse IDE I install many drivers but none of them worked but .
But when I installed Moborobo it detected my device and it was working very well untill install genymobile emulator now neither genymobile emulator is working nor my device get detected . I don't want to uninstall genymobile is this common is there any solution please reply
Restart your eclipse or go to command line navingate to android sdk tool directory and run following commands.
adb kill-server
adb start-server
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.
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.