If touch works in emulator, read source code of emulator and kernel and see how it works, then do same thing in your kernel.
On Mar 24, 5:33 am, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote: > Hi, > > It would be great if you could throw some light on "how can > synaptics touchscreen (RMI) driver can be integrated with Android". We > do report "X, Y, X2, Y2, Pressure, ABS_FINGERS and TOOL_WIDTH to the > input subsystem. However Android does not seem to be responding to the > touch events. Any suggestions? > > Warm Regards, > Anil > > On Wed, Mar 19, 2008 at 1:05 PM, hackbod <[EMAIL PROTECTED]> wrote: > > > On Mar 17, 1:21 am, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote: > > > Android reads raw X,Y and Pressure info from touch driver. > > > And the device node being opened for touch is /dev/input/event1. > > > Regarding the network, you will have to set the DNS and LOCAL-IP using > > > the setprop utility. > > > It shouldn't matter what name you publish your input device under /dev/ > > input -- we just scan through all of the devices there and examine the > > events they report to classify them. So for something to be > > considered a touch driver, you just need to make sure you say you > > report X, Y, and the key code for the primary mouse button. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
