Comment 26 for bug 1576986

Revision history for this message
Timo Leppiniemi (timo-leppiniemi) wrote : Re: [Bug 1576986] Re: UT does not discover bluetooth smart (BLE) devices

Hi,

I can confirm that my Belkin slim style keyboard now works with the silos 37 and 60 installed.
It even works after shutdown and restart! :)

I need to do some more comprehensive testing with the keyboard and mouse later today.

Thank you!

> On 07 Aug 2016, at 21:01, Pat McGowan <email address hidden> wrote:
>
> This is in silos 37 (Bluez) and 60 (settings)
> FYI install the phablet-tools-citrain package, use the citrain tool to install each silo.
> This will make you device writable but next update should overwrite these.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1576986
>
> Title:
> UT does not discover bluetooth smart (BLE) devices
>
> Status in Canonical System Image:
> Confirmed
> Status in ubuntu-system-settings package in Ubuntu:
> Confirmed
>
> Bug description:
> I am actually typing this on a Microsoft Universal Foldable Keyboard
> connected to my M10 tablet.
>
> Device: Bq Aquaris M10
> OS: OTA-10.1
>
> Generally bluetooth devices that are not version 4 or bluetooth smart
> (BLE) seem to work and pair fine with the Aquaris E4.5 and the M10.
> However, when it comes to BLE/version 4, things obviously get too
> complicated for the system bluetooth settings because it doesn't even
> manage to discover these devices.
>
> OTA-10.1 uses Bluez version 5.37, which is perfectly capable of
> discovering and pairing with BLE devices, but in Ubuntu Touch it
> requires the use of "bluetoothctl" in the terminal. I will describe
> the steps needed below:
>
> phablet@ubuntu-phablet:-$ bluetoothctl
> [bluetooth]# scan on
>
> wait for device to show up in list, typically:
> [NEW] Device 01:02:FF:A8:BB:00 DeviceName
>
> [bluetooth]# discoverable on
> Changing discoverable on succeeded
> [bluetooth]# agent on
> Agent registered
> [bluetooth]# default-agent
> Default agent request successful
> [bluetooth]# pairable on
> Changing pairable on succeeded
>
> Now tell bluetoothctl to pair the device
> [bluetooth]# pair 01:02:FF:A8:BB:00
> Attempting to pair with 01:02:FF:A8:BB:00
>
> If pairing with MS Universal Foldable Keyboard, you will probably see
> a 6-digit code, punch that code on the keyboard and hit return.
>
> [CHG] Device 01:02:FF:A8:BB:00 Connected: yes
> [agent] Passkey: 123456
>
> You should be good to go.
>
> However, the MS Foldable Keyboard does not show up in system bluetooth
> settings (see attached screenshot) and getting the M10 to recognize
> that the Keyboard is turned off seems to require a reboot (and
> possibly also bluetooth turned off). Otherwise, the onscreen keyboard
> doesn't show up.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576986/+subscriptions