Rather than a bug this was just a incorrect usage of the available
tools. Normally when we connect a device through the UI it gets marked
as trusted directly. However when just doing that with bluetoothctl this
remains a manual step the user has to do.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
** Changed in: canonical-devices-system-image
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1494250
Title:
HID devices doesn't reconnect reliable
Status in Canonical System Image:
Invalid
Status in bluez package in Ubuntu:
Invalid
Bug description:
With bluez 5.33 on Nexus 4 with silo 43 installed.
* Pair and connect a HID device (mouse or keyboard)
-> pairing/connect works
* Use them for a bit
* Power HID device off
* Power HID device on again
* Start using the HID device
-> It doesn't reconnect automatically and also manually connection doesn't
seem to work.
With krillin an rc-proposed image 122 (ubuntu 20150914, device
20150821-736d127) this doesn't happen and the keyboard reconnects
reliable back to the phone when enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494250/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
