Hi, It seems like Steven managed to get his headset working routing the sound over HCI. The FR has this high tech sound chip that is directly connected to the GSM module and hence can (theoretically at least) keep the CPU off while you're on a phone call. This mode also supports full duplex (which AFAIK is unsupported using HCI routing) which means you can use both the mic and speakers of the headset for a phone call. I'm not sure if anyone has been able to send sound to the headset from the CPU on a Freerunner using the Wolfson chip directly. The way the FR is supposed to work though is the control channel of the headset needs to be routed through HCI and the sound should be through the wolfson, else it will end up eating out the battery. I've not been able to get my Jawbone working with either way, it doesn't have A2DP support... It works with the same version of Bluez using my laptop and other devices... The most I've gotten out of the FR is that the connect and disconnect happens properly and it's acked by the headset - HCI packets get sent using the method above, but no sound on the FR. Same for the wolfson way. I've tried setting all the alsa params possible... Maybe someone can shed some more light on this.
On Mon, Jan 19, 2009 at 6:41 AM, Steven King <sfkin...@yahoo.com> wrote: > On Sunday, January 18, 2009 1:50:26 Lothar Behrens wrote: >> Hi, >> >> I like to know if someone has used this bluetooth stereo headset and >> how the steps are to got it running. >> Also I like to know what distributions are actually having a fully >> functional bluetooth. > > I have 2008.12 paired with my bt3030. I had to install bluez-audio and > bluez-util, restart bluetoothd and then run passkey-agent and then with the > bt3030 in pairing mode, follow the steps from > http://wiki.bluez.org/wiki/HOWTO/AudioDevices to connect to the bt3030. A > trivial attempt at a2dp seemed to work correctly. Now if I can get the > freerunner to do HSP with the bt3030 I'll be a happy camper... > > my /etc/asound.conf looks like: > # default dmix configuration > > pcm.!default { > type plug > slave.pcm "dmix" > } > > ctl.mixer0 { > type hw > card 0 > } > > pcm.bluetooth { > type bluetooth > device "XX:XX:XX:XX:XX:XX" > profile "auto" > } > > the sequence was something like: > > ~# opkg install bluez-audio blue-util > > ~# /etc/init.d/bluetooth stop > > ~# /etc/init.d/bluetooth start > > ~# passkey-agent --default 0000 & > > ~# dbus-send --system --print-reply --dest=org.bluez /org/bluez \ > org.bluez.Manager.ActivateService string:audio > > ~# dbus-send --system --type=method_call --print-reply \ > --dest="org.bluez" /org/bluez/audio org.bluez.audio.Manager.CreateDevice \ > string:XX:XX:XX:XX:XX:XX > > where XX:XX:XX:XX;XX is the baddr of the bt3030. Then > > ~# dbus-send --system --type=method_call --print-reply \ > --dest="org.bluez" "/org/bluez/audio/device0" org.bluez.audio.Sink.Connect > > at that point I was able to do: > > ~# aplay -D bluetooth phone.wav > > and get what sounded like a2dp on the bt3030. > > > _______________________________________________ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community