You should capture the input event stream using "getevent". Paste your getevent output for taps (just tap your finger on the screen), for long presses (press your finger for a couple of seconds) and for slides (slide your finger on the screen). You can compare the working getevent output from a good device with the getevent output from your device. Post it here and those kindly Google engineers may help you solve their problem.
On Mon, Mar 1, 2010 at 10:18 PM, AchimNohl <achim.n...@coware.com> wrote: > Hi, > > have you tried to debug EventHub::getEvent in frameworks/bas/libs/ui/ > EventHub.cpp? I once had problems with my touchscreen after waking up > from suspend as the device was destroyed and got a new file > descriptor. I finally ended up in debugging this method. It does a > "poll" system call to wait for data on the touchscreen device. You may > want to add some LOGS here to see if it get passed poll when you hit > the ts and see the printk info from the kernel. > > Regards, > Achim > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
