Ghost Crank Inputs

Hi everyone, I’m Danilo. I’ve been a developer for over 10 years and I received my Playdate less than a month ago—I think it’s absolutely fantastic!
My apologies if this isn't the right section; I wasn't able to find one more specific for my issue.

I’m reaching out because I’ve encountered a strange issue while developing a game that triggers sounds based on crank movement. I noticed that audio would occasionally trigger even when the crank was supposedly stationary.

The Issue: After opening the Input Test in the system settings, I confirmed that the crank is reporting rapid, tiny positive and negative input values even when it is not being touched.

Tests I’ve Conducted: To rule out external factors, I performed the following:

  • Placed the console on a flat, stable table (no vibrations).
  • Tested the crank at various angles/positions.
  • Restricted the crank physically by resting it against the table surface to ensure zero mechanical movement.

In all cases, the diagnostic screen still shows flickering input values. I have attached videos of the diagnostic screen showing this behavior.

My Question: Is this a known software/calibration quirk that I should account for with a small deadzone in my code, or does this look like a hardware defect (noisy sensor/potentiometer) specific to my unit?

Any insight would be greatly appreciated!

Screen videos:

  • on table with crank raised
    Playdate 2026-02-04_22:55:13

  • on table with crank aligned with console
    Playdate 2026-02-04_22:58:43

  • on table with crank resting against the table surface
    Playdate 2026-02-04_23:08:33

1 Like

out of curiosity do you have one of the official cases on your playdate? I’ve definitely seen the magnets in the case interfere with the magnet in the crank. I’d be curious if taking it off fixes what you’re seeing.

1 Like

Yes, I have the official case and I also thought it might be that. I removed it, but the problem wasn’t resolved.

1 Like

The sensor is a bit noisy, so there's a 0.2 degree rotation threshold it has to pass before it registers as a change. When I added that it filtered out these spurious changes but I'm sure there are environmental factors that can affect this, also variation in the sensor hardware. I filed an issue to test this on the units I have here and I'll see if we need to adjust that value. In the meantime can you add another threshold in your code?

1 Like

Sure, I'll add a threshold to my code, thanks.
I was just trying to figure out if it was a problem with my unit or something that needed to be fixed at the software level.