I have no idea where to post this, I assumed…since its a gaming mouse, the gaming linux community would be appropriate, Apologies if I am mistaken.
I have a g502 hero, and it is giving me no end of grief… namely with regards to the DPI settings.
First and foremost, it just randomly resets itself to an absurdly high DPI
I use Piper, since everything I’ve found online says Piper works great for g502 mice on linux, and while I can use it to set the colors of the LEDs… the DPI settings just don’t stick.
I’ve tried setting all the DPI options to the same DPI I prefer, Doesnt work. I’ve tried disabling all the DPI settings except one, and doesnt work. I’ve even tried running piper via sudo and the DPI settings still don’t change on the mouse (they change in Piper, though)
It seems like nothing I can set, as far as DPI goes, works. I know it is communicating with the mouse cause, like I said, I can change the LED colors and button configs… but the DPI settings just wont stick, and worse, randomly change.
and I know, I say random, and some people might thing I’m accidentally hitting the resolution up button since its right there next to m1, but I’m not. I can have the DPI set, via the DPI up/down buttons on the mouse, then get up and walk away… and when i come back, its back at absurd meth speed again.
Its genuinely not only driving me nuts, but really screwing with my ability to play games.
If anyone has any suggestion or solution, can you please share them with me?
If you got this far, then thankyou for reading this half rant half, half tech plea.
My g502 mostly works okay in mint with flatpak piper, but did have a bug that would swap default and sniper DPI every time I switch profile. Fixed by removing all profiles and creating new ones from scratch. Another thing, try and do a firmware update with the official logitech software in a VM or in a windows machine.
I’m unsure if this is related, but I’ve had some small issues with settings getting “stuck” in the Piper GUI and just not translating well to the actual device.
To fix this, use the underlying ratbagctl program in the terminal to clear out the DPI settings on the mouse itself. This only needs to be done once and the next time you open Piper it should read from the mouse and clear whatever GUI issue you were having,
ratbagctl list ratbagctl screaming-chipmunk profile <PROFILE_NUMBER> dpi set <DPI_VALUE>
Replace screaming-chipmunk with whatever your device is listed as from
ratbagctl list
, it’ll be something similar. Hope that helps!I have had problems with mine and my only solution was to make a virtual machine with windows and use the official Logitech software to change my buttons and dpi and save It to the mouse. Absolutely nothing else I found that works for me. I’m also on a steam deck so I Piper didn’t really work or solaar either.
Boot up into windows, create profiles switch to onboard mode and select said profiles.
Sadly Ive yet to find anything that works except this
// Solar can change dpi but if you change dpi on the mouse it goes back to default
Beat me to it, exactly what I do with the exact same mouse, only needs to be done one time, and your are gtg!
Also, man the Logitech software is just god awful. Good mouse though for the money
Btw, a VM (eg. in QEMU) works just as well. You only need to pass through the USB device itself, so it won’t be accessible anymore to the host device, so have a second mouse at hand (or learn to control QEMU fully with the kb)
The VM is what I’m doing, it works well for the rare times I need to adjust something. Piper works good for everything else. I just use Gnome Boxes for my VM though. It’s pretty easy to pass USB input into it temporarily.
Same with QEMU
Sounds good! I don’t have a lot of experience with plain QEMU, so when you mentioned needing a second mouse I thought maybe it was a bit more complicated to do the passthrough.
You’ll usually use QEMU through virtmanager on desktop, and there (and also when using QEMU manually afaik), you have a menu option “Virtual Machine”, and there “Redirect USB Device”. The main problem is that this hard-redirects the USB-Device itself, so the host can no longer interact with it. So to end it, you either need a second mouse to navigate the menu, or need to do it via KB. There’s also the option to add the passthrough and end passthrough via the command line on the host, so you don’t need to navigate through the menu. That’s easier on my setup because switching to another workspace prevents QEMU from grabbing the KB again easily.
Have you tried Solaar?