Okay then.
I have desided to use Bluez4 for bluetooth streaming, cause bluez4 does support ALSA, which the new Bluez5 doesent.
I tried and succeded compiling bluez5, and pulseaudio with the bluez5 enabled. -Problem is, that pulseaudio uses way to much cpu power.
-anyway i never succeded streaming audio on bluez5.
So status now is :
Compiled and created bluez4-a.tcz (the -a is just for my own sake)
patched the .tcz file with the following : <allow send_type="method_call"/>, according to this :
http://thethingsystem.com/dev/Bootstrapping-the-Raspberry-Pi.html <policy user="root">
<allow own="org.bluez"/>
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent"/>
<allow send_interface="org.bluez.HandsfreeAgent"/>
<allow send_interface="org.bluez.MediaEndpoint"/>
<allow send_interface="org.bluez.MediaPlayer"/>
<allow send_interface="org.bluez.Watcher"/>
<allow send_interface="org.bluez.ThermometerWatcher"/>
<allow send_type="method_call"/>
</policy>
I can start bluetoothd, and a bluetoothd --version gives me following :
tc@PlayBox:~/bluez-4.101/test$ bluetoothd --version
4.101
Top returns :
2231 1 root S 12740 2.8 0 44.8 /home/tc/squeezelite/squeezelite-armv6hf -z -a 80 4 -n PlayBox -m xx xx xx xx xx 5E -s 192.168.1.133
10441 7331 tc R 3124 0.7 0 1.2 top
2298 1921 root S 4832 1.0 0 0.4 sshd: tc@pts/0
7 2 root SW 0 0.0 0 0.2 [rcu_preempt]
2288 1 root S 17228 3.8 0 0.0 /usr/local/bin/shairport -d -a PlayBox -b 95
1921 1 root S 4748 1.0 0 0.0 /usr/local/sbin/sshd
7943 1 root S 4488 1.0 0 0.0 bluetoothd
7331 7326 tc S 3124 0.7 0 0.0 sh
2301 2298 tc S 3124 0.7 0 0.0 -sh
1870 1 tc S 3124 0.7 0 0.0 -sh
7326 7296 root S 3124 0.7 0 0.0 sh
7283 2301 root S 3124 0.7 0 0.0 sh
7290 7288 root S 3124 0.7 0 0.0 sh
7296 7290 tc S 3124 0.7 0 0.0 sh
7288 7283 tc S 3124 0.7 0 0.0 sh
1874 1871 root S 3016 0.6 0 0.0 /sbin/getty -L ttyAMA0 115200 vt100
1 0 root S 3012 0.6 0 0.0 init
1871 1 root S 3012 0.6 0 0.0 {startserialtty} /bin/sh /usr/sbin/startserialtty
2247 1 root S 3012 0.6 0 0.0 /sbin/udhcpc -b -i eth0 -x hostname PlayBox -p /var/run/udhcpc.eth0.pid
7410 1 tc S 2608 0.5 0 0.0 /usr/local/bin/dbus-daemon --system
So next step is to have the bluez4 scripts running (python)
A bluetooth scan seems to work
tc@PlayBox:~$ sudo hciconfig hci0 up
tc@PlayBox:~$ sudo hcitool scan
Scanning ...
xx:xx:xx:xx:xx:1D iPhone
tc@PlayBox:~$ sudo hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1A:7D:DA:71:15 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:4051 acl:0 sco:0 events:84 errors:0
TX bytes:1105 acl:0 sco:0 commands:68 errors:0
Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'PlayBox-0'
Class: 0x400100
Service Classes: Telephony
Device Class: Computer, Uncategorized
HCI Version: 4.0 (0x6) Revision: 0x22bb
LMP Version: 4.0 (0x6) Subversion: 0x22bb
Manufacturer: Cambridge Silicon Radio (10)
But for pairing i need the tools inside the bluez4 package.
This is here i am fighting the python.
tc@PlayBox:~/bluez-4.101/test$ ls
agent.c hciemu.1 lmptest.c service-did.xml simple-service test-input test-serial-proxy
attest.c hciemu.c monitor-bluetooth service-ftp.xml test-adapter test-manager test-service
avtest.c hsmicro mpris-player.c service-opp.xml test-attrib test-nap test-telephony
bdaddr.8 hsplay rctest.1 service-record.dtd test-audio test-network test-textfile.c
bdaddr.c hstest.c rctest.c service-spp.xml test-device test-oob test-thermometer
btiotest.c ipctest.c sap-client simple-agent test-discovery test-proximity uuidtest.c
dbusdef.py l2test.c scotest.c simple-endpoint test-health test-sap-server
gaptest.c list-devices sdptest.c simple-player test-health-sink test-serial
So when trying to start e.g simple-agent i got :
tc@PlayBox:~/bluez-4.101/test$ python simple-agent
Traceback (most recent call last):
File "simple-agent", line 5, in <module>
from gi.repository import GObject
File "/usr/local/lib/python2.7/site-packages/gi/__init__.py", line 27, in <module>
from ._gi import _API
ImportError: libgirepository-1.0.so.1: cannot open shared object file: No such file or directory
It's hard to get going
Rgds; and goodmorning Jesper