You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debouncing does not seem to be present when pressing down the button.
Maybe adding around 100ms would be nice.
Justification
Sometimes the button "double-clicked" by itself, occurrence seem to be 1 in 10 or less (at least on my device).
Although it does not seem much, but it is rather annoying when it happens, especially when entering the last digit pin, causing unwanted "invalid pin" incidents.
Nice.
Since different unit may have different tolerances, would it be better if we can customise it?
If not can we increase to maybe 150ms-200ms, to reduce this issue further?
I have this issue with my early unit, it seems the scroll wheel starts to do this after lots of use. This will just get worse and worse until the wheel stops working. I've replaced this unit with a new one that I think has a better scroll wheel installed. The new one doesn't exhibit any issues but it's only been 6 months.
@limpkin I can click but it will sometimes scroll at the same time. Just touching the scroll wheel lightly will sometimes make it scroll very quickly in one direction or the other. If I push down on the scroll wheel while clicking it works much better. This leads me to think the issue is hardware, the scroll wheel has failed and the contacts and/or wheel are lose. I have a very early unit and I use it all the time so perhaps the scroll wheel part isn't robust enough.
Yes, I suspect the scroll wheel contacts are broken or worn out. This is an early unit and I use it all the time so it may just need a new scroll wheel component. The battery doesn't hold a charge any more (and yes I've run the refresh several times), is it possible to replace it?
Activity
limpkin commentedon May 7, 2023
there's actually already a debounce: https://github.com/mooltipass/minible/blob/master/source_code/main_mcu/src/INPUTS/inputs.c#L275, set to 100ms
lwYeo commentedon May 7, 2023
Nice.
Since different unit may have different tolerances, would it be better if we can customise it?
If not can we increase to maybe 150ms-200ms, to reduce this issue further?
limpkin commentedon May 7, 2023
that's indeed a great idea!
My1 commentedon May 8, 2023
might this be the same reason why i sometimes dont get a wheel move when moving quickly through the numbers when trying to enter my pin?
limpkin commentedon May 9, 2023
not exactly no
CGuy-1 commentedon May 29, 2023
I have this issue with my early unit, it seems the scroll wheel starts to do this after lots of use. This will just get worse and worse until the wheel stops working. I've replaced this unit with a new one that I think has a better scroll wheel installed. The new one doesn't exhibit any issues but it's only been 6 months.
limpkin commentedon May 30, 2023
Hello, are you saying you aren't able to click anymore?
seviu commentedon May 31, 2023
I got same problem
limpkin commentedon May 31, 2023
@seviu : can you expand on your symptoms? :)
CGuy-1 commentedon May 31, 2023
@limpkin I can click but it will sometimes scroll at the same time. Just touching the scroll wheel lightly will sometimes make it scroll very quickly in one direction or the other. If I push down on the scroll wheel while clicking it works much better. This leads me to think the issue is hardware, the scroll wheel has failed and the contacts and/or wheel are lose. I have a very early unit and I use it all the time so perhaps the scroll wheel part isn't robust enough.
limpkin commentedon Aug 30, 2023
@CGuy-1 is this still happening? I could offer a device swap...
CGuy-1 commentedon Sep 6, 2023
Yes, I suspect the scroll wheel contacts are broken or worn out. This is an early unit and I use it all the time so it may just need a new scroll wheel component. The battery doesn't hold a charge any more (and yes I've run the refresh several times), is it possible to replace it?
limpkin commentedon Sep 6, 2023
send me a quick email, we'll work something out :)