Difference between revisions of "Transfer files between your Bluetooth device"

From RSWiki
Jump to navigation Jump to search
Line 1: Line 1:
 +
{{AdWords}}
 +
 +
== Bluetooth and Linux quick howto ==
 +
 +
 
This method is using ussp-push, for this your device must support something called OBEX Object push. For this you need to have all the regular bluetooth stuff installed [bluez-utils,etc] and a little utility called [http://www.xmailserver.org/ussp-push.html ussp-push]
 
This method is using ussp-push, for this your device must support something called OBEX Object push. For this you need to have all the regular bluetooth stuff installed [bluez-utils,etc] and a little utility called [http://www.xmailserver.org/ussp-push.html ussp-push]
  
Line 33: Line 38:
  
 
of course you can replace hcid.conf with whatever file you want. the second filename is what it will be received as on the device. I am only using hcid.conf as an example.
 
of course you can replace hcid.conf with whatever file you want. the second filename is what it will be received as on the device. I am only using hcid.conf as an example.
 +
 +
{{AdWords2}}
  
 
[[Category:Linux| ]]
 
[[Category:Linux| ]]

Revision as of 19:00, 15 January 2008

Template:AdWords

Bluetooth and Linux quick howto

This method is using ussp-push, for this your device must support something called OBEX Object push. For this you need to have all the regular bluetooth stuff installed [bluez-utils,etc] and a little utility called ussp-push

Now you need to find the bluetooth address of the device you are trying to send stuff to.

hcitool scan

you should then see a list like this one

       00:12:D1:8C:57:E5       BackBlerry
       00:0E:ED:B0:AF:34       The Brick

now you just need to find what channel the OBEX push service is on. you should get a long list of stuff, but the one you are interested in is pretty obvious

Service Name: OBEX Object Push
Service RecHandle: 0x10001
Service Class ID List:
 "OBEX Object Push" (0x1105)
Protocol Descriptor List:
 "L2CAP" (0x0100)
 "RFCOMM" (0x0003)
   Channel: 9
 "OBEX" (0x0008)
Language Base Attr List:
 code_ISO639: 0x454e
 encoding:    0x6a
 base_offset: 0x100
Profile Descriptor List:
 "OBEX Object Push" (0x1105)
   Version: 0x0100

The good news is you only have to do this once, the address and the channel are pretty much permanent Now for the easy bit.

 ussp-push  00:12:D1:8C:57:E5@9 hcid.conf mcid.conf

of course you can replace hcid.conf with whatever file you want. the second filename is what it will be received as on the device. I am only using hcid.conf as an example.

Template:AdWords2