Hi there.. I've got it paired and workable. I can heard an audio from my BT earpiece without the "test-audio" action. BTW, there is also needed to append some more code in the file .asoundrc or the /etc/alsa/default.conf for bluetooth, then I can test audio playback from BT by command below. #gst-launch audiotestsrc ! alsasink device=bluetooth
More question, can I route bluez audio data to pulseaudio sound server for audio mixing? I am fail to test audio playback by "pulsesink" element. BRs Maceo 2011/2/23 Johan Hedberg <[email protected]> > Hi, > > On Wed, Feb 23, 2011, Zhao, Forrest wrote: > > 1 for pairing with remote BT device, "hcitool cc remote-mac-address" > > is what you need. Actually you can find more hcitool usage by "hcitool > > --help" > > No, hcitool isn't needed for pairing. hcitool cc is just a testing > command that should only be used by developers (and even as a developer > I've almost never needed it). If there's no GUI available for pairing > you can use the simple-agent script from BlueZ to pair: > > simple-agent hci0 <remote address> > > > 2 for audio test, there was a bluez wiki page to describe the audio > > usage (e.g. > > http://www.xmarks.com/site/wiki.bluez.org/wiki/HOWTO/AudioDevices). > > However it seems that wiki.bluez.org does not work anymore. You may > > ask around in bluez mailing list. > > wiki.bluez.org only contained (when it existed) information for BlueZ > 3.x so I doubt it'd be useful. There's a test-audio script that comes > with BlueZ that can be used to connect to audio devices after first > pairing with them: > > test-audio connect <remote address> > > Johan > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines >
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
