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
Related
I'm near frustration. I'm trying to get my react native app to run for hours. all tutorials I find, are skipping the part of Android Virtual devices not starting properly.
I have my react package via node and expo.
HOME and JAVA variables are set. VT-X is enabled. Android Studio is up to date. Whenever I start the Android Virtual Device (set up as Pixel 2) the Android device keeps presenting the Animated Google Logo, but doesn't start.
When I try to start the Android Device via Expo localhost I get an error about USB debugging, which I don't want.
Couldn't start project on Android: Error running adb: No Android
device found. Please connect a device and follow the instructions here
to enable USB debugging:
https://developer.android.com/studio/run/device.html#developer-device-options.
If you are using Genymotion go to Settings -> ADB, select "Use custom
Android SDK tools", and point it at your Android SDK directory.
Error occurred because the current computer and emulator are not connected.
Did you set up the Genymotion as described in the error?
If you hadn't, go to Settings -> ADB, select "Use custom Android SDK tools" ->
and point it at your Android SDK directory.
Download the SDK from here: http://developer.android.com/sdk/ to C:\android-sdk\
C:\android-sdk\
Run emulator, click developer options, enable USB debugging and enable Wi-Fi to Cellular.
Run the Genymotion Shell and type devices list to find the IP address of the device.
Open the terminal and enter adb connect deviceIp:5555. Make sure the connection to adb device is correct. Enter adb usb and adb tcpip 5555.
Android adb documentation
I'd like to connect to android emulator on bluestacks 4 with adb.
but I've got an error with adb.exe -s emulator-5554 shell
checking devices.
$ adb.exe devices
List of devices attached
BH901... device
CB512... unauthorized
emulator-5554 device
once I shutdown bluestacks window, the emulator-5554 will be hidden from above command's result. thus I think emulator-5554 means bluestacks.
then commnad as below to use adb.
$ adb.exe -s emulator-5554 shell
error: closed
but as you know, an error occured.
First, in Bluestacks, go to Settings -> Preferences -> Enable Android Debug Bridge (ADB). Like this:
At this point, Bluestacks enables its adb functionality and exposes itself to the localhost at port 5555 (the default port)
So, in your command line, type adb connect localhost:5555 and you should be good to go.
I did exactly as the chosen approved answer but i still could not connect my android studio to Bluestack 4. Hence i think the problem both of us are encountering could be due to bluestack device ip has changed. (Even if you had detect the device using adb devices command earlier on). Each time i open up my bluestack emulator, i notice that its ip is always different. Hence that could be one of the reason why you could not add adb to bluestack4.
The following step works for me. 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 platform tools folder path: Click on address bar, alternatively press Alt + D. Now when address bar is highlighted, type cmd in the bar. Press Enter key.
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 andriod studio. you would be able to see your bluestack
emulator
[
And I have test bluestack 4 in windows 10 and enable the adb permission in bluestacks 4 settings. It works for me.
After enabling adb in blue stack
go to platform-tools folder
e.g. "C:\Users\Your Username\AppData\Local\Android\Sdk\platform-tools"
run this in cmd "adb connect localhost:5555" or whatever port given by bluestack.
or just run directly from Win+R
"C:\Users\Your
Username\AppData\Local\Android\Sdk\platform-tools\adb connect
localhost:5555"
n.b. localhost = 127.0.0.1
On BlueStack 5 it should be in Advanced -> Android Debug Bridge
I am starting my first android project using nativescript.
I want to run my project with genymotion.
In genymotion GUI settings/ADB I am using custom Android SDK tools and genymotion tells me the android SDK tools are found. Also the VirtualBox path is valid, and when I renamed the device the VirtualBox name and Genymotion name both changed. The Virtualbox VM is powered down.
I start genymotion and get the emulator open with a black screen. I then run:
tns run android
per the nativescript docs
I get as output:
Cannot find connected devices. Reconnect any connected devices, verify that your system recognizes them, and run this command again.
I then tried running:
adb devices
and got an empty list so it seems my device is not being recognized, I just don't know why.
I have also tried running:
tns run android --emulator --geny nameOfDevice
This starts the emulator but again just a blank screen. So I guess nativescript knows about the device but adb doesnt?
Any help would be greatly appreciated and apologies in advance if I am missing some obvious android issue.
You should also make sure that your GenyMotion is using the right SDK.
Go to: >> Settings >> ADB
And choose Use custom Android SDK Tools
If the SDk path is found it will be marked with
Android SDK Tools successfully found!
Do not open genymotion before adb initialisation.
Start adb server first
by adb start-server
and then open genymotion to initialise emulator.
After that you should be able to see emulator in list of running devices through adb command. I ran into the same scenario where adb does not list emulators if genymotion is opened before adb initialisation. I hope it helps.
My working solution is:
cd /opt/genymobile/genymotion/tools
./adb devices
You have to use its own adb tool.
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
My android device can't be located using Eclipse or ADB no matter what I do. I tried everything:
Restarting both the Windows 7 computer and the Android device.
Checked Debugger in Developer options
Checked run unsigned APKs
Setting Eclipse to manually select the device to run on
I can't figure this out.
I eventually found this website http://adbdriver.com/downloads/ and it turns out the driver I was using to connect my device to my computer was installed incorrectly.
Check this out. as mentioned. you should add vendor id to
~/.android/adb_usb.ini
then restart adb server