Shouldn't the driver reinterpret a change in the state of the button as a momentary press of KEY_MICMUTE, observing that a change in state happens when the user actually presses the button? Then the button would work as expected with software that supports that keycode.
Announcement
Collapse
No announcement yet.
Google Hangouts Meet Speakermic Getting A Linux Driver To Address Mute Button Quirk
Collapse
Comment