From: Georges Toth <georges.toth@gmail.com>
To: Brian Swetland <swetland@google.com>
Cc: Dirk Behme <dirk.behme@googlemail.com>, linux-omap@vger.kernel.org
Subject: Re: [android-internals] Re: Android on Nokia n810 (OMAP2420)
Date: Sun, 06 Apr 2008 17:14:45 +0200 [thread overview]
Message-ID: <47F8E8E5.7060301@gmail.com> (raw)
In-Reply-To: <20080406140804.GA21945@bulgaria.corp.google.com>
Brian Swetland wrote:
> [Georges Toth <georges.toth@gmail.com>]
>
>> The touchscreen doesn't work yet, but I hope we can figure that out too.
>> -> The driver works, there is output when one does a cat on
>> /dev/input/event3, but android doesn't recognize it.
>>
>> Some buttons don't work ... wrong mapping.
>> If anybody has an idea how to see what keycodes certain buttons are bound
>> to and how to edit the mapping in android that would be great :-).
>>
>
> Here's a brute force approach to sorting out input events: run getevent
> on the emulator and on the target hardware and compare the results. It's
> in /system/bin.
>
> I believe the touchpad issue has to do with sending events that the
> system recognizes as "pen down" and "pen up" events. Haven't looked at
> this in a while.
>
Thanks for the tip, I'll have a look at that.
> Keylayouts live in /system/usr/keylayout/*.kl and are used to translate
> from the raw input event codes to android keycodes.
>
> Keymaps live in /system/user/keychars/*.kcm.bin (undocumented binary
> format right now, sorry) and are used to describe how the key events
> and modifiers and such are related.
>
I would need to add/change the event code for the DPAD_CENTER event.
Do you perhaps know of a simple way of seeing what code a certain button
generates ?
--
regards,
Georges Toth
next prev parent reply other threads:[~2008-04-06 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2a9ba570-9005-4eed-8f1a-f45c909f9fe3@m36g2000hse.googlegroups.com>
[not found] ` <f6c5b8d90804020736m3d80fef9h2d377aea7fab52bf@mail.gmail.com>
[not found] ` <0b2d3f9c-e29a-406a-ac8d-d8589d457a0f@m36g2000hse.googlegroups.com>
[not found] ` <0b799c72-1a04-4224-8307-18b7ab10d17f@b5g2000pri.googlegroups.com>
[not found] ` <9a810d71-bc48-4bab-8ad6-93ebc310a110@z38g2000hsc.googlegroups.com>
[not found] ` <999ed349-dc22-4db4-a679-60511d9339f7@a23g2000hsc.googlegroups.com>
[not found] ` <9ff5cf01-f4aa-4560-b71e-bb948a69d9b9@t54g2000hsg.googlegroups.com>
[not found] ` <9583cd73-79d6-4f4e-b5a3-e27c4f165993@p39g2000prm.googlegroups.com>
[not found] ` <105bd206-af76-4fbb-affa-6fc8efdf6133@59g2000hsb.googlegroups.com>
[not found] ` <f6e0615c-d180-4a3e-a112-c5320cde1cfd@c65g2000hsa.googlegroups.com>
2008-04-05 17:09 ` [android-internals] Re: Android on Nokia n810 (OMAP2420) Nishanth Menon
2008-04-06 7:41 ` Dirk Behme
2008-04-06 13:31 ` Georges Toth
2008-04-06 14:08 ` Brian Swetland
2008-04-06 15:14 ` Georges Toth [this message]
2008-04-06 13:23 ` Brian Swetland
2008-04-06 15:04 ` Georges Toth
2008-04-06 16:36 ` andrzej zaborowski
2008-04-06 19:36 ` Georges Toth
2008-04-06 23:41 ` andrzej zaborowski
2008-04-06 22:25 ` Brian Swetland
2008-04-07 6:47 ` Jarkko Nikula
2008-04-07 6:51 ` Brian Swetland
2008-04-07 7:13 ` Jarkko Nikula
2008-04-08 20:08 ` Tony Lindgren
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=47F8E8E5.7060301@gmail.com \
--to=georges.toth@gmail.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap@vger.kernel.org \
--cc=swetland@google.com \
/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