public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] K800i sends correct usage IDs, get	mis-interpreted by Xorg
Date: Fri, 04 May 2007 08:43:26 +0200	[thread overview]
Message-ID: <1178261006.25425.29.camel@violet> (raw)
In-Reply-To: <200705010532.30291.daff@dword.org>

Hi Andreas,

> this is my first post here and I am not sure whether I've come to the 
> right forum for my problem. I'll try nonetheless.
> 
> Using bluez-* 3.9 on Kubuntu 7.04 (Feisty), with Xorg 7.2.
> 
> I use my Sony Ericsson K800i to remote control my desktop and it works 
> almost fine. I defined an HID profile using the USB HID usage tables 
> [1] and the Bluetooth HID remote control developer information [2] by 
> Sony Ericsson.
> 
> The problem is that some usage IDs don't get interpreted correctly by 
> Xorg. An example:
> 
> <KEY_VOL_UP>
>   <ACTION>
>     <KEYBOARD MODIFIERS = "00" USAGEID = "4E" />  <!-- Page Down -->
>   </ACTION>
> </KEY_VOL_UP>
> 
> This sets the phone's volume up key to send the usage ID 4E (unmodified) 
> which is the keyboard equivalent of Page Down according to the HID 
> specs.
> 
> However, testing this with xev yields the following:
> 
> KeyPress event, serial 31, synthetic NO, window 0x1800001,
>     root 0x1a5, subw 0x0, time 3560039, (107,75), root:(1705,822),
>     state 0x0, keycode 117 (keysym 0xffaf, KP_Divide), same_screen YES,
>     XKeysymToKeycode returns keycode: 112
>     XLookupString gives 1 bytes: (2f) "/"
>     XmbLookupString gives 1 bytes: (2f) "/"
>     XFilterEvent returns: False
> 
> Apparently Xorg interprets that usage ID as KP_Divide ("/") or keycode 
> 117, which it definitely is not.
> 
> This is just a real example, other usage IDs are also problematic. 
> 
> Also of note should be that I set up an Xorg input device for the phone. 
> Without it no mouse events would ever occur:
> 
> Section "InputDevice"
>     Identifier              "k800i"
>     Driver                  "evdev"
>     Option  "Protocol"      "Auto"
>     Option "Name"           "Sony Ericsson Remote Control of PC 
> applications and other devices"
>     Option  "Buttons"       "3"
>     Option  "SendCoreEvents"
> EndSection
> 
> Before getting into any more detail, could this a problem of Xorg or is 
> this the doing of bluez? 

this is not a BlueZ problem. It is either Xorg or the HID<->Input
translation in the kernel.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-05-04  6:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01  3:32 [Bluez-users] K800i sends correct usage IDs, get mis-interpreted by Xorg Andreas Ntaflos
2007-05-04  6:43 ` Marcel Holtmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1178261006.25425.29.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox