You are not logged in.
What? Do you have any logitech sources for that? No offense, but that sound insane.
An analog signal is any signal produced by a physical phenomenon. Bluetooth, Wi-Fi, Radio and other similar technologies are all analog signals received by the creation of radio waves and lightspeed logitech including, it by definition cannot be digital. Basic physics
If the cause is found, I'll report it in the next post
Offline
No, that is EM radiation.
The *signal* is gonna be digital and it will not distort because you're increasing the digital volume at the source would create soem analog noise or whatever you're fantasizing there.
And when everythign is set right, the speakers would send the key event to the OS and the OS sends a "go louder" signal back to the speakers - nothing more.
Offline
No, that is EM radiation.
Any radio wave is electromagnetic radiation, it all depends on the frequency. So is infrared radiation, X-rays or microwave radiation, and even ordinary visible light that enters our eyes. The concept of electromagnetic radiation is very large, but it is all a stream of photons and so is a radio wave.
And digital signal is just a representation of analog in computer, nowadays of course more often binary representation. A signal in real life cannot be digital, it can only be converted to analog to transmit.
Offline
That frankly makes no sense in the context we are dealing with.
On topic, FWIW I see two candidates here, systemd 257 changed handling of F20 function keys, maybe a fallout from that, or the libinput 1.27 release.
Offline
maybe a fallout from that, or the libinput 1.27 release.
Yeah, I think libinput has something to do with it, I remember borrowing it while I was setting up the DualShock
P.S Once again, I am new to Linux/GNU in general, and do not use many popular tools like systemd. What is it? )
P.P.S I get it, it's a basic component, sorry)
still over bluetooth the headphones do not integrate as HID and I can control the volume of the headphones (Profille: High Fidelity playback Codec: SBC).
evtest lightspeed headphone:
/dev/input/event15: Logitech G series G435 Wireless Gaming Headset Consumer Control
/dev/input/event16: Logitech G series G435 Wireless Gaming Headset
/dev/input/event17: Logitech G series G435 wireless gaming headset
/dev/input/event18: Logitech G series G435 Wireless Gaming Headsetevtest bluetooth headphone:
/dev/input/event31: G435 Bluetooth Gaming Headset (AVRCP)from event15 just come XF86AudioRaiseVolume
Event codes are different between event31 and event15, although they should be essentially the same, event31 has fewer of them
Last edited by sparr0w (2024-12-17 23:08:54)
Offline
The solution has been found - independent key binding
Instructions for Hyprland:
1. Install alsa-utils
2. Use alsamixer to find out the ID of the card (in this case G435 headphones) and the name of the volume control (in my case - 'G435 Wireless Gaming Headset Playback Volum').
3. Enter vim at the path
.config/hypr/hyprland.conf4. Add the lines
binde = , XF86AudioRaiseVolume, exec, amixer -c [ID card] -- set 'G435 Wireless Gaming Headset Playback Volum' 17.5+and
binde = , XF86AudioRaiseVolume, exec, amixer -c [ID card] -- set 'G435 Wireless Gaming Headset Playback Volum' 17.5-Done, the buttons are once again tied to the audio control on the headphones.
This can be done with Xinput or any other key binding tools
Offline