Hey everyone,
it finally happened: We are switching to BlueZ 5.x on our Touch images
on all supported devices. To make this happen a huge amount of work
through the last five months from different people was needed. Thank
you all for the great work and support to make this happen!
QA approved all silos now and they will be merged by the CI guards
today. All device tarballs for supported devices (krillin, vegetahd,
arale, mako, flo) were updated to support everything needed for BlueZ
5.x and are already available in the rc-proposed channel.
This is just a first step for better Bluetooth support on Ubuntu
Touch. We now have the same bluetooth stack in the kernel on all our
devices which makes it a lot easier to fix bugs at the same time
across all our devices.
As this is a very huge and complex landing things can break. We spent
a lot time to make sure this doesn't happen. However as Bluetooth is a
very complex technology there can and will still be interoperability
issues with devices on the market.
As we're now releasing this into rc-proposed and will ship this to our
users with OTA 9 it would be great if anybody running rc-proposed and
experience any problems sends us bug reports. There is a guideline in
the wiki at [1] which describes necessary steps to include additional
information about what goes wrong in the system. Bugs can be filed
against the bluez package at [2].
NOTE: There is currently a suspend issue with the new bluetooth stack
in the kernel on arale. See [3] for more details. We're working
actively on a fix for that.
One final word: Generally having BlueZ 5.x will give us a lot more
stable Bluetooth experience. What we're landing right now will not
directly bring any new Bluetooth features. This is just the base for
future work but opens the gate for a lot things :)
regards,
Simon
[1]: https://wiki.ubuntu.com/DebuggingBluetooth
[2]: https://bugs.launchpad.net/ubuntu/+source/bluez
[3]: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1505241
