Results 1 to 3 of 3

Thread: BlueZ 5.10 Gets OBEX Command Line Client

  1. #1
    Join Date
    Jan 2007
    Posts
    15,130

    Default BlueZ 5.10 Gets OBEX Command Line Client

    Phoronix: BlueZ 5.10 Gets OBEX Command Line Client

    A new release of BlueZ is out that projects a command-line client for its Bluetooth OBject EXchange support...

    http://www.phoronix.com/vr.php?view=MTQ4NjQ

  2. #2
    Join Date
    May 2010
    Posts
    126

    Default automatic hciconfig up

    Since the topic is Bluez 5, does anyone have a good solution for autostarting paired devices when they're available that works with bluez 5? I use to use blueman but it's not compatible.

    Preferably the solution wouldn't be graphical or tied to a particular desktop - the system is a media center that runs openbox but autostarts into xbmc. I have a bluetooth keyboard that I was using with it.

    Edit:
    System is ArchLinux, so I have udev and systemd at my disposal.

  3. #3
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,911

    Default

    Quote Originally Posted by TheCycoONE View Post
    Since the topic is Bluez 5, does anyone have a good solution for autostarting paired devices when they're available that works with bluez 5? I use to use blueman but it's not compatible.

    Preferably the solution wouldn't be graphical or tied to a particular desktop - the system is a media center that runs openbox but autostarts into xbmc. I have a bluetooth keyboard that I was using with it.

    Edit:
    System is ArchLinux, so I have udev and systemd at my disposal.
    Not sure what the format would be but you could write a 'oneshot' systemd unit that depends upon bluetooth.

    example:

    Code:
    [Unit]
    Description=Set %i interface in promiscuous mode
    After=network.target
    
    [Service]
    Type=oneshot
    ExecStart=/usr/bin/ip link set dev %i promisc on
    RemainAfterExit=yes
    
    [Install]
    WantedBy=multi-user.targe
    Change after to be bluetooth.target if there is one, otherwise maybe set it to be after bluetooth.service? Keep the type to be one shot, ExecStart would be whatever the command is to pair the devices via command line. Keep the install section. RemainAfterExit i dont know if it would be yes or no for this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •