Every time I touch my touchpad (which usually acts as a mouse) on my Surface Pro 3, my screen turns off. It doesn't shut down the whole tablet, it basically just locks it. The mouse icon might move slightly with my finger, but after about a second my screen goes black. I can touch a key on the keyboard to turn the screen back on, and log back in, but if I use my touchpad again the same error happens. So my keys work fine, but my touchpad does not.
I am experiencing the same problem. Can you be specific about how you cleaned the connectors? (where, with what, etc...) I'd appreciate it if you could email me at czay...@gmail.com. I only have an Outlook account because it was used to register my Surface and I really don't use it.
... and if you read it carefully, you will see that the problem is resolved for me and other people who have #ash-debug-shortcuts enabled but definitely NOT for anyone who does not have that debug state enabled; in fact, they will be reporting a problem because their touchpad will no longer work once they upgrade to version 75 and they will have no way to activate it without enabling that flag and then doing Shift+Search+P.
I have also communicated this fact to the ChromiumOS developer who helped resolve the problem in the first place. I am assuming that HP has its own relationship with the developers of ChromiumOS and it device-specific versions as ChromeOS that are associated with Chromebooks like the HP X2 that I am using to write this response.
I must have failed to make clear that "shift+search+p" no longer works to disable my X2 touchpad when the debug-keyboard-shortcuts flag is enabled... though "shift+search+t" can be used to toggle the touchscreen. I had been using these "features" on my Acer c720 for a couple of years and have found them indispensible when using a Chromebook for typing long texts... and the HP X2 touchpad is even larger and more sensitive than the one on the Acer.
Are you suggesting that it works on the same hardware for you? What version of CrOS are you using? I'd be happy to give more information about the configuration of my device as perhaps there is something to be gleaned from a comparison.
This is the only options to disable touchpad on a Chromebook. Refer to this YouTube video showing How To Disable the Touchpad on a Chromebook
If this fails then this computer doesn't have the ability to change those settings.
As I previously stated, I tried this suggested approach on my HP X2 and "shift+search+p" does NOT work for the touchpad while "shift+search+t" does work fine for the touchscreen. It also still works for both functionalities on the Acer c720 and, apparently, on other Chromebooks.
I am very disappointed by your statement that "this computer doesn't have the ability to change those settings" when that is only half true. I am presuming from your profile that you are an HP employee and, as such, will conclude that HP cannot help me resolve what should, in my experienced opinion, be a simple matter that is of obvious value and that is implemented in all other operating systems with which I am familiar. I will continue to pursue a solution with the Chromebook and ChromeOS communities and developers until I either find a solution or am convinced that there is a reasonable explanation for the behavior of the HP X2, though it would probably lead me to abandon the device for another.
I am pleased to report that this problem was resolved in version 75 of ChromeOS. My system just updated to the stable version and I am able to toggle the touchpad with Shift+Search+P as desired.
Fyi, I found a contact among the ChromiumOS developers who confirmed that this was problem because the detachable keyboard w/touchpad on this device was being treated as an external device and the "hotkey" that can be used by enabling chrome://flags/#ash-debug-shortcuts was only intended for use with internal devices. My contact requested the change to the source in the next version and I only has to wait for the update.
One important point: I found the touchpad was initially deactivated when I tried to use my device after the update. All it took was Shift+Search+P for the touchpad to be activated; however, I am not sure that it will be activated for people who do NOT have the chrome://flags/#ash-debug-shortcuts enabled, so I will now send this note and will report back after deactivating the flag and restarting my device... Please standby...
I have communicated this to the person supporting ChromiumOS who introduced the change in the source. I also suggested that it should not be necessary, in my opinion, to set a special flag in order to toggle the state of the touchpad or the screen, but I am doubtful a more permanent change will occur any time soon.
Thank you for posting this; I'm having the exact problem. I have a Latitude E5550 and the touchpad and pointingstick work, I just don't have access to adjusting their setting or using gestures. Dell Touchpad software is opening, but I only have options on the mouse; touchpad and pointingstick don't show. A Google search resulted in troubleshooters that addressed getting Dell Touchpad to showup, but nothing on this issue. I had to search by image just to find this. Hopefully we get an answer soon.
Loading default settings in BIOS can help when the system is unable to function properly due to changed or corrupted settings. When you load default settings, BIOS will be restored to the original settings that were set when the motherboard was manufactured.
If after BIOS restoration and EC reset, the touchpad is functional in the BIOS/UEFI screen but becomes inoperative upon entering the Windows system, please proceed to the next section to update the BIOS and drivers.
Note: If the touchpad still cannot operate in the BIOS/UEFI screen, it might be a hardware issue with the touchpad. We recommend visiting an authorized ASUS service center for further diagnosis.
Please go to the ASUS support site to download and install the following drivers. Here you can learn more about How to search and download drivers. (The following pictures are the current version as a reference, please download the latest version from the ASUS Support Site.)
If the problem happens recently, and if you have ever created a restore point or there is an automatic system restore existed, try to restore the device to a point before the problem began to resolve the problem. Here you can learn more about How to use restore point to restore the system. If the problem persists, please continue the next troubleshooting step.
If the problem persists after all troubleshooting steps are completed. Please backup your personal files, then reset the device to back to its original configuration. Here you can learn more about How to reset the system.
I am trying to troubleshoot why my touchpad does not work anymore with Debian on Wayland (after pressing FN9 and FN8), continuing from the thread Why lost communication to Touchpad on Wayland Debian Stretch after FN-8/9 keys?
Restarting the system does not restore the touchpad. So some touchpad setting files have been affected. I really would like to troubleshoot which those files are such that the touchpad could work again.
As the topic says i would like to connect a touchpad to an arduino atMega328. I was searching on the internet and seeing some documentation about how is it done and there is a lot describing the procedure but normally with touchpads that have 4 pinouts...
Now in this documentation , it helpedme understanding the similarities between this type of interface with the PS/2 interface.
However this model has 14 pinouts or so(cant count them so well because they are very very tiny) and after a lot of search i cant found any example that is related with this type of model, normally i find touchpads with 4 pinouts, even the documentation is not saying about a synaptics model that is like the one i have...