[PROBLEM] Issue with Blutooth in 4.1

[TheOldPresbyope]

Hi guys,
hello to everyone on this new forum.
I will tell you my story on bluetooth stack.
By default I was not able to pair any device iOS, Android or Windows devices.
On iOS I could pair but I couldn't connect, when I tried it failed and then it removed the devices.
On Windows devices I could connect but it disconnected after a while.
On Android it refuses to pair
So I did some tries starting the bluetooth stack manually and everything works flawlessy.
When I started the bluealsa service everything stops working.
So I tried to download version 1.2.0 instead of the master and everything started working.
Those are the step I used to build this version:
...

@badbat75
Haven't seen anyone else report this level of BT difficulty with r4.1. Tim's been using his iOS devices. I've never had a problem getting my Android (Marshmallow, Nougat, Oreo) devices to pair. I have had an issue with my Android devices then connecting with moOde but not streaming audio to it until I've disconnected and connected again. Not nearly as severe a problem as you report.
Are you running vanilla r4.1?
What was the basis for your decision to revert to a year-old release of bluez-alsa?
Inquiring minds want to know
Regards,
Kent

Hi Kent,
yes it was vanilla r4.1.
When I saw the problems raised during the startup of the bluezalsa service I tried to understand where was the problem, but I was not able to find it.
With moode r4.0 everything was working fine, so I tried first the standard bluez package provided with raspbian (same results), then I tried the bluez 5.49 and the latest stable version of bluezalsa (1.2.0) and it worked!!! I also saw that master branch of bluezalsa is very lively: the last change is 7 hours ago now in the src folder (for example) so probably the package change at every build and probably if I generate a new build now perhaps could work...
Stability is the main reason I decided to stay stuck to 1.2.0.
Let me know what you think.

@badbat75

I think you are very meticulous in your programming work and that's a good thing

I hadn't twigged to the bluez-alsa release number issue. I suppose one could dig through to find the most recent stable commit but that's a lot of work.

I'm taking a shortcut by reverting an existing r41 to last year's bluezalsa v1.2.0 release to see if this solves my Android BT connection issue. Of course I have to try your custom builder too but that's a project for when I have a block of time available later.

***UPDATE*** 
Having reverted to the v1.2.0 release, it seems like my Android Nexus 6P phone (Oreo) is establishing a working connection with moOde r4.1 on the first try. It seems like my Android Nexus 9 tablet (Nougat) is a little more fiddly but it still established a working connection without the rigmarole I was going through before.
***

Back when I had only early-generation RPis I sped up my moOde build-cycle using distcc to distribute compilations to cross-compilers on fast x86 hosts. Haven't done it since the release of the RPi3B. Building moOde on it with the Automated moOde OS Builder is fast enough to not want to bother.

Regards,
Kent