I have now flattened the battery to the point it turned off and wouldn't turn back on. I then recharged it. No apparent change.
Does D36.read() return true even when the touchscreen has stopped responding and the screen is definitely unlocked? That's the important one really.
Not sure how to check "definitely unlocked". It shouldn't be locked (it hasn't had enough time to timeout), and yet whenever I run setLocked(0) the touch begins responding again (and D36.read() returns true in any case).
It's almost as if it's locking too soon, or not in response to being touched (I would expect that touching would reset the lock delay, but perhaps it is not?).
Or maybe unlocking it is clearing something and allowing the events to restart.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I have now flattened the battery to the point it turned off and wouldn't turn back on. I then recharged it. No apparent change.
Not sure how to check "definitely unlocked". It shouldn't be locked (it hasn't had enough time to timeout), and yet whenever I run setLocked(0) the touch begins responding again (and D36.read() returns true in any case).
It's almost as if it's locking too soon, or not in response to being touched (I would expect that touching would reset the lock delay, but perhaps it is not?).
Or maybe unlocking it is clearing something and allowing the events to restart.
Are there next steps I can take?