XDA-Bam

> That's a bummer, but it means that it is not just a lost step. There must be something else going on. > > @XDA-Bam I have a couple questions...

Video is attached. You will see that this time, it took me quite some time (~25 s) to trigger the bug while scrolling the menus. After that, it stayed and...

> I'll keep trying to reproduce this for some days. I'm starting to suspect that in that type of encoder, internal haptic dents can slide a bit with respect to...

@dbuezas With your latest changes, the bug has changed and it subjectively appears to trigger less often. What happens now is that you can still get occasions where one step...

> > It should disappear as soon as the encoder is left alone for half a second. Forgot to test that earlier. Just checked and yes: The bug is also...

I tried the suggested `#define RESET_ENCODER_AFTER_MS 250` and didn't feel a substantial difference. It may be quicker to clear the error, but it's closing in on a level where it...

Just updated to 9e21330d7ae8b4979fee10099294e9e61c939613 and tested the latest changes. I specifically also tested slow scrolling, which isn't how I typically navigate the menus. I think I noticed the occasional lost...

> > > If these suggested changes are implemented, I would say we'll reach a state where CR10_STOCKDISPLAY can't be improved much further > > So specifically that's the previous...

I would expect the encoder to jump nonetheless, but it takes like 3 minutes to test so let's test.

@dbuezas Just tested 2100d45 and I'd say it is an improvement over 92c4c7d but still occasionally double steps. I certainly provoked it by intentionally changing directions quite often, but in...