On Saturday, September 29, 2012 12:27:09 AM UTC-6, ffxx68 wrote:
>
> Hi sarika, have a look at the diffs here:
>
> https://github.com/Renesas-EMEV2/RenesasEV2-BSPGB-Kernel/commit/910c76b7bbd631ba8e4384b57cb1c201fbdd2f05
That link is no longer valid. Do you have the diff posted anywhere else?
Hi sarika, have a look at the diffs here:
https://github.com/Renesas-EMEV2/RenesasEV2-BSPGB-Kernel/commit/910c76b7bbd631ba8e4384b57cb1c201fbdd2f05
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Hi Weston,
thanks for suggesting those debug tools. Here's my output
$ adb shell su -- getevent -lp /dev/input/event2
add device 1: /dev/input/event2
name: "gt80x"
events:
ABS (0003): ABS_HAT0X : value 0, min 0, max 0, fuzz 0, flat
0, resolution 0
ABS_HAT1
Are you sure the driver is sending up the correct events? Fire up get event
with:
adb shell su -- getevent -lt /dev/input/event1
make sure the commands that are comming in, are what your idc/keymap are
expecting... more info on that here:
http://source.android.com/tech/input/getevent.html
Westo
Hi cnet,
yes, that's what I've also done. Indeed looks like the kernel driver isn't
the main problem, I think...
Here's what I've achieved so far. I've introduced the .idc file for the
touch device, so it gets recognized as an actual "touch" screen, not as a
"pointer" pad. Then I've set the "s
You need to add a .idc file for each TouchScreen that defines it's
characteristics:
http://source.android.com/tech/input/input-device-configuration-files.html
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
