Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Feb 2008 18:12:01 +1100
From:      Peter Jeremy <peterjeremy@optushome.com.au>
To:        freebsd-ports <freebsd-ports@freebsd.org>
Subject:   Re: obexftp - call for testers
Message-ID:  <20080220071201.GH51095@server.vk2pj.dyndns.org>
In-Reply-To: <20080218041901.GA45835@blaxxtarz.evangelion.free>
References:  <20080215135036.GA6988@blaxxtarz.evangelion.free> <20080216104809.GJ64299@server.vk2pj.dyndns.org> <47B84C42.40603@lissyara.su> <20080218041901.GA45835@blaxxtarz.evangelion.free>

next in thread | previous in thread | raw e-mail | index | archive | help

--dDRMvlgZJXvWKvBx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 18, 2008 at 05:19:01AM +0100, Dierk Sacher wrote:
>(1) BD_ADDR in raw format (it's _not_ resolving literal device names)
>(2) the Channel (by using the -B option)

OK.  This works on my Motorola L6i but it seems that Motorola didn't
bother with the telecom/ nodes or capability support so obexftp can't
do anything that obexapp can't (unfortunately).

turion% obexftp --bluetooth `bthost -b PeterPhone` --channel 9 -v -l picture
Connecting...failed: connect
Still trying to connect
Connecting...done
Receiving "picture"...|<?xml version=3D"1.0" ?>
<!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd">
<folder-listing>
<parent-folder />
<file name=3D"04-02-08_1533.jpg" size=3D"90634" type=3D"image/jpeg" modifie=
d=3D"20080220T180803Z" user-perm=3D"RW" />
</folder-listing>
done
Disconnecting...done
turion%=20

>One final note: my mobiles firmware obviously left the drawing table a
>bit, uhm, early. You may have to reset your bluetooth devices and/or the
>whole mobile (by removing batteries in my case :-() after doing some
>transfers. This is *not* a problem specific to obexftp. Its happening
>with a lot of other peers and usage scenarios too.

I don't see that but usually have to execute commands multiple times for
the phone to acknowledge.

--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.

--dDRMvlgZJXvWKvBx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHu9LB/opHv/APuIcRAv1vAJ9FR7Gg4IO/VttCEUMcDSeCfYP+lACfbA3x
3IO+mafpgZIVbjI7ZQy8i+k=
=PBDc
-----END PGP SIGNATURE-----

--dDRMvlgZJXvWKvBx--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080220071201.GH51095>