rebooting Palm Treo 650 bluetooth + ftp
edgecase
Ubuntu Karmic "Browse..." of device, or with $ obexftp -X
It seems the specs only allow x-obex/capability for USB connection,
not
Bluetooth.
The below fixes it for me.
$ diff -uN obex-data-server-0.4.4/src/ods-session.c obex-data-
server-0.4.4.work/src
--- obex-data-server-0.4.4/src/ods-session.c 2009-01-28
17:43:06.000000000 -0500
+++ obex-data-server-0.4.4.work/src/ods-session.c 2009-12-05
22:15:45.866027263 -0500
@@ -1541,9 +1541,9 @@
{
GError *error = NULL;
- if (session->priv->service != ODS_SERVICE_FTP) {
+ if ((session->priv->service != ODS_SERVICE_FTP) || (session-
>priv->usbintfnum < 1)) {
g_set_error (&error, ODS_ERROR,
ODS_ERROR_NOT_SUPPORTED,
- "Function not
supported by selected profile");
+ "Function not
supported by selected profile or not USB");
dbus_g_method_return_error (context, error);
g_clear_error (&error);
return FALSE;
Tadas Dailyda
transports). Your fix implies that you are using USB connection but not
FTP profile and it is unusual. Could you be more specific about how you
use obex-data-server.
Regards,
Tadas Dailyda
>
> You received this message because you are subscribed to the Google Groups "obex-data-server developers" group.
> To post to this group, send email to ods-...@googlegroups.com.
> To unsubscribe from this group, send email to ods-devel+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ods-devel?hl=en.
>
>
>
Jeremy Jackson
> specs allow x-obex/capability for FTP profile (both Bluetooth and USB
> transports). Your fix implies that you are using USB connection but not
> FTP profile and it is unusual. Could you be more specific about how you
> use obex-data-server.
the Treo, I can browse files on the ROM or the SD memory card.
Originally it would show the top level directory and immediately the
Treo would reboot. A few seconds later the window would close when the
bluetooth connection was detected as dropped.
With the patch I can browse, copy files to/from the Treo, etc.
Jeremy Jackson
Coplanar Networks
(519)489-4903
http://www.coplanar.net
je...@coplanar.net
Jeremy Jackson
the same thing I found:
http://www.gsmhacks.com/forums/bluetooth/14173-maximum-file-size.html
"In another article, you said you can't retrieve the OBEX Capability
Object(it is also written in the following). The OBEX Capability
Object is the object that has the MIME type of "x-obex/capability",
you mean? If so, I think it is not used for Bletooth OBEX, differently
from IrOBEX.
It is unnecessary to have the OBEX Capability Object for Bluetooth
OBEX services(OPP, FTP, Sync), because they have the Service Record to
expose its own capabilities instead of the OBEX Capability Object. If
you want to get the OBEX capability of a peer device, you are supposed
to retrieve the Service Record using SDP(Service Discovery Protocol)
and analyze it."
On Tue, 2009-12-15 at 20:34 +0200, Tadas Dailyda wrote:
> specs allow x-obex/capability for FTP profile (both Bluetooth and USB
> transports). Your fix implies that you are using USB connection but not
> FTP profile and it is unusual. Could you be more specific about how you
> use obex-data-server.
>
> Regards,
> Tadas Dailyda
Tadas Dailyda
Bluetooth OBEX. Although some capability information can be exported
through SDP record, virtually no device/bluetooth implementation uses it
while OBEX Capability object is available in all cases.
Jeremy Jackson
> This is completely wrong. OBEX Capability object is used for USB and
> Bluetooth OBEX. Although some capability information can be exported
> through SDP record, virtually no device/bluetooth implementation uses it
> while OBEX Capability object is available in all cases.
Is it possible that older OBEX spec didn't include x-capability? That
combined with poor handling of unknown commands by Palm OS (total device
reboot, eek!) is the problem then. As a workaround, perhaps the x-obex
command could be omitted for older obex protocol devices (any way to
detect this?) or for Palm models.
>
> On 2009.12.18 18:07, Jeremy Jackson wrote:
> > I can't locate the USB OBEX spec anymore, but here's a post describing
> > the same thing I found:
> >
> > http://www.gsmhacks.com/forums/bluetooth/14173-maximum-file-size.html
> >
> > "In another article, you said you can't retrieve the OBEX Capability
> > Object(it is also written in the following). The OBEX Capability
> > Object is the object that has the MIME type of "x-obex/capability",
> > you mean? If so, I think it is not used for Bletooth OBEX, differently
> > from IrOBEX.
> >
> > It is unnecessary to have the OBEX Capability Object for Bluetooth
> > OBEX services(OPP, FTP, Sync), because they have the Service Record to
> > expose its own capabilities instead of the OBEX Capability Object. If
> > you want to get the OBEX capability of a peer device, you are supposed
> > to retrieve the Service Record using SDP(Service Discovery Protocol)
> > and analyze it."
> >
> > On Tue, 2009-12-15 at 20:34 +0200, Tadas Dailyda wrote:
> >
> >> specs allow x-obex/capability for FTP profile (both Bluetooth and USB
> >> transports). Your fix implies that you are using USB connection but not
> >> FTP profile and it is unusual. Could you be more specific about how you
> >> use obex-data-server.
> >>
> >> Regards,
> >> Tadas Dailyda
> >>
> >
> >
>
> --
>
> You received this message because you are subscribed to the Google Groups "obex-data-server developers" group.
> To post to this group, send email to ods-...@googlegroups.com.
> To unsubscribe from this group, send email to ods-devel+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ods-devel?hl=en.
>
>
Tadas Dailyda
specification (from IrDA) and it is supported on rather old devices.
Even if your device doesn't support Capability object it should just
return NOT_IMPLEMENTED obex response. There are no special commands
involved in requesting/getting capability object so devices which don't
support it should work just fine. In your case I would guess that you
are dealing with some nasty bug in Palm software.