Toralf Lund
2010-Jul-23 09:50 UTC
[CentOS] Sending files from mobile to CentOS via Bluetooth
Has anyone here managed to send files from a mobile phone to a CentOS
system via Bluetooth? I'm trying with a Samsung E1310, using the GNOME
tools, but can't get it to work. I can send files from the Linux box to
this phone using the Nautilus bluetooth plugin
(nautilus-sendto-bluetooth), and have also managed to "pull" some data
I've been trying to send, via "obexftp". If I try to initiate a
transfer
from the phone, however, it will just display a generic "connection
failed" message. If I run gnome-obex-server from the command line while
doing this, I get
$ gnome-obex-server
conn_request: bdaddr <addres of phone>
conn_complete: status 0x00
But that's pretty much it. Any ideas? I'll also include some hcidump
output below... Note that based on a simple web search, it does look
like others have experienced the same thing, but I didn't really get
much out of the information I found in terms of figuring out how to
resolve the problem.
I'm using the latest packages from the CentOS 5 repositories. I also
tried slightly older versions of bluez-utils and blues-libs as report at
Red Hat Bugzilla suggested this might help, but it didn't really.
- Toralf
------------------------------------------------------------------------
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Read Remote Supported Features (0x0b) plen 11
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Command Status (0x0f) plen 4
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
> HCI Event: Max Slots Change (0x1b) plen 3
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
< ACL data: handle 11 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
< ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
> ACL data: handle 11 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 11 flags 0x02 dlen 24
L2CAP(d): cid 0x0040 len 20 [psm 1]
SDP SSA Req: tid 0x1 len 0xf
pat uuid-16 0x1105 (OBEXObjPush)
max 672
aid(s) 0x0004 (ProtocolDescList)
cont 00
< ACL data: handle 11 flags 0x02 dlen 11
L2CAP(d): cid 0x0040 len 7 [psm 1]
SDP Error Rsp: tid 0x1 len 0x2
code 0x3 info none
> HCI Event: Remote Name Req Complete (0x07) plen 255
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 24
L2CAP(d): cid 0x0040 len 20 [psm 1]
SDP SSA Req: tid 0x1 len 0xf
pat uuid-16 0x1105 (OBEXObjPush)
max 672
aid(s) 0x0004 (ProtocolDescList)
cont 00
< ACL data: handle 11 flags 0x02 dlen 11
L2CAP(d): cid 0x0040 len 7 [psm 1]
SDP Error Rsp: tid 0x1 len 0x2
code 0x3 info none
> ACL data: handle 11 flags 0x02 dlen 24
L2CAP(d): cid 0x0040 len 20 [psm 1]
SDP SSA Req: tid 0x1 len 0xf
pat uuid-16 0x1105 (OBEXObjPush)
max 672
aid(s) 0x0004 (ProtocolDescList)
cont 00
< ACL data: handle 11 flags 0x02 dlen 11
L2CAP(d): cid 0x0040 len 7 [psm 1]
SDP Error Rsp: tid 0x1 len 0x2
code 0x3 info none
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
This e-mail, including any attachments and response string, may contain
proprietary information which is confidential and may be legally privileged. It
is for the intended recipient only. If you are not the intended recipient or
transmission error has misdirected this e-mail, please notify the author by
return e-mail and delete this message and any attachment immediately. If you are
not the intended recipient you must not use, disclose, distribute, forward,
copy, print or rely on this e-mail in any way except as permitted by the author.
Olaf Mueller
2010-Jul-23 10:37 UTC
[CentOS] Sending files from mobile to CentOS via Bluetooth
Toralf Lund wrote: Hello.> Has anyone here managed to send files from a mobile phone to a CentOS > system via Bluetooth?Yes, send and receive files by bluetooth, under CentOS 5.5 with a SE T630 phone and the following setup: # rpm -qa | grep blue bluez-gnome-0.8-2.fc7 python-bluez-0.15-1.el5.rf bluez-libs-3.9-1.fc7 bluez-utils-3.9-2.fc7 bluez-libs-devel-3.9-1.fc7 gnome-bluetooth-0.7.0-10.2.el5 gnome-bluetooth-devel-0.7.0-10.2.el5 bluez-hcidump-1.32-1 gnome-bluetooth-libs-0.7.0-10.2.el5 The following programs start at user-login: gnome-obex-server bluetooth-applet> I'm trying with a Samsung E1310, using the GNOME > tools, but can't get it to work.It works for me since replacing some of the original CentOS packages with packages from Fedora Core 7 (fc7). regards Olaf