I wrote an app which communicates with an Android app and transfers data continuously. Everything works fine until the watch seems to (soft) reset for seamingly no reason. What I did so far:
use 2v16 release build
Android app drives communication (no Bluetooth.write unless requested)
continuously log memory consumption using Terminal.println and buzz when exceeding ~2/3
disabled home button (set option btnLoadTimeout to 0) and implemented a 3s count down with buzz when holding a button to reenable the home button
Because it takes a couple of minutes to appear and the timespan varies a lot (observed 7m and 12m from sent data), I didn't "see" what happens on screen so far.
I would appreciate any information on what I should "log", on JS or C level, to get a grip on this.
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.
Hi,
I wrote an app which communicates with an Android app and transfers data continuously. Everything works fine until the watch seems to (soft) reset for seamingly no reason. What I did so far:
Bluetooth.write
unless requested)Terminal.println
and buzz when exceeding ~2/3btnLoadTimeout
to 0) and implemented a 3s count down with buzz when holding a button to reenable the home buttonBecause it takes a couple of minutes to appear and the timespan varies a lot (observed 7m and 12m from sent data), I didn't "see" what happens on screen so far.
I would appreciate any information on what I should "log", on JS or C level, to get a grip on this.
Thanks in advance!