You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I continued to use my Pro 4, which had ghost touch issues. After calibrating, and fine-tuning the values in config, t's almost OK. (Heat is the main problem, external, and the display backlight). (Palm detection works fine, if i tap the screen on a larger area, it resets the touch and ghost touches disappear for a while.)
The two new issues :
Cannot stop iptsd@hidraw2 . I have hidraw0, 1, and 2, the find script returns the 2 as the main one. Simple systemctl stop iptsd@hidraw0 kills the 0, 1 the 1, but systemctl stop iptsd@hidraw2 does nothing. If i kill the process, it stops, and the touch works further, and ghost touches go away. Guess that it falls back to one-touch mode.
(In addition; after killing the Iptsd, this is in the dmesg :
...is there a way to start Iptsd in event mode...?)
Sometimes the whole UI stops working when there are extraordinarily high number of ghost touches. Window manager restart helps, but i lose touch. This can have other root causes, but it seems to be in relation with high number of ghost touches. (It does not happen when i kill the Iptsd.)
Sometimes after waking the device from suspend, the iptsd does not start. Then the dmesg output contains :
[ 2800.135013] ipts 0000:00:16.4-3e8d0870-271a-4208-8eb5-9acb9402ae04: Failed to reset sensor: -11
[ 2800.135022] ipts 0000:00:16.4-3e8d0870-271a-4208-8eb5-9acb9402ae04: Failed to switch modes: -11
After this, starting the service, even if it keeps being running, it does nothing.
Debian testing/testing, Pro 4... Iptsd from repo.
Thanks for any help :)
Update : figured out how to stop iptsd correctly, so after stopping, it goes to event mode. Wrote a script to stop the service after startup and wakeup, but it's not the perfect solution. Sometimes after waking up the touch does not work; so need to put the device in sleep again, and wake up again... :D
The text was updated successfully, but these errors were encountered:
Hi,
I continued to use my Pro 4, which had ghost touch issues. After calibrating, and fine-tuning the values in config, t's almost OK. (Heat is the main problem, external, and the display backlight). (Palm detection works fine, if i tap the screen on a larger area, it resets the touch and ghost touches disappear for a while.)
The two new issues :
(In addition; after killing the Iptsd, this is in the dmesg :
...is there a way to start Iptsd in event mode...?)
Sometimes the whole UI stops working when there are extraordinarily high number of ghost touches. Window manager restart helps, but i lose touch. This can have other root causes, but it seems to be in relation with high number of ghost touches. (It does not happen when i kill the Iptsd.)
Sometimes after waking the device from suspend, the iptsd does not start. Then the dmesg output contains :
After this, starting the service, even if it keeps being running, it does nothing.
Debian testing/testing, Pro 4... Iptsd from repo.
Thanks for any help :)
Update : figured out how to stop iptsd correctly, so after stopping, it goes to event mode. Wrote a script to stop the service after startup and wakeup, but it's not the perfect solution. Sometimes after waking up the touch does not work; so need to put the device in sleep again, and wake up again... :D
The text was updated successfully, but these errors were encountered: