On Sun, 2007-12-02 at 05:12 -0500, Matt Thompson wrote: > Hi, > > I was wondering if anyone knows anything about the Bluetooth sync > capabilities. I have a 7290 that supports sync to blackberry desktop > with bluetooth. It would be great to have it available in Linux :)
It is, http://sourceforge.net/projects/xmblackberry Okay, maybe not full sync, but backup/restore at least. It uses the original serial protocol. > > After pairing with the BB, running 'sdptool browse' shows the following > serial ports available: > > Service Name: BlackBerry Desktop Service P:0x2053730F R:0x03 V:0x20004 This is the one you need. > Service RecHandle: 0x10002 > Service Class ID List: > UUID 128: 426c6163-6b42-6572-7279-44736b746f70 > "Serial Port" (0x1101) > Protocol Descriptor List: > "L2CAP" (0x0100) > "RFCOMM" (0x0003) > Channel: 3 > Language Base Attr List: > code_ISO639: 0x656e > encoding: 0x6a > base_offset: 0x100 > > Service Name: BlackBerry Bypass Service P:0x2053730F R:0x03 V:0x20003 I haven't figured out what to do with this one yet. It is also available by way of the usb. > Service RecHandle: 0x10003 > Service Class ID List: > UUID 128: 426c6163-6b42-6572-7279-427970617373 > "Serial Port" (0x1101) > Protocol Descriptor List: > "L2CAP" (0x0100) > "RFCOMM" (0x0003) > Channel: 4 > Language Base Attr List: > code_ISO639: 0x656e > encoding: 0x6a > base_offset: 0x100 > > > In my Ubuntu /etc/bluetooth/rfcomm.conf: > > rfcomm1 { > bind yes; > device 00:0F:86:96:C4:0D; > channel 3; > comment "BlackBerry Desktop Service"; > } XmBlackBerry -device /dev/rfcomm1 would start you talking to it. > > rfcomm2 { > bind yes; > device 00:0F:86:96:C4:0D; > channel 4; > comment "BlackBerry Bypass Service"; > } > > > This sets up /dev/rfcomm1 and /dev/rfcomm2 as virtual serial ports to > the BB. > > If I open /dev/rfcomm1, the Blackberry shows 'Connecting to desktop' on > the screen. There is a magic handshake that has to take place to complete the connection. > Opening /dev/rfcomm2 shows that there is an active bluetooth connection. > > I believe the bypass service serial port is used for least-cost routing > to BES. least-cost over bluetooth seems to be supported with BES and > blackberry desktop. > > If the protocol used over the bluetooth connection is similar/the same > as the USB protocol, would it not just be a matter of writing a wrapper > to the Packet API and a bluetooth library? It's a vary layered approach. The higher layers are the same, the device layer is very different. A wrapper would not work very well, you need to replace the low level stuff with a separate "driver". > > Cheers, > Matt Thompson > > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
