Yeah I found that too, thanks. I am actually trying to make sense of the "call stack" of input generation events. I noticed that this driver registers with the drivers/input/input.c system, and when it receives an interrupt, it calls the handle_event() function, which in turn switch-case's over various types, which later disposes the event on.
I'm new to "handling input" but it could be nice to know what happens next in the chain. It would be very quite educational and helping to figure out what is the topmost "linux" element in this chain, and what is the bottom "Android" element. I saw in some forum that as far as Android goes there are two places to look for: "KeyInputQueue.java" which I haven't found yet, and "EventHub.cpp" which I still need to make sense of, but apparntly implements some Observer-Notifier pattern on by calling "inotify_add_watch()" on the /dev/input/ files. I only had a very quick look at it, and I am still very unfamiliar with Android. I noticed that there is a disposition, type, code and value tupples, where for examples "code" represents the key stroke. I think all of the devices in the emulator are actually a single device which is called qwerty2 . Is that correct? On a similar subject: Looking at my google nexus one, I found out that there are more input devices synaptics-rmi-touch-screen // touch screen mahimai-keypad // keypad mahimai-nav // I think it's the trackball compass // Would every android device have this? Does anyone know what exactly is it used for? Is that really a compass? Maybe referring to gyros? this device sends events all the time lightsensor-level I suppose the emulator does not deal with anything other than the qwerty, is that correct? Would other android systems contain the same input elements, or similar to those I listed for the Nexus One example? Thanks, Ron >From what I noticed, also on my Google Nexus One device, On Wed, Aug 10, 2011 at 5:59 PM, Viral Mehta <viral....@gmail.com> wrote: > Yes, > > later on I hacked > common/drivers/input/keyboard/goldfish_events.c > file to solve my problem... > > Let me know what problem you are facing, I might be able to help you..... > > On Wed, Aug 10, 2011 at 6:30 AM, Ron M <ron...@gmail.com> wrote: > >> Hi Viral, >> Did you find a solution for this issue? Can you please share it if you >> did? I am facing the same problem here. >> >> Thanks. >> >> On Jan 5, 11:41 pm, vkmgeek <viral....@gmail.com> wrote: >> > Hi, >> > >> > I looked further and I can see file >> > external/qemu/hw/goldfish_events_device.c is the file which sends >> > events to /dev/input and through qemud probably. >> > >> > I am not sure is this good to change this file or not ? >> > If I change this file, it will change "emulator" binary which ofcourse >> > is not acceptable. >> > >> > But, still I want to tweak input touch events at lower layer.... >> > Can someone suggest me some pointers ? >> > >> > On Dec 30 2010, 11:53 am, vkmgeek <viral....@gmail.com> wrote: >> > >> > >> > >> > >> > >> > >> > >> > > Hi >> > > Can someone help me to solve following questions in understanding how >> > > touch events are emulated in Android Emulator ? >> > >> > > 1. Mouse events are used as touch events. >> > > 2. But, I am not able to find any "goldfish_mouse*.c" file in >> > > emulator/ >> > > goldfish kernel. >> > >> > > 3. If there is no such file, who creates /dev/input/event0 device on >> > > emulator ? Is it drivers/input/keyboard/goldfish-events.c file ? If >> > > yes, I do not see any code related to sending touch events like >> > > input_report_abs(,,,)? >> > >> > > Thanks, >> > > Viral >> > >> > > PS - I also posted the same message on android-platform. But, it looks >> > > more relevant here though it is regarding emulated kernel. >> > > > > -- > Thanks, > Viral Mehta > -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
