Sustainability Navigation

MX Keys volume keys stick

Answered

Comments

65 comments

  • Official comment
    Balaji P

    Hi Dennis, thank for reaching out and sorry to hear about the experience with Logitech product. We apologize for delay in response. Kindly click on the troubleshooting link provided below and try the steps, this below article has helped our customer's to resolve their issue.

    Button troubleshooting: https://support.logi.com/hc/articles/360023371053-Keyboard-Mice-Buttons-or-keys-do-not-work-correctly

    Thank you so much, and looking forward for your response.

    Comment actions Permalink
  • Brian Fournier

    I am having the same issue.

    9
    Comment actions Permalink
  • Kevin Van Cott

    Thank goodness I am not the only one. This happens to me too. So far I have noticed it only when using my unifying receiver. What happens is that I'll press the volume up key a few times, and all of a sudden it will go all the way up to 100, and it won't let me go down until I turn the keyboard off and on again. Same things happens if I press the volume down key a couple times. It will go all the way to 0 and then I won't be able to get it back above 0 until I restart the keyboard again. It is acting like someone is holding the keys down. To be clear, this is not a physical problem. It is definitely a software bug. My Logitech options software says everything is up to date.

    3
    Comment actions Permalink
  • Dennis Campillo

    Hi Brian,

    Does your computer have Bluetooth capability? Since I switched the keyboard to Bluetooth instead of the receiver, I haven't had the problem recur at all in over a week (before, it was happening once or twice a day).

    I've experimented to see if I can get the keyboard to work with the receiver correctly by switching from USB 2 to USB 3.1 Gen 1 and Gen 2, but still haven't had any luck. I have the ability to up the voltage slightly on my USB ports, which may help, but I don't want to void my warranty if anything should go wrong.

    Unfortunately, I get the feeling that it's going to require a firmware update to the receivers to fix this issue. But I'm not sure if Logitech even knows this issue exists, since I don't think they check these forums very often.

    2
    Comment actions Permalink
  • Jason Zenowski

    I am having the same issues as stated above. I will also update firmware and monitor results as I do not have Bluetooth and need to rely on the Unifying Receiver.

     

    *edit* Thanks for the suggestions!

    2
    Comment actions Permalink
  • Dennis Campillo

    Hi Jason,

     

    Unfortunately, the firmware update did not resolve the issue. The problem has recurred multiple times today. So, I went ahead and opened a ticket with support. I'll continue to update this thread with anything I learn.

    2
    Comment actions Permalink
  • Tim Neumann

    This seems to be a firmware bug in either the keyboard or the receiver.

    I don't know for sure if this is related, but check this out.. When the keyboards is powered on, it has its factory configuration loaded. You can tell by pressing a with Logitech Options configured key within a second of turning on the keyboard. It will perform the standard command, not the newly assigned one. For example, I configured the lock button in the upper right corner to open the Action Center in Windows. But if I press it within a second of when the keyboard is powered on, the PC will actually lock, the factory assigned command. If you keep either of the volume buttons pressed down during the time the user configuration seems be to getting loaded, it will get stuck until you power off the keyboard. This is almost 100% reproducible. Turn keyboard off, turn on, immediately keep either volume up or down pressed for 1 or 2 seconds, the key will get "stuck" in almost all cases. Only the configurable keys seem to be affected.

    The keyboard could be waking up from some kind of deep sleep mode, maybe the processor was switched off completely, and thereby trigger this bug if the user presses one of the volume buttons (or other configurable ones) during this time. This would also explain why rebinding the volume buttons seems to help, since the functionality only is available after the user configuration has already been loaded. I've noticed that the volume keys sometimes didn't respond right away when the bug appeared, which fits the theory nicely that the device was rebooting or waking up during that moment. Changing to Bluetooth might avoid the bug due to a different way of loading the user config.

    This, however, makes me wonder why RMAing fixed the problem for the OP. Maybe the affected keyboards have a defect that causes them to sometimes reboot/reload config when waking up.

    Dennis, what's the firmware version of your new keyboard and receiver? Is it the same?

    Did you change anything else? Like e.g. did you bind keys differently, use a different USB port, or remove another Logitech receiver, etc.?

    2
    Comment actions Permalink
  • Karl2862

    Hi Tim, I can confirm what you are describing is true for my keyboard also.

    The bug typically occurs when I haven't typed anything in a minute or so, then go to change the volume. I usually notice a delay before the command is processed then the 100% vol loop begins.

    I tried switching the vol up & down keys so that at least if it looped it would decrease the vol to 0% rather than 100%, but as you say, the keyboard reverts to its default hardware setting for a short period while it comes out of its sleep state. For a keyboard this expensive, its a joke that custom key commands are not stored in onboard memory on the keyboard.

    The lag when it comes out of the sleep state is also unacceptable. I've been using a Dell wireless keyboard at work for the last 2 years and it does not experience any of these issues.

    I raised this bug with support, would encourage you to do the same.

    MX Keys firmware ver: 012.000.00011
    Unifying Receiver firmware ver: 012.011.00032

    I have also updated firmware using this tool https://support.logi.com/hc/en-au/articles/360035037273 and the bug still occurs.

    2
    Comment actions Permalink
  • Kyle VanWagner

    I'm also having this issue on two separate MX Keys keyboards, one at home and one at work. Can confirm it's likely that this happens after hitting the volume key having not typed anything else in a while.

    2
    Comment actions Permalink
  • Karl2862

    Good to hear a new keyboard has resolved your issues Dennis. Unfortunately, Logitech are telling me there is no available stock they can offer me for replacement, and no ETA, so I'm stuck with occasional volume shocks loud enough to wake up the neighbour hood.

    1
    Comment actions Permalink
  • Dennis Campillo

    As a workaround, before receiving the replacement keyboard, I found that connecting via Bluetooth resolved the issue. Another trick that worked for me was remapping the volume up/down function to different keys (I used the brightness up/down on F1 and F2)

    1
    Comment actions Permalink
  • Tim Neumann

    Karl,

    thank you for replying.

    The firmware on my keyboard is the same, my Unifying Receiver is on version 024.011.00036. Both are up-to-date according to the updater you mentioned, and also according to the Logitech Unifying Software (you can download it from the Logitech website or use the one built into Logitech Options, as Dennis described earlier).

    I can also confirm that the configuration most likely isn't stored on the keyboard itself. I had suspected it, and further testing with my laptop produced predictable results. This perfectly explains why the issue worsened while the receiver was plugged into the back of my PC - not more than an arm length away from the keyboard, I have to add.

    I've already contacted customer support. However, since the whole issue seems to boil down to more than just a bug, I'm likely going to refund my MX Keys entirely. I would be willing to try a replacement though, since it's possible that our units have some sort of underlying issue, which e.g. might cause it to lose connection and thereby redownload the config when it normally wouldn't do that. That would also explain the lag you are talking about.

    I've just noticed, while typing this, that the Logitech Unifying Software logo (the orange star thing that is printed on the receiver) just popped up for 2 seconds. I think it has done that before. I wasn't sure though, since it was gone so quickly. Maybe there really is an issue with our specific units that causes reconnects.

    1
    Comment actions Permalink
  • Mario

    Tim Neumann, i have the same issue and tried a few things to get rid of the problem. What i found is, that the problem does not occur if the "Options Software" is not installed. Had it uninstalled for 2-3 weeks and it doesn´t happen in this time. Now with your finding it makes perfect sense, so i want to add one more condition to trigger the bug:

    - A 'Unified Receiver' is being used

    - The keyboard is reconnecting (waking up)

    - One of the media volume buttons is being pressed down

    - Logitech Options installed

     

    This gives me hope that it can be solved via software.

    1
    Comment actions Permalink
  • Mario

    The disconnection after ~5 minutes is normal. I tried my old K800 keyboard and it does the same, but without any problems. The K800 is controlled by Setpoint, so i think the problem is caused by Logitech Options.

    I also did a small test with my MX Master mouse, which is also controlled by "Options" and it does the same as the keyboard. For 1 second or so, after deep sleep or turning on, it performs the standard command instead of the assigned command.

    Looks like it takes a second for Options to take control over the devices.

    1
    Comment actions Permalink
  • Massimo

    Hi,

    I have the same issue. But I want to add a detail that go against the assumption I read before: the issue appear not only after a "sleep", sometimes after few consecutive tap on volume keys.

    M

    1
    Comment actions Permalink
  • Karl2862

    I'd recommend everyone submit a support ticket describing the problem and a link to this thread. There's enough information here for engineering to reproduce the issue.

    I noticed there was a recent update for Logitech Options 8.10.84. Will start using my volume keys again to see if the issue is still happening.

    1
    Comment actions Permalink
  • Tim Neumann

    Yup, that sums it up pretty well. Plus the Logitech online store provider in the EU (Digital River Inc.) is currently violating EU regulations by providing false information in their cancellation policy and ignoring/refusing any refund requests via the address provided, which is mind-boggling.

    For everyone who doesn't want to read trough all these posts - you currently have 2 options to get around the issue:

    A) Uninstall Logitech Options or

    B) Use Bluetooth.

     

    1
    Comment actions Permalink
  • Eldin Didic

    I can confirm that removing the Logitech Options software resolves the issue - it has now been uninstalled for solid a week now with no issues on volume adjustments. Yippee, who would have thought?...

    I no longer volume adjust "in concern" that I will go deaf and that waking up my neighborhood is a high probability.

    Props to Tim Neumann for the suggestion, worked a treat mate.

    I opened a support ticket back in December, and it took only two and a half months to get a complete refund (not that I was after one - but it was offered), I was also offered alternative product replacements that I refused politely to - I feel like this is their best made keyboard to date.

    I now own a completely working MX Keys keyboard for free, thanks to a software bug, which I actually wish never existed in the first place to be perfectly honest.

    Dear Logitech - a software fix should correct the issue for all your beloved MX Keys customers :)

    1
    Comment actions Permalink
  • Sphinx

    Max G, I have yet to see Logitech acknowledge a problem with any of their products, let alone come up with a solution.

    1
    Comment actions Permalink
  • Sphinx

    There is also widely reported problems with the scroll function on the MX Master 3 mouse.  Logitech have not acknowledged this issue either.  I would question they are a 'good brand'.  I would not buy Logitech again.

    1
    Comment actions Permalink
  • Tijmen Godfroid

    I am having the same problem, sometimes when I push the volume down button it get stuck, not mechanically but it keeps sending the message to the PC or so.

    I have made a Poll, maybe if everyone can fill this in, we can hand it over to Logitech?

    https://docs.google.com/forms/d/e/1FAIpQLSdlNDqiRBqbtcEU_FHaHw_RHortohgyePr0Z03jZrMthVJFVA/viewform?usp=sf_linkhttps://forms.gle/cSxmHKL9ecfvXN9g7 

    I also made a video of the problem. 

    https://photos.app.goo.gl/3CiUhaBYiF5pfhaS7 

    1
    Comment actions Permalink
  • Jonas Heylen

    Two weeks ago I also logged this issue and specifically requested to provide the proper information to the developers so it wouldn't just be stuck with the support staff. The reply I got:

    "I would like to inform you that the feedback is sent to the developers. However, we are expecting it to be fixed in our next software update."

    Fingers crossed they actually fix it this time. Unfortunately they could not provide a time window for the next update.

    1
    Comment actions Permalink
  • Sphinx

    I do not want to sound defeatist, but I can say with some confidence that Logitech will not fix this issue.

    I have the same problem in addition to scrolling issues on the MX Master 3 mouse and Logitech have made no attempt to fix any of the issues or even to fully admit that any issues exist at all.

    Same thing with ongoing issues with bluetooth speakers I have.

    I am voting with my feet and will never purchase another Logitech product.

    1
    Comment actions Permalink
  • Brian Fournier

    Yes my computer does have Bluetooth, I will try connecting it that way and see if it improves. It would be nice if they did follow the forums and make improvements based on feedback, we shall see.
    Thanks for the response.

    0
    Comment actions Permalink
  • Dennis Campillo

    I just discovered that there is a way to update firmware for the keyboard that I was previously unaware of (It's not very intuitive). But, I'm currently testing to see if it resolves the issue. Here is how to get to the update if you'd like to try it yourself. 

     

    1. In the Logitech Options software, click "Add Device" in the bottom left corner:

     

    2. Open the "Advanced Unifying App:

     

    3. When the Unifying App opens, click on "Advanced"

     

    4. Click on the device you wish to update on the left, then click "Update Firmware" on the right. Then follow the instructions. It'll have you turn off and on the device, then that should be it.

     

    I've switched my keyboard back to the receiver, and have been pressing my volume up and down keys repeatedly for a few minutes now and haven't had the issue recur yet, but I'll update this post with my results after a day or two.

     

    *******************************************************************************************

    Update: Unfortunately, this did not resolve the problem. It looks like it's back to Bluetooth for me. I'm not sure who to contact to escalate this to their development team since it most definitely seems like a software/firmware issue, but I'm going to try.

    0
    Comment actions Permalink
  • Jason Zenowski

    Thanks for your efforts with this Dennis!

    0
    Comment actions Permalink
  • Karl2862

    Hi Dennis, I have the same issue. Did you come to any solution with support?

    0
    Comment actions Permalink
  • Dennis Campillo

    Hi Karl,

    Sorry I haven't updated this sooner. I ran through the troubleshooting steps with support, but it still did not resolve the problem, so customer support recommended that I RMA the keyboard. I've had the new keyboard for about 2 - 3 weeks now, and haven't had the problem reoccur yet, so I'd considered this resolved on my end. I'd recommend opening a ticket and going through the RMA process as well. Support made it quick and painless.

    0
    Comment actions Permalink
  • chaoswing

    나도 아직 없어요.

    0
    Comment actions Permalink
  • Tim Neumann

    I had a look at the Logitech Options software and noticed that my keyboard frequently loses connection while not in use for a while (a few minutes sometimes), even though I'm very close to the receiver. This frequent reconnecting on wake-up is what causes the bug. The battery indicator LED and the LED in the key will light up if the keyboard is reconnecting when the proximity sensor fires. If the connection is already established, these LEDs will stay off.

    From our observations I conclude that the bug is being triggered if the following conditions are simultaneously met:

    1. A 'Unified Receiver' is being used.

    2. The keyboard is reconnecting (waking up).

    3. One of the media volume buttons is being pressed down.

    What remains to be determined is whether this frequent disconnecting, after being idle for as little as a few minutes, is intended behavior or the result of a hardware defect and/or faulty software.

    0
    Comment actions Permalink

Please sign in to leave a comment.