Mode change only works by restarting the operating system

[jorgetamayo21]

I have a setup with two modes, mode 1 for work and mode 2 for play, unfortunately when I switch to mode 2, even though the mode 1 buttons are demapped, the mode 2 buttons don't seem to load until I reboot the OS or until I disconnect and reconnect the mouse.

I am attaching my settings.ini

settings.ini.txt

[so1der]

Hello!
I tested it on my system, with my mouse, and unfortunately, it behaves the same.
When changing mouse mode via cli, its sends a package that official software sends as well. But if I had to guess, I would say that official software also restarts the mouse, so the user won't have to do it manually. Maybe because it's a complex HID device, with a keyboard functionality and etc. Unfortunately, I don't know how to implement this kind of restart into this script because it would need a root access, however You can google something like "how to restart USB device on Linux", but it's kinda messy solution IMO.
But as a workaround, I can suggest You to bind the seventh button (which is at the bottom of the mouse) as "change_mode" button. When the mouse changes mode by button, You don't need to reconnect it, as far as I can tell. Sorry if that's not what you wanted to hear :(

I also noticed some strange values in Your .ini file.

; This parameter sets speed for the "Neon" lighting effect
; Possible values are 1-3
neon_speed = -46

I encountered them as well with my mouse, but I still haven't figured out why they occur, as once this bug suddenly disappeared. I edited .ini file, You can upload this one if it's fine for You to change mode by button.
settings.ini.txt

[so1der]

Hello once again. So I tried to reset the mouse via pyUSB and via C script, and unfortunately, it did not lead to any results. dmesg says that the USB device was reset, but the keyboard-related part of the mouse (key combinations, macros, etc.) still not working without physically reconnecting the mouse. At this point I can't even guess why it doesn't work as it should. So for now the only solution to this problem is to use 'change_mode' button.

[so1der]

Hello again! I finally find some sort of solution! With root access we can "reattach" usbhid module. In this case, this module will poll USB devices again, and gain new information about mouse, or something. It can be done with this simple bash script:

#!/bin/bash

sudo modprobe -r usbhid
sudo modprobe usbhid

with option -r we removing usbhid module, and after that - we loading it again.

But beware, You can't just enter those commands separately into terminal, since we removing usbhid module, You will lose ability to use HID devices - keyboard, mouse, etc (in my case, I still was able to use laptop keyboard though, but not a usb one). That's why bash script should be used, so it'll load usbhid module again. Or of course You can compose those commands with '&&', and paste them into the terminal:

sudo modprobe -r usbhid && sudo modprobe usbhid

Since those actions require root access, I don't know if I can implement them into 'm601' script.
I also don't know how it's affects other HID or USB devices, but in my case everything was fine.