The same hardware platform, from gingerbread at graft touch screen driver to ics top view kernel portion of the touch screen to report the position and status are normal accurate, but the top did not touch effect, keystrokes and mouse inputs are normal, getevent command can also get to the touch screen events There is not a friend who might be able to help analyze a problem that place, very grateful .......
<-! Main posts under Banner (D4) -><-! Posts under the main text (D5) ->
Reply:
Very strange, is not this just emphasized the phenomenon
Reply:
Look EventHub related to it, Gingerbreak there is this, I do not know ICS have EventHub this component.
Reply:
Looked at the source side of the description, it seems, and idc about, but by his example to change a little or no effect, but the touch screen can interrupt the sleep process, and should have received the news. Might be there Other configuration parameters causes no problems to achieve results, please provide the following on your side (tp_input_device_name) named. idc file to refer to, ah, thank you.
Reply:
There are also some of the ICS, in frameworks / base / services / input in this directory. Mouse and keys can be used, and should not be the problem
Reply:
android4.0 android2.3 and touch the calculation method has been modified, that is as long as the id track data, it is considered that the touch point is valid, it records currently valid point and collected the last valid point comparison: If the new , that it is the new point DOWN, UP
is noBoth before and after that MOVE, send your own point of action (up / down / move) will not be adopted
Estimated that the landlord is to support multi-touch driver, and there is no next regardless of other touch points are again reported data, so data disorder occurs, you can move LOCK interface after startup, if the lock is moved, then, is the problem, you can modify kernel upload method, or inputReader.cpp,
Idc when another needs a configuration file table is touchsreen, to calculate the sampling helpful
Finally, driver of ABS_MT_POSITION_X, ABS_MT_POSITION_Y property has a max, min parameter must be achieved, if ineffective, then, android4.0 considered invalid device, not support
Reply:
idc files configured should be no problem.
Supports multi-put framework / base / data / etc multi-point feature added to the system to
Reply:
Well, driving inside the same point is also continuously reported data, but also locks LOCK interface does not move, the next week, then look to the company, the changes should be made about what to do to handle it? Thank you.
Reply:
IDC section and source parameters for a moment there, it should be nothing problem is to support multi-point, "the framework / base / data / etc multi-point feature added to the system to" This is not very understanding, can not to say a little bit of trouble in detail, thank you
Reply:
That is, the driver ABS_MT_POSITION_X, ABS_MT_POSITION_Y properties max, min, these two parameters are not achieved
android4.0 will be considered invalid device
Reply:
Oh, thank you, this parameter, then there should also be implemented in the drive which has set such a statement:
input_set_abs_params (ts-> input_dev, ABS_MT_POSITION_X,
ts-> abs_x_min, ts-> abs_x_max, 0, 0);
input_set_abs_params (ts-> input_dev, ABS_MT_POSITION_Y,
ts-> abs_y_min, ts-> abs_y_max, 0, 0);
input_set_abs_params (ts-> input_dev, ABS_MT_TOUCH_MAJOR,
ts-> abs_pressure_min, ts-> abs_pressure_max,
0, 0);
input_set_abs_params (ts-> input_dev, ABS_MT_WIDTH_MAJOR,
ts-> abs_width_min, ts-> abs_width_max, 0, 0);
., And the parameters are correct assignment log to see such a part of the Android tips:.. Touch device 'atmel-touchscreen' could not query the properties of its associated display 0 The device will be inoperable until the display size becomes available related log The output is on the inside frameworks / base / services / input / InputReader.cpp this document, I do not know and this is not relevant, is currently not find a specific reason.
Reply:
Hal layer may be wrong.
Reply:
max, min is 0, which is valid not mean that you write is achieved,
android4.0 found that the two values are 0, then considered to be an invalid value, the device does not support this,
It seems that this issue is 100%
Reply:
ouch device 'atmel-touchscreen' could not query the properties of its associated display 0. The device will be inoperable until the display size becomes available.
This is normal, which means that your device has not reported surface size up, it will automatically reported up later, this is normal print
Reply:
Well, carefully looked really get back to the relevant information:
I / EventHub (132): New device: id = 1, fd = 97, path = '/ dev/input/event1', name = 'atmel-maxtouch', classes = 0x55, configuration = '/ system / usr / idc / atmel-maxtouch.idc ', keyLayout =' / system / usr / keylayout / Generic.kl ', keyCharacterMap =' / system / usr / keychars / Generic.kcm ', builtinKeyboard = false
........
Device reconfigured: id = 1, name = 'atmel-maxtouch', surface size is now 800x480, mode is 1
max and min values in the normal range, then the driving part is the value set, and I'll check under the top response is not there to see what the problem is, thank you
Reply:
Well, carefully looked really get back to the relevant information:
I / EventHub (132): New device: id = 1, fd = 97, path = '/ dev/input/event1', name = 'atmel-maxtouch', classes = 0x55, configuration = '/ system / usr / idc / atmel-maxtouch.idc ', keyLayout =' / system / usr / keylayout / Generic.kl ', keyCharacterMap =' / system / usr / keychars / Generic.kcm ', builtinKeyboard = false
........
Device reconfigured: id = 1, name = 'atmel-maxtouch', surface size is now 800x480, mode is 1
max and min values in the normal range, then the driving part is the value set, and I'll check under the top response is not there to see what the problem is, thank you
Reply:
Well, carefully looked really get back to the relevant information:
I / EventHub (132): New device: id = 1, fd = 97, path = '/ dev/input/event1', name = 'atmel-maxtouch', classes = 0x55, configuration = '/ system / usr / idc / atmel-maxtouch.idc ', keyLayout =' / system / usr / keylayout / Generic.kl ', keyCharacterMap =' / system / usr / keychars / Generic.kcm ', builtinKeyboard = false
........
Device reconfigured: id = 1, name = 'atmel-maxtouch', surface size is now 800x480, mode is 1
max and min values in the normal range, then the driving part is the value set, and I'll check under the top response is not there to see what the problem is, thank you
Reply:
Hey, our two touch screen, a can, a very strange expression, there is a response, but not correct, check the progress of the day nothing, looked under google document, the original drive to change:
http://source.android.com/tech/input/touch-devices.html
14. As of Android Ice Cream Sandwich 4.0, touch screen drivers may need to be changed to comply with the Linux input protocol specification.
The following changes may be required:
When a tool becomes inactive (finger goes "up"), it should stop appearing in subsequent multi-touch sync reports. When all tools become inactive (all fingers go "up"), the driver should send an empty sync report packet, such as SYN_MT_REPORT followed by SYN_REPORT.
Previous versions of Android expected "up" events to be reported by sending a pressure value of 0. The old behavior was incompatible with the Linux input protocol specification and is no longer supported.
Physical pressure or signal strength information should be reported using ABS_MT_PRESSURE.
Previous versions of Android retrieved pressure information from ABS_MT_TOUCH_MAJOR. The old behavior was incompatible with the Linux input protocol specification and is no longer supported.
Touch size information should be reported using ABS_MT_TOUCH_MAJOR.
Previous versions of Android retrieved size information from ABS_MT_TOOL_MAJOR. The old behavior was incompatible with the Linux input protocol specification and is no longer supported.
Touch device drivers no longer need Android-specific customizations. By relying on the standard Linux input protocol, Android can support a wider variety of touch peripherals, such as external HID multi-touch touch screens, using unmodified drivers.
Reply:
ICS and GR should do a lot to improve
http://source.android.com/tech/input/touch-devices.html
http://source.android.com/tech/input/touch-devices.html
Reply:
Thank you for the enthusiastic reply, referring http://blog.21ic.com/user1/6273/archives/2012/88350.html this problem is resolved, thank you.
Reply:
I also debug this problem, I installed your http://blog.21ic.com/user1/6273/archives/2012/88350.html this post to the next test, and now there are effects can touch, but touch it there will be a small circle, and touch insensitive, do not know if you have this problem yet?
Reply:
I also have a ring, and like a mouse's
No comments:
Post a Comment