Am Dienstag 03 April 2007 08:55 schrieb Krzysztof Burghardt: > Hendrik Sattler wrote: > > Any clues? As root it starts. Oh yes, I am in the following groups: > > hendrik dialout cdrom floppy audio video plugdev netdev fuse > > This bug is similar to #387542. Are you sure that it is a bluetooth-alsa > problem and not something more general?
"hcitool cc" does not work as user, so #387542 applies to me, too. Running a2dtp as root actually works as my player (amarok) uses it via the alsa interface and thus the different users do not matter. The device does not support for SDP and the protcol does not require it. Works anyway. The split user has the problem of a non-working remote control of amarok via A2RCP (my headset supports this and so does a2dpd). This can be worked around with dcop options --user or --all-users. BTW: can run two a2dpd instances at the same time? How are they addressed? Use case: two headsets, two (one?) bt dongle, two music players If this is not possible, two users could interfere with each other (or one can block the other). I do not see a problem with running this as root. Since it does not work as user, wouldn't a start script be useful? The .asoundrc snipped could be integrated into a global asoundrc file. Other notes that I couldn't figure out? * Is the required patch in the debian standard kernel? If not, can this be done? How well does it work? With earlier versions (2 years ago) and a mono headset (Logitech) I could hear audio but the reverse direction (micro) was not working (worked with my mobile phone). * Can a2dpd theoretically (I know you cannot test this) manage a SCO connection and a A2DP connection to the same device with one instance? E.g. it should stop A2DP (media player) while doing the SCO stuff (telephony). Is there actually any telefony application for linux that can use it SCO? (skype cannot). If I find one, I could test this. > Also can you check if you have paired with device properly (using PIN) > and if you can use l2ping to check if it respond. The pairing is done with the first audio stream, no second earlier. So starting up a2dtp will not initiate a pairing immediately. > Please check it both with and without root permissions. [...] > Probably. I have only SBC headset (mono aka voice). > So I'm unable to test A2DP profile. Any suggestions welcome! After a while, a2dpd is printing on the console: append_to_ring_buffer: Ring buffer is full Sometimes, there are also short periods of silence. I also experienced those with a hardware-only solution (audio->bt adapter) but not that often. With KDE4, the audio routing choice is supposed to get better, so the ALSA route it not that bad. Writing an ALSA driver that uses the daemon would enable applications that only look for hardware-only devices, though. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
