On a working device, if I touch the far left:
> absolute axis event at 6366.763794, ABS_MT_POSITION_X event at 6366.763794, code 53, type 03, val 00
And on the far right:
> absolute axis event at 6371.031397, ABS_MT_POSITION_X event at 6371.031397, code 53, type 03, val 1535
In a broken state:
> absolute axis event at 6705.620880, ABS_MT_POSITION_X event at 6705.620880, code 53, type 03, val 91
> absolute axis event at 6707.924863, ABS_MT_POSITION_X event at 6707.924863, code 53, type 03, val 1453
So... something goes into a state where the input "area" grows out of the device... The whole physical area is still active, but the delivered events are "closer" to the center of the device.
After further investigation, this indeed seems to be a problem at the driver/ android/ somewhere level...
The device capabilities:
So min=0, max=1536.
On a working device, if I touch the far left:
> absolute axis event at 6366.763794, ABS_MT_POSITION_X event at 6366.763794, code 53, type 03, val 00
And on the far right:
> absolute axis event at 6371.031397, ABS_MT_POSITION_X event at 6371.031397, code 53, type 03, val 1535
In a broken state:
> absolute axis event at 6705.620880, ABS_MT_POSITION_X event at 6705.620880, code 53, type 03, val 91
> absolute axis event at 6707.924863, ABS_MT_POSITION_X event at 6707.924863, code 53, type 03, val 1453
So... something goes into a state where the input "area" grows out of the device... The whole physical area is still active, but the delivered events are "closer" to the center of the device.