Avatar for Numerist

Numerist

Member since Jan 2021 • Last active Jun 2021
  • 4 conversations
  • 42 comments

Most recent activity

    • 33 comments
    • 1,275 views
  • in Bangle.js
    Avatar for Numerist

    After about a week of experiments, it seems that something in the code of Dozenal Time is the problem. Despite occasional slight variations (gaining or losing time by small amounts), it seems to cause a gain of about 2 seconds a day despite the custom boot gps fix.

    I'll see if I can find someone to look at it and I'll continue to observe the situation.

  • in Bangle.js
    Avatar for Numerist

    Over the past 36 hours the watch gained a little over 3 seconds. I don't know what I may be doing wrong, or what else may be wrong. I'm going to try a few more things and report back here.

  • in Bangle.js
    Avatar for Numerist

    Temperature moderate. Even if warm weather has been a problem, the script should fix that. My wifi time is the same as time.is.

    Shortly after 11:00 (central eastern North America) May 27 I did a new GPS fix and uploaded the custom boot with the new code above in the last line. I checked the watch once an hour at some point between 9 and 35 minutes after each hour, from 11:09 to 23:10. The watch was on Clock A except briefly as noted below.

    At 11+ to 18+ : accurate, fairly constant.
    At 19+ : ahead by a second or a little more. No clue why.
    At 20+ : still ahead by a second or a little more (same as at 19+).
    At 21+ : I switched to Clock B. Surprisingly, the time was accurate, as from 11+ to 18+. I switched back to Clock A with no further change. It's unlikely that the sudden change was caused by my switching (see below).
    At 22+ : ahead by a little (less than a second).
    At 23+ : ahead by a little more (still less than a second in total). I switched to Clock B and back to Clock A again. Unlike at 21+, there was no change.

    Of course, I don't know how the GPS timekeeper was doing over those hours. Nonetheless, the results from this one day are puzzling. (I'm not looking for a precision timepiece!)

  • in Bangle.js
    Avatar for Numerist

    It may be. Even after an hour or more, if I change apps, does the code then cease to work?

    What may I do to ensure that the resetting of the time continues to work? Or what should I not do?

    May code be placed or created that will set the time every hour regardless of changing apps, as long as the watch isn't rebooted?

    I appreciate your continued attention to this!

  • in Bangle.js
    Avatar for Numerist

    For the first time, something happened to steady the watch some. At some point in the second half of the day, it appears to have reverted to a more correct time. Not my doing; I didn't redo the GPS fix or reupload the script into the custom boot app. I've merely moved back and forth between my clock and the morphing clock.

    It would be good to know what's happening, even if that's a difficult question. I'll continue to observe.

  • in Bangle.js
    Avatar for Numerist

    The problem may be something I'm not doing, or not doing correctly. Gordon may have a further suggestion.

  • in Bangle.js
    Avatar for Numerist

    (Version 2v09, 7247a2c4 here.) In the emulator MYSCRIPT returns 1, so that's okay. I may still be missing something to activate the script on the watch.

    (Note to d3nd3-o0: thanks for the suggestion. I started off with no boot code and manual setting. Same problem.)

  • in Bangle.js
    Avatar for Numerist

    After a few days' trial, it seems to me that the watch still gains almost 2 seconds a day. Because the new script is in custom boot, perhaps I'm missing a boot action to activate it? All I'm doing after the GPS fix and uploading the custom boot is pressing BTN3. (A more serious reboot seems to replace the time with a default time.) I may be missing something.

    Would the script be more likely to work as desired (and not be subject to nullification by a novice) if embedded into the watch's own script?

  • in Bangle.js
    Avatar for Numerist

    I'm still observing, to get a better idea of how steady the watch can be with your script installed. Meanwhile, has anyone else mentioned unsteadiness in its timekeeping?

Actions