I bought a G915 X keyboard a short while ago and it seemed to work properly until very recently under the following conditions:
Logitech GHub closed completely or to systray
Windows 11 Dynamic Lighting off
Connected either by cable or by Lightspeed connection
In the later case it would go idle after a couple of minutes (which is great) and relight on keypress and continue with the light scene. I was happy with that.
However, a few days ago, I started to experience sporadic issues in wireless mode. I think it might have started with the recent big update which included scene previews?
The problems are:
There’s no device “G915 X LS” anymore but only a generic USB receiver icon and something like “Logitech Device”. The corresponding LED display (in “Layout”) does hint at a keyboard but there are way less LEDs and their layout seems strange.
Sometimes, the lighting effects would simply stop. Restarting SignalRGB sometimes does the trick but it’s not reliable.
After going idle and switching the LEDs off, there’s a high chance that the lighting will not restart after keypress anymore resulting in a similar scene as above.
Please note that this behavior is sporadic and happens quite often but there are still times when everything is behaving properly. At least for a while.
As soon as I attach the cable the keyboard is displayed properly in SignalRGB as “G915 X LS” again and can be used correctly. However, the problem reappears as soon as I disconnect the cable again.
I haven’t found a reliable workaround but fiddling with keyboard on/off and SignalRGB restarts and cable connect/disconnect sometimes helps.
Any advice would be much appreciated.
Thank you and best regards.
edit: I just realized that the generic “Logitech Device” is available as soon as the Lightspeed dongle is attached. It’s not a “replacement” for the actual “G915 X LS” entry. I therefore now assume that the G915 X is not recognized as connected and thus goes dark after some time?
I also have a G915 X LS and first encountered this issue yesterday and I think the solution may be to keep typing on the keyboard until it goes from the default rainbow lighting to whatever Signalrgb lighting you have set up. It took less than 10 seconds for it to work for me, and has worked for me twice so far.
If that doesn’t work, close Signalrgb and open LGHub. Then close LGHub along with LGHub in the hidden icons. Open Signalrgb and type randomly.
Make sure LGHUBUpdaterService and logi_lamparray_service are deactivated in the services section of the task manager while Signalrgb is active or the keyboard lighting will turn off after a few minutes. You do need LGHUBUpdaterService to be active for LGHub to open, so activate it when you need to open LGHub and deactivate it after you close LGHub for Signalrgb to work properly. Hope this works for you too.
Thank you for your suggestions. I tested them after the issue appeared just now.
Continuing to type for a up to 30s doesn’t fix the issue, sadly. The keyboard remains unlit.
Closing SignalRGB, then starting/closing Logitech Hub, then start SignalRGB doesn’t help either.
Disabling the said services didn’t change a thing as well.
That being said: after having typed for approx. 5 minutes without actually fiddling mit SignalRGB or anything light-related, the keyboard suddenly lit up again with the expected RGB settings. But only to go dark after a while once more…
Very annoying. (Especially, as the keyboard keys are barely readable without lighting. Which is, ofc a Logitech issue.)
I just did some more tests and the fix I recommended still worked for me. After startup, wait for Signalrgb to start working for all other rgb components. Then type randomly like you’re writing a letter and it worked in less than 10 seconds. It may take longer to work, but so far this has been what I have observed.
One thing I didn’t mention before is in addition to the 2 services being disabled, On-Board Memory mode has to be turned off in LGHub. This may be what is making the lights turn off after a while. To turn it off go into LGHub and click on the square with 12 lines sticking out of it, 3 lines on each side. In addition, make sure the keyboard is configured to the following in LGHub:
-Low Battery Mode: Auto
-Set to Breathing Red
-Effect: Dim Active Effect
-Brightness: 50%
-Start After: Never
-All Lights Off After: Never
To make matters worse, I have a Logitech G502X Plus LS and in LGHub On-Board Memory Mode is supposed to be on for it to work with Signalrgb. Gotta love LGHub and it’s buggy nature.
First of all: thank your for your efforts and detailed instructions. In the meantime, I discovered the Discord channel and at least one other person with the same issue. I was then told that SignalRGB is aware of this issue and their development is on it. So… fingers crossed!
Regarding workarounds: pnboard-memory is inactive for my keyboard, so that’s something. If I disable every Logitech related service it kinda works as it doesn’t appear to go to idle anymore at all. So there’s no issue with wake-up anymore but it eats a lot of battery.
Which is kind of strange as you’re saying that in your keyboard is going idle with your settings? Otherwise it wouldn’t wake up?
(I have the G502 but as it’s connected via cable I’ve never had any issue. Didn’t touch it, too, just to be safe )
Glad I could be of help. In regards to the battery, it may be related to the charging source. I know my mouse had some serious battery drainage because of this. I was charging it from my power strip, but then bought a cable that could reach to the back of my computer and so far the battery life has been much better. I haven’t needed to charge it for almost a week and it reads 70% at this point.
My keyboard on the other hand is charged through the power strip and I haven’t had any issues with the battery draining heavily. That’s pretty much the reason I went with Logitech over other brands. Just not a fan of the buggy nature of their software and how it contributes to the battery draining more than it should, among other things.
Something I noticed just jow is the following pattern:
Start Windows which autostarts SignalRGB and (in theory as it doesn’t appear in systray): Logitech Ghub.
The keyboard appears as generic “Logitech Device” in SignalRGB. Its RGB also only shows the Logitech default pattern.
I now start the Logitech Logitech Ghub explicitly resulting in:
The “Logitech Device” changes into the proper “G915 X LS”
The RGB effects start to play on keyboard
LGhub is killed immediately by SignalRGB
I assume that going to idle breaks things again afterwards.
To be honest: it does sound a lot like something you’ve mentioned before but either I didn’t quite get it then or there’s a difference between “straight after boot” and “later after idle” in my case.
(I’m actually quite curious why the LGhub isn’t available after boot despite autostart. Maybe it starts before SignalRGB and is then immediately killed by the later before there’s a chance to recognize the device type? I’m obviously just guessing.)
Regarding battery life: I prefer “idle” to be working in order to save battery, if possible.
But you say the battery life depends on the energy source which was used to charge beforehand? Haven’t heard anything like that before, wow.
Yeah, the Logitech software is more than annoying. I still haven’t figured out how to properly setup certain key configurations. Fortunately, it’s easy enough to use the Gx-keys with SignalRGB as they are all recognized as F13-F21 even in combination with modifiers.
Are you able to send us an email with your snapshot?
Right click the device in the devices list and select “Save snapshot”, then send that file to support@signalrgb.com
Sorry for the late reply. I’m going to prepare something and send it to you.
To be frank: I’ve experienced a couple of other, hardware related issues with this specific keyboard and I’m fed up with the product. I’m going to send it back for a refund so this issue will resolve itself - at least for me.
But if there’s anything I can help you with until then I’ll try to do so. Maybe it’ll help other users.
)