Now you have a working image we need to rebuild/test with different BlueZ versions. To guide the process we will download sources for BlueZ and start a "bisect" process in the BlueZ source directory by marking known-good (v5.72) and known-bad (v5.73) release commits (using the commit githashes):
cd ~/
git clone https://github.com/bluez/bluez
cd bluez
git bisect good 770ad5614e7e8074133e6f563495ce4822f63fe4
git bisect bad 19f8fcdc2084048bebe5bd9ea4fb97f7ece16df0
git bisect start
Bisect will now suggest a githash to test. Change to the LE buildsystem (open another tab in Terminal to make copy/pasting easier) and edit packages/network/bluez/package.mk and make changes:
--- a/packages/network/bluez/package.mk
+++ b/packages/network/bluez/package.mk
@@ -3,11 +3,11 @@
# Copyright (C) 2019-present Team LibreELEC (https://libreelec.tv)
PKG_NAME="bluez"
-PKG_VERSION="5.73"
-PKG_SHA256="257e9075ce05c70d48c5defd254e78c418416f7584b45f9dddc884ff88e3fc53"
+PKG_VERSION="770ad5614e7e8074133e6f563495ce4822f63fe4"
+PKG_SHA256=""
PKG_LICENSE="GPL"
PKG_SITE="http://www.bluez.org/"
-PKG_URL="https://www.kernel.org/pub/linux/bluetooth/${PKG_NAME}-${PKG_VERSION}.tar.xz"
+PKG_URL="https://github.com/bluez/bluez/archive/${PKG_VERSION}.tar.gz"
PKG_DEPENDS_TARGET="toolchain dbus glib readline systemd"
PKG_LONGDESC="Bluetooth Tools and System Daemons for Linux."
PKG_TOOLCHAIN="autotools"
Display More
^ We change PKG_VERSION to use whatever githash bisect is asking to test (change this each time). We also null PKG_SHA256 so it is ignored (to make testing easier). We also change PKG_URL to download from the BlueZ mirror on GitHub instead of the normal repo as this supports downloading at any githash in the repo (the kernel repo only has release versions).
Once package.mk is modified, run the "PROJECT=xxx ARCH=xxx" image build command again and the buildsystem will detect the BlueZ package changed and it will rebuild that package and create a new image. You can then transfer (e.g. scp) the built image (.img.gz or .tar file) to /storage/.update/ on your test device and reboot to see if the image works?
If the image is good run "git bisect good" in the BlueZ source dir, and if bad run "git bisect bad" and bisect will suggest another githash to test. Keep repeating this process (edit githash, rebuild, test, mark good/bad) until bisect tells you the first bad (breaking) commit. Then report back here with that info.
Good luck