Issue: Sometimes, the device doesn't fire when the fire button is pressed. The screen also stays as if no button had been clicked. Average Frequency: About once for each hundred puffs/clicks Device: Joyetech Evic Primo Mini, Hardware 1.00 Observed with Firmware: ArticFox 170603, but also Joyetech V6.04 and V6.06 I've had the Primo mini for a few days and have experienced this issue with both the factory firmware and the last non-nightly ArticFox release (170603). Some further info: As soon as I press the fire button again after a missed click, it works perfectly. It doesn't seem to be a double press missfire: I've got the “Reset Counters” screen configured for 2 clicks, and it doesn't switch to it. It doesn't seem to be because of lack of pressure or a button contact issue: To test for it, I’ve maintained the button pressed when it has happened, increased and decreased the pressure, and moved the finger up, down and to the sides of the button - all of that without actually doing another click/press, - with the mod still not firing. This, coupled with it working flawlessly when clicking again, make me think it's not a button contact issue, but that it should rather be circuit/firmware related. This is probably anecdotical, but I'll mention it: I made several conscious attempts to replicate the issue after upgrading to ArticFox and couldn’t - even after a few hundred clicks. I did so by clicking the fire button about once per second. But even though I couldn’t replicate the issue this way, the missed clicks still do happen every 100 puffs/clicks or so with normal usage. Maybe there's some variable at play here by which something is different when using it normally vs. when firing it repeatedly with minimal delay as I did while testing; but it also might be pure chance. I should mention the device wasn't asleep, locked, usb connected, or low in battery when this has happened. My hope is that this is some circuitry/firmware issue that can be solved, even if it is a factory defect - which I'm thinking could be as it also happened with the factory firmware. Has anyone else experienced this issue? Is there any possibility there is a viable firmware solution for it?