1. I downloaded the full source code (both kernel and android) from
android-x86.org;
2. Based on elo.c, I designed the touchscreen driver for my product;
3. I made the driver the built-in module of the kernel;
4. I written the application load_comtouch so that it can change the line
discipline of /dev/ttyS0 and make the serio connect with our driver. Both the
driver and the application works pretty well in 3.2 Android-x86.
5. I built the whole system and test the .iso image in one All-in-one PC, all
is OK but the touchscreen is not working.
6. I am sure that this driver and application can work well in 3.2 Android-x86.
7. I add one USW_SAW_TOUCH.idc to /system/usr/idc and the system recognize this.
The following is the logcat message:
//-----------------------------------------------------------------
I/EventHub( 1159): New device: id = 7, fd=208, path='/dev/input/event8',
name='USW_SAW_TOUCH', classes=0x4, configuration='/system/usr/
idc/USW_SAW_TOUCH.idc', keyLayout='', keyCharacterMap='', builtinKeyboard=false
I/InputReader (1159): Reconfiguring input devices. changes=0x00000004
I/InputReader (1159): Device reconfigured: id=7, name='USW_SAW_TOUCH', surface
size is now 800x600, mode is 1
I/InputReader (1159): Device added: id=7, name='USW_SAW_TOUCH',
sources=0x00001002
//--------------------------------------------------------------------
8. After this, the InputReader still can not dump the rawEvent message. I use
DEBUG_RAW_EVENTS to output the rawEvents message.
9. I add the set_bit(INPUT_PROP_DIRECT, input_dev->propbit); code piece to the
touchscreen driver, now, the InputReader can dump the raw Event messages:
D/InputReader( 1159): Input EV_ABS event: X Position = 4024
D/InputReader( 1159): Input EV_ABS event: Y Position = 2111
D/InputReader( 1159): Input EV_ABS event: X Position = 4037
D/InputReader( 1159): Input BTN_TOUCH = 0
But the touchscreen still does not work!!
Originally, I don't think it is a big problem to get the RS232 single-touch
touchscreen work in Android 4.0, but Why?
Who can help me?
Original issue reported on code.google.com by stty...@163.com on 22 Apr 2012 at 8:57
Original issue reported on code.google.com by
stty...@163.com
on 22 Apr 2012 at 8:57