phablet@ubuntu-phablet:~$ hciconfig -a
hci0: Type: BR/EDR Bus: UART
BD Address: 38:BC:1A:18:B5:CD ACL MTU: 1021:8 SCO MTU: 244:4
DOWN
RX bytes:778 acl:0 sco:0 events:52 errors:0
TX bytes:3483 acl:0 sco:0 commands:52 errors:0
Features: 0xbf 0x3e 0x8d 0xfe 0xdb 0xff 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
phablet@ubuntu-phablet:~$ sudo hciconfig hci0 up
phablet@ubuntu-phablet:~$ hciconfig
hci0: Type: BR/EDR Bus: UART
BD Address: 38:BC:1A:18:B5:CD ACL MTU: 1021:8 SCO MTU: 244:4
UP RUNNING
RX bytes:1423 acl:0 sco:0 events:85 errors:0
TX bytes:4183 acl:0 sco:0 commands:85 errors:0
Now its up but it does not see the mouse in pairing mode
--
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/1531925
Title:
Can't connect Logitech Living Room Keyboard [LE]
Status in Canonical System Image:
New
Status in bluez package in Ubuntu:
Confirmed
Status in ubuntu-system-settings package in Ubuntu:
Confirmed
Bug description:
Cannot connect a Logitech Illuminated Living Room keyboard to a device
running bluez5. There are two versions of the keyboard, a unifying
receiver version, and a Bluetooth version. The latter has a BT symbol
on the 'del' key. To put the BT version in pairing mode, power on the
keyboard, then briefly hold the FN and 'del' key together and release.
A green LED at the top right of the keyboard should start flashing
quickly.
Once in pairing mode, the device will become visible on desktop using
the BT settings UI, however it's *never* shown in the UI on a device
running the latest Touch ( OTA9.1+ ). Note, this includes devices
running a silo version of bluez 5.37, including both arale and
krillin. On both devices, the keyboard *is* viewable using
bluetoothctl.
It should be noted that LE keyboard support on touch should be a
considered a missing feature.
Here's the reported attributes of the device from my macair running
15.10 + bluez 5.37:
Device DF:08:A9:A0:13:93
Name: K830
Alias: K830
Appearance: 0x03c1
Icon: input-keyboard
Paired: yes
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
Modalias: usb:v046DpB335d0010
From bluetoothctl on both my laptop and my desktop, I'm able to pair,
trust and connect the device, and info reflects these changes, however
the device never actually connects, it's LED remains blinking fast,
and the keyboard cannot be used.
Note, before pairing, I issued the command 'agent KeyboardOnly' and
'default-agent'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+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
