Bangle.js 2 touch panel auto standby

Hi Gordon, I noticed that the 816tp does not enter auto standby. I can see that you are using the accel for tp wakeup, so I guess it is a known issue and this is the way you bypassed it.

included are the registers from a p8, a rock, and a bangle.js 2, all using the same 816 tp model, p8 is ver1, rock is ver4 and the bangle is ver3.

So the question is the following: If the tp firmware on the 816 on the bangle does not have auto standby mode, could it be possible that firmware be upgraded? I know that it can, I can see the procedure on the 816 manual, but it is beyond my skills, so what I mean is could you have a look if you ever find some time?

Using the tp panel to wake the watch is better that using the accel I think, feeling wise. I was trying to use down gesture to unlock, and double tap to unlock and turn on the back-light, I can understand that I can do it using the tap/double tap of the accel, but it just does not feel the same as on the rock/p8.

(p8)
new Uint8Array([4, 0, 0, 191, 0, 103, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 64, 19, 40, 22, 33, 17, 233, 18, 77, 17, 167, 17, 189, 17, 253, 18, 32, 23, 105, 19, 38, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 0, 6, 0, 12, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 180, 0, 1, 0, 0, 0, 0, 0, 0, 0, 200, 0, 211, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 100, 0, 10, 1, 6, 1, 240, 1, 231, 1, 35, 3, 7, 50, 2, 17, 5, 10, 0, 0, 0])

(rock)
new Uint8Array([2, 0, 0, 113, 0, 86, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 64, 25, 120, 23, 10, 19, 213, 19, 223, 19, 119, 18, 253, 18, 7, 18, 133, 17, 148, 17, 132, 16, 236, 16, 39, 0, 0, 0, 0, 0, 0, 0, 96, 0, 0, 0, 0, 0, 8, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 3, 0, 5, 0, 6, 0, 6, 0, 0, 0, 0, 0, 0, 0, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 180, 22, 4, 0, 0, 0, 0, 0, 0, 0, 199, 0, 212, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 100, 0, 10, 1, 6, 0, 0, 0, 0, 1, 35, 3, 7, 50, 2, 17, 5, 10, 0, 0, 0])


(bangle)
new Uint8Array([4, 0, 0, 131, 0, 95, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 64, 20, 34, 17, 223, 12, 220, 12, 140, 12, 127, 12, 235, 12, 43, 11, 126, 13, 127, 13, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 0, 6, 0, 0, 0, 0, 0, 6, 0, 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 180, 0, 3, 0, 0, 0, 0, 0, 0, 0, 188, 0, 187, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 10, 1, 6, 0, 0, 0, 0, 1, 48, 3, 7, 40, 2, 17, 0, 0, 0, 0, 0])

Before Christmas someone was asking about this and I can't for the life of me find the post now... But they'd got a much better datasheet on the touchscreen and were poking around with registers trying to enable the auto-sleep mode on it.

So it might well be possible even with current firmware.

For the firmware updates, yes, that's definitely possible but I got the impression the firmware included adjustments for the specific LCD screen (eg what range of values it reports back so it matches pixel density) so even if a new firmware were uploaded on it (and could be done safely) I think we may have to try and find one with the correct pixel density which could be tricky...

Before Christmas someone was asking about this and I can't for the life of me find the post now... But they'd got a much better datasheet on the touchscreen and were poking around with registers trying to enable the auto-sleep mode on it.

So it might well be possible even with current firmware.

That would be super. I played a bit too, my goal/hope was to make a post saying that I found out how to do it, but I failed, I cannot make it auto sleep.

I understand that upgrading the firmware may be challenging if even truly possible, I will try to find the post you mentioned, enabling auto sleep using registers would be super.

but I got the impression the firmware included adjustments for the specific LCD screen (eg what range of values it reports back so it matches pixel density)

Yes I think you are correct, this is why I think upgrading is out of my league :) For example, I have noticed that when I enable auto sleep on the rock, the HRM sensor is involved too, in the sense that the screen will only wake on touch if the watch is on the hand.

one more question, a bit irrelevant. How does the Bangle.setLocked(true) disables the BTN1? I can see that the BTN1 state is reported ok (with BTN1.read() ) when locked, but my setWatch is not working. Does it automatically disables setWatch in the background?

How does the Bangle.setLocked(true) disables the BTN1?

Yes, it's done in software - here: https://github.com/espruino/Espruino/blob/master/libs/banglejs/jswrap_bangle.c#L1766-L1781

So the hardware watch isn't disabled, it's just not passed on to JS. The idea is the lock stops accidental interaction with the watch, but it includes touchscreen and buttons right now