Bug#435643: not working due to lack of btsco
Package: bluetooth-alsa Version: 0.5cvs20070714-1 Severity: normal Hi, Last year I needed to connect my Logitech HS01-V14 headset with my laptop. Back then I had to compile the necessary software myself, so when I eventually found the package in the repo I was very pleased. Unfortunately I'm unable to get the headset working with it. From what I read I understood that, since that's a mono SCO headset, I need btsco to get it working. I noticed that you're the maintainer of the Ubuntu one as well and that there's a bluez-btsco package, unfortunately by someone else. Could you please make it available for Debian or, since it's only btsco that's in the package, simply merge them together? I also found a front-end to it written in python, if you're interested that is. http://www.stgraber.org/category/gbtsco Cheers, Raf -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-1-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluetooth-alsa depends on: ii libasound2 1.0.14a-2ALSA library ii libbluetooth2 3.12-1 Library to use the BlueZ Linux Blu ii libc6 2.6-5GNU C Library: Shared libraries ii libdbus-1-3 1.1.1-3 simple interprocess messaging syst ii libdbus-glib-1-20.74-1 simple interprocess messaging syst ii libglib2.0-02.12.13-1The GLib library of C routines ii libsbc0 0.0cvs20070327-1 Subband codec (SBC) library bluetooth-alsa recommends no packages. -- no debconf information -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435643: not working due to lack of btsco
severity 435643 wishlist tags 435643 wontfix thanks 2007/8/2, Rafal Czlonka [EMAIL PROTECTED]: Unfortunately I'm unable to get the headset working with it. From what I read I understood that, since that's a mono SCO headset, I need btsco to get it working. This is simply not true. Where you read it? I noticed that you're the maintainer of the Ubuntu one No. I'm not. Moreover I had never been. AFAIK Ubuntu package was automatically build from Debian sources without any human interaction. as well and that there's a bluez-btsco package, unfortunately by someone else. Bluez-btsco is old and deprecated one. Have you read http://bluetooth-alsa.sourceforge.net/build.html (at the end) ? Quoted: If for some reason you need to try the old driver, instead of checking out plugz above, check out btsco and build it the same way. Do we need old driver? New works perfectly for me. What steps you follow to configure it? Could you please make it available for Debian or, since it's only btsco that's in the package, simply merge them together? Yes, but why? What is the point? I also found a front-end to it written in python, if you're interested that is. http://www.stgraber.org/category/gbtsco Can it work or can it be ported to use new driver? Regards, -- Krzysztof Burghardt [EMAIL PROTECTED] http://www.burghardt.pl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435643: not working due to lack of btsco
Krzysztof Burghardt wrote: This is simply not true. Where you read it? /usr/share/doc/bluetooth-alsa/build.html [...] Configure A2DP Driver This driver allows audio to be sent from an alsa client to a stereo bluetooth headset. [...] Configure SCO (aka mono, aka voice) Driver This driver will let you do 2-way audio to and from a mono headset. [...] By this analogy, it somehow implies it. Apparently I wasn't the only one who thought the same. If it's not true, then the docs should be more specific. No. I'm not. Moreover I had never been. AFAIK Ubuntu package was automatically build from Debian sources without any human interaction. OK, I wasn't aware of that. Bluez-btsco is old and deprecated one. Have you read http://bluetooth-alsa.sourceforge.net/build.html (at the end) ? Yes I did. Below I've written a list why I thought it is a good idea. Quoted: If for some reason you need to try the old driver, instead of checking out plugz above, check out btsco and build it the same way. Do we need old driver? New works perfectly for me. What steps you follow to configure it? Steps from html docs in /usr/share/doc/bluetooth-alsa/ Could you please make it available for Debian or, since it's only btsco that's in the package, simply merge them together? Yes, but why? What is the point? As I've written before: 1. It was btsco I used the first time, and it worked. 2. Because the above analogy I thought my device is the old SCO one. 3. Almost every HOWTO/tutorial online on configuring bluetooth headsets has a part with btsco. 4. Because btsco IS used in Ubuntu. Actually I don't care about Ubuntu itself but since it is more luser-friendly, I thought ... 5. Because not so long ago a new version of the graphical front-end for btsco has been released (releasing graphical front-ends for deprecated software seems a bit odd to me). That's why I thought it was a good idea. After your reply it seems it's not, thank you for clarifying that. Can it work or can it be ported to use new driver? Apparently it does work, although one needs to run it as root (IMO it should use some kind of sudo calling mechanism automatically). It only works with btsco but it seems that he's planning to include A2DP support if future releases. It's just a wrapper to btsco, so without knowing the difference between the drivers I can't say whether it is possible, and if so, how hard/easy is it going to be - I'm not a programmer. OK, once again thank you for clarifying it, sorry for the nasty bug report. I guess I'll have to take a deeper look into it. Cheers, -- Raf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435643: not working due to lack of btsco
2007/8/2, Rafal Czlonka [EMAIL PROTECTED]: Krzysztof Burghardt wrote: This is simply not true. Where you read it? /usr/share/doc/bluetooth-alsa/build.html And where it mention that you need to use btsco? By this analogy, it somehow implies it. Apparently I wasn't the only one who thought the same. If it's not true, then the docs should be more specific. They are. Have you looked into README.Debian? Steps from html docs in /usr/share/doc/bluetooth-alsa/ Try also sample configuration files from this directory. Yes, but why? What is the point? As I've written before: 1. It was btsco I used the first time, and it worked. Me too. But it have better replacement now. 2. Because the above analogy I thought my device is the old SCO one. There is no two versions of devices. There is only older and newer driver. 3. Almost every HOWTO/tutorial online on configuring bluetooth headsets has a part with btsco. Most of them are outdated. Like everything else you can found using typical search engine. 4. Because btsco IS used in Ubuntu. Actually I don't care about Ubuntu itself but since it is more luser-friendly, I thought ... Maybe that's the point. OK, once again thank you for clarifying it, sorry for the nasty bug report. I guess I'll have to take a deeper look into it. I'll investigate this too. Thanks for your time, and let me known if you need any help with bluetooth-alsa, -- Krzysztof Burghardt [EMAIL PROTECTED] http://www.burghardt.pl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435643: closed by Krzysztof Burghardt [EMAIL PROTECTED] (Re: Bug#435643: not working due to lack of btsco)
I'm closing bug #435643. It seems that you didn't configure yout BT headset.
I did follow the instructions from the docs, but I might have missed
something.
All you need is to append
/usr/share/doc/bluetooth-alsa/sample.asoundrc to your ~/.asoundrc and
set default address to point to HW address of your device.
Did that the first time, confusion with the naming of the audio device
came from sample.a2dpd:
Address of your alsa output (default : plughw:0,0)
I was looking for the wrong one ;^)
E.g.:
@args.BDADDR {
type string
default 00:12:34:56:78:90 # Put your HS address here
}
I did all that before, but I admit that was looking for an extra card to
show up in the system rather than play with the settings. Only thing I
gained so far is the ability to change the volume of the headset, but
nothing else. Before I was able to change it both in the system and on
the headset and changing one affected the other, now changing it on the
headset doesn't have any effect on the system (can't hear anything but
the volume bar simply doesn't move). I can choose it as mixer in xmms or
beep but that prevents the software from playing at all. I tried to
record something and that's what I got:
; rec -t alsa headset file.wav
rec stio: Failed reading `headset': cannot open audio device
; headsetd -n
headsetd[6063]: Bluetooth headset daemon version 0.5
headsetd[6063]: Configuration phase ended: target bdaddr is 00:0D:44:02:F1:1F,
timeout is 6000 ms
headsetd[6063]: Changing state: Idle--Paging
headsetd[6063]: unable to connect L2CAP socket to headset: Permission denied
headsetd[6063]: Changing state: Paging--Idle
I've attached the output of strace.
Than fire up headsetd (with -n to see it's messages).
Finally set your application input/output device to headset. It is
bi-directional.
This is easiest way to get it work. Obviously you have to pair your HS
with Bluetooth HCI (Bluetooth dongle) before. Hardware address of
device can be obtained using hcitool or sdptool.
As I've written before, I had done it over half a year ago and it
worked which meant that I DO know all that.
It it does not work for you do not hesitate to reopen this bug.
I don't think I'll do it only because it doesn't work for me or after
spending couple of hour I still can't get my bluetooth headset to work.
Cheers,
--
Raf
execve(/usr/bin/headsetd, [headsetd, -n], [/* 26 vars */]) = 0
brk(0) = 0x10017000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x3001f000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=210345, ...}) = 0
mmap(NULL, 210345, PROT_READ, MAP_PRIVATE, 3, 0) = 0x3003
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libbluetooth.so.2, O_RDONLY) = 3
read(3, \177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\0b@..., 512) = 512
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x3002
fstat64(3, {st_mode=S_IFREG|0644, st_size=95816, ...}) = 0
mmap(0xffc8000, 160184, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xffc8000
mprotect(0xffde000, 65536, PROT_NONE) = 0
mmap(0xffee000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x16000) = 0xffee000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\1\346..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1413584, ...}) = 0
mmap(0xfe4d000, 1483224, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0)
= 0xfe4d000
mprotect(0xffa, 65536, PROT_NONE) = 0
mmap(0xffb, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x153000) = 0xffb
mmap(0xffb5000, 8664, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xffb5000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x30021000
mprotect(0xffb, 4096, PROT_READ)= 0
mprotect(0x3002e000, 4096, PROT_READ) = 0
munmap(0x3003, 210345) = 0
umask(077) = 022
socket(PF_FILE, SOCK_DGRAM, 0) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
connect(3, {sa_family=AF_FILE, path=/dev/log}, 110) = -1 EPROTOTYPE (Protocol
wrong type for socket)
close(3)= 0
socket(PF_FILE, SOCK_STREAM, 0) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
connect(3, {sa_family=AF_FILE, path=/dev/log}, 110) = 0
brk(0) = 0x10017000
brk(0x10038000) = 0x10038000
time(NULL)
