Chosen Solution
Whenever I press L2 the left stick claims to move forward! How can I fix this? I initially thought that it was a dirt issue - that through whatever side effect the system would pick up soft forward motion on the left stick. After cleaning and no change in behavior I looked at the USB HID logs: In center position the left stick (ABS_Y) is at jitterung around 108 109 110 (the value range is 0…255) and the L2 - which is identified as ABS_Z is at zero. Now If I swiftly press L2 the follow happens: Event: time 1615892603.331589, ————– SYN_REPORT ———— Event: time 1615892603.335600, type 3 (EV_ABS), code 1 (ABS_Y), value 86 Event: time 1615892603.335600, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007 Event: time 1615892603.335600, type 1 (EV_KEY), code 312 (BTN_TL2), value 1 Event: time 1615892603.335600, type 3 (EV_ABS), code 2 (ABS_Z), value 13 Event: time 1615892603.335600, ————– SYN_REPORT ———— Event: time 1615892603.339612, type 3 (EV_ABS), code 1 (ABS_Y), value 84 Event: time 1615892603.339612, type 3 (EV_ABS), code 2 (ABS_Z), value 19 Event: time 1615892603.339612, ————– SYN_REPORT ———— Event: time 1615892603.343615, type 3 (EV_ABS), code 1 (ABS_Y), value 81 Event: time 1615892603.343615, type 3 (EV_ABS), code 2 (ABS_Z), value 24 Event: time 1615892603.343615, ————– SYN_REPORT ———— Event: time 1615892603.347616, type 3 (EV_ABS), code 1 (ABS_Y), value 79 Event: time 1615892603.347616, type 3 (EV_ABS), code 2 (ABS_Z), value 31 Event: time 1615892603.347616, ————– SYN_REPORT ———— Event: time 1615892603.351593, type 3 (EV_ABS), code 1 (ABS_Y), value 82 Event: time 1615892603.351593, type 3 (EV_ABS), code 2 (ABS_Z), value 39 Event: time 1615892603.351593, ————– SYN_REPORT ———— Event: time 1615892603.355607, type 3 (EV_ABS), code 1 (ABS_Y), value 81 Event: time 1615892603.355607, type 3 (EV_ABS), code 2 (ABS_Z), value 41 Event: time 1615892603.355607, ————– SYN_REPORT ———— Event: time 1615892603.359583, type 3 (EV_ABS), code 1 (ABS_Y), value 79 Event: time 1615892603.359583, type 3 (EV_ABS), code 2 (ABS_Z), value 56 Event: time 1615892603.359583, ————– SYN_REPORT ———— Event: time 1615892603.363586, type 3 (EV_ABS), code 1 (ABS_Y), value 75 Event: time 1615892603.363586, type 3 (EV_ABS), code 2 (ABS_Z), value 64 Event: time 1615892603.363586, ————– SYN_REPORT ———— Event: time 1615892603.367586, type 3 (EV_ABS), code 2 (ABS_Z), value 70 Event: time 1615892603.367586, ————– SYN_REPORT ———— Event: time 1615892603.371578, type 3 (EV_ABS), code 1 (ABS_Y), value 76 Event: time 1615892603.371578, type 3 (EV_ABS), code 2 (ABS_Z), value 79 Event: time 1615892603.371578, ————– SYN_REPORT ———— Event: time 1615892603.375607, type 3 (EV_ABS), code 2 (ABS_Z), value 86 Event: time 1615892603.375607, ————– SYN_REPORT ———— Event: time 1615892603.379609, type 3 (EV_ABS), code 1 (ABS_Y), value 71 Event: time 1615892603.379609, type 3 (EV_ABS), code 2 (ABS_Z), value 95 Event: time 1615892603.379609, ————– SYN_REPORT ———— Event: time 1615892603.383609, type 3 (EV_ABS), code 2 (ABS_Z), value 106 Event: time 1615892603.383609, ————– SYN_REPORT ———— Event: time 1615892603.387606, type 3 (EV_ABS), code 1 (ABS_Y), value 69 Event: time 1615892603.387606, type 3 (EV_ABS), code 2 (ABS_Z), value 114 Event: time 1615892603.387606, ————– SYN_REPORT ———— Event: time 1615892603.391578, type 3 (EV_ABS), code 2 (ABS_Z), value 116 Event: time 1615892603.391578, ————– SYN_REPORT ———— Event: time 1615892603.395576, type 3 (EV_ABS), code 2 (ABS_Z), value 120 Event: time 1615892603.395576, ————– SYN_REPORT ———— Event: time 1615892603.399605, type 3 (EV_ABS), code 2 (ABS_Z), value 124 Event: time 1615892603.399605, ————– SYN_REPORT ———— Event: time 1615892603.403600, type 3 (EV_ABS), code 1 (ABS_Y), value 67 Event: time 1615892603.403600, type 3 (EV_ABS), code 2 (ABS_Z), value 128 Event: time 1615892603.403600, ————– SYN_REPORT ———— Event: time 1615892603.407572, type 3 (EV_ABS), code 1 (ABS_Y), value 65 Event: time 1615892603.407572, type 3 (EV_ABS), code 2 (ABS_Z), value 136 Event: time 1615892603.407572, ————– SYN_REPORT ———— Event: time 1615892603.411571, type 3 (EV_ABS), code 2 (ABS_Z), value 143 Event: time 1615892603.411571, ————– SYN_REPORT ———— Event: time 1615892603.415601, type 3 (EV_ABS), code 1 (ABS_Y), value 66 Event: time 1615892603.415601, type 3 (EV_ABS), code 2 (ABS_Z), value 151 Event: time 1615892603.415601, ————– SYN_REPORT ———— Event: time 1615892603.419595, type 3 (EV_ABS), code 1 (ABS_Y), value 63 Event: time 1615892603.419595, type 3 (EV_ABS), code 2 (ABS_Z), value 155 Event: time 1615892603.419595, ————– SYN_REPORT ———— Event: time 1615892603.423598, type 3 (EV_ABS), code 1 (ABS_Y), value 61 Event: time 1615892603.423598, type 3 (EV_ABS), code 2 (ABS_Z), value 159 Event: time 1615892603.423598, ————– SYN_REPORT ———— Event: time 1615892603.427568, type 3 (EV_ABS), code 1 (ABS_Y), value 58 Event: time 1615892603.427568, type 3 (EV_ABS), code 2 (ABS_Z), value 166 Event: time 1615892603.427568, ————– SYN_REPORT ———— Event: time 1615892603.431566, type 3 (EV_ABS), code 1 (ABS_Y), value 59 Event: time 1615892603.431566, type 3 (EV_ABS), code 2 (ABS_Z), value 172 Event: time 1615892603.431566, ————– SYN_REPORT ———— Event: time 1615892603.435592, type 3 (EV_ABS), code 1 (ABS_Y), value 57 Event: time 1615892603.435592, type 3 (EV_ABS), code 2 (ABS_Z), value 181 Event: time 1615892603.435592, ————– SYN_REPORT ———— Event: time 1615892603.439571, type 3 (EV_ABS), code 1 (ABS_Y), value 55 Event: time 1615892603.439571, type 3 (EV_ABS), code 2 (ABS_Z), value 187 Event: time 1615892603.439571, ————– SYN_REPORT ———— Event: time 1615892603.443588, type 3 (EV_ABS), code 1 (ABS_Y), value 49 Event: time 1615892603.443588, type 3 (EV_ABS), code 2 (ABS_Z), value 197 Event: time 1615892603.443588, ————– SYN_REPORT ———— Event: time 1615892603.447587, type 3 (EV_ABS), code 1 (ABS_Y), value 48 Event: time 1615892603.447587, type 3 (EV_ABS), code 2 (ABS_Z), value 206 Event: time 1615892603.447587, ————– SYN_REPORT ———— Event: time 1615892603.451538, type 3 (EV_ABS), code 1 (ABS_Y), value 46 Event: time 1615892603.451538, type 3 (EV_ABS), code 2 (ABS_Z), value 212 Event: time 1615892603.451538, ————– SYN_REPORT ———— Event: time 1615892603.455584, type 3 (EV_ABS), code 1 (ABS_Y), value 43 Event: time 1615892603.455584, type 3 (EV_ABS), code 2 (ABS_Z), value 221 Event: time 1615892603.455584, ————– SYN_REPORT ———— Event: time 1615892603.459559, type 3 (EV_ABS), code 1 (ABS_Y), value 38 Event: time 1615892603.459559, type 3 (EV_ABS), code 2 (ABS_Z), value 231 Event: time 1615892603.459559, ————– SYN_REPORT ———— Event: time 1615892603.463560, type 3 (EV_ABS), code 1 (ABS_Y), value 31 Event: time 1615892603.463560, type 3 (EV_ABS), code 2 (ABS_Z), value 244 Event: time 1615892603.463560, ————– SYN_REPORT ———— Event: time 1615892603.467550, type 3 (EV_ABS), code 1 (ABS_Y), value 25 Event: time 1615892603.467550, type 3 (EV_ABS), code 2 (ABS_Z), value 255 Event: time 1615892603.467550, ————– SYN_REPORT ———— Event: time 1615892603.471558, type 3 (EV_ABS), code 1 (ABS_Y), value 17 Event: time 1615892603.471558, ————– SYN_REPORT ———— Event: time 1615892603.475574, type 3 (EV_ABS), code 1 (ABS_Y), value 8 Event: time 1615892603.475574, ————– SYN_REPORT ———— Event: time 1615892603.479584, type 3 (EV_ABS), code 1 (ABS_Y), value 0 ABS_Y first jumps down to 80 then even further, only if I simultaneously wiggle the stick I can counter this effect a bit. In the scenario above It ends with ABS_Y being 0, so the stick is claimed to be at maximum upwards position. Is something miswired?
Hi, This problem is usually cause by dirt in the potentiometer that is responsible for up and down movement on the joystick. If cleaning it doesn’t work, it probably need to be replace. This video should help you out to do your repair : https://youtu.be/RcIza5Zz8qY
