[Pkg-bluetooth-maintainers] Bug#532098: is silent, but mplayer complains loudly

Harald Dunkel harri at afaics.de
Thu Mar 31 08:38:23 UTC 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry, but some Gnome or Kde applets are no option. Making A2DP depend
upon unrelated and highly complex functionality like Gnome or KDE just
to enter 0000 is just asking for troubles. On the next update some
internal XML crap (please excuse the expression) might get changed, and
its broken again. I saw this happen several times before.

Looking at your example I would like to write in my .asoundrc something
like

pcm.bluetooth {
  type bluetooth
  device 00:0F:59:11:XX:XX
  pin 0000			<<<<<<<
}

pcm.!default {
 type plug
 slave {
   pcm bluetooth
 }
}

That gives you all information needed for pairing: The device and the
pin. 0000 should be the default pin, of course.

This change could help _alot_ to improve A2DP support on Linux.

BTW, I was never asked to enter 0000 on my Belkin A2DP receiver.
It doesn't even have a single key to press. _Thats_ ease of use.


Regards

Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2UPX8ACgkQUTlbRTxpHjfDogCaA08j53INMx4UYdmlX+3AEuld
GKgAoIrvf6t9n3k0Rpk/xcrDepjU5S/0
=xokl
-----END PGP SIGNATURE-----





More information about the Pkg-bluetooth-maintainers mailing list