I was looking at swipe event, it only has left/right. and then there is drag event with yz but not the action id, but it is not a problem really, I used the drag event with the i2c.writeTo(0x15,0xFA,17);
so now I get no Arbitration error, it actually works very nice.
On the reset issue, I think we are not talking about the same one.
There is one that resets the watch on a 10sec hold, handles the dfu mode, this is very nice.
but there is another one as well, it fires at 1.5-2 sec in, and it issues an E.reboot() and the screen displays "loading".
I have noticed that it is only started after I call the Bangle.getOptions() or set an option, or set a event. If I do not, I can bypass it, so I guess I could work around it.
I also tried calling E.kickWatchdog() , it doesn't seem to work, I guess it is not the watchdog, because I get a message from E.kill event, and the manual says this should not work on a watchdog timer reset.
On the reset issue, I think we are not talking about the same one.
Yes, you initially described it as "It restarts the watch on long press, is there a way to customize that?" so I was thinking you mean the watchdog reset that restarts whole watch. Not the one that exits the app.
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 was looking at swipe event, it only has left/right. and then there is drag event with yz but not the action id, but it is not a problem really, I used the drag event with the i2c.writeTo(0x15,0xFA,17);
so now I get no Arbitration error, it actually works very nice.
On the reset issue, I think we are not talking about the same one.
There is one that resets the watch on a 10sec hold, handles the dfu mode, this is very nice.
but there is another one as well, it fires at 1.5-2 sec in, and it issues an E.reboot() and the screen displays "loading".
I have noticed that it is only started after I call the Bangle.getOptions() or set an option, or set a event. If I do not, I can bypass it, so I guess I could work around it.
I also tried calling E.kickWatchdog() , it doesn't seem to work, I guess it is not the watchdog, because I get a message from E.kill event, and the manual says this should not work on a watchdog timer reset.