I want to connect my Samsung Gear Live with my Samsung Smartphone Device and am trying to follow the giveninstruction. Also kept searching on stackoverflow with similar problems, but it seems that it is something else.
So this what happens when I am using the terminal to connect:
Denjos-MacBook-Pro-2:platform-tools Denjo$ cd /Users/Denjo/Library/Android/sdk/platform-tools
Denjos-MacBook-Pro-2:platform-tools Denjo$ ./adb forward tcp:4444 localabstract:/adb-hub
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Denjos-MacBook-Pro-2:platform-tools Denjo$
What am I probably doing wrong?
I solved it this way, that I changed the USB-cord.
Related
I know this is an duplicate question and believe me I have read every thread there is on this post
1) adb: CreateFileW 'null' failed: The system cannot find the specified file
2) Daemon not running. starting it now on port 5037 * Cannot open 'nul': The system cannot find the file specified
3) ddms: 'adb.exe,start-server' failed — run manually if necessary, Android Studio
I have tried EVERYTHING!!!
a)Uninstalling android studio,its emulators,sdk and deleting every folder saying android in my system
from C:/Users/${HOME}/AddData/Local & Roaming to even C:/Windows/[All System Folders(No adb was found in these folders)},Program Data etc.
b)Uninstalling and Reinstalling Platform Tools from Tools->SDK Manager->SDK Tools after android studio reinstallation
c)Manually going to ${ANDROID_SDK_HOME}/platform-tools folder, opening cmd as administrator and running
->adb start-server[Gives Same Error As Above]
->adb kill-server[Unable to connect to target machine ip xxx.xx.xx connection actively refused]
->adb start-server[Same Error As My Question]
d)Tried to verify if any apps running on port 5037
netstat -aon | findstr 5037
nothing
My specs are[No new updates are available for any of the below specifications]
1)Android Studio 3.5.1
2)Platform Tools 29.0.4
3)gradle 5.4.1
4)Windows 10 64 bit
Also i have geny motion installed but with no adb the emulator is not recognized in the device list
I know this issue was posted atleast an year back but i hope some new light has been shed on the issue
plzz help thank u in advanced
I have a Dell device and suddenly I cannot connect the Android studio to the emulator. I get the following error message:
unable to open connection to: localhost/127.0.0.1:5037, due to:
java.net.connectexception: connection refused: connect
Any Idea how to fix it ?
Try Manually Starting the Server.
Location to your ADB.exe Android\Sdk\platform-tools\adb.exe start-server
I had the same problem after some unknown operations with my Windows 10. I tried many different ways, and finally solved it with the following steps:
open Command Prompt with Adminstrator privilege. (If you don't know how to, please google.)
"netstat -ao" to find which process takes the port of 127.0.0.1:5037. FOr example, something like
TCP 127.0.0.1:5037 mypcname:0 LISTENING 15752
Here the culprit PID is 15752.
"taskkill /PID /F PID" to kill the process. Replace PID with your number, e.g., 15752.
retry adb. If it works, you may sometimes have to proceed with the following steps.
If it is a Windows service that is using the port, it may start automatically, and blocks adb subsequently. You could specify another adb server port for environment variable ANDROID_ADB_SERVER_PORT.
If the Windows service is LogsAndAlerts (which is the common case for many), you can disable or delete it with:
sc config "LogsAndAlerts" start= disabled
sc delete "LogsAndAlerts"
Download this and extract it to in my case
C:\Users\Dev\AppData\Local\Android\Sdk\platform-tools.
It worked for me.
It's been a while since I opened android studio. It's all good until today.
Today the android emulator can't connect to the internet (tried with chrome browser and my application in the emulator), altough it's wifi is connected.
How to fix this?
I already tried:
your_path_of_android_sdk\tools\emulator -avd -dns-server 8.8.8.8, but failed with message: PANIC: Missing emulator engine program for 'x86'
remove emulator, and add a new one from AVD manager
restart pc
reinstall android studio
emulator wifi settings (auto ip / dhcp):
Nexus 5S Api 28
ip address: 192.168.232.2
gateway: 192.168.232.1
subnetmask: 255.255.248.0
dns: 10.0.2.3
Is there a possibility I accidentally uninstall something important / removing network adapter in the 'Control Panel\Network and Internet\Network Connections' ?
( there is only one adapter in there )
Images:
wifi connected, no internet
emulator wifi settings
network adapter on win 7
Just found the solution
your_path_of_android_sdk\tools\emulator -avd -dns-server 8.8.8.8, but failed with message: PANIC: Missing emulator engine program for 'x86'
it does work! but i have to use emulator.exe in the "emulator" folder, not the one in the "tools" folder
the complete command is:
F:\AndroidSDK\emulator>emulator -avd Nexus_5X_API_28_x86 -dns-server 8.8.8.8
where Nexus_5X_API_28_x86 is my android emulator name (found in the avd manager in the android studio).
I was facing the same problem. So while using emulator in outside network it was working and then at my home network, same emulator was showing no internet. The possible cause is due to DNS.
But the solution I opted for this issue is to start emulator, turn off Wi-Fi and turn off data connection of emulator. And then turn on both again and see it will get connected to Internet eventually.
I'm attempting to connect via node.js to an ELM327 Bluetooth OBD-II adapter using Eric Smekens node-bluetooth-obd package, but I'm getting an error I'm not sure how to debug. I am doing this on a Beagle Bone Black running Ubuntu. I'm able to pair with the device using bluez-simple-agent:
sudo bluez-simple-agent hci0 00:0D:18:A0:4E:35
And I've updated the MAC address in the second line of the Readme.md example to match the MAC address of the device:
var btOBDReader = new OBDReader('00:0D:18:A0:4E:35', 14);
However, when I run the script, I get this error:
Error with OBD-II device: Error: Cannot connect
I'm still pretty new with bluetooth comms, so I don't really know where to start debugging this. Any suggestions?
I am trying to perform serial communication on between Ubuntu 12.04 and a JY-MCU bluetooth serial module connected to an Arduino.
I have created this configuration in /etc/bluetooth/rfcomm.conf
rfcomm0 {
# # Automatically bind the device at startup
bind yes;
#
# # Bluetooth address of the device
device 00:12:11:19:08:54
# # RFCOMM channel for the connection
channel 1;
# # Description of the connection
comment "Linvor Bluetooth Module";
}
I can use putty to communicate with the /dev/rfcomm0 serial port and this works perfectly.
However, despite many attempts I simply cannot see how to create a serial port in Processing that works in any way.
For example :
println(Serial.list());
prints nothing at all.
If I execute:
String portName = "/dev/rfcomm0";
myPort = new Serial(this, portName, 9600);
println(myPort);
I see this in the monitor:
processing.serial.Serial#1712651
But if I then call:
myPort.write('9');
I get an exception:
java.lang.NullPointerException
at processing.serial.Serial.write(Serial.java:572)
...
I can't understand why this fails. I have been following all the instructions from Tom Igoe's "Making Things Talk", but this just does not work the way he says...
Any help would b great!
Thanks,
Bob
Aftert searching high and low, I have made this work.
The key issue is that processing uses the rxtx java library (RXTX-2.1-7) for serial communications.
The RXTX wiki says:
"rxtx tries to detect ports on by scanning /dev for files matching any
of a set of known-good prefixes, such as 'ttyS', 'ttym', and since 2.2
'ttyUSB' and so on. "
And since the bluetooth device is named rfcomm* it cannot be detected.
The trick is to create a sym link to fool rxtx (use a ttyS device that is not yet assigned):
$ sudo ln -s /dev/rfcomm0 /dev/ttyS99
Then, connect:
$ sudo rfcomm connect 0
Connected /dev/rfcomm0 to 00:12:11:19:08:54 on channel 1
Press CTRL-C for hangup
At this point the red led on the JY-MCU becomes solid and processing can detect it:
println(Serial.list());
output is:
[0] "/dev/ttyACM0"
[1] "/dev/ttyS99"
So, serial communication can work.
To summarize, the following process will allow a processing script to communicate via a serial port with a JY-MCU device in a BlueZ linux framework
One time setup:
power up the JY-MCU,
use the following command to get its hardware address, mine is 00:12:11:19:08:54
$ hcitool scan
use that to create the /etc/bluetooth/rfcomm.conf file; you'll note that I chose 0 for the rfcomm device , we need that for connection later:
$ cat /etc/bluetooth/rfcomm.conf
rfcomm0 {
bind yes;
device 00:12:11:19:08:54;
channel 1;
comment "Linvor Bluetooth Module";
}
use BlueMan to pair the JY-MCU.
Every time you want to use the JY-MCU
create the sym link:
$ sudo ln -s /dev/rfcomm0 /dev/ttyS99
connect to the JY-MCU:
$ sudo rfcomm connect 0
Connected /dev/rfcomm0 to 00:12:11:19:08:54 on channel 1
Press CTRL-C for hangup
you can now run a processing script and connect to the JY-MCU with
the code:
String portName = "/dev/ttyS99";
myPort = new Serial(this, portName, 9600);
after running the processing script, be sure to CTRL-C at the
command line to disconnect the JY-MCU.
That should do it!
Ciao,
Bob
Just something popped up in my mind.
I had similar problems that were caused due to channel 1 is already used. If you bind to a channel which already is in use, bad things may happen.
sdptool browse local
Use that command to see which channels are available on your Ubuntu device.