Jumpy Cursor

Issues Related to Hardware (Sound, Video, Printers, Scanners, Webcams, Touchpads, Keyboards, Sensors, Drives, GRUB, etc.)

Moderator: Moderators

Jumpy Cursor

Postby nemesis » Sat Apr 30, 2011 16:15

Is there an option similar to *tu's JumpyCursorThreshold for synaptics/synclient? I've looked around, found palm detect, but it's not quite what I'm looking for, though similar. Basically the cursor becomes really jumpy when I inadvertently touch the pad with a second finger while using it. JumpyCursorThreshold prevents that.
nemesis
Simple Hen
 
Posts: 69
Joined: Sun Feb 04, 2007 0:19
Location: Grovetown, GA

Re: Jumpy Cursor

Postby Fitzcarraldo » Sat May 07, 2011 2:00

From ArchWiki - Asus Eee PC 1005HA:

Code: Select all
# This will make cursor not to jump if you have two fingers on the touchpad and you lift one
# (which you usually do after two-finger scrolling)
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Jumpy Cursor Threshold" 32 110


On my main laptop, the xinput command's help switch tells me the possible commands are:

Code: Select all
$ xinput --help
usage :
        xinput get-feedbacks <device name>
        xinput set-ptr-feedback <device name> <threshold> <num> <denom>
        xinput set-integer-feedback <device name> <feedback id> <value>
        xinput get-button-map <device name>
        xinput set-button-map <device name> <map button 1> [<map button 2> [...]]
        xinput set-pointer <device name> [<x index> <y index>]
        xinput set-mode <device name> ABSOLUTE|RELATIVE
        xinput list [--short || --long] [<device name>...]
        xinput query-state <device name>
        xinput test [-proximity] <device name>
        xinput create-master <id> [<sendCore (dflt:1)>] [<enable (dflt:1)>]
        xinput remove-master <id> [Floating|AttachToMaster (dflt:Floating)] [<returnPointer>] [<returnKeyboard>]
        xinput reattach <id> <master>
        xinput float <id>
        xinput set-cp <window> <device>
        xinput test-xi2 <device>
        xinput list-props <device> [<device> ...]
        xinput set-int-prop <device> <property> <format (8, 16, 32)> <val> [<val> ...]
        xinput set-float-prop <device> <property> <val> [<val> ...]
        xinput set-atom-prop <device> <property> <val> [<val> ...]
        xinput watch-props <device>
        xinput delete-prop <device> <property>
        xinput set-prop <device> [--type=atom|float|int] [--format=8|16|32] <property> <val> [<val> ...]

so the syntax of the command to set the property for the touchpad is:

Code: Select all
xinput set-int-prop <device> <property> <format (8, 16, 32)> <val> [<val> ...]

You find out the <device> by using the command xinput list. Here is what that command returns on my main laptop:

Code: Select all
$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft Optical Mouse with Tilt Wheel id=10   [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=15   [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)]
    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
    ↳ USB 2.0 Camera                            id=11   [slave  keyboard (3)]
    ↳ NOVATEK USB Keyboard                      id=12   [slave  keyboard (3)]
    ↳ NOVATEK USB Keyboard                      id=13   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=14   [slave  keyboard (3)]
    ↳ ENE eHome Infrared Remote Receiver        id=16   [slave  keyboard (3)]

so I see that <device> for my touchpad is "SynPS/2 Synaptics TouchPad" (i.e. the same as the ArchWiki example), so I could also use:

Code: Select all
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Jumpy Cursor Threshold" 32 110

Give it a try. To make it permanent, configure your DE to execute that command at start up.
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7984
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: Jumpy Cursor

Postby Fitzcarraldo » Sat May 07, 2011 2:35

A possible alternative to the above, although I have not tried this myself...

Using the command locate synaptics I see that my main laptop has a file /usr/share/X11/xorg.conf.d/50-synaptics.conf. Its contents are as follows:

Code: Select all
Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
EndSection

I don't know if it would work, but you could try adding the following line into the Section "InputClass" in that file:

Code: Select all
Option "JumpyCursorThreshold" "32"

(or whatever value you were using successfully in Ubuntu).

Try that too, to see if it works.
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7984
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: Jumpy Cursor

Postby Panuzio » Fri Aug 30, 2013 20:45

What do you think about this page?
http://wiki.gentoo.org/wiki/Asus_Eee_PC_1005HA
Is it useful for Sabayon, in your opinion?
(Anyway, I'll have to find dvd of this netbook, which I put somwhere I don't remember and know; I've "only" the netbook and the package).
Francesco
Ride of Sabayon (Mania) penguins
Gnome is dead!
Gnome 2 forever!

Linux portatile 4.4.0-sabayon #1 SMP Sat May 14 18:04:56 UTC 2016 x86_64 Intel(R) Core(TM) i3 CPU M 350 @ 2.27GHz GenuineIntel GNU/Linux
Panuzio
Growing Hen
 
Posts: 148
Joined: Mon May 19, 2008 20:04
Location: Firenze, Toscana, Italia (Florence, Tuscany, Italy)


Return to Hardware

Who is online

Users browsing this forum: No registered users and 1 guest