Tell HN: Can we surface the M1 Mac laggy/choppy cursor and scroll bug?
Just want to surface this to see if anyone has it fixed or so anyone at Apple can give it a look. I remember finding a fix involving editing a cursor file a while back, but it must not work as I've been seeing it again (and can't find that fix searching anymore).
There's a lot of reports:
https://www.reddit.com/r/macbookair/comments/pome1y/mba_m1_c...
https://www.reddit.com/r/MacOS/comments/nlbf6w/weird_cursor_...
https://www.reddit.com/r/mac/comments/qtfc2e/lagging_jittery...
https://www.reddit.com/r/mac/comments/qj77mq/cursor_lag_cont...
https://discussions.apple.com/thread/252777347
https://discussions.apple.com/thread/253079227
https://discussions.apple.com/thread/252732117
There's this one video with a fix, but I already have shake to locate off and it happens without using any bluetooth mouse:
31 comments
[ 4.2 ms ] story [ 85.9 ms ] threadI think this is part of what makes things like this hard: most people might be misdiagnosing what they're seeing.
> I have two M1 macbook airs, both have this issue. It's only present when macOS resumes after running out of battery. Restarting fixes it, but that's a pain and defeats the whole point of the low battery resume feature.
> Interestingly the cursor isn't the only thing that's slow. I maintain an old OpenGL codebase and rendering performance is degraded until I restart. I've optimized for the M1 so it's definitely not a rosetta issue. It's almost like the gpu gets stuck in a low power mode after shutting down due to low battery.
I can attest to this - also with an M1 Air. When macOS resumes from 0% battery, it's stuck in 30Hz mode. Not just the cursor - everything. I've always restarted to fix.
[0] https://www.reddit.com/r/mac/comments/qj77mq/cursor_lag_cont...
This sounds like detailed, testable data; I wonder how much effort it is to query this in code at resume just to confirm?
I have had better luck with the magic Trackpad plugged in via USB than over BT.
If it happens on the trackpad, it could be a defect on the trackpad itself, or something overloading the USB hub it's attached to.
It could also be a sign of swapping, too many interrupts, badly prioritized processes, etc.
A bug in adaptive refresh rate might do it.
A process messing with events (such as an app listening on mouse moves or an antivirus).
It may not be a single bug, but just a symptom of something else.
I use a Magic trackpad, and when it occurs the built-in trackpad still works fine.
To fix it I disable Bluetooth on the M1, then re-enable and everything is fine again.
This lead me to believe it was related to the Bluetooth stack, but if people are experiencing it while using built-in trackpad if be interested to know if my workaround still fixes it.
https://www.reddit.com/r/Monitors/comments/s36bam/very_weird...
There's also a wakeup-immediately-after-sleep issue, which seems to be linked to the USB stack, as well.
[0] https://www.reddit.com/r/mac/comments/qtfc2e/comment/hrd7ztn...