[Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Timo Veith]

Hi bluez-devel readers,

I bought the nice BlueLogic WingKey Keyboard. Unfortunately I wasn't able to 
get it working yet. On http://www.holtmann.org/linux/bluetooth/hid.html you 
wrote that it should work with linux.

At least I can type some characters. But when I start to type the keyoard 
randomly begins to produce characters after some time. Like so:

ddddddddddddddddddd

Then I have to press backspace on my normal keyboard (which is still 
connected) to stop that behaviour. It's not always a "d", it depends on what I 
typed before. Also sometimes some characters get mixed.

The trackball and the mouse buttons aren't working at all. This keyboard was 
so expensive and it would be a great pity if I couldn't use it now. :(

Here are some infos about my system: I am using Gentoo Linux with kernel 
2.6.11-gentoo-r4, bluez-libs and bluez-utils 2.15. The bluetooth daemon is 
started and when I plug in the usb dongle the log says:

Mar 20 19:42:02 tristan usb 3-1: new full speed USB device using uhci_hcd and 
address 2
Mar 20 19:42:03 tristan Bluetooth: HCI USB driver ver 2.8
Mar 20 19:42:03 tristan hcid[7523]: HCI dev 0 registered
Mar 20 19:42:03 tristan usbcore: registered new driver hci_usb
Mar 20 19:42:03 tristan hcid[7523]: HCI dev 0 up
Mar 20 19:42:03 tristan hcid[7523]: Starting security manager 0


And when I push the power button of the keyboard I get:

Mar 20 19:42:21 tristan hidd[7529]: New HID device 00:02:72:49:3C:2D 
(Bluelogic Technologies Inc. Bluetooth Keyboard)


So far, everything seems to be good, but if I press some keys the upper 
mentioned behaviour takes place and I see the following kind of messages in 
the log file:

Mar 20 19:42:43 tristan hidp_input_report: Unknown key (scancode 0xbe) 
pressed.
Mar 20 19:42:43 tristan hidp_input_report: Unknown key (scancode 0xbe) 
released.
Mar 20 19:42:43 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:42:43 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:42:44 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:42:44 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:42:52 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:42:54 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:01 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:43:01 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:04 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:43:05 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:05 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:43:06 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:06 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:43:06 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:07 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:43:07 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:07 tristan hidp_input_report: Unknown key (scancode 0xcd) 
pressed.
Mar 20 19:43:07 tristan hidp_input_report: Unknown key (scancode 0xcd) 
released.
Mar 20 19:43:08 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:43:08 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:09 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:43:10 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:12 tristan hidp_input_report: Unknown key (scancode 0xff) 
pressed.
Mar 20 19:43:12 tristan hidp_input_report: Unknown key (scancode 0xff) 
released.
Mar 20 19:43:15 tristan hidp_input_report: Unknown key (scancode 0xae) 
pressed.
Mar 20 19:43:15 tristan hidp_input_report: Unknown key (scancode 0xae) 
released.

It would be really nice get some help here, because I am completly lost. 
Please tell me if I can provide more info. Thanks in advance and kind 
regards,

Timo


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Marcel Holtmann]

Hi Timo,

> I bought the nice BlueLogic WingKey Keyboard. Unfortunately I wasn't able to 
> get it working yet. On http://www.holtmann.org/linux/bluetooth/hid.html you 
> wrote that it should work with linux.
> 
> At least I can type some characters. But when I start to type the keyoard 
> randomly begins to produce characters after some time. Like so:
> 
> ddddddddddddddddddd
> 
> Then I have to press backspace on my normal keyboard (which is still 
> connected) to stop that behaviour. It's not always a "d", it depends on what I 
> typed before. Also sometimes some characters get mixed.
> 
> The trackball and the mouse buttons aren't working at all. This keyboard was 
> so expensive and it would be a great pity if I couldn't use it now. :(
> 
> Here are some infos about my system: I am using Gentoo Linux with kernel 
> 2.6.11-gentoo-r4, bluez-libs and bluez-utils 2.15. The bluetooth daemon is 
> started and when I plug in the usb dongle the log says:
> 
> Mar 20 19:42:02 tristan usb 3-1: new full speed USB device using uhci_hcd and 
> address 2
> Mar 20 19:42:03 tristan Bluetooth: HCI USB driver ver 2.8
> Mar 20 19:42:03 tristan hcid[7523]: HCI dev 0 registered
> Mar 20 19:42:03 tristan usbcore: registered new driver hci_usb
> Mar 20 19:42:03 tristan hcid[7523]: HCI dev 0 up
> Mar 20 19:42:03 tristan hcid[7523]: Starting security manager 0
> 
> 
> And when I push the power button of the keyboard I get:
> 
> Mar 20 19:42:21 tristan hidd[7529]: New HID device 00:02:72:49:3C:2D 
> (Bluelogic Technologies Inc. Bluetooth Keyboard)
> 
> 
> So far, everything seems to be good, but if I press some keys the upper 
> mentioned behaviour takes place and I see the following kind of messages in 
> the log file:
> 
> Mar 20 19:42:43 tristan hidp_input_report: Unknown key (scancode 0xbe) 
> pressed.
> Mar 20 19:42:43 tristan hidp_input_report: Unknown key (scancode 0xbe) 
> released.
> Mar 20 19:42:43 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:42:43 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:42:44 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:42:44 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:42:52 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:42:53 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:42:54 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:01 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:43:01 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:04 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:43:05 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:05 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:43:06 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:06 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:43:06 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:07 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:43:07 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:07 tristan hidp_input_report: Unknown key (scancode 0xcd) 
> pressed.
> Mar 20 19:43:07 tristan hidp_input_report: Unknown key (scancode 0xcd) 
> released.
> Mar 20 19:43:08 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:43:08 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:09 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:43:10 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:12 tristan hidp_input_report: Unknown key (scancode 0xff) 
> pressed.
> Mar 20 19:43:12 tristan hidp_input_report: Unknown key (scancode 0xff) 
> released.
> Mar 20 19:43:15 tristan hidp_input_report: Unknown key (scancode 0xae) 
> pressed.
> Mar 20 19:43:15 tristan hidp_input_report: Unknown key (scancode 0xae) 
> released.
> 
> It would be really nice get some help here, because I am completly lost. 

can you try a 2.6.11-mh2 kernel first and see if that works. Otherwise I
need the "hcidump -X -V" for your connection.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Timo Veith]

Marcel Holtmann wrote:
> can you try a 2.6.11-mh2 kernel first and see if that works. Otherwise I
> need the "hcidump -X -V" for your connection.

I chose the hcidump alternative first :). -X and -V are no recognized 
options with my hcidump version. So I only used -x assuming that you 
meant that. I typed "1" , "2", and so on as you can see and after the 
"6" the mentioned behaviour started.

If this isn't enough I will get your patchset and try again.

Here is the hcidump:

tristan root # hcidump -x
HCIDump - HCI packet analyzer ver 1.9
device: hci0 snap_len: 1028 filter: 0xffffffff
 > HCI Event: Mode Change (0x14) plen 6
   00 29 00 00 00 00
 > ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 1E 00 00 00 00
1> ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 00 00 00 00 00
 > HCI Event: Mode Change (0x14) plen 6
   00 29 00 02 20 00
 > ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 1F 00 00 00 00
2> ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 00 00 00 00 00
 > HCI Event: Mode Change (0x14) plen 6
   00 29 00 00 00 00
 > HCI Event: Mode Change (0x14) plen 6
   00 29 00 02 A0 00
 > HCI Event: Mode Change (0x14) plen 6
   00 29 00 00 00 00
 > ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 20 00 00 00 00
3> ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 00 00 00 00 00
 > HCI Event: Mode Change (0x14) plen 6
   00 29 00 02 20 00
 > ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 21 00 00 00 00
4> ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 00 00 00 00 00
 > ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 22 00 00 00 00
5> ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 00 00 00 00 00
 > ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 23 00 00 00 00
6> ACL data: handle 0x0029 flags 0x02 dlen 13
     L2CAP(d): cid 0x41 len 9 [psm 0]
       A1 01 00 00 00 00 00 00 00
mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm> HCI Event: Mode 
Change (0x14) plen 6
   00 29 00 00 00 00
mm> HCI Event: Mode Change (0x14) plen 6
   00 29 00 02 A0 00
mmmmmmmm> HCI Event: Mode Change (0x14) plen 6
   00 29 00 00 00 00
 > HCI Event: Mode Change (0x14) plen 6
   00 29 00 02 20 03

Hmm, I don't know if this is of importance but I just noticed that if I 
start bluetoothd I get an error for hid2hci. It says: No devices in HCI 
mode found.

Kind regards and TIA,

Timo


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Timo Veith]

Hm if I try to patch the gentoo-dev-sources kernel I get this:

tristan linux # zcat /home/timo/tmp/patch-2.6.11-mh2.gz | patch -p1 
--dry-run
patching file drivers/bluetooth/bluecard_cs.c
patching file drivers/bluetooth/hci_bcsp.c
patching file drivers/bluetooth/hci_usb.c
patching file include/net/bluetooth/hci_core.h
patching file MAINTAINERS
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file net/bluetooth/hci_conn.c
patching file net/bluetooth/hci_event.c
patching file net/bluetooth/hci_sysfs.c
patching file net/bluetooth/hidp/core.c
patching file net/bluetooth/hidp/hid.c
patching file net/bluetooth/hidp/hid.h
patching file net/bluetooth/hidp/hidp.h
patching file net/bluetooth/hidp/Makefile
patching file net/bluetooth/rfcomm/core.c

There is one failure. Should I use vanilla sources or is this ok? I 
found a little HOWTO in the gentoo forums where a similar failure was 
described as "normal".

http://forums.gentoo.org/viewtopic-t-231506-highlight-devices+hci.html

Timo


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Marcel Holtmann]

Hi Timo,

> Hm if I try to patch the gentoo-dev-sources kernel I get this:
> 
> tristan linux # zcat /home/timo/tmp/patch-2.6.11-mh2.gz | patch -p1 
> --dry-run
> patching file drivers/bluetooth/bluecard_cs.c
> patching file drivers/bluetooth/hci_bcsp.c
> patching file drivers/bluetooth/hci_usb.c
> patching file include/net/bluetooth/hci_core.h
> patching file MAINTAINERS
> patching file Makefile
> Hunk #1 FAILED at 1.
> 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
> patching file net/bluetooth/hci_conn.c
> patching file net/bluetooth/hci_event.c
> patching file net/bluetooth/hci_sysfs.c
> patching file net/bluetooth/hidp/core.c
> patching file net/bluetooth/hidp/hid.c
> patching file net/bluetooth/hidp/hid.h
> patching file net/bluetooth/hidp/hidp.h
> patching file net/bluetooth/hidp/Makefile
> patching file net/bluetooth/rfcomm/core.c
> 
> There is one failure. Should I use vanilla sources or is this ok? I 
> found a little HOWTO in the gentoo forums where a similar failure was 
> described as "normal".

a clash with the Makefile is fine. If you look at Makefile.rej you will
see why this must happen ;)

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Timo Veith]

Marcel Holtmann wrote:
> a clash with the Makefile is fine. If you look at Makefile.rej you will
> see why this must happen ;)
> 

Hello Marcel,

I applied your patch and it works now. Thanks a lot! :)

Will your patch be integrated into the offical kernel and if yes when?

Kind regards and thanks again

Timo


-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Marcel Holtmann]

Hi Timo,

> I applied your patch and it works now. Thanks a lot! :)
> 
> Will your patch be integrated into the offical kernel and if yes when?

what you applied with that patch is a proof of concept for the report
protocol mode. The current mainline kernel only supports the boot mode
and this should also work in most cases. I don't know why it does not
work for your keyboard and until someone donates such keyboard to me, we
will may never know.

The work for the generic HID parser is on going and when this is merged
back into mainline then Bluetooth will get full HID report mode protocol
support.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard

[Marcel Holtmann]

Hi Timo,

> > can you try a 2.6.11-mh2 kernel first and see if that works. Otherwise I
> > need the "hcidump -X -V" for your connection.
> 
> I chose the hcidump alternative first :). -X and -V are no recognized 
> options with my hcidump version. So I only used -x assuming that you 
> meant that. I typed "1" , "2", and so on as you can see and after the 
> "6" the mentioned behaviour started.

no, I actually meant "-X -V". Update your hcidump to the latest version
and try to get everything. Especially the connection setup.

> Hmm, I don't know if this is of importance but I just noticed that if I 
> start bluetoothd I get an error for hid2hci. It says: No devices in HCI 
> mode found.

If you don't have a HID proxy dongle the hid2hci is not useful.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel