Tweak and fine-tune touchpads and mice

Here are some pointers on how to fine-tune the behavior of mice and trackpads.

 Note that this is unofficial, unsupported, etc  .:-) 

 

To experiment with changing settings (not permanent):

  1. Get to a shell (ctl+alt+t when logged in, then run "shell" cmd)
  2. Find your device ID by running 
    xinput -list
    to see all devices - use the name of the devices to locate your touchpad or mouse.
  3. Once you have that id #, you want to list all the properties the device has so you can decide what to adjust, so run 
    xinput list-props [id#]
  4. Now you can look through that list and find the attribute you want to change. Take note of the attribute id # which is found in the parentheses at the end of the attribute name. 
  5. Decide what you want the new value to be (you'll have to guess-and-check at what the right adjustments are for any given device), and then you can change the attribute value this way:
    xinput set-prop [device id#] [attribute id#] [new value]

 

Test the results and repeat that process until you know the value you like. 

Now, these actions will only last until your next reboot.

 

To make changes persistent (or close): 

Once you have found the different commands (step 5 above) that make the device behave how you want, put them together, each on their own line, in a .txt file (various Chorme apps and websites will let you compose these). Save that .txt file in Downloads folder (and back it up to GDrive).

 

Now copy the .txt and rename the copy to a .sh (script.txt > script.sh) - try to make the name brief and easy to remember.

 

Now you have "script.sh" which is your own personal input-device-fixer. To make those fixes present all the time, you need this script to run at startup. You can try to setup something that runs at startup automatically, but it's a little complex on CloudReady (compared to init scripts on Ubuntu, etc).

 

If you're willing to do just a little manual work each boot, you can go this simpler route:

Copy script.sh into your path and modify it to be executable by executing these three cmds:

sudo mount -o rw,remount /

sudo cp ~/Downloads/script.sh /usr/bin/

sudo chmod 777 /usr/bin/script.sh

 

Once you've done that, you can fix device behavior each time you reboot by opening a shell (see #1 and 2 above) and simply running the cmd

script

It should only take a couple seconds if you use ctl+alt+t, and you can avoid all the complexity of a startup script.

Have more questions? Submit a request

3 Comments

  • Avatar
    Dan Atha

    When I try to use this and run script.sh after reboot, I get "command not found"
    I'm running an xinput command so it says "xinput: command not found"
    If I type in my xinput command right below the error, it works fine. Something is missing when running the .sh file. I tried adding sh in front of xinput but then got sh: command not found.
    Help.

  • Avatar
    SignedAdam

    @Dan Atha - Maybe you have to install Chromebrew!

    https://neverware.zendesk.com/hc/en-us/articles/216335208-Want-a-Package-Manager-Try-Chromebrew-

    then install xinput using Chromebrew!, just a guess

     

    when i run the command, I get "unable to connect to X server"

    Edited by SignedAdam
  • Avatar
    Anunay Jain

    @Dan Atha - You need to run these commands as chronos to do this :
    Type "shell" (without quotes)
    then it will ask for a password type "chrome"
    now you will be in shell type those commands to fine tune your device

Please sign in to leave a comment.
Powered by Zendesk