The misfiring isn't a defect; it's a feature
After 13 seconds of idleness the device does not enter into sleep mode, its display screen simply turns off. Pressing the fire button at this precise moment does not fire the device, does not "wake up" the device, and does not turn on the display screen. In other words, the button press was not registered. Henceforth, it was dubbed a misfire. Subsequent button press(es) will be registered and the mod will function as usual.
The display screen timeout value would not be hardwired into the board, it would be a value assigned in its software. If firmware upgrade was available it could have, at the very least, offered possibilities of changing this value to another number.
The cause for the device not registering the button press could either be due to the board itself or its software, or a combination of both. It would be a difficult task for the typical end user to solve. However, it would not be the most difficult task to solve at the manufactoring and design stage.
Whilst this particular issue could be classed as a con, it remains inferior to the device's other cons. Whilst the device does have its list of cons, it should not imply it does not have a list of pros.
Sent from my SM-G900I using Tapatalk