Keyboard RGB turning off after a few minutes on USB 2.0

[Brionac95]

The Keyboard RGB turns off at random times (sometimes after a few minutes, other times after even an hour) when it's plugged to an USB 2.0 port. The keyboard still works while this happens, and it's possible to turn on RGB again via Wootility or by using Fn + Brightness Up/Down, or by changing profile.

So far I could only reproduce this issue on USB 2.0 ports, both on motherboard ports and on case's front ports. It doesn't seem to happen on USB 3.0 ports, but I didn't test this long enough to confirm it.

The issue happened on Windows 10 Pro 20H2, but as of now I'm on Windows 10 Enterprise LTSC 1809 and it doesn't seem that the issue is reproduceable. I'll keep this post updated if it happens on this Windows version as well.

EDIT: Seems it happens on Windows 10 Enterprise LTSC 1809, still on USB 2.0 ports. Now I'm gonna test the keyboard with USB 3.0 ports to see what happens. EDIT2: RGB lights turned off once after a Windows reboot, while on USB 3.0. During normal activity it still didn't happen, I'll keep this post updated.

This is my current build: CPU: Intel Core i9 9900K @ 3.60GHz (OCed to 5GHz) RAM: G.Skill F4-3600C16D-16GTZNC x2 (OCed to 3600MHz through XMP Profile) GPU: Gigabyte GTX 1070 Ti Motherboard: Gigabyte Z390 Aorus Master Rev. 1.0 SSD 1: Samsung 970 EVO Plus NVMe M.2 SSD 500 GB (MZ-V7S500BW) SSD 2: Sabrent 1TB ROCKET NVMe PCIe M.2 2280 (SB-ROCKET-1TB) HDD: Western Digital Caviar Blue 1TB PSU: Corsair RM750x

Keyboard Type: Wooting Two (ISO German) Wootility Version: 3.5.12 Keyboard Firmware Version: 1.29.3

[DarrenVs]

EDIT2: RGB lights turned off once after a Windows reboot

I have the same problem

Booting my Windows machine; my Wooting One in a USB2.0 port will almost always show 0% brightness until toggling between profiles or using brightness buttons.

[Brionac95]

EDIT2: RGB lights turned off once after a Windows reboot

I have the same problem

Booting my Windows machine; my Wooting One in a USB2.0 port will almost always show 0% brightness until toggling between profiles or using brightness buttons.

For me, it happened only once when rebooting Windows, but on USB 3.0 ports. Apart from that instance, RGB seems to work fine on USB 3.0, but on 2.0 it starts giving me the issue at random. So far I'm sure to say USB 3.0 is more stable with RGB.

[Brionac95]

So, a little update: I tried Wootility 3.6.7-beta, in which there was a firmware update that was supposed to fix this issue, to test how the keyboard would behave on 2.0 ports. It seems like the RGB turns off less often. It still happens, but whenever RGB turns off by itself, it turns back on after half a second or so. Definitely a step towards the right direction, but I think the issue seems to still be there.

For most of the time I had this keyboard, I used it on 3.0 ports, and so far I had no issues with RGB.

So, quick recap:

• RGB used to turn off on Wootility 3.5.12, but with the new firmware on Wootility 3.6.7-beta, it seems like whenever it turns off it turns back on again.
• The issue doesn't seem to happen on USB 3.0, except for one single instance in which the keyboard RGB didn't turn on on Windows 10 Startup.

[Rocky04]

Previously the Wooting had a problem to wake up correctly after sleep. It happened when the system put the device into sleep but haven't send the wake up properly. That was fixed later on by adding a fallback.

I have no insights but I assume the problem you mention that the LEDs are still off is related to the same mechanism. I assume Wooting has adding this fallback mechanism to the LED controller handling. Haven't got any confirmation if this is true. At least I have recommended this a while ago. This underlying problem would explain the behavior you encountered. The LEDs must go off when the system puts the device into sleep mode. But they should go on again when the sleep state is ended.

So I assume when you had this problem on a USB 3.X port the system was in sleep mode right before. I also assume that your system put the Wooting into sleep mode from time to time when the device in connected to a USB 2.0 port. To prevent this you need to disable the power savings for the Wooting. Go to the device manager and unmark the option that the system can put the Wooting device into sleep.

Also it can be that the port don't provide enough power, the Wooting is very power hungry on full brightness. But then you should hear the USB dis- and connect sound and while this happens the keyboard don't work. Like this can easily happen on a USB hub which isn't active.

[PastaJ36]

So, a little update: I tried Wootility 3.6.7-beta, in which there was a firmware update that was supposed to fix this issue, to test how the keyboard would behave on 2.0 ports. It seems like the RGB turns off less often. It still happens, but whenever RGB turns off by itself, it turns back on after half a second or so. Definitely a step towards the right direction, but I think the issue seems to still be there.

For most of the time I had this keyboard, I used it on 3.0 ports, and so far I had no issues with RGB.

So, quick recap:

• RGB used to turn off on Wootility 3.5.12, but with the new firmware on Wootility 3.6.7-beta, it seems like whenever it turns off it turns back on again.
• The issue doesn't seem to happen on USB 3.0, except for one single instance in which the keyboard RGB didn't turn on on Windows 10 Startup.

Thanks for confirming. The fix was mostly focussed on ensuring we reset the brightness when awakening from sleep. Before it could happen if the keyboard would get multiple sleep/awakes it could be awake, but with brightness still set to 0.

Now for your USB 2.0 it sounds like it's getting sleep commands, but is now awakening from it correctly? Do you have similar "flashing" behaviour with other devices on that port?

[Brionac95]

Thanks for confirming. The fix was mostly focussed on ensuring we reset the brightness when awakening from sleep. Before it could happen if the keyboard would get multiple sleep/awakes it could be awake, but with brightness still set to 0.

Now for your USB 2.0 it sounds like it's getting sleep commands, but is now awakening from it correctly? Do you have similar "flashing" behaviour with other devices on that port?

A little late, but to answer what you asked, I never had any issues with other RGB devices, my old Keyboard (Logitech G810 Orion Spectrum) worked just fine, and never experienced this issue with it. My Logitech G Pro X mouse turns off after a while, but it's intended to do so in my Logitech G Hub profile.

I also noticed that after the beta firmware update, sometimes the keyboard turns itself on when the pc is turned off, which didn't happen before the update. I can fix this by disabling the USB power on option in the BIOS, problem is that it doesn't seem I can find it. Other keyboards I had didn't turn on when the pc was off though, so I don't know what's happening here.

To prevent this you need to disable the power savings for the Wooting. Go to the device manager and unmark the option that the system can put the Wooting device into sleep.

I already tried, but it seems like it didn't solve my problem.

[Brionac95]

It has been a while, but I wanted to wait a little before posting again to be sure of the issue.

After that Wootility 3.6.7-beta update, the RGB issue fix seemed like it worked, but there's still something that's not right with it. RGB still turns off, but it immediately turns back on after less than a second.

I can also confirm again that sometimes the keyboard turns itself on when the pc is turned off, which didn't happen before the update.