unable to send files via bluetooth to phone

A lot of phones actually have to be in a "receiving" mode to receive files. Does yours have such a mode possibly? Is this a regression from intrepid or hardy?

This problem occurred towards the end of Hardy and beginning of Intrepid (around the time I reported bug #270077, end of September). Prior to that it worked fine in both early Hardy and Gutsy. The phone is set to 'always allow' connections. When a file is sent to the phone, via bluetooth, the phone normally asks whether I wish to receive a file. This is no longer happening.

This error still occurs in Jaunty kernel 2.6.28-7 64 bit. I've just commented that I can now drag and drop files to the phone, via Nautilus, in bug report 294613, but if I use the 'Send To' method detailed here, I still get the same error as mentioned above.

For sure this is a nautilis-sendto issue.
Kevin, I guess you're using jaunty now, could you test now, I think it should work.
Could you also test using the send-to functionnality in the bluetooth-applet?

Thanks

It's still not working. If I use either the Nautilus Send-To or the Bluetooth Applet Send-To I get the 'org.openobex.Error.Connection.Refused' error. Drag and drop is still fine.
Current installed bluetooth package revisions are
bluetooth 4.30-0ubuntu1 Bluetooth support
bluez 4.30-0ubuntu1 Bluetooth tools and daemons
bluez-alsa 4.30-0ubuntu1 Bluetooth audio support
bluez-cups 4.30-0ubuntu1 Bluetooth printer driver for CUPS
bluez-gnome 1.8-0ubuntu2 Bluetooth utilities for GNOME
bluez-gstreamer 4.30-0ubuntu1 Bluetooth gstreamer support
bluez-utils 4.30-0ubuntu1 Transitional package
I'm using the latest Jaunty Kernel updated and rebooted prior to these tests. The kernel is 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:27:53 UTC 2009 x86_64 GNU/Linux.

Using kernel 2.6.28-11-generic #35-Ubuntu SMP Wed Mar 18 21:55:34 UTC 2009 x86_64 GNU/Linux
This error has now been fixed. If I right-click on the the bluetooth applet and select 'send to device' I receive a file on my K800i phone. If I open Nautilus and select 'Send To' again I can receive a file.
Please close this bug report.

the bug should be sent to bugzilla.gnome.org by somebody having the issue

Sebastien. Does the problem still need to go to Bugzilla as it's fixed in kernel 2.6.28.11 ?
Please confirm and I'll then make a report in Bugzilla.

the previous comments suggested that was a nautilus-sendo bug but if that's fixed closing the bug now

Please re-open this bug as again it no longer works in Jaunty kernel 2.6.28.11 (for some reason). Packages are as follows:
bluetooth 4.32-0ubuntu4
bluez 4.32-0ubuntu4
bluez-alsa 4.32-0ubuntu4
bluez-cups 4.32-0ubuntu4
bluez-gnome 1.8-0ubuntu5
bluez-gstreamer 4.32-0ubuntu4
bluez-utils 4.32-0ubuntu4
Same error as previously reported by me on K800i.

I'm getting exactly the same error, I'm also unable to send via the bluetooth applet. Using :

Kernel : 2.6.28-12 64bit
bluetooth 4.32-0ubuntu4.1
bluez 4.32-0ubuntu4.1
bluez-alsa 4.32-0ubuntu4.1
bluez-cups 4.32-0ubuntu4.1
bluez-gnome 1.8-0ubuntu5
bluez-gstreamer 4.32-0ubuntu4.1
bluez-utils 4.32-0ubuntu4.1

Sending to a HTC with WinMo6.1

Dervish. Have you ever been able to send files to your HTC phone ? HTC phones are very flakey when it comes to sending and receiving files via bluetooth as they don't quite meet all bluetooth standards, (I have an HTC phone myself that refuses to work 100%).

Yes I can send and receive to and from my phone from any other phone without issues, the bluetooth browser works perfectly so I've been using that.

Just to clarify, can you send to/from a PC (using Windows XP, for example) ? Between phones is not a problem, but between a phone and another PC is likely to be (my HTC only works one way, unlike Ericsson,Sony Ericsson, Nokia phones).
Thanks.

I'm sorry but I am using Jauny to try and transfer files to an HTC Blackstone (Touch HD) and it's not working for me. I continue to get the 'org.openobex.Error.Connection.Refused' error.

I have the same problem with a HTC Touch Diamond, very annoying....

i get this error in KDE when using the Send To... option in the right click menu of the KBluetooth4 tray icon
I can receive files and in GNOME i can send and recieve files

It doesn't work in 64-bit Karmic either. My mobile doesn't even notice that sth is trying to send a file to it. While browsing a device I also can't create new files, getting an error:

There was an error creating the directory in obex://[XX:XX:XX:XX:XX:XX]/STH
Operation not supported by backend

Look at bug #451835, they can be connected.

Kevin,

Do you still experience the same problem as reported?
thanks for the answer.

On the PC 'hcitool scan' shows the phone but I'm unable to connect or browse the phone (Connection refused). Phone shows that the connection failed when try to connect to the PC via the phone. I'll see if I can connect with another phone to Jaunty later and get back to you.

Raphael - you'll find that some HTC phones are not true Bluetooth v2.0, 2.1 compatible and so will only connect one way (like my HTC Monet).

On Tue, Mar 23, 2010 at 4:41 PM, KevinM <email address hidden> wrote:
> On the PC 'hcitool scan' shows the phone but I'm unable to connect or
> browse the phone (Connection refused). Phone shows that the connection
> failed when try to connect to the PC via the phone. I'll see if I can
> connect with another phone to Jaunty later and get back to you.
>

Kevin,

Could open a root shell and run the commands hcidump -XVt and then try
to connect.
the logs should show some error (post them here).
Are you confident your phone support obex FTP?

--
Baptiste Mille-Mathias
Les gens heureux ne sont pas pressés

Yes the K800i does support obex FTP and has previously worked fine in 7.10, 8.04 (early Hardy) and at first in early kernel 2.6.28-11 (see above). I've just tried a Motorola phone and get the same problem as previously reported (org.openobex.Error.Connection.Refused).
Output of command on SonyEricsson K800i:
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
2010-03-23 17:13:11.224534 < HCI Command: Periodic Inquiry Mode (0x01|0x0003) plen 9
    max 24 min 16 lap 0x9e8b33 len 8 num 0
2010-03-23 17:13:11.230573 > HCI Event: Command Complete (0x0e) plen 4
    Periodic Inquiry Mode (0x01|0x0003) ncmd 1
    status 0x00
2010-03-23 17:13:12.211487 > HCI Event: Inquiry Result (0x02) plen 15
    bdaddr 00:1E:DC:86:44:2D mode 1 clkoffset 0x0005 class 0x5a0204
2010-03-23 17:13:17.384297 < HCI Command: Exit Periodic Inquiry Mode (0x01|0x0004) plen 0
2010-03-23 17:13:17.394084 > HCI Event: Command Complete (0x0e) plen 4
    Exit Periodic Inquiry Mode (0x01|0x0004) ncmd 1
    status 0x00
2010-03-23 17:13:18.123995 < HCI Command: Create Connection (0x01|0x0005) plen 13
    bdaddr 00:1E:DC:86:44:2D ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5
2010-03-23 17:13:18.131023 > HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
2010-03-23 17:13:18.724981 > HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 41 bdaddr 00:1E:DC:86:44:2D type ACL encrypt 0x00
2010-03-23 17:13:18.725053 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 41
2010-03-23 17:13:18.739960 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 0
2010-03-23 17:13:18.755965 > HCI Event: Max Slots Change (0x1b) plen 3
    handle 41 slots 5
2010-03-23 17:13:18.778970 > HCI Event: Command Status (0x0f) plen 4
    Unknown (0x00|0x0000) status 0x00 ncmd 1
2010-03-23 17:13:18.779019 < HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:1E:DC:86:44:2D mode 2 clkoffset 0x0000
2010-03-23 17:13:18.794958 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2010-03-23 17:13:18.818964 > HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 41
    Features: 0xff 0xe9 0x8d 0xfe 0x9b 0xe9 0x00 0x00
2010-03-23 17:13:18.819012 < ACL data: handle 41 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
2010-03-23 17:13:18.843953 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 00:1E:DC:86:44:2D name 'K800i'
2010-03-23 17:13:18.844955 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41 packets 1
2010-03-23 17:13:18.859955 > ACL data: handle 41 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x0000
2010-03-23 17:13:18.860003 < ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
2010-03-23 17:13:18.865956 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41 packets 1
2010-03-23 17:13:18.886954 > ACL data: handle 41 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 sc...

Closing due to age.
If a similar bug appears in 13.10 please open a new report.