I've managed local hotsync via bluetooth

  • Previous message: CVS problem
  • Next message: I've managed local hotsync via bluetooth
  • Paul LeoNerd Evans leonerd at leonerd.org.uk
    Wed Nov 10 21:37:54 EST 2004

     

    Hi all...
    
    According to all your documentation, you say that local hotsync by
    bluetooth isn't possible, only LAN-based sync.
    
    Well, I've managed to get it to work. It's somewhat non-trivial currently,
    but I'm hoping to write a patch for pilot-link to do a lot of the messy
    work.
    
    The basic process is the following:
    
    1. On startup or some other appropriate time, register SP (serial port)
    with SDP:
      # sdptool add SP
    
    2. Start bluetooth listening on channel 1:
      $ rfcomm listen 0 1
    
    Now press the "HotSync" button on the palm, set to a local sync over
    bluetooth to the previously-discovered and paired computer.
    
    At this stage, rfcomm will indicate that it has an incoming connection.
    
    3. Now run the pilot-link program of your choice, pointed at /dev/rfcomm0:
      $ pilot-xfer -p /dev/rfcomm0 -l
    
    Hey presto, there should now ensue the list of databases, transfered via
    bluetooth. :)
    
    I've had a look at the source for rfcomm and it's actually really quite
    simple. I'm planning to add support to pilot link so it will perform that
    first listen step automatically.
    
    Any thoughts on this before I begin..? I don't want to start only to be
    told someone else has already done it, or anything else like that. :)
    
    -- 
    Paul "LeoNerd" Evans
    
    leonerd at leonerd.org.uk
    ICQ# 4135350       |  Registered Linux# 179460
    http://www.leonerd.org.uk/
    
    

     

     

    More information about the pilot-link-general mailing list