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?
Ok, guys, so I have a theory: It might actually be a double press missfire. The issue is, in a double click, if you maintain the fire button pressed in the second click, the firmware actually nulls both the fire action and the "2 clicks" action. So it does nothing. I believe it might be solved if the firmware fired up the coils when the fire button stayed pressed in the second click - If the user didn't wanted to fire the mod, why else would him/her be keeping it pressed? - instead of nulling all actions when this happens. Is there any way this might get implemented?
Hi, Try please this nightly build: https://nfeteam.org/forum/threads/arcticfox-170610.150/ I encountered a similar situation and the modification of the multi-click handler in this build helps.
Seems like the behavior is no longer there! That's awesome. If it was the double click it should be solved... let's wait and see
@ReikoKitsune Is this version coming earlier than the one that maelstrom posted in my issue? Because on the 170613 the issue's still there. At least on evic dual [emoji20]
We can go deeper if you can explain what we should do to reproduce your issue. Sequence of button presses, from what state, etc.
From deep sleep, pressing the fire button doesn't turn on the device. Stays in a hibernation state. If I click it for a second time, it turns on. Double clicking the fire button in the same hibernation state as said before (which in my configuration is set to edit action) turns the mod on in edit mode, but the single click doesn't work.
@dil3mm4 OFW also has this behavior? As i noticed this happens not often and only on the one of your devices.
