Skip to content

Don't disable the proximity out quirk

The proximity out quirk forces a proximity out if we don't receive a tablet event for a hard-coded timeout. Originally enabled one-by-one for broken tablets, commit 9bba1499 enabled the prox-out quirk for all tablets but disabled it when a correct sequence was encountered.

As seen in #248 (closed) the Lenovo Flex 5 sometimes sends the right sequence, causing the quirk to be disabled and the device to be broken afterwards.

Fix this by simply forcing the quirk always on. Devices that behave correctly will stop the timer anyway whenever a correct sequence comes through, so this is mostly fine. Affected are only the touch+tablet tests where the timeout can be triggered while we're testing touch events.

Merge request reports