What was up with that? Why did it do that?
I might be wrong, but I think that’s due to crappy mouse sensors/firmware.
With teams/idle checking, these days, I almost wish everyone had one of those to keep PCs active all the time.
You might be interested in these things called mouse jigglers, they range from a tiny USB dongle that simulates a mouse, to motorised movement pads that you can place under a real mouse, which would be undetectable by software.
PS: You’re welcome. ;)
Just be careful using them at work as there are other methods to detect if someone is working or gaming the system and it could get you fired (source: fired someone for using one of these)
Just curious: What is the basis of firing people using these? I mean, what’s the justification, public or otherwise, for saying this is not allowed?
I use an autohotkey script for something similar myself, mainly so the laptop doesn’t fall asleep while I’m waiting for something. I don’t really care about what my employer may or may not think about it though, as I handed in my notice last month.
Yeah, the USB ones are an interesting thing, I’m sure writing up the code in an Arduino is trivial these days. Sometime like
#include jiggler.h mouse.jiggle(excitation,time);
I work with hardware that uses fans though, and a piece of paper flailing in the wind does a great job if I’m running a long test.
I think this is probably the case. The old roller ball mice did not seem to have this problem, but early optical mice did.
- noisy mouse sensor
- threshold setting.
- above threshold: must be a mouse movement.
- below threshold: its noise, ignore.
You’d usually want the threshold to be low to get more mouse sensitivity. But too low and it starts doing stuff like moving to the left with no input.
I think the only times I’ve ever personally dealt with that was when a wired mouse was slowly moving because the wire was dragging it. No idea about any other problems that could caus it.
