Skip to main content
Super User

Return to Answer

Toned down the gaudy.
Source Link
Protector one
Protector one
  • 1.3k
  • 3
  • 22
  • 29

Since disabling SmartSense didn't solve the problem for me, I had to go all Morpheus on this hole. (Popped both blue and reddig a little deeper.)
After much toil and bickering with various forms of Sony'sSony Support, I gave up and tried messing with the Registry. After some failed attempts to disable the Synaptics filter driver that's attached to the keyboard, I found something that worked.

Solution:
In the Registry, go to the key HKEY_LOCAL_MACHINE\SOFTWARE\Synaptics\SynTP\Defaults, and set the value of all string entries of the form PalmKms…, to 0. (Of course, they probably don't all need to be 0, but have fun finding out which one(s) you actually need!)
These values determine the amount of ms that the touchpad stays disabled after keyboard input has been detected.

I think Sony will probably issue an update to the VAIO Control Center where you can simply disable this functionality, but until that day, this fixes the issue.

Since disabling SmartSense didn't solve the problem for me, I had to go all Morpheus on this hole. (Popped both blue and red.)
After much toil and bickering with various forms of Sony's Support, I gave up and tried messing with the Registry. After some failed attempts to disable the Synaptics filter driver that's attached to the keyboard, I found something that worked.

Solution:
In the Registry, go to the key HKEY_LOCAL_MACHINE\SOFTWARE\Synaptics\SynTP\Defaults, and set the value of all string entries of the form PalmKms…, to 0. (Of course, they probably don't all need to be 0, but have fun finding out which one(s) you actually need!)
These values determine the amount of ms that the touchpad stays disabled after keyboard input has been detected.

I think Sony will probably issue an update to the VAIO Control Center where you can simply disable this functionality, but until that day, this fixes the issue.

Since disabling SmartSense didn't solve the problem for me, I had to dig a little deeper.
After much toil and bickering with various forms of Sony Support, I gave up and tried messing with the Registry. After some failed attempts to disable the Synaptics filter driver that's attached to the keyboard, I found something that worked.

Solution:
In the Registry, go to the key HKEY_LOCAL_MACHINE\SOFTWARE\Synaptics\SynTP\Defaults, and set the value of all string entries of the form PalmKms…, to 0. (Of course, they probably don't all need to be 0, but have fun finding out which one(s) you actually need!)
These values determine the amount of ms that the touchpad stays disabled after keyboard input has been detected.

I think Sony will probably issue an update to the VAIO Control Center where you can simply disable this functionality, but until that day, this fixes the issue.

Source Link
Protector one
Protector one
  • 1.3k
  • 3
  • 22
  • 29

Since disabling SmartSense didn't solve the problem for me, I had to go all Morpheus on this hole. (Popped both blue and red.)
After much toil and bickering with various forms of Sony's Support, I gave up and tried messing with the Registry. After some failed attempts to disable the Synaptics filter driver that's attached to the keyboard, I found something that worked.

Solution:
In the Registry, go to the key HKEY_LOCAL_MACHINE\SOFTWARE\Synaptics\SynTP\Defaults, and set the value of all string entries of the form PalmKms…, to 0. (Of course, they probably don't all need to be 0, but have fun finding out which one(s) you actually need!)
These values determine the amount of ms that the touchpad stays disabled after keyboard input has been detected.

I think Sony will probably issue an update to the VAIO Control Center where you can simply disable this functionality, but until that day, this fixes the issue.