obexftp - call for testers

[Dierk Sacher]

Hello,

thank you for your feedback.

For doing obex over bluetooth, obexftp needs both the

(1) BD_ADDR in raw format (it's _not_ resolving literal device names)
(2) the Channel (by using the -B option)

So, on my K750i, which has  I do something like this (I will use long
options for better understanding):

# get the capability list:
obexftp --bluetooth `bthost -b k750ieva` --channel 6 --capability

Channel 6 is OBEX File Transfer on that phone. IrMC (8 for me) will also
do. You won't be succesful doing this on OBEX Object Push.

If you need to find out the proper channel for your mobile, do something
like

  sdpcontrol -a k750ieva Browse

The whole point of using obexftp over obexapp is (for me), that obexapp
is not able to retrieve all the telecom/ nodes, which won't show up in
filebrowsing and return an error if you try to traverse the path level
by level.
Thatswhy you have to specify the path as a whole in 'get' command
blindly
to successfully retrieve them. This is AFAIK only a restriction of some
(including obviously all my) mobile phones.

So this is where the -S (--nopath) parameter comes handy:


obexftp --bluetooth `bthost -b k750ieva` --channel 6 --nopath \
  --uuid SYNCH --get telecom/devinfo.txt

(You may also try telecom/pb.vcf or telecom/cal.vcs and *PLEASE* backup
your contacts first! It's perfectly possible to bust your databases so
all your valuable contacts go down the drain and I won't be the one to
be put in charge for that.)

As you see, I also need to specify the SYNCH (IRMC will also do). Please
look up the manpage, cause my understanding of this rather limited (in
other words: I'm just using it).

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.

Gruss
Dierk


Zitiere Alex Keda vom Sun, Feb 17, 2008 at 06:01:22PM +0300:
> Peter Jeremy ?????:
> >On Fri, Feb 15, 2008 at 02:50:36PM +0100, Dierk Sacher wrote:
> >  
> >>This is a 'works for me' port. I've only been able to test it with
> >>6.2-RELEASE on i386 with only one mobile over bluetooth. I did not test
> >>anything else (usb, IR ...).
> >>    
> >
> >I wouldn't mind having obexftp to talk to my phone but unfortunately
> >this port doesn't work for me on 6.3-PRERELEASE/amd64 over bluetooth,
> >though that could be just that I'm not driving it correctly:
> >
> >turion# obexftp -b PeterPhone -v -x
> >Scanning for PeterPhone ...
> >Browsing PeterPhone ...
> >Connecting...failed: connect
> >Still trying to connect
> >Connecting...failed: connect
> >Still trying to connect
> >Connecting...failed: connect
> >Still trying to connect
> >turion# 
> >
> >And hcidump shows no data so I suspect it's not even trying BlueTooth.
> >ktrace shows that it's not searching /etc/bluetooth/hosts but directly
> >specifying the BD_ADDR has no improvement and the connect() is returning
> >EINVAL.
> >  
> With - nokia-6085 - obexapp-1.4.8 work correct.
> But this port:
> 
> ussr$ obexftp --bluetooth nokia-6085 -x
> Scanning for nokia-6085 ...
> Browsing nokia-6085 ...
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> 
> ussr$ obexftp --bluetooth siemens-sl56 -x
> Scanning for siemens-sl56 ...
> Browsing siemens-sl56 ...
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> 
> ussr$ obexftp --bluetooth siemens-sl56 -X
> Scanning for siemens-sl56 ...
> Browsing siemens-sl56 ...
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> 
> ussr$ obexftp --bluetooth nokia-6085 -X
> Scanning for nokia-6085 ...
> Browsing nokia-6085 ...
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> 
> ussr$ uname -a
> FreeBSD ussr.lissyara.int.otradno.ru 6.3-RELEASE FreeBSD 6.3-RELEASE #0: 
> Sun Jan 20 09:47:57 MSK 2008     
> lissyara at ussr.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console  
> i386
> 
> ussr$ obexftp --bluetooth siemens-sl56 -p 
> /usr/home/lissyara/Desktop/nokia_freebsd.txt
> Scanning for siemens-sl56 ...
> Browsing siemens-sl56 ...
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> Connecting...failed: connect
> Still trying to connect
> 
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"

-- 
|----+----|----+----|----+----|----+----|----+----|----+----|----+----|--<
 GPG Fingerprint: D14C 12BB 37A6 6745 7F4F  F420 9E59 D79E A492 2A96
 GPG KeyID      : A4922A96  
+------------------------------------------------------------------------+
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20080218/0958f4b9/attachment.pgp