Open faceless2 opened 8 years ago
The daemon binds to port TCP port 5000, maybe you have something running on that port?
I do indeed. Can this be changed?
The next release will add this as a command line option. Right now I have my hands full of Android development so it might take a while :(
Well I suppose it is a beta! No problem. I look forward to a few more options, a bit more API documentation, "daemon" being renamed to "flicd", and maybe even stuff like service announcement with "avahi" to save you having to hardcode the port in the client :-)
I will leave this issue open for the edification of others.
I have compiled and installed bluez 5.37 on a Raspberry Pi and I am running "src/bluetoothd -nEd" to start it. Then in another window I run "./daemon -l -f test.sqlite3" (beta 3 build). Both run as root. The output from the "daemon" command is:
The output from "bluetoothd" in the other window
In a third window I run "flic" and then type "startScan", then press a button either briefly, or for eight seconds - nothing. I get no further output from bluetoothd or daemon from this point.
There is one USB BT LE adapter plugged in and it's up - output of "hciconfig -a"
and if I run "hcitool lescan" I can see what I presume are my four buttons.
I have tried both "armv6l" and "armv7l" versions, and now I am at a loss how to proceed further. Which socket is daemon trying to bind to?