#Keys keep being registered after being released

1 messages · Page 1 of 1 (latest)

sand depot
#

My keys keep showing up and keep being registered after released

icy grottoBOT
# sand depot My keys keep showing up and keep being registered after released

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Hub or via email to social@wooting.io
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

All of these types of requests need to be made via the Wooting Hub or by emailing social@wooting.io directly!

tacit wing
#

Yup nod
@hoary forge

hoary forge
#

Just to check a few points:

  • Does this problem happen everywhere or only in-game? If so, which game?
  • Was there any recent change, like a firmware update, when this suddenly happened?
sand depot
#

everywhere

#

nope

#

it just strted a random day

#

i might have worn out the springs maybe?

hoary forge
#

is it localized to one switch or mutiple ?

sand depot
#

multiple

#

so far my most used keys like 1-5 w a s d f and other random keys

hoary forge
#

Hmm, just to check if it is a firmware issue, as there was a firmware update a while ago that changed how the hall sensor analog values are processed, you can revert back to firmware version 2.7.2 and see if there is any improvement.

To do this, you can launch Wootility, then:

  1. Go to Settings
  2. Select Updates
  3. Choose My Devices
  4. Select "Revert back"
sand depot
#

just reverted back

#

ill just spam the keys with issues

#

if this does fix it what should i do

#

never update?

#

its not happening now so far

sand depot
hoary forge
#

If that is the case and this fixes it, I'll give Simon a heads-up that there is another case of a known issue.

If you are okay with a bit of further data collection so we can see how the keyboard is processing the analog values, we would appreciate it. This would require using the "wooting-analog-monitor."

(sorry bit slow game/typing)

sand depot
#

its fine

sand depot
#

its right back to it

#

its getting stuck

hoary forge
#
  1. you can Download the software from #1196768306602983494 message.
  2. Once downloaded click on “wooting-analog-monitor.exe”
  • If you receive a notification that you are missing the "Wooting Analog SDK," you can download and install this software from our GitHub:
    https://github.com/WootingKb/wooting-analog-sdk/releases
    For Windows users, this will require the installation of wooting_analog_sdk-0.7.5-x86_64.msi
     
    Once installed try running the “wooting-analog-monitor.exe” again.
  1. Once the monitor software is running can you check for the behavior below and press the [Save Plot] to take Screenshots.
#

Hmm, can you try out that software still? It can help show what the keyboard detects and might help explain what is happening.

This seems a bit odd since it is affecting multiple multiplexers and switches, so it seems like it is internal power-related.

Just to double-check if you have attempted the following:

  • Lowering the global brightness to 0%
  • Differnt usb port
  • Differnt USB-C cable
sand depot
#

ill switch the usb port again

#

also everytime i open my wootility app it reconnected my keybaord?

hoary forge
#

was just to doublecheck

#

is there a disconnect warning like this in wootility?

sand depot
#

no

#

every time i open the app right

#

in the top right

#

it says like device found device being connected

hoary forge
#

like these ?

as this would be normal

sand depot
#

yeah

#

every time i open the app

#

just wanted to make sure it was normal

#

anything else we can test

hoary forge
#

can you try the "wooting-analog-monitor" software would be interested to see if there is some type of behavior that could explain the current issues

  1. you can Download the software from #1196768306602983494 message.
  2. Once downloaded click on “wooting-analog-monitor.exe”
  • If you receive a notification that you are missing the "Wooting Analog SDK," you can download and install this software from our GitHub:
    https://github.com/WootingKb/wooting-analog-sdk/releases
    For Windows users, this will require the installation of wooting_analog_sdk-0.7.5-x86_64.msi
     
    Once installed try running the “wooting-analog-monitor.exe” again.
  1. Once the monitor software is running can you check for the behavior below and press the [Save Plot] to take Screenshots.
sand depot
#

ill do that later cause it wont let me rn says may harm pc i can just do it later i took a screen shot of what you said anything else

hoary forge
#

The only test that wasn't conducted was the "RT-Display" test, which is to double-check if this problem is caused by the keyboard or by some software on the system.

Normally, I recommend the "RT-Display" test earlier than the "wooting-analog-monitor" as it is easier and as the "monitor" software is in development and hasn't purchased a certification, so it can trigger a warning from Windows/anti-virus.

If you wish to give it a go, I'll include the method to enable it.

To Enable the RGB effect “RT-Display” you can use one of the Two Methods
Method one:
importing the already created "(Test Profile) RT-Display" profile into wootility

  1. Copy the Code: d1c508f2450941b50a9c33b0468d5a20b5bc
  2. Click the "Import Profile" Button which can be found on the left side of wootility
  3. Select the newly imported Profile

Method Two:
To manually create or enable the effect, you can do the following:

  1. Select the "Color" Tab
  2. Under Effect layers, add or change the current effect to RT-Display
  3. For better visibility set Base Brightness to 0%
    Example image
sand depot
#

now what

#

i did method one

hoary forge
#

So, the RGB effect "RT-Display" will show the state of the switch: green if it is detected as pressed, and red if released.

In some circumstances, the keyboard could be working fine, but some software or issues on the system are causing the keys to be registered as "stuck."

Normally, I start off with this troubleshooting method as it is easier, but I kind of skipped a few steps.

sand depot
#

its doing green when pressed down red when going up

hoary forge
#

when the switch is detected as stuck by the system is the keyboard still showing green?

sand depot
#

no

hoary forge
#

ok.. this might not be a problem with the keyboard.
if it is working fine with the RGB effect

(Kinda wish i did not skip this step now)

sand depot
#

lol

#

what else could it be

hoary forge
#

A few points:

  • Drivers
  • Windows
  • Background applications
    • This tends to be the most common cause for these issues but havent heard of any that cause the input to latch on
sand depot
#

drivers all up to date

#

background applications are limited

#

i have none

#

well like none i wun 78 windoes processes

#

and 60 are windows/motherboard software

hoary forge
#

In this case, I would recommend that you use the keyboard on another system just to check if the problem is isolated to that system.

As for tests:

  • Non-Windows related background applications:

    • You can run the computer in "Safe Mode." This disables all non-Windows software running in the background that could be interfering with how the keys are being processed.
  • Driver & registry flush:

    • The keyboard uses common drivers that are preinstalled with any Windows Vista or above, but forcing a reinstall may fix it. This link goes through the process of flushing all drivers and registry files associated with the keyboard.
  • System:

    • This one is a bit tricky as it may involve repair and i dont tend to recommend it unless it other troubleshooting show no change and the problem is isolated to the system .
sand depot
#

after this is done what next?

hoary forge
#

when the system was in "Safe Mode" did it work normaly such as the system did not force the inputs to stay on ?

sand depot
#

i think i figured it out

#

sorry for the wait i took my keybaord apart and the usc is bent and the bottem of the board is a lil scratched

#

maybe it idk

#

everything thing else you have said to do just hasn;t worked might just get a new keybaord

hoary forge
#

just to check the RGB effect "RT-Display" dosnt show any problems of the key staying pressed after release?

sand depot
#

wdym?

#

oh no

#

it doesn't

hoary forge
#

Ah, I wasn't sure when you mentioned taking the keyboard apart; I thought I missed something was a bit confused.

But yeah, I'm not sure about system-side issues, as there could be many factors involved.

sand depot
#

imma just get a new keybaord tbh ive done everything and nothing works thanks for your help im sorry man

hoary forge
#

no problem

if you dont have the problem on anouther keyboard would be interested to know if there if there is something unquie to wooting keyboard that could be causeing this

sand depot
#

ok

#

ill let you know

hoary forge
#

👍

sand depot
#

@hoary forge i fixed it i bought new springs and opened all the switchs switch them out and now no issues

#

ive only had the keybaord for 6 months so very strange