single touch touchscreen no longer working

[Daniel Kenzelmann]

Hi,

in older versions, i proposed a patch to recognize single-touch touchscreens that emit a BTN_LEFT instead of BTN_TOUCH

That was included in the following commit:

https://osdn.net/projects/android-x86/scm/git/frameworks-native/commits/08ad017dc59bfc7dc93f4eb2d5348f9b0c6ae877

However with 8.1-rc1, the touchscreen is only used as a mouse again.

Is there any chance to apply that kind of patch and make my touchscreen work again?

Thanks,
Daniel

[Chih-Wei Huang]

2018-06-23 3:56 GMT+08:00 Daniel Kenzelmann <daniel.k...@gmail.com>:
> Hi,
> in older versions, i proposed a patch to recognize single-touch touchscreens
> that emit a BTN_LEFT instead of BTN_TOUCH
> That was included in the following commit:
> https://osdn.net/projects/android-x86/scm/git/frameworks-native/commits/08ad017dc59bfc7dc93f4eb2d5348f9b0c6ae877

Your patch has already been applied to 8.1-rc1 as you've pointed out.
Or is there anything I missed?

> However with 8.1-rc1, the touchscreen is only used as a mouse again.
> Is there any chance to apply that kind of patch and make my touchscreen work
> again?

What's dumpsys input say?

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Daniel Kenzelmann]

Output is attached..

[Daniel Kenzelmann]

Any idea what could be wrong?

It's the same touchscreen as I was using with older android-x86 versions but now it seems to be used as relative input instead of absolute.

[Chih-Wei Huang]

Indeed it's treated as a touch input with type pointer device:

Device 10: 3M 3M MicroTouch USB controller
Generation: 25
IsExternal: true
HasMic: false
Sources: 0x00002002
KeyboardType: 0
Motion Ranges:
X: source=0x00002002, min=0.000, max=1023.000, flat=0.000,
fuzz=0.000, resolution=0.000
Y: source=0x00002002, min=0.000, max=767.000, flat=0.000,
fuzz=0.000, resolution=0.000
PRESSURE: source=0x00002002, min=0.000, max=1.000, flat=0.000,
fuzz=0.000, resolution=0.000
Touch Input Mapper (mode - pointer):
Parameters:
GestureMode: multi-touch
DeviceType: pointer
AssociatedDisplay: hasAssociatedDisplay=true,
isExternal=false, displayId=''
OrientationAware: false


I don't know why. Probably because some kernel changes.
Maybe you can override that by an idc file:

https://source.android.com/devices/input/touch-devices

[Daniel Kenzelmann]

Excellent, the idc file worked, thanks!!

[Chih-Wei Huang]

2018-07-09 0:04 GMT+08:00 Daniel Kenzelmann <daniel.k...@gmail.com>:
> Excellent, the idc file worked, thanks!!

Great! Please provide the idc file.
I'll add it.

[ma...@xemi.net]

Unrelated to his problem, but the following IDC is needed for mouse to work properly on hyper-v.

[Daniel Kenzelmann]

Hi,

If I remember correctly I just created the file called

3M_3M_MicroTouch_USB_controller.idc

with the following value inside:

touch.deviceType = touchScreen

(Had to create on the device itself using vi and already wiped it to test the CM/LineageOS builds thus can't put the original here..)

[Chih-Wei Huang]

2018-07-11 14:23 GMT+08:00 Daniel Kenzelmann <daniel.k...@gmail.com>:
> Hi,
> If I remember correctly I just created the file called
> 3M_3M_MicroTouch_USB_controller.idc
> with the following value inside:
> touch.deviceType = touchScreen

Sorry to forget it.
I just added it.
Thank you.