On Wed, Oct 2, 2013 at 11:28 AM, Tanu Kaskinen <tanu.kaskinen at linux.intel.com> wrote: > On Tue, 2013-10-01 at 10:43 -0300, Jo?o Paulo Rechi Vita wrote: >> Ack. Same question about testing applies here, and I should have made >> it more generic, actually: Do you have audio devices to be able to >> test these changes? > > Devices aren't a problem (I have two A2DP/HFP headsets and one HFP-only > headset), but I haven't yet installed BlueZ 5. So, these patches have > not been tested. > > What would you recommend as an easy-to-use GUI to replace the Gnome > Bluetooth applet, which will inevitably break if I replace BlueZ 4 with > BlueZ 5? (I don't have the newest Gnome version yet, and I'm not going > to install Gnome from source.) > I don't use any GUI with BlueZ 5 atm. In my tests I use the scripts under the tests/ dir in the bluez repo. There is also bluetoothctl, which is under the client/ repo, that aggregates the functionality of most test scripts altogether. I haven't used it much tho, mostly because I was lazy to look much at it. If you want to use the scripts you should be able to find your device with test-discovery and pair using "./simple-agent <hci> <device_address>". <hci> will most likely be hci0, but you can check what hciconfig lists for you. The device address will be shown as an output of test-discovery. You also should be able to disconnect/reconnect with a paired device using "./test-device connect <device_address>". Last, "./test-device list" will list you all the paired devices. bluetoothctl is an interactive tool (like pacmd), so the help command should get you going :) -- Jo?o Paulo Rechi Vita http://about.me/jprvita
