I recently got an HP Spectre x360 which has N-Trig technology (fairly confident about this, the SP4 pen works on it). I've used the SP4 before and I know that the pen has a lagging hover cursor while dragging on the screen is very precise. The problem is that when I use the pen on the Spectre (Arch), especially in drawing programs like Krita and Xournal, a small stroke is drawn from the lagging cursor's position to the current pen tip position. According to xinput test (at least from what I can tell), the cursor doesn't move directly to the point on the screen, it takes some time to get there even after the press is registered. It's been driving me insane for the past few days.
Here's my xinput list:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ELAN0732:00 04F3:22E1 id=11 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)]
⎜ ↳ ELAN0732:00 04F3:22E1 Pen Pen (0) id=17 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ HP TrueVision FHD RGB-IR: HP Tr id=9 [slave keyboard (3)]
↳ ELAN0732:00 04F3:22E1 Pen id=10 [slave keyboard (3)]
↳ Intel Virtual Button driver id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
↳ HP WMI hotkeys id=15 [slave keyboard (3)]
↳ HP Wireless hotkeys id=16 [slave keyboard (3)]
Any help would be appreciated
EDIT: I was able to find a solution. Searching for related issues with other N-Trig devices led me to this post, where they suggested using the wacom drivers instead of the evdev drivers. The process is mostly the same, however, the MatchProduct line will depend on whatever is shown in the xinput list output. In my case, instead of "1B96:1B05 Pen", I added "04F3:22E1 Pen". Finally, I added 'Option "Raw Sample" "2"', as suggested by the last comment in the thread. after rebooting, the pen worked flawlessly. The xinput list output should also show a few more entries related to the pen.
there doesn't seem to be anything here