-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aerox 3 wireless - Color's are not saving #191
Comments
Sadly, this is not a bug: on newer devices, colors are not saved anymore in the mouse memory... So it get back to the default (that can be a rainbow effect or off) :( I will have to find a way to restore it automatically at startup, at wake up and when the device is plugged in... |
Damn that's sad. I'm just used to mice storing lighting in memory. Thanks for letting me know on that. |
Is there a way to run rivalcfg as a daemon, so whenever the computer wakes up, or the mouse reconnects, the commands run again? I'm having the same issue, so I created a bash script to reset the color options (that runs at startup), but I'm not sure how to make it run whenever the mouse reconnects or the computer wakes up from idle. |
It is possible to run a command when a specific device is plugged to the computer using udev:
But I do not think it will work for the wireless mice that wake up after IDLE as the USB dongle is never disconnected from the computer. |
Can confirm that this option is working on Aerox 3
Originally posted by @flozz in #195 (comment) This issues should be marked as closed |
Thank you for the feedback :) |
Bug description
RGB color selections is not saving.
What happened
Changing colors seems to be fine at first but when the mouse disconnects or when the USB dongle disconnects, the RGB colors go back to what it was before.
What was expected
Turning off/disconnecting the mouse, and the colors stay the same before turning off/ disconnecting the mouse.
Step to reproduce
Change the z1, z2, and z3 colors to whatever. Turn off the mouse and watch rainbows come back.
→
System information
The text was updated successfully, but these errors were encountered: