After the migration of my development environment from El Capitan to Sierra and updating Tizen Studio from 1.0.1 to 1.1.1 the SDB CLI does not work any more on my new machine. I have installed JDK 1.8.0_121.
I can not really start a SDB server.
$ sdb devices
* server not running. starting it now on port 26099 *
fatal: server listener(26099) cannot bind
Then the following is returned:
* server started successfully *
But I can not connect to devices or list them:
$ sdb devices
runs into endless loop without feedback.
I have tested also the old Tizen Studio version 1.0.1 but got the same result. Can this be a Java or MacOS problem?
Any hints what can be the problem?
Seems to be an issue with SDB and probably Mac OS Sierra.
I have downgraded to Smart Development Bridge version 2.2.67 and sdb works fine. All newer version occur the same problem.
You need to kill the process that sdb cannot bind and then start sdb again with sdb start-server
To find out what process port 26099 is taking
sudo lsof -i:26099
The output
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sdb 3495 lucasbatista 5u IPv4 0x401834fdf37019a7 0t0 TCP *:26099 (LISTEN)
To kill the process
kill <pid>
In this case
kill 3495
Note:
I realized that the process that occupies this port, is usually the emulator itself when we started with Tizen Studio.
Now, I don't know why sdb simply does not choose another port to start or the emulator does not start on another port, since the developers of Tizen Studio, must have the knowledge that the default sdb port is 26099
Anyway, this step by step that I mentioned above, works for me, I hope it works for you too
Related
I have just recently installed Genymotion and VirtualBox on Solus and when I start a virtual device y I get this error:
The connection to the virtual device has been lost.
Please restart the virtual device.
When I start the machine the screen loads but it's all in black and then I get that error.
I googled that and I found that I must reconfigure de Host-only network adapter but unfortunatly it didn't resolve the problem.
I also tried reinstalling virtualbox and genymotion but it didn't solve the problem.
Here's my log file: http://pastebin.com/CsdCJAw3 (I posted it in pastebin because it exceeds the characters limit here)
Thanks in advance
Are you running a VPN client like Cisco Any Connect. I was running it and Genymotion was continuously showing me the same issue. I just had to stop the VPN and close the VPN app if any.
Restart Genymotion and voila it connected.
You can start your VPN after that and it should work.
In case it still doesn't work. After stopping the VPN or if you're not running the VPN client before starting Genymotion try running this command.
This used to help me when something was causing an issue with the virtual box daemon.
sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart
I'm trying to Kernel Debug Raspberry PI3 using Bus Pirate, I've followed the instructions to connect them, and also the steps from
(https://developer.microsoft.com/en-us/windows/iot/docs/Windbg.htm)
However everytime I run the following command
windbg.exe -k com:port=com3,baud=921600
but once I restart I get "waiting to reconnect..." and nothing happens?
Any advice, have you come across this problem? My target is a PI3 and using the latest, 10.0.14393.693 version of Win 10 IoT Core.
Solved this by running the following on Raspberry PI
bcdedit /dbgsettings serial debugport:1 baudrate:115200
On the Host machine running the baudrate of the following
C:\Program Files (x86)\Windows Kits\10\Debuggers\x86>windbg.exe -k com:port=COM3,baud=921600
Good morning to all,
I have installed Centos 6.7 x86 64 on a Virtual Machine. It is not the first time I'm using this virtual machine...I have already installed a Windows xp 32 bit system, and a Centos 7 with graphical interfac system, and they both connected as well. This time I can't start a connection. In the virtual machine I set the parameters on "NAT" and "Connected Cable", and here I report my inux configurations:
Configure eth0
#
vi /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
NM_CONTROLLED="yes"
ONBOOT=yes
HWADDR=A4:BA:DB:37:F1:04
TYPE=Ethernet
BOOTPROTO=static
NAME="System eth0"
UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
IPADDR=192.168.8.171
NETMASK=255.255.255.0
Configure Default Gateway
#
vi /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=centos6
GATEWAY=192.168.8.3
Restart Network Interface
#
/etc/init.d/network restart
Configure DNS Server
#
vi /etc/resolv.conf
nameserver 8.8.8.8
"
I've copied this parameters from a website guide. Anyway, I tried also setting NM_CONTROLLED=no and ONBOOT=no, but nothing works.
Even if I try to pinging google by the command
ping www.google.it
it doesn't work.
Any suggestions?
So I have been running a few scala programs on Ubunutu and I have noticed that whenever I run a program for some reason Java starts listening on some random port and won't stop listening.
I am running scala version 2.9.2 on ubuntu 14.10.
Is this meant to happen and does it happen for anyone else?
To check open ports I am using
sudo netstat -anltp
lsof -i
Thanks
I am working an on Android app. Today a "phantom" emulator has appeared on my system. It shows up when I have NOTHING connected and I run "adb devices". I steals "logcat" output when I am developing in Eclipse and I can't see the REAL emulator I start to tun my app.
When I start a single emulator, I actually have two.
The only change I made recently is to install the WIMM emulator (see www.wimm.com). I don't start that one however.
Any clues would be appreciated. Thanks.
It happens to me too sometimes. I do
"adb kill-server"
"adb start-server"
and usually it connects again.
Although I don't know why that happens. I'm very new to android...
Try to running
"/path/to/android-sdk/tools/android update adb"
follow by:
"adb kill-server"
"adb start-server"
This should fix your problem. It's probably due to the recents adb tools changes when you install the WIMM Add-ons.
I had something like this.
ADB watch some port to check if emulators are launched. I had an application using the port 5555.
So type the following command (unix / mac / linux) :
lsof -i -P | grep 5555
It will give you the application and pid that use the port :
uHD-Netwo 320 jva 7u IPv4 0x07b77338 0t0 TCP localhost:5555 (LISTEN)
uHD-Netwo 320 jva 16u IPv4 0x0861b788 0t0 TCP localhost:5555->localhost:55265 (ESTABLISHED)
Then simply kill the app :
kill -9 320
The emulator shouldn't be there anymore.