Trackpoint moving by itself - Keyboard connector not seated properly?

[xsixt]

Is there any relationship between the seating of the keyboard connector - and the movement of the trackpoint?

I briefly replaced a WLAN card, so the keyboard was in and out in a couple of minutes notice. I placed the keyboard face up so nothing was resting on the trackpoint. I hardly use the trackpoint and it's never done this before, but after reconnection now it moves around on its own. The only thing I can think of is, I didn't press the keyboard connector in firmly enough - however, everything on the keyboard works fine...

Thanks in advance.

[Thinkpad4by3]

The trackpoint moving by itself means either it is internally broken and is calibrating itself wrong(never seen it before on 40+ TP's) or the more likely issue is the cap is banging against the Trackpoint and making it move. Try removing the cap and seeing if it stops.

[RealBlackStuff]

Did you switch off before you disconnected?

[xsixt]

Did you switch off before you disconnected?

Certainly did.

The trackpoint moving by itself means either it is internally broken and is calibrating itself wrong(never seen it before on 40+ TP's) or the more likely issue is the cap is banging against the Trackpoint and making it move. Try removing the cap and seeing if it stops.

I tried pushing the trackpoint around, to its extremes and back to the middle.

It sometimes stayed in the middle for a minute or two, and drifted off slowly or fast.

I have disabled it for the moment. Very annoying

[zoltan87]

Same issue on my dad's ThinkPad X201. The mouse cursor keeps drifting away sometimes slow, sometimes really fast. I am going to change the whole keyboard, because it's getting to a state, where it's just unusable with the trackpoint. Very annoying, because the keyboard otherwise is fine (apart from the fact that the keycaps became shiny over the years).

[TOTAL]

Excavating in case. My third thinkpad, and each has had this issue.

Nearly fixed by uninstalling the synoptix or whatever it is called mouse software (different versions produce different issues) and using autohotkey script to make the pointer both more responsive and more controllable.

See autohotkey webpage for the details. The solution itself is totally free, intuitive and with plenty of application.

In case you want ready code, here is what works for me on windows 7:

Code: Select all

#InstallKeybdHook
#InstallMouseHook

#SingleInstance force
#NoEnv


;   ---------------------------------------------------------------------------------------------
; GET INTIAL MOUSE SPEED: 
; 0x70 (SPI_GETMOUSESPEED), third parameter is the speed (range is 1-20, 10 is default) 
;DllCall("SystemParametersInfo", UInt, 0x70, UInt, 0, UIntP, Mouse_Speed_Orig, UInt, 0) 


SetMouseDelay,-1 ;
SetBatchLines, -1
Process, Priority,, High

    DllCall("SystemParametersInfo", UInt, 0x71, UInt, 0, UInt, 15, UInt, 0) 
; ----------------------------------------------------------------------------------------------------


; <COMPILER: v1.0.48.5>
Critical
CoordMode, Mouse, Screen

SendMode, Input
#Persistent
 
 
SetTimer, WatchCursor, 20
return
 
WatchCursor:
MouseGetPos, , , id, control
 
xlast = %xpos%
ylast = %ypos%
 
 
MouseGetPos, xpos, ypos
 
 
xmove := xpos-xlast
ymove := ypos-ylast
 
X := xmove
Y := ymove
 
X /= 3.5
Y /= 3.5
 
if (xmove!=0&&ymove!=0)
{
 
MouseEvent(X,Y)
}
return
 

 
MouseEvent(a_xpos, a_ypos)
{
   DllCall("mouse_event", uint,1, int,a_xpos, int,a_ypos, uint,0, int,0 )
}
 

mbutton:: mbutton