Jump to content
ArchWiki

Talk:Logitech MX Master

From ArchWiki
Latest comment: 13 June 2025 by Ribyn in topic Other Mice then MX Master affected

Getting the name of the device for logiops config

Latest comment: 17 March 2020 1 comment1 person in discussion

Probably, it's needed to be explained more accurately how to receive a device's name for logiops configuration. In my case when I run logid -v, I did not received any name in [INFO] strings of the output. But after I removed all paired devices from the unifying receiver (there were several mices and keyboards) via solaar, and then running logid -v again, it started to output detected devices normally:
[INFO] M720 Triathlon detected: device 4 on /dev/hidraw0
Also, I think you can get this name from solaar safely. But I am not sure.
Ashark (talk) 23:01, 17 March 2020 (UTC) Reply


Wayland Horizontal Wheel

Latest comment: 8 August 2020 1 comment1 person in discussion

I was able to macro the horizontal mousewheel in Wayland and Wine(which wasn't working with xbindkeys) by repurposing this bash script: https://github.com/mathportillo/wayland-mouse-mapper

#!/usr/bin/bash
event_type=EV_KEY
action_type=POINTER_AXIS 
scrolled="horiz"
readarray -t devices <<<$(libinput list-devices | grep pointer -B3 | grep -o '/dev/input/event[1-9]*') 
# COMMANDS MAP
HWHEEL_UP=(KEY_VOLUMEUP)
HWHEEL_DOWN=(KEY_VOLUMEDOWN)
function pressKey(){
 device=1ドル; key=2ドル
 evemu-event /dev/input/${device} --sync --type ${event_type} --code ${key} --value 1;
 evemu-event /dev/input/${device} --sync --type ${event_type} --code ${key} --value 0;
}
function pressCommand(){
 device=1ドル; wheel=2ドル; movement=3ドル
 if [ ${wheel} = ${scrolled} ]; then
 if [ ${movement} -gt 0 ]; then
 pressKey ${device} ${HWHEEL_UP}
 else
 pressKey ${device} ${HWHEEL_DOWN}
 fi
 fi
}
function parseEventLine(){
 device=1ドル
 action=2ドル
 wheel=6ドル
 movement=${7%%.*}
 # compute only if right action
 if [ ${action} = ${action_type} ] && [ ${movement} -ne 0 ]; then
 pressCommand ${device} ${wheel} ${movement}
 fi
}
function mapDevice(){
 device=1ドル
 while read line; do
 parseEventLine ${line}
 done < <(stdbuf -oL libinput debug-events --device ${device} & )
}
for device in ${devices[@]}; do
 ( mapDevice ${device} ) &
done
wait

Figured it might help some people. It's kind of a hacked together solution, catered to only my specific needs(it's technically possible to macro any button like this but I only needed the volume), so I'm not sure it's of the quality to post it on the main page. But figured it could still help someone. Unsure if it'll work on X or not. —This unsigned comment is by Gdishun (talk) 05:12, 8 August 2020‎ (UTC). Please sign your posts with ~~~~!Reply

Power section

Latest comment: 25 August 2021 1 comment1 person in discussion

Power section says you can get the battery life using Solaar and refers to Logitech Unifying Receiver which does not describe (that I can see) how to obtain battery life. —This unsigned comment is by Whitetigerswt (talk) 15:57, 25 August 2021 (UTC). Please sign your posts with ~~~~!Reply

Other Mice then MX Master affected

Latest comment: 13 June 2025 1 comment1 person in discussion

The wiki should be renamed, to be more generic because its not a MX Master only thing.

Im using the Logitech G903 LS, had the issue, and the post guidance fixed it for me. Ribyn (talk) 07:57, 13 June 2025 (UTC) Reply

AltStyle によって変換されたページ (->オリジナル) /