[PROBLEM] Issue with Blutooth in 4.1

[TheOldPresbyope]

Hi Kent,

Nice to hear that revert to -b v1.2.0 may be the solution :-)

Did you just recompile over top of existing blues-alsa using procedure below from @badbat75  ? If yes then I'll do same on my end and begin testing with my IOS and Anker devices.

Code:

# 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

-Tim

Yes, but I have to say I still have reservations about whether this is *the* solution. It's been so easy to chase down blind alleys with BT, not that I'm telling you anything new. I struggle to bring both moOde and my Android devices to a pristine state before each test and I'm not sure I'm succeeding.

I found a comment in the bluez-alsa issues log which may suggest an explanation for my problem:

A2DP is muted when HFP profile is activated

HFP is the Bluetooth Hands-Free Profile. It looks there have been HFP-related commits to bluez-alsa over the last two years but important ones (such as "HFP-HF service level connection procedure") came after the v1.2.0 release. Why I could get audio by disconnecting and reconnecting is still a mystery.

If the v1.2.0 release of bluez-alsa works well enough in testing, fine, otherwise we may need to search for the latest commit to bluez-alsa which does.

Regards,
Kent