Date: Wed, 20 Feb 2008 01:32:19 +0300 From: Alex Keda <admin@lissyara.su> To: freebsd-ports@freebsd.org Subject: [Fwd: Re: obexftp - call for testers] Message-ID: <47BB58F3.7070300@lissyara.su>
next in thread | raw e-mail | index | archive | help
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@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@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >> > > ================= nokia =============== ussr# obexftp --bluetooth `bthost -b nokia-6085` --channel 10 --capability Connecting...done Receiving "(null)"...|<?xml version="1.0" ?> <!DOCTYPE Capability SYSTEM "obex-capability.dtd"> <Capability Version="1.0"> <General> <Manufacturer>Nokia</Manufacturer> <Model>RM-198</Model> <SN>358630018080756</SN> <SW Version="V 05.03" Date="20070809T120000"/> <HW Version="1402"/> <Language>ru</Language> <Memory> <MemType>DEV</MemType> <!-- DEV memory --> <Free>4168192</Free> <Used>4202496</Used> </Memory> <Memory> <MemType>MMC</MemType> <!-- MMC memory --> <Free>820772864</Free> <Used>209059840</Used> </Memory> </General> <Inbox> <Object> <Type>text/x-vCard</Type> <Name-Ext>vcf</Name-Ext> </Object> <Object> <Type>text/x-vCalendar</Type> <Name-Ext>vcs</Name-Ext> </Object> </Inbox> <Service> <Name>Folder-Browsing</Name> <UUID>F9EC7BC4-953c-11d2-984E-525400DC9E09</UUID> <Version>1.0</Version> <Object> <Type>x-obex/folder-listing</Type> </Object> <Access> <Protocol>IrDA</Protocol> <Target>F9EC7BC4-953c-11d2-984E-525400DC9E09</Target> </Access> <Ext> <XNam>Images</XNam> <XVal>Folder=Π€ΠΎΡΠΎ\</XVal> <XVal>MemType=DEV</XVal> </Ext> <Ext> <XNam>Videos</XNam> <XVal>Folder=ΠΠΈΠ΄Π΅ΠΎ\</XVal> <XVal>MemType=DEV</XVal> </Ext> <Ext> <XNam>Music</XNam> <XVal>Folder=ΠΡΠ·ΡΠΊΠ°\</XVal> <XVal>MemType=DEV</XVal> </Ext> <Ext> <XNam>Graphics</XNam> <XVal>Folder=ΠΡΠ°ΡΠΈΠΊΠ°\</XVal> <XVal>MemType=DEV</XVal> </Ext> <Ext> <XNam>Tones</XNam> <XVal>Folder=Π‘ΠΈΠ³Π½Π°Π»Ρ\</XVal> <XVal>MemType=DEV</XVal> </Ext> <Ext> <XNam>Recordings</XNam> <XVal>Folder=ΠΠ°ΠΏΠΈΡΠΈ\</XVal> <XVal>MemType=DEV</XVal> </Ext> <Ext> <XNam>Applications</XNam> <XVal>Folder=Π ΠΎΠ»Π»Π΅ΠΊΡΠΈΡ\</XVal> <XVal>MemType=DEV</XVal> </Ext> <Ext> <XNam>Games</XNam> <XVal>Folder=ΠΠ³ΡΡ\</XVal> <XVal>MemType=DEV</XVal> </Ext> <Ext> <XNam>MMC</XNam> <XVal>Folder=Victoriya\</XVal> <XVal>MemType=MMC</XVal> </Ext> </Service> <Service> <Name>Infolog</Name> <Object> <Type>x-irmc/info.log</Type> <Name-Ext>log</Name-Ext> </Object> </Service> <Service> <Name>SyncML</Name> <UUID>SYNCML-SYNC</UUID> <Version>1.1</Version> <Object> <Type>application/vnd.syncml+wbxml</Type> </Object> </Service> </Capability> done Disconnecting...done ussr# ================ end nokia ===================== for siemens-sl56 i not find channel number ussr# sdpcontrol -a siemens-sl56 Browse Could not execute command "Browse". Host is down ussr# sdpcontrol -a nokia-6085 Browse Record Handle: 0x0001003c Service Class ID List: Dial-Up Networking (0x1103) Generic Networking (0x1201) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Bluetooth Profile Descriptor List: Dial-Up Networking (0x1103) ver. 1.0 Record Handle: 0x0001003d Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 15 Record Handle: 0x0001003e Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 3 Record Handle: 0x0001003f Service Class ID List: Handsfree Audio Gateway (0x111f) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 13 Bluetooth Profile Descriptor List: Handsfree (0x111e) ver. 1.5 Record Handle: 0x00010040 Service Class ID List: Headset Audio Gateway (0x1112) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 12 Bluetooth Profile Descriptor List: Headset (0x1108) ver. 1.0 Record Handle: 0x00010046 Service Class ID List: Network Access Point (0x1116) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 15 BNEP (0x000f) Protocol specific parameter #1: u/int/uuid16 256 Protocol specific parameter #2: 0x09 0x86 0xdd 0x09 0x08 0x06 Bluetooth Profile Descriptor List: Network Access Point (0x1116) ver. 1.0 Record Handle: 0x00010048 Service Class ID List: OBEX Object Push (0x1105) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 9 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX Object Push (0x1105) ver. 1.0 Record Handle: 0x00010049 Service Class ID List: OBEX File Transfer (0x1106) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 10 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX File Transfer (0x1106) ver. 1.0 Record Handle: 0x0001004b Service Class ID List: 0x00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 11 OBEX (0x0008) Record Handle: 0x0001004c Service Class ID List: Audio Source (0x110a) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 25 AVDTP (0x0019) Protocol specific parameter #1: u/int/uuid16 256 Bluetooth Profile Descriptor List: Advanced Audio Distribution (0x110d) ver. 1.0 Record Handle: 0x0001004d Service Class ID List: A/V Remote Control Target (0x110c) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 23 AVCTP (0x0017) Protocol specific parameter #1: u/int/uuid16 256 Bluetooth Profile Descriptor List: A/V Remote Control (0x110e) ver. 1.0 Record Handle: 0x0001004e Service Class ID List: A/V Remote Control (0x110e) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 23 AVCTP (0x0017) Protocol specific parameter #1: u/int/uuid16 256 Bluetooth Profile Descriptor List: A/V Remote Control (0x110e) ver. 1.0 Record Handle: 0x0001004f Service Class ID List: SIM Access (0x112d) Generic Telephony (0x1204) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 4 Bluetooth Profile Descriptor List: SIM Access (0x112d) ver. 1.1 ussr# =========== any additional commands?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47BB58F3.7070300>