Re: Synaptics Hp Touchpad Driver Windows 10
Harold Yengo
Synaptics' TouchPad device drivers are customized and supported by notebook manufacturers to meet specific driver requirements for their individual products. To ensure the appropriate driver for your device, always use the driver your specific notebook OEM supports.
Synaptics has a rich heritage in capacitive touch sensing, dating back to 1995 and our launch of the first notebook PC TouchPad. Today touchpads are ubiquitous, and we continue to innovate and advance technologies that strive to perfect the user experience.
My Synaptics touchpad driver disappeared. Which is a pain, because I like the ability to toggle between the mouse and touchpad, but even better I like the feature of turning off the touchpad when a mouse connection is detected. So now I have a piece of paper taped over the touchpad because HP's fancy touchpad design, didn't include a hardware button to turn it off. Note that the double tap doesn't turn it off either (how could it, with the driver missing?).
Initially a major Win10 update overwrote my Synaptics TP driver. I was able to rollback the driver update, and Synaptics driver reappeared. Next Win10 update same thing. This time when I tried to rollback the update the driver just disappeared. Now, I have no touchpad driver, not even the default MS driver. From my Device Manager:
Well that is weird, because there is no driver installed per Device Manager. So I went to Add/Remove and found the "Synaptics Clickpad Driver Driver", and tried to uninstall, and received this error message:
I appreciate your efforts to try and resolve the issue. I would suggest performing system factory reset will put the computer back to the original factory settings in this way all corrupted and outdated software will be removed.
Restoring Files that were Backed Up Using HP Recovery Manager (Windows)You can also contact HP support for assistance. They can remotely access your system to help alleviate difficulties: www.hp.com/contacthp/
I went through all the recommended steps, did the latest recommended Windows update. Checked Troubleshooting and updated the BIOS. I reviewed all the Yellow messages, which really were suggested HP features. But went through them all. Tried the Virtual Support assistant which didn't help, as it assumed the Synaptics driver was installed. Did the system test for the Mouse/Touchpad, but that is just a drag & drop test, which works fine, and is not the issue I am having. So after going through all this, I still don't have the right driver installed for my touchpad. (Setting/Devices/Touchpad/Additional Settings). I've been to Touchpad Troubleshooting, and I cannot install a new driver as recommended, because a corrupted driver is still there.
Thanks for the recommendation. A factory reset is a big task to fix a small problem -- a lot of squeeze for not a lot of juice. Besides backing-up my documents/files, there are also the other programs and devices that have been installed. Can't I run the Reset with the Keep My Files option? Will this also work?
But the biggest problem is that it does not address the issue of MS overwriting existing drivers. This will happen again during the next big Win10 update. After doing a little research, there is a setting where you can turn off driver updates. Here is the article: -to-stop-windows-10-updating-device-drivers. Of course the problem is that this will wholesale prevent driver updates, some of which may be necessary for security or bug issues. Choose your poison. There's gotta be a better way.
I would request you to contact our Support and our Support Engineers should be able to Remote into your computer and sort this out. HP Support can be reached by clicking on the following link: www.hp.com/contacthp/
I've been attempting to solve an issue on my ThinkPad T420 laptop, namely trying to force X to use the Synaptics touchpad driver instead of evdev. The main issue is that my touchpad is sometimes (actually quite frequently) detected as a mouse by the system instead of a touchpad - as demonstrated with xinput below. Previous searches online for solutions give nothing other than "file a bug report" and "update your kernel" (I am using the newest linux-zen kernel - the newest version of linux and linux-lts kernels don't make a difference), so I had to find a workaround through modprobe. Reloading the psmouse module will fix the issue half the time, half the time it will do nothing. As a result, I've been attempting to write a shell script executed by a systemd service on boot to repeatedly reload the psmouse module on boot until the Synaptics driver has been loaded correctly, but to no avail. My main difficulty is writing the condition to stop the script once the Synaptics driver has been loaded - having tried to grep Xorg.0.log and using the exit status of synclient has not worked thus far - any ideas?
The kernel option you gave unfortunately doesn't work.
Before you replied I also tried dmesg grep "synaptics", but that also didn't work in that if the Synaptics driver didn't load first time it would be stuck perpetually reloading the psmouse module and because of that my touchpad would not work at all.
I also edited the service file to change multi-user.target to graphical.target:
I'm pretty much a newbie to shell script beyond the basics, so I don't know if I'm doing anything wrong here.
Upon closer inspection when my shell script seems to perpetually loop, it seems that whether my touchpad is detected as a mouse or actually a touchpad is completely random each time the psmouse module is reloaded, as evidenced below:
Alternatively, to solve my issue I could simply remove the evdev configuration file from /etc/X11/xorg.conf.d, but then I'd like to somehow change the default input driver for any mouse from libinput to evdev - and I can't seen to find a way to do that yet.
The whole original goal of moving away from the libinput driver for all of this was to completely disable pointer acceleration, after reading on some post here that libinput did not support truly flat acceleration profiles and only had a half-arsed implementation of them. I would also be fine with using evdev as my touchpad driver, if it were not for the lack of features such as 2-finger scrolling, edge scrolling, among others that Synaptics brings.
Appears to be solved now, after adding a sleep 1 statement to my shell script - maybe the commands inside the until loop were being executed too fast for the actual condition to be evaluated beforehand... although that theory doesn't seem plausible. At least it appears that the Synaptics driver is being consistently loaded on boot now, rather than evdev sometimes. There is a short delay before the cursor becomes active on the login screen, but I can live with that.
I owned a Lenovo before purchasing the UX303UB in Jan 2018. I truly hate this touchpad. Waaaay too sensitive and it constantly interrupts workflow with a range of things opening up. I have turned down sensitivity to its lowest and still a problem. I would love to use the synaptics driver I had with my old lenovo but I was told by Asus Official support that it is not compatible. I have my doubts and wanted to ask the team here if it was possible.
The primary method of configuration for the touchpad is through an Xorg server configuration file. After installing xf86-input-synaptics, a default configuration file is located at /usr/share/X11/xorg.conf.d/70-synaptics.conf. Users can copy this file to /etc/X11/xorg.conf.d/ and edit it to configure the various driver options available. Refer to the synaptics(4) manual page for a complete list of available options. Machine-specific options can be discovered using #Synclient.
Next to the traditional method of configuration, the Synaptics driver also supports on the fly configuration. This means that users can set certain options through a software application, these options are applied immediately without needing to restart Xorg. This is useful to test configuration options before you include them in the configuration file or a script. Note that on the fly configuration is not persistent and lasts only until the Xorg server exists.
evtest needs exclusive access to the device which means it cannot be run together with an X server instance. You can either kill the X server or run evtest from a different virtual terminal (e.g., by pressing Ctrl+Alt+F2).
The tool xorg-xev can display taps, clicks, pressure, placement and other measured parameters in real-time, allowing still further refinement of the default Synaptics settings. xev can be run in X and needs no specifics. using the -event parameter, it is possible to restrict the types of events that are reported.
Circular scrolling is a feature that Synaptics offers which closely resembles the behaviour of iPods. Instead of (or additional to) scrolling horizontally or vertically, you can scroll circularly. Some users find this faster and more precise. To enable circular scrolling, add the following options to the touchpad device section of /etc/X11/xorg.conf.d/70-synaptics.conf:
Specifying something different from zero may be useful if you want to use circular scrolling in conjunction with horizontal and/or vertical scrolling. If you do so, the type of scrolling is determined by the edge you start from.
GDM stores the Xauthority files in /var/run/gdm in a randomly-named directory. You should find your actual path to the Xauthority file which can be done using ps ax. For some reason, multiple authority files may appear for a user, so a rule like this will be necessary:
d3342ee215