Search results for:

May there also be a good way to do this without setTime? One that would allow a smaller decrement. There's presumably a way to getMilliseconds.

I get it. I'll try 210 ms every hour.

Reply function not always working…reply is above.

Thanks. I'm experimenting with 35 ms every 10 minutes first. Or is that beyond the watch's ability to perform? Again, I'm only chasing after decent accuracy, nothing extreme.

I'd like to try that. Is there an output result (i.e. a word) that needs to be inserted into my watch's code as input after running that? Or if I preface my code with yours, is that all that's necessary?

Got any specifics? I can try to do an offset, say 630 ms every 3 hours for starters, if I can understand my watch's code. Or is there a generic way to do that?

Have you had success?

Have you done anything to correct the drift you and I have noticed?

Meanwhile, to clarify: you get the fix, the Bangle takes up GPS time outside (via a widget or via inserted code), and you walk indoors. What is the watch timing doing after that? Sorry to ask, but I don't know the explicit answer.

If using GPS time is possible only outdoors, it's of limited use, obviously.

Does that work (with Bangle.js 1) indoors? Independently of the watch's built-in timing? What updating does it need, do you think, to work with watch 2?

I'm a novice at this. After getting a satellite's GPS fix outdoors, what's next? There needs to be code inserted into a watch's script to use the GPS time, correct? I may be missing something…what's the procedure to get the watch to use GPS time, and does it work?

Is there a GPS use that will work? Including indoors after the fix, of course.

Thanks for clarifying. Unfortunately that's only a little better than reconnecting to the Internet any other way. It's a manual necessity. Maybe an app that would disconnect and reconnect at specified intervals automatically? That would do it.

We need a way to get iPhones to send their time (at certain intervals) to the Bangle without intervention. One way has been discussed elsewhere but currently seems difficult and possibly also awkward, and I can't determine how well it works.

Connect Browser has a tendency either not to find the watch or to freeze it )-:

See reply above.

Interesting, thanks.

If it always updates time "when we connect," must the watch be disconnected and reconnected in order to keep using the phone's time?

I'd have to reprint a lot of code (written by someone else). Do you have something that works?

Temperature no problem, high accuracy not needed. I'd settle for altering shown time only as an improvement over the situation without it.

Probably doing something every 10 minutes will use too much power, so a longer interval will be better. I suppose I have to find how my script gets the time and then alter that (maybe every three hours).

There are four ways I know of to regulate the watch’s time:

1) from the app loader download a watch script a few times a day. Not a great solution.
2) sync to an iPhone. Probably tricky, and I don’t know enough to do that. I don't have Android.
3) sync to GPS time. I have tried code that doesn’t seem to work.
4) slow down the watch by about 35 ms every 10 minutes, those numbers being adjustable.

For 4) is there a function I can try for slowing by 35 ms repeatedly? I understand setTimeout for calling a function every 10 minutes, but not much more about javascript. I’m not a coder. (My Dozenal Time watch was coded by someone who left the project. Possibly the way it gets the time is not standard.)

Does that mean disconnecting and reconnecting only once? Or how often?

(A further question: how much of your code is needed, and how should that be used for a given watch script?)

@jeffmer
Any luck with Gordon's fix for using the iOS time?

I assume (as a non-programmer) that the recent (interesting) posts aren't about trying to get the time from an iOS device. Do correct if that's wrong.

@Mark_M
Like some other people here, I'm interested in whatever will work with an iPhone. (Android and Gadgetbridge are not possibilities.)

Some people here is working on a connectionless (ads based) way of time synchronizing with jitter < 10ms.

Which devices will provide the synchronization?

@jeffmer
As expected, what I did makes no difference. I assume that I have to call setTimefromPhone in my code and make sure nothing interferes with that. I have my own font size, colour, etc., and I'll have to see whether my determination of the time interferes or may preferably be overridden by yours. (Someone else wrote my code but has left the project.)

If your code synchronizes only once, is there an easy way to get it to do that 4 or 24 times a day, for example? Just call the function at the desired times?

I'd be grateful for any further advice, including whether Gordon's update changes what I may or need to do.

@jeffmer
Thanks for that help. I'm not a programmer, so don't understand much of your discussion with Gordon. I've placed your code before the code for my watchface, loaded the lot onto my watch, then cut that connection and paired with my iPhone. If something different or more needs to be done, just let me know.

The left side of the IDE delivers these apparently non-fatal messages on loading your code with mine:
WARNING: SD ERR 0x11 (BUSY) (:1803)
WARNING: SD ERR 0x11 (BUSY) (:650)

Anyhow, how often (at what interval) does your code make the watch's time the same as the iPhone's time?

(I'll see how the experiment's gone in 12 hours.)

I use similar hardware and software. My only suggestion is to try turning the watch off, then on, and if that doesn't work, try restarting the computer. The latter got my watch back to pairing.

Thanks for that. Resetting the watch had to be combined with restarting the computer, to enable recognition. ("Don't scoff, just turn it off.") I've now uploaded the app manager.