bluetooth pet test
I think when installed before, I didn't have enough space in the save file.
Now I get messages:
Code: Select all
# ./bluetooth
+ killall dbus-launch
+ killall bluetoothd
killall: bluetoothd: no process killed
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
Stopping system message bus: dbusStarting system message bus: dbusUnknown group "bluetooth" in message bus configuration file
+ sleep 1
+ mkdir /root/bluetooth-share
+ sleep 1
+ /usr/lib/obexd/obexd --ftp --opp --auto-accept -r /root/bluetooth-share -n
+ bluetoothd -n
bluetoothd[23788]: Bluetooth deamon 4.66
bluetoothd[23788]: Starting SDP server
Failed to connect to socket /tmp/dbus-hfPdyJo47H: Connection refused
obexd[23789]: manager_init failed
bluetoothd[23788]: opening L2CAP socket: Protocol not supported
bluetoothd[23788]: Server initialization failed
bluetoothd[23788]: Starting experimental netlink support
bluetoothd[23788]: Failed to find Bluetooth netlink family
bluetoothd[23788]: Failed to init netlink plugin
bluetoothd[23788]: Failed to open control socket: Protocol not supported (93)
bluetoothd[23788]: Can't init bnep module
bluetoothd[23788]: Failed to init network plugin
bluetoothd[23788]: Unable to start SCO server socket
bluetoothd[23788]: Failed to init audio plugin
bluetoothd[23788]: HCI dev 0 registered
bluetoothd[23788]: accept: Socket operation on non-socket (88)
bluetoothd[23788]: HCI dev 0 up
bluetoothd[23788]: Starting security manager 0
bluetoothd[23788]: Failed to listen on control channel
bluetoothd[23788]: input-server: Operation not permitted (1)
bluetoothd[23788]: Failed to start DUN server: socket(STREAM, RFCOMM): Protocol not supported (93)
bluetoothd[23788]: pnat-server: Input/output error (5)
bluetoothd[23788]: Adapter /org/bluez/23788/hci0 has been enabled
bluetoothd[23788]: Failed to access HAL
# + bluetooth-applet
** Message: adding killswitch idx 0 state 1
** Message: killswitch 0 is 1
** Message: killswitches state 1
** Message: killswitch 0 is 1
** Message: killswitches state 1
#
I tried the two commands as well:
Code: Select all
# hcitool scan
Scanning ...
00:16:20:19:E8:89 K700i
# sdptool browse
Inquiring ...
Failed to connect to SDP server on 00:16:20:19:E8:89: Protocol not supported
#
I also see that L2CAP and RFCOMM is needed.
I don't have those modules in 5X7SMP or in the pet package.
Specially RFCOMM is interesting as it is needed for DUN as far as I understand.
And as a side effect, SeaMonkey is complaining now that the dbus-daemon isn't running now, so no config info can be saved.
So there seems to be a conflict with the daemon started by bluetooth.
I also wonder how I have to pair the PC with the phone.
This is what I have to do in Windows to get the connection working.
From the phone the PC bluetooth is found, but I have to enter the access key. The one I am used to in the phone when powering on isn't accepted.
And I don't see what the access key is in this bluetooth pet.
When trying to do so I get:
Code: Select all
# bluetoothd[23788]: pin_code_request (sba=00:11:67:9E:02:E6, dba=00:16:20:19:E8:89)
process 23788: arguments to dbus_pending_call_set_notify() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 596.
This is normally a bug in some application using the D-Bus library.
bluetoothd[23788]: pin_code_request (sba=00:11:67:9E:02:E6, dba=00:16:20:19:E8:89)
process 23788: arguments to dbus_pending_call_set_notify() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 596.
This is normally a bug in some application using the D-Bus library.
bluetoothd[23788]: pin_code_request (sba=00:11:67:9E:02:E6, dba=00:16:20:19:E8:89)
process 23788: arguments to dbus_pending_call_set_notify() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 596.
This is normally a bug in some application using the D-Bus library.