* [Bluez-devel] bluetooth headset not working
@ 2007-10-18 17:45 Kevin Fenzi
2007-10-18 17:59 ` Jim Carter
0 siblings, 1 reply; 11+ messages in thread
From: Kevin Fenzi @ 2007-10-18 17:45 UTC (permalink / raw)
To: Bluez-devel
[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]
Greetings.
I recently had a chance to look at the new bluez-utils and the setup
for headsets. Very much nicer than any of the old methods. :)
However, I can't seem to get my headset working with twinkle (or any
other phone app).
I have setup my ~/.asoundrc.
I can play audio to my headset via mplayer or aplay fine.
When I try and set twinkle to use the ALSA bluetooth device it seems
like it opens the headset, and then it spits out:
ALSA lib pcm_bluetooth.c:417:(bluetooth_hsp_hw_params) Protocol not
available (92)
ALSA lib pcm_bluetooth.c:417:(bluetooth_hsp_hw_params) Protocol not
available (92)
Then it goes to 100% cpu and unresponsive.
ALSA bug? or bluez-utils? Anyone seen this before or have
a work around?
twinkle-1.1-3.fc8.x86_64
alsa-lib-1.0.15-0.2.rc2.fc8.x86_64
bluez-utils-3.20-2.fc8.x86_64
I talked with the twinkle developers, and they say it's not an issue
with twinkle. See:
http://tech.groups.yahoo.com/group/twinklephone/message/1879?l=1
Happy to provide info or debugging... CC me for faster response.
kevin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-devel] bluetooth headset not working
2007-10-18 17:45 [Bluez-devel] bluetooth headset not working Kevin Fenzi
@ 2007-10-18 17:59 ` Jim Carter
2007-10-18 18:48 ` Kevin Fenzi
0 siblings, 1 reply; 11+ messages in thread
From: Jim Carter @ 2007-10-18 17:59 UTC (permalink / raw)
To: BlueZ development; +Cc: kevin
On Thu, 18 Oct 2007, Kevin Fenzi wrote:
> I have setup my ~/.asoundrc.
> I can play audio to my headset via mplayer or aplay fine.
> When I try and set twinkle to use the ALSA bluetooth device it seems
> like it opens the headset, and then it spits out:
>
> ALSA lib pcm_bluetooth.c:417:(bluetooth_hsp_hw_params) Protocol not
> available (92)
aplay or mplayer are talking to the ALSA device that uses the A2DP profile.
The phone app needs to use the device with the HFP profile. It looks like
you got that set up in .asoundrc since a plausible subroutine is reporting
the error. Next question: does your headset do HFP, or is it purely a
music headset (A2DP)? Some headsets, including the Motorola HT820, will
auto-switch, but I think not every music headset will do so. Hope this
helps!
James F. Carter Voice 310 825 2897 FAX 310 206 6673
UCLA-Mathnet; 6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555
Email: jimc@math.ucla.edu http://www.math.ucla.edu/~jimc (q.v. for PGP key)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-devel] bluetooth headset not working
2007-10-18 17:59 ` Jim Carter
@ 2007-10-18 18:48 ` Kevin Fenzi
2007-10-19 16:03 ` Jim Carter
0 siblings, 1 reply; 11+ messages in thread
From: Kevin Fenzi @ 2007-10-18 18:48 UTC (permalink / raw)
To: Jim Carter; +Cc: BlueZ development
[-- Attachment #1.1: Type: text/plain, Size: 1180 bytes --]
On Thu, 18 Oct 2007 10:59:50 -0700 (PDT)
Jim Carter <jimc@math.ucla.edu> wrote:
> On Thu, 18 Oct 2007, Kevin Fenzi wrote:
>
> > I have setup my ~/.asoundrc.
> > I can play audio to my headset via mplayer or aplay fine.
> > When I try and set twinkle to use the ALSA bluetooth device it seems
> > like it opens the headset, and then it spits out:
> >
> > ALSA lib pcm_bluetooth.c:417:(bluetooth_hsp_hw_params) Protocol not
> > available (92)
>
> aplay or mplayer are talking to the ALSA device that uses the A2DP
> profile. The phone app needs to use the device with the HFP profile.
Humm... do all headsets do A2DP? I thought mine did not.
> It looks like you got that set up in .asoundrc since a plausible
> subroutine is reporting the error. Next question: does your headset
> do HFP, or is it purely a music headset (A2DP)? Some headsets,
> including the Motorola HT820, will auto-switch, but I think not every
> music headset will do so. Hope this helps!
I am using a jabra BT 250v headset.
It's not a music headset.
I have a few more headsets I can dig up here to test with if you think
it's something with the jabra.
kevin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-devel] bluetooth headset not working
2007-10-18 18:48 ` Kevin Fenzi
@ 2007-10-19 16:03 ` Jim Carter
2007-10-19 16:42 ` Johan Hedberg
2007-10-19 19:23 ` Kevin Fenzi
0 siblings, 2 replies; 11+ messages in thread
From: Jim Carter @ 2007-10-19 16:03 UTC (permalink / raw)
To: Kevin Fenzi; +Cc: BlueZ development
On Thu, 18 Oct 2007, Kevin Fenzi wrote:
> On Thu, 18 Oct 2007 10:59:50 -0700 (PDT)
> Jim Carter <jimc@math.ucla.edu> wrote:
> > aplay or mplayer are talking to the ALSA device that uses the A2DP
> > profile. The phone app needs to use the device with the HFP profile.
>
> Humm... do all headsets do A2DP? I thought mine did not.
The ones with 2 earpieces and a mass of about 100 grams invariably (?) do
A2DP which transmits stereo at 44100 Hz or 48000 Hz, compressed with the
SBC codec. The single-ear ones with a mass of about 20 grams invariably
(?) do HSP/HFP, monaural at 8000 Hz, I think uncompressed. That would be
your Jabra BT 250v. Some but not all of the music headsets can switch
protocols and have call control buttons for HFP; these are advertised as
"works with Skype".
So the Jabra is capable of doing the HSP protocol, and when the message
says the protocol is "not available", the problem is likely not in the
headset. Not likely that the headset is broken or has buggy firmware, but
just for paranoia, it would be a good data point if the same message were
seen with a different headset.
I've seen a similar message when I didn't have bluetoothd-service-audio
configured to autostart and forgot to start it manually. Do you have the
corresponding protocol/profile daemon running? I don't have my laptop
handy to look up the name of this daemon but I think it's
bluetoothd-service-sco. This is in bluez-utils-3.19 (3.20 is latest;
probably came in at 3.16.)
Unfortunately that's about the limit of my expertise, since I haven't
messed with the HSP/HFP feature of the Motorola HT-820 that I have.
James F. Carter Voice 310 825 2897 FAX 310 206 6673
UCLA-Mathnet; 6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555
Email: jimc@math.ucla.edu http://www.math.ucla.edu/~jimc (q.v. for PGP key)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-devel] bluetooth headset not working
2007-10-19 16:03 ` Jim Carter
@ 2007-10-19 16:42 ` Johan Hedberg
2007-10-19 19:23 ` Kevin Fenzi
1 sibling, 0 replies; 11+ messages in thread
From: Johan Hedberg @ 2007-10-19 16:42 UTC (permalink / raw)
To: BlueZ development
On Oct 19, 2007, at 19:03, Jim Carter wrote:
> I've seen a similar message when I didn't have bluetoothd-service-
> audio
> configured to autostart and forgot to start it manually. Do you
> have the
> corresponding protocol/profile daemon running? I don't have my laptop
> handy to look up the name of this daemon but I think it's
> bluetoothd-service-sco.
Actually bluetoothd-service-audio takes care of both A2DP and HSP.
Unless you specified explicitly the profile to use in your .asoundrc
(e.g. "profile a2dp") the selection process goes as such that A2DP is
used if available and otherwise HSP.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-devel] bluetooth headset not working
2007-10-19 16:03 ` Jim Carter
2007-10-19 16:42 ` Johan Hedberg
@ 2007-10-19 19:23 ` Kevin Fenzi
1 sibling, 0 replies; 11+ messages in thread
From: Kevin Fenzi @ 2007-10-19 19:23 UTC (permalink / raw)
To: Jim Carter; +Cc: BlueZ development
[-- Attachment #1.1: Type: text/plain, Size: 2126 bytes --]
On Fri, 19 Oct 2007 09:03:43 -0700 (PDT)
Jim Carter <jimc@math.ucla.edu> wrote:
> On Thu, 18 Oct 2007, Kevin Fenzi wrote:
>
> > On Thu, 18 Oct 2007 10:59:50 -0700 (PDT)
> > Jim Carter <jimc@math.ucla.edu> wrote:
> > > aplay or mplayer are talking to the ALSA device that uses the A2DP
> > > profile. The phone app needs to use the device with the HFP
> > > profile.
> >
> > Humm... do all headsets do A2DP? I thought mine did not.
>
> The ones with 2 earpieces and a mass of about 100 grams invariably
> (?) do A2DP which transmits stereo at 44100 Hz or 48000 Hz,
> compressed with the SBC codec. The single-ear ones with a mass of
> about 20 grams invariably (?) do HSP/HFP, monaural at 8000 Hz, I
> think uncompressed. That would be your Jabra BT 250v. Some but not
> all of the music headsets can switch protocols and have call control
> buttons for HFP; these are advertised as "works with Skype".
Right. Thats my understanding as well.
> So the Jabra is capable of doing the HSP protocol, and when the
> message says the protocol is "not available", the problem is likely
> not in the headset. Not likely that the headset is broken or has
> buggy firmware, but just for paranoia, it would be a good data point
> if the same message were seen with a different headset.
I can duplicate it with another headset here later...
> I've seen a similar message when I didn't have
> bluetoothd-service-audio configured to autostart and forgot to start
> it manually. Do you have the corresponding protocol/profile daemon
> running? I don't have my laptop handy to look up the name of this
> daemon but I think it's bluetoothd-service-sco. This is in
> bluez-utils-3.19 (3.20 is latest; probably came in at 3.16.)
bluetoothd-service-audio?
Yeah, seems to run fine, but makes no difference in the output. ;(
> Unfortunately that's about the limit of my expertise, since I haven't
> messed with the HSP/HFP feature of the Motorola HT-820 that I have.
Bummer. Thanks for helping out!
If anyone else has any ideas I would love to get this working...
kevin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Bluez-devel] bluetooth headset not working
@ 2007-10-20 2:10 KyoYin
2007-10-20 12:45 ` Johan Hedberg
2007-10-23 7:13 ` Johan Hedberg
0 siblings, 2 replies; 11+ messages in thread
From: KyoYin @ 2007-10-20 2:10 UTC (permalink / raw)
To: BlueZ development; +Cc: BlueZ development, bluez-devel-bounces
hi johan
>Actually bluetoothd-service-audio takes care of both A2DP and HSP.
>Unless you specified explicitly the profile to use in your .asoundrc
>(e.g. "profile a2dp") the selection process goes as such that A2DP is
>used if available and otherwise HSP.
Do u mean the bluetoothd-service-audio will read .asoundrc?
could you tell me how to write .asoundrc if i want to use a2dp and
hsp.now my .asoundrc is:
pcm.headset {
type bluetooth
}
ctl.headset {
type bluetooth
}
pcm.bluetooth {
type bluetooth
device 00:0D:3C:EB:53:F0
}
when i use "aplay -D bluetooth -f S16_LE /1.wav ",i will get the following
error.
audio[837]: Accepted new client connection on unix socket (fd=7)
audio[837]: Package PKT_TYPE_CFG_REQ:0
audio[837]: avdtp_ref(0x37ef8): ref=2
audio[837]: a2dp_source_request_stream: selected SEP 0x376b8
audio[837]: avdtp_ref(0x37ef8): ref=3
hcid[825]: link_key_request (sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0)
hcid[825]: pin_code_request (sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0)
hcid[825]: link_key_notify (sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0)
audio[837]: AVDTP: connected signaling channel to 00:0D:3C:EB:53:F0
audio[837]: session_cb
audio[837]: DISCOVER request succeeded
audio[837]: seid 1 type 1 media 0 in use 0
audio[837]: seid 2 type 1 media 0 in use 0
audio[837]: session_cb
audio[837]: GET_CAPABILITIES request succeeded
audio[837]: seid 1 type 1 media 0
hcid[825]: link_key_request (sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0)
audio[837]: session_cb
audio[837]: GET_CAPABILITIES request succeeded
audio[837]: seid 2 type 1 media 0
audio[837]: Discovery complete
audio[837]: avdtp_set_configuration(0x37ef8): int_seid=1, acp_seid=1
audio[837]: session_cb
audio[837]: SET_CONFIGURATION request succeeded
audio[837]: SBC Source: Set_Configuration_Cfm
audio[837]: avdtp_ref(0x37ef8): ref=4
audio[837]: stream state changed: IDLE -> CONFIGURED
audio[837]: session_cb
audio[837]: OPEN request succeeded
audio[837]: stream state changed: CONFIGURED -> OPEN
audio[837]: AVDTP: connected transport channel to 00:0D:3C:EB:53:F0
audio[837]: SBC Source: Open_Cfm
audio[837]: session_cb
audio[837]: START request succAlignment trap: bluetoothd-serv (837)
PC=0x0001ce50 Instr=0xe1c320b0 Address=0xbe871a89 FSR 0x813
eeded
audio[837]: SBC Source: Start_Cfm
audio[837]: SBC Source SEP 0x376b8 locked
hcid[825]: Service owner exited: :1.1
hcid[825]: Removing record with handle 0x10000
hcid[825]: Service classes 0x08
hcid[825]: Removing record with handle 0x10001
hcid[825]: Service classes 0x00
aplay: main:546: audio open error: Input/output error
hcid[825]: Audio service (audio) was killed by signal 7
/ $ hcid[825]: link_key_request (sba=00:80:E1:00:AB:BA,
dba=00:0D:3C:EB:53:F0)
hcid[825]: link_key_request (sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0)
i do not know the reason,and i have used alsa-lib-1.0.15/alsa-utils-1.0.15
/dbus-1.02/dbus-glib-0.74/glib-2.12.13/blueZ-lib-3.20/blueZ-utils-3.20
if i lack some lib?or my configure is wrong?
thanks
kyo
|---------+----------------------------------------->
| | Johan Hedberg |
| | <johan.hedberg@gmail.com> |
| | Sent by: |
| | bluez-devel-bounces@lists.sour|
| | ceforge.net |
| | |
| | |
| | 2007-10-20 00:42 |
| | Please respond to BlueZ |
| | development |
| | |
|---------+----------------------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
| |
| To: BlueZ development <bluez-devel@lists.sourceforge.net> |
| cc: |
| Subject: Re: [Bluez-devel] bluetooth headset not working |
>-------------------------------------------------------------------------------------------------------------------------------|
On Oct 19, 2007, at 19:03, Jim Carter wrote:
> I've seen a similar message when I didn't have bluetoothd-service-
> audio
> configured to autostart and forgot to start it manually. Do you
> have the
> corresponding protocol/profile daemon running? I don't have my laptop
> handy to look up the name of this daemon but I think it's
> bluetoothd-service-sco.
Actually bluetoothd-service-audio takes care of both A2DP and HSP.
Unless you specified explicitly the profile to use in your .asoundrc
(e.g. "profile a2dp") the selection process goes as such that A2DP is
used if available and otherwise HSP.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Bluez-devel] bluetooth headset not working
2007-10-20 2:10 KyoYin
@ 2007-10-20 12:45 ` Johan Hedberg
2007-10-23 7:13 ` Johan Hedberg
1 sibling, 0 replies; 11+ messages in thread
From: Johan Hedberg @ 2007-10-20 12:45 UTC (permalink / raw)
To: BlueZ development
On Oct 20, 2007, at 5:10, KyoYin@mxic.com.cn wrote:
> Do u mean the bluetoothd-service-audio will read .asoundrc?
No. The values in .asoundrc are given to the bluetooth alsa plugin
which then passes them over to the audio service using a unix socket.
> could you tell me how to write .asoundrc if i want to use
> a2dp and
> hsp.now my .asoundrc is:
>
> pcm.headset {
> type bluetooth
> }
>
> ctl.headset {
> type bluetooth
> }
>
> pcm.bluetooth {
> type bluetooth
> device 00:0D:3C:EB:53:F0
> }
If you want to have one alsa device for A2DP and another for HSP it
might be a good idea to explicitly state the profile you want to use
for each device. You do this by providing a line such as "profile
a2dp" in addition to the device and type lines. I just checked the
code and the plugin will map "hifi" and "a2dp" to A2DP and "voice"
and "hfp" to HSP (it's actually a bug that it doesn't recognize "hsp").
> when i use "aplay -D bluetooth -f S16_LE /1.wav ",i will get the
> following
> error.
<snip>
> audio[837]: START request succAlignment trap: bluetoothd-serv (837)
> PC=0x0001ce50 Instr=0xe1c320b0 Address=0xbe871a89 FSR 0x813
> eeded
> audio[837]: SBC Source: Start_Cfm
> audio[837]: SBC Source SEP 0x376b8 locked
> hcid[825]: Service owner exited: :1.1
Looks like the audio service crashed. What architecture are you
running this on and what compiler did you use? It would be good if
you could try to reproduce this by running bluetoothd-audio-service
through valgrind or gdb and get a proper backtrace of the crash. To
do this remove the /etc/bluetooth/audio.service file (hcid should
detect this and unregister the service but if it doesn't you need to
restart hcid), and run "/usr/lib/bluetooth/bluetoothd-service-audio -
s" either through gdb or valgrind.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Bluez-devel] bluetooth headset not working
2007-10-20 2:10 KyoYin
2007-10-20 12:45 ` Johan Hedberg
@ 2007-10-23 7:13 ` Johan Hedberg
2007-10-23 7:53 ` KyoYin
1 sibling, 1 reply; 11+ messages in thread
From: Johan Hedberg @ 2007-10-23 7:13 UTC (permalink / raw)
To: BlueZ development
(resending since the first try seems to have gotten stuck somewhere
between gmail and sourceforge)
On Oct 20, 2007, at 5:10, KyoYin@mxic.com.cn wrote:
> Do u mean the bluetoothd-service-audio will read .asoundrc?
No. The values in .asoundrc are given to the bluetooth alsa plugin
which then passes them over to the audio service using a unix socket.
> could you tell me how to write .asoundrc if i want to use
> a2dp and
> hsp.now my .asoundrc is:
>
> pcm.headset {
> type bluetooth
> }
>
> ctl.headset {
> type bluetooth
> }
>
> pcm.bluetooth {
> type bluetooth
> device 00:0D:3C:EB:53:F0
> }
If you want to have one alsa device for A2DP and another for HSP it
might be a good idea to explicitly state the profile you want to use
for each device. You do this by providing a line such as "profile
a2dp" in addition to the device and type lines. I just checked the
code and the plugin will map "hifi" and "a2dp" to A2DP and "voice"
and "hfp" to HSP (it's actually a bug that it doesn't recognize "hsp").
> when i use "aplay -D bluetooth -f S16_LE /1.wav ",i will get the
> following
> error.
<snip>
> audio[837]: START request succAlignment trap: bluetoothd-serv (837)
> PC=0x0001ce50 Instr=0xe1c320b0 Address=0xbe871a89 FSR 0x813
> eeded
> audio[837]: SBC Source: Start_Cfm
> audio[837]: SBC Source SEP 0x376b8 locked
> hcid[825]: Service owner exited: :1.1
Looks like the audio service crashed. What architecture are you
running this on and what compiler did you use? It would be good if
you could try to reproduce this by running bluetoothd-audio-service
through valgrind or gdb and get a proper backtrace of the crash. To
do this remove the /etc/bluetooth/audio.service file (hcid should
detect this and unregister the service but if it doesn't you need to
restart hcid), and run "/usr/lib/bluetooth/bluetoothd-service-audio -
s" either through gdb or valgrind.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Bluez-devel] bluetooth headset not working
2007-10-23 7:13 ` Johan Hedberg
@ 2007-10-23 7:53 ` KyoYin
2007-10-23 10:02 ` Johan Hedberg
0 siblings, 1 reply; 11+ messages in thread
From: KyoYin @ 2007-10-23 7:53 UTC (permalink / raw)
To: BlueZ development
[-- Attachment #1.1: Type: text/plain, Size: 3436 bytes --]
hi Johan
the crash of bluetoothd-service-audio has been resolved now.i think it
is a bug.in avdtp_stream_get_transport(),the mtu pointer will be
unaccessible.
In a2dp_setup_complete(),avdtp_stream_get_transport() wants to pass the
address of cfg->pkt_len.but the cfg is a packed struct.so the normal
pointer of uint16(pointer mtu in avdtp_stream_get_transport is this type)
should not be used here.of cause my cpu is arm.
thanks
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kyo Yin(Jian)
MXIC Technology Co.,Ltd.
NO.5, Xinhai street, Suzhou Industrial Park
Tel: 86-512-87650888-3463
E-Mail: kyoyin@mxic.com.cn
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Johan Hedberg <johan.hedberg@nokia.com>
Sent by: bluez-devel-bounces@lists.sourceforge.net
2007-10-23 00:22
Please respond to
BlueZ development <bluez-devel@lists.sourceforge.net>
To
BlueZ development <bluez-devel@lists.sourceforge.net>
cc
Subject
Re: [Bluez-devel] bluetooth headset not working
(resending since the first try seems to have gotten stuck somewhere
between gmail and sourceforge)
On Oct 20, 2007, at 5:10, KyoYin@mxic.com.cn wrote:
> Do u mean the bluetoothd-service-audio will read .asoundrc?
No. The values in .asoundrc are given to the bluetooth alsa plugin
which then passes them over to the audio service using a unix socket.
> could you tell me how to write .asoundrc if i want to use
> a2dp and
> hsp.now my .asoundrc is:
>
> pcm.headset {
> type bluetooth
> }
>
> ctl.headset {
> type bluetooth
> }
>
> pcm.bluetooth {
> type bluetooth
> device 00:0D:3C:EB:53:F0
> }
If you want to have one alsa device for A2DP and another for HSP it
might be a good idea to explicitly state the profile you want to use
for each device. You do this by providing a line such as "profile
a2dp" in addition to the device and type lines. I just checked the
code and the plugin will map "hifi" and "a2dp" to A2DP and "voice"
and "hfp" to HSP (it's actually a bug that it doesn't recognize "hsp").
> when i use "aplay -D bluetooth -f S16_LE /1.wav ",i will get the
> following
> error.
<snip>
> audio[837]: START request succAlignment trap: bluetoothd-serv (837)
> PC=0x0001ce50 Instr=0xe1c320b0 Address=0xbe871a89 FSR 0x813
> eeded
> audio[837]: SBC Source: Start_Cfm
> audio[837]: SBC Source SEP 0x376b8 locked
> hcid[825]: Service owner exited: :1.1
Looks like the audio service crashed. What architecture are you
running this on and what compiler did you use? It would be good if
you could try to reproduce this by running bluetoothd-audio-service
through valgrind or gdb and get a proper backtrace of the crash. To
do this remove the /etc/bluetooth/audio.service file (hcid should
detect this and unregister the service but if it doesn't you need to
restart hcid), and run "/usr/lib/bluetooth/bluetoothd-service-audio -
s" either through gdb or valgrind.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
[-- Attachment #1.2: Type: text/html, Size: 5204 bytes --]
[-- Attachment #2: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Bluez-devel] bluetooth headset not working
2007-10-23 7:53 ` KyoYin
@ 2007-10-23 10:02 ` Johan Hedberg
0 siblings, 0 replies; 11+ messages in thread
From: Johan Hedberg @ 2007-10-23 10:02 UTC (permalink / raw)
To: BlueZ development
On Oct 23, 2007, at 10:53, KyoYin@mxic.com.cn wrote:
> the crash of bluetoothd-service-audio has been resolved now.i
> think it is a bug.in avdtp_stream_get_transport(),the mtu pointer
> will be unaccessible.
> In a2dp_setup_complete(),avdtp_stream_get_transport() wants to pass
> the address of cfg->pkt_len.but the cfg is a packed struct.so the
> normal pointer of uint16(pointer mtu in avdtp_stream_get_transport
> is this type) should not be used here.of cause my cpu is arm.
Thanks for this info. It should now be fixed in the CVS.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2007-10-23 10:02 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-18 17:45 [Bluez-devel] bluetooth headset not working Kevin Fenzi
2007-10-18 17:59 ` Jim Carter
2007-10-18 18:48 ` Kevin Fenzi
2007-10-19 16:03 ` Jim Carter
2007-10-19 16:42 ` Johan Hedberg
2007-10-19 19:23 ` Kevin Fenzi
-- strict thread matches above, loose matches on Subject: below --
2007-10-20 2:10 KyoYin
2007-10-20 12:45 ` Johan Hedberg
2007-10-23 7:13 ` Johan Hedberg
2007-10-23 7:53 ` KyoYin
2007-10-23 10:02 ` Johan Hedberg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox