Most recent activity
-
Indeed. Also if you trop the .min from the name you get a human readable version:
https://cdn.jsdelivr.net/npm/discrete-wavelets@5/dist/discrete-wavelets.umd.js -
I would grab the unified version from cdn and put it in the espruino ide and see what happens. Usual approach is to fetch the library as a single javascript file and save a copy in the bangle repo, e.g. see suncalc.js
-
WHO_AM_I is usually a register with a fixed value that helps you to identify that you are talking to the right chip on the bus. If this value is not read this is not good and usually means hardware problems
-
Try nail polish on the contacts. For the display try scratch remover polish. Not sure what to do about the button.
-
uhm, what do you mean by "worn out"?
-
Basically yes. It tells me that you were in state awake since 7:00 which is why it woke you up at 7:30. If it would wake you up later there is a risk for you falling into a deeper sleep state again.
What confuses me is the long awake phase from approx. midnight to 4:00.
You could do the following test
- Create an alarm at least 45 minutes into the future.
- Start sleepphasealarm and put the watch on a stable surface (table) and do not touch it
- Approx. 10 minutes before the alarm move the watch. The alarm should go off exactly when you move the watch.
- Create an alarm at least 45 minutes into the future.
-
For debugging purposes a higher value helps, lets say 8h?
-
So I assume you set your alarm to 8:00. The question is why was the sleep tracking only started at 7:00? Did you set "Run before alarm" to only 1h?
-
@tipans You should be able to view the sleep plots in the development app loader:
https://espruino.github.io/BangleApps/?id=sleepphasealarm
Or how about the buds having build in storage?