[PROBLEM] Issue with Blutooth in 4.1

[badbat75]

Hi @badbat75,

I extracted the Bluetooth recipe from your custom Builder at https://github.com/badbat75/rpi_moode_build

Am I correct in understanding that this bluetooth build resolved your connection issues?

Code:

# Remove current bluez installation
sudo apt-get -y remove bluez libbluetooth-dev libbluetooth3

# Compile bluez
wget http://www.kernel.org/pub/linux/bluetooth/bluez-5.49.tar.xz
#cp ./rel-stretch/other/bluetooth/bluez-5.49.tar.xz ./
tar xvf bluez-5.49.tar.xz
cd bluez-5.49
./configure \
   --prefix=/usr \
   --libdir=/usr/lib/arm-linux-gnueabihf \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --enable-library \
   --enable-manpages \
   --enable-deprecated \
   --disable-cups \
   --disable-hid \
   --disable-hog \
   --disable-network \
   --disable-obex
make
sudo make install
cd ~
rm -rf ./bluez-5.49*

# Install pi bluetooth
git clone https://github.com/RPi-Distro/pi-bluetooth
sudo cp pi-bluetooth/usr/bin/btuart /usr/bin/
sudo cp pi-bluetooth/debian/pi-bluetooth.hciuart.service /etc/systemd/system/hciuart.service
sudo systemctl daemon-reload
rm -rf pi-bluetooth

# Compile bluez-alsa
cd /tmp
git clone -b v1.2.0 --single-branch https://github.com/Arkq/bluez-alsa.git
cd bluez-alsa
autoreconf --install
mkdir build
cd build
../configure --disable-hcitop --with-alsaplugindir=/usr/lib/arm-linux-gnueabihf/alsa-lib
make
sudo make install
cd ~
rm -rf /tmp/bluez-alsa

# Services are started by moOde Worker so lets disable them here
sudo systemctl daemon-reload
sudo systemctl disable bluetooth.service
sudo systemctl disable hciuart.service

# Finish up
sudo mkdir -p /var/run/bluealsa
sudo sync

-Tim

Yes, if you don't want to change your build environment created by the official moode builder, the only thing I made to solve the problem is to specify the tag of the bluezalsa repository (-b 1.2.0). All the other things are little tuning of what is already working, I mean I tested everything with the recipe you attached to the moode package.
Those are my little changes in the build procedures:

• First of all, I like to have a clean environment, so I removed the bluez and all related libraries from raspbian, then I built the bluez disabling all the modules not needed (the disable-obex is not working really, because the configure script leaves indeed the build and the installation of the obexd server and all related tools). I want to test in the next days if the enable-thread configuration parameter is really needed and if there are performance and RAM benefits. (In the official raspbian build the threads are enabled)
  
• Unfortunately the removal of the bluez packages remove also the pi-bluetooth (specific for bluetooth device integrated in the rPi3) package because dependant, so the need to get the sources and install like others (not tested yet, I will try in my rPi3 build device)
  
• At the end the bluezalsa module (nothing changed here).
  

Anyway Moode is the only HiFi project I trust because it is simple to manage and you can really customize what you wants.

Hi,

I'm seeing same version number from master branch, at least from the last time I ran a build which was at moOde 4.1 release.
pi@moode:~ $ bluealsa -V
1.2.0

Is the issue that master branch has changes not in -b 1.2.0 ?

-Tim

There are a lot of changes, the code was tagged one year ago.  Meanwhile there were a lot of commits, but they left the version to 1.2.0, that's the problem IMHO...