paulster wrote:
> Okay, so I've got the Bluetooth module loading at bootup, I can do a
> hcitool scan and see my device, I can execute hcitool -i hci0 cc
> 00:11:22:33:44:55 without error.
>
> When I run hcitool con it briefly shows the device connected, but it
> doesn't last.
> hcitool auth 00:11:22:33:44:55 comes back with HCI authentication
> request failed: Input/output error
>
> Before I get into configuring the output device in /etc/asound.conf is
> there a foolproof way to know whether I've got it properly pairing?
> It's difficult to gauge when I don't know what the expected behaviour
> is.
The procedure is scan, connect, pair, trust
The speaker should emit a connected tone when it's connected.
You also may need to edit /etc/bluetooth/audio.conf to include:
Code:
--------------------
[General]
Enable=Source,Sink,Media,Socket
Master=true
SCORouting=PCM
AutoConnect=true
--------------------
You need to install bluez-utils, before you try any connecting, etc.
I found that it was best to remove any unsuccessful attempts - delete
the content of /var/lib/bluetooth
and start again
You can check through my 'guide' for some tips (I apologise that it is
so scrappy - there are errors which I couldn't correct later) -
http://www.raspberrypi.org/forums/viewtopic.php?p=255217#p255217
HOWEVER I found the only way I could get bt working with some devices
was to use the workaround here:
Start `bluez-simple-agent` ( as root ) in one terminal
In another terminal start `hcitool cc 00:13:70:D1:XX:XX && hcitool auth
00:13:70:D1:XX:XX`
In the first window you may be asked for the pin - enter 0000. This
last part is hit'n'miss - sometimes nothing happens. You may see error
messages - ignore.
If it works you should hear the confirmation tone.
At this point issue the audio connect command:
Code:
--------------------
bluez-test-audio connect [address]
--------------------
At this point issue the trust command:
Code:
--------------------
bluez-test-device trusted [address] yes
--------------------
You need to get the device connectng so that you can switch it off then
on again - you should hear the connected beep.
Be prepared to get very frustrated when it doesn't work - just start
again
Touch - Muse M50 EX TPA3123 T-Amp Mini - Acoustics Q10 speakers
Logitech Radio
Logitech UE Smart Radio
Raspberry Pi + Squeezeplug LMS + Squeezelite - Logitech Mini Boombox
speaker (mothballed)
Cubieboard + Debian 7 + LMS 7.8.1 + Squeezelite - Soundwave SW100
bluetooth speaker - Airplay
O2 Joggler + SqpOS + Aune X2 T-amp + Mordaunt Short ms-3.40 speakers -
Airplay
IBOX + Debian 7 + LMS 7.8.1 + Squeezelite - Logitech Mini Boombox
speaker - Soundwave SW100 bluetooth speaker - AirPlay
------------------------------------------------------------------------
castalla's Profile: http://forums.slimdevices.com/member.php?userid=15624
View this thread: http://forums.slimdevices.com/showthread.php?t=101872
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
