Closed Susensio closed 1 week ago
When does the the reset happen? Is it after the mouse has not been used for a while?
Run Solaar as solaar -ddd
and post the output around the time that the problem happens. Also run solaar show
when you notice the problem.
When does the the reset happen? Is it after the mouse has not been used for a while?
Run Solaar as
solaar -ddd
and post the output around the time that the problem happens. Also runsolaar show
when you notice the problem.
The reset happens mid use, maybe when my computer is busier but It's never above 50% usage neither cpu nor ram.
diff solaar show
diff show_bad.txt show_good.txt
13c13
< Device activity counters: 1=206, 2=145
---
> Device activity counters: 1=165, 2=61
In both cases solaar show
shows the device DPI as 2300.
At 11:14:57 the mouse connects, probably because it was inactive. At this point the mouse DPI may be its default value. Solaar sets the value to 2300 at 11:15:01 as part of setting up the mouse. The delay is largely due to a timeout - Solaar sent a request to the device and did not receive an answer for several seconds.
The timeout may be due to some other program communicating to the device. Solaar saw about 20 responses from the device. These responses look similar to the responses that would be expected from the commands sent by the device driver.
This analysis would indicate that the problem occurs when the device reconnects after being inactive or the communications link to the device being down. Solaar communications to the device then sometimes are ignored causing a delay in Solaar setting the correct DPI. There isn't a Solaar bug then, just an unfortunate problem communicating with the device.
How can I debug the connection problem? The mouse was not inactive (I mean I was using it just before, so it does not went to sleep)
I expect that the reconnection is noted in the system log so you could look there to see if there are any patterns. The system log might show information relevant to the disconnection as well. You could also run Solaar as solaar -ddd
and look for lines like
2024-07-15 11:14:57,079,079 DEBUG [SolaarListener:hidraw0] logitech_receiver.notifications: <Device(1,4082,MX Master 3 Wireless Mouse,C4A67048)>: protocol 4 connection notification: software=True, encrypted=True, link=False, payload=False
but all that would get you would be the reconnection times.
There is something that is causing the reconnection, either in the mouse (low battery?), in the wireless connection (distance? interference?), in the receiver (loose connection?), or elsewhere (other loose connection?). It may be difficult to diagnose and the problem may even be a hardware fault internal to the receiver or mouse.
This is driving me nuts...
Let's recapitulate, things that I've tried and can be ruled out:
Things that I've yet to try:
- Keep the Mx Master 3 always connected to the power (battery issues?)
I've been working with the power cable plugged in for 2 days and the problem has disappeared! I'm going to find a new battery and try it out
Information
Linux 6.9.7-amd64 x86_64 GNU/Linux
solaar show
:~/.config/solaar/config.yaml
(or~/.config/solaar/config.json
if~/.config/solaar/config.yaml
not present):Describe the bug From time to time, the DPI configuration of my Mx Master 3 gets lost. This is noticeable because the mouse sudently moves slower than usual. If I open the solaar config, and cycle the DPI button from
(no changes) -> (ignore) -> (changes)
it usually comes back to normal. The log pasted shows the messages surrounding this event. It seems that connection is lost? IdkIt's been happening for weeks and I don't know how to go from here.
To Reproduce This failure shows up randomly several times a day. I've tried keeping the solaar config window open, with no luck. I've tried changing the usb unifying receiver from one port to another with no luck. I have another receiver but I could not get it to connect, I could not figure out the sequence