You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
-
@user147320 but you're sure that Wake on Touch is off in your case? In that LCD menu, literally the only Wake on XXX menu item that is checked is Wake on BTN1?
Unfortunaly yes, only wake on BTN is enabled :(
I will try the cutting edge-build later anyway to see if this changes anything.
Edit: Uploading the cutting Edge-Firmware hangs at about 20-30%, so i don't know if this would help
it's two down from
Wake on BTN1
- I meantWake on Touch
.It's a bit confusing but it's documented in the readme there - the touchscreen draws a bunch of power when on so we do wake on touch by detecting a 'tap' from the accelerometer. Just touching won't wake it, you have to tap it such that the watch actually moves.
So @HughB and @d3nd3-o0 it's what I said in your case with the spurious tap events, original report at https://forum.espruino.com/conversations/390041/#comment17120157
And yes turning the HRM on resets the hrmWearDetect/hrmPushEnv values @d3nd3-o0 but I don't think that's related to @user147320's issue. If you want to see how to use env values check out https://banglejs.com/apps/?id=flashcount
@user147320 but you're sure that
Wake on Touch
is off in your case? In that LCD menu, literally the onlyWake on XXX
menu item that is checked isWake on BTN1
?