Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit charge 6) compared to my phone (Lenovo G52).
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit charge 6) compared to my phone (Lenovo G52).
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit charge 6) compared to my phone (Lenovo G52).
Fitbit charge 6Mine counts steps OK, but it's poor at recognising flights of stairs
On 28.10.25 19:13, Carlos E.R. wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit
charge 6) compared to my phone (Lenovo G52).
When you do what?
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit
charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
That would be normal, because the Fitbit has its own clock. It only
syncs once in a while with your phone.
Anyway, how can you seem that 'delay', because the Fitbit only
displays whole minutes (not seconds)? Or do you wait for the Fitbit to rollover and then check your phone?
FYI, I have a Charge 5, but I just checked my wife's Charge 6 [1] and--
I only see whole minutes there.
BTW, my phone and laptop are within 1 second. Phone gets the time from
the mobile network. Laptop gets the time via NTP.
[1] Why do 'they' always have the better (well, newer) stuff!? :-)
Carlos E.R. wrote:
Fitbit charge 6Mine counts steps OK, but it's poor at recognising flights of stairs climbed, yours?
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit charge 6) compared to my phone (Lenovo G52).
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit >> charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only syncs once in a while with your phone.
5 seconds delay is not acceptable.
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit >>>> charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only
syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
"not acceptable"? I don't think there's a spec for that. Anyway, what
can you do about it?
Perhaps you can do a manual sync to/from your phone and see if that
makes the offset smaller. I just did that for my Fitbit and that seems
to make the offset smaller, now some 2 seconds, but not zero.
Anyway, the Fitbit must be able to work without the phone for extended periods. For example when the phone is not in Bluetooth range, when there
is no mobile coverage, when the phone is in airplane mode, etc., etc..
Example: Our very long flights to Australia, our travels in Outback Australia (where the *is* no mobile coverage for days on end), etc..
Bottom line: It's a watch.
[...]--
I just noticed that there is a 6 seconds delay on my smart watch
(Fitbit charge 6) compared to my phone (Lenovo G52).
You can synchronize the time using the app via Bluetooth, so my question
is do you keep Bluetooth alive 24/7?
I would expect that such a synchronization is run once a day, then even
a bad clock chip running in then Fitbit for one day should not end up in such a deviation.
If the clock chip has one of one to three seconds per day amd BT is off
and cannot synchronize then you can get a 6 sec deviation easily.
On 2025-10-29 17:07, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit >>>> charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only >>> syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably closer to 4. So I think 5 to 6 seconds is not that bad.
"not acceptable"? I don't think there's a spec for that. Anyway, what can you do about it?
A difference in clocks beyond 1 second this far in the century in
devices that have some networking capabilities is not acceptable. It is
an engineering failure.
Do? Probably nothing, that's why I'm asking.
Perhaps you can do a manual sync to/from your phone and see if that makes the offset smaller. I just did that for my Fitbit and that seems
to make the offset smaller, now some 2 seconds, but not zero.
I have not seen where to force a sync.
Anyway, the Fitbit must be able to work without the phone for extended periods. For example when the phone is not in Bluetooth range, when there is no mobile coverage, when the phone is in airplane mode, etc., etc..
Sure. But that was not the case. I verified by asking the application to download data in the watch. They call that syncing. Syncing data.
Australia (where the *is* no mobile coverage for days on end), etc..
Bottom line: It's a watch.
I expect perfection in the time keeping aspect.
--- Synchronet 3.21a-Linux NewsLink 1.2[...]
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-29 17:07, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit >>>>>> charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only >>>>> syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
"not acceptable"? I don't think there's a spec for that. Anyway, what >>> can you do about it?
A difference in clocks beyond 1 second this far in the century in
devices that have some networking capabilities is not acceptable. It is
an engineering failure.
Do? Probably nothing, that's why I'm asking.
Perhaps you can do a manual sync to/from your phone and see if that
makes the offset smaller. I just did that for my Fitbit and that seems
to make the offset smaller, now some 2 seconds, but not zero.
I have not seen where to force a sync.
Dragging down the 'home' ('Today') screen of the Fitbit app, like you described in another response.
I have a stone-age version of the app (don't ask), so it may not be
the same for you, but my app also has an alternative manual sync:
Home/Today page -> Your avatar at the top left -> 'Account' screen ->
tap on your device -> your device screen -> Sync -> Sync Now.
BTW, yesterday I happened to notice that a manual sync not always--
fully syncs, even if it implies to do so. I was charging my Charge 5 and
the watch said 83%, but the app still said 28%, even after several
manual syncs ("a moment ago"). Much later, the correct percentage of the watch was reported by the app.
So perhaps your time-offset problem is (also) due to syncing problems.
[Left for reference:]
Anyway, the Fitbit must be able to work without the phone for extended >>> periods. For example when the phone is not in Bluetooth range, when there >>> is no mobile coverage, when the phone is in airplane mode, etc., etc..
Sure. But that was not the case. I verified by asking the application to
download data in the watch. They call that syncing. Syncing data.
Australia (where the *is* no mobile coverage for days on end), etc..
Bottom line: It's a watch.
I expect perfection in the time keeping aspect.
[...]
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit >>>> charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only
syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
Bottom line: It's a watch.
On 2025-10-30 15:11, Frank Slootweg wrote:[...]
Carlos E.R. <robin_listas@es.invalid> wrote:
I have not seen where to force a sync.
Dragging down the 'home' ('Today') screen of the Fitbit app, like you described in another response.
I have a stone-age version of the app (don't ask), so it may not be
the same for you, but my app also has an alternative manual sync:
Home/Today page -> Your avatar at the top left -> 'Account' screen ->
tap on your device -> your device screen -> Sync -> Sync Now.
Yes, I have both. But it is a data sync, not time sync.
Well, the second method says now last sync was 14 hours ago and is not refreshing, even though I used the first method a minute ago.
Maybe I need a phone reboot. Each day, I notice my phone has more
difficulty connecting to my car (Android Auto thing), till one day I
have to reboot my phone or it will not connect at all. Maybe the same happens with the watch.
One day, recently, the watch would not sync data at all. I had to delete
the watch from the phone, and add it again. As a benefit, it offered me
I think it was 60 days of the Pro mode, but I said no. It would be
cheating, and anyway, Pro mode is good but not worth the money they ask.
Still waiting for the phone to restart. Ah, now.
Well, the watch is now 3 seconds off.
Now the second mode of sync on Fitbit app works, says synced 9 minutes
ago. I syc with first method, and second method says "just now". Improvement.
Trying with watch restart.
Two seconds off.
This is ridiculous.
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit
charge 6) compared to my phone (Lenovo G52).
You can synchronize the time using the app via Bluetooth, so my question is do you keep Bluetooth alive 24/7?
I would expect that such a synchronization is run once a day, then even a bad clock chip running in then Fitbit for one day should not end up in such a deviation.
If the clock chip has one of one to three seconds per day amd BT is off and cannot synchronize then you can get a 6 sec deviation easily.
Carlos E.R. wrote:
Fitbit charge 6Mine counts steps OK, but it's poor at recognising flights of stairs climbed, yours?
Andy Burns wrote:
Mine counts steps OK, but it's poor at recognising flights of stairs
climbed, yours?
I just checked for my Fitbit Charge 5. I climbed 7 (sets of) stairs
(to the 7th floor) and it counted some 140 steps, which seems OK.
N.B. I do remember that earlier Fitbits, probably also the earlier
Charge models, didn't count steps on stairs very well or at all.
Frank Slootweg, 2025-10-29 17:07:
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit >>>>> charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only >>>> syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
I would consider it *bad* if a watch is always 5-6 seconds off when it >connects via Bluetooth to a smartphone and could easily adjust it's time >then.
My Casio ABL100 is syncing its time 4 times a day with my smartphone and
it is always accurate within around 0.2 seconds.
[...]
Bottom line: It's a watch.
Yes - and a watch should show the exact time and not 5-6 seconds off.
Even cheap digital watches are able to do this.
On 10/31/25 2:52 AM, Arno Welzel wrote:
Frank Slootweg, 2025-10-29 17:07:
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit >>>>>> charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only
syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
I would consider it *bad* if a watch is always 5-6 seconds off when it
connects via Bluetooth to a smartphone and could easily adjust it's time
then.
My Casio ABL100 is syncing its time 4 times a day with my smartphone and
it is always accurate within around 0.2 seconds.
[...]
Bottom line: It's a watch.
Yes - and a watch should show the exact time and not 5-6 seconds off.
Even cheap digital watches are able to do this.
Wow. Complaining over being a few seconds off?? I guess I must have had a tough youth then. My windup watch was a minute off a day. The horror!! But the good part was I got my exercise when I had to wind it. And gosh I often had to (gasp) reset it. How did I ever survive?? You kids today just don't know how good you have it... ;)
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-30 15:11, Frank Slootweg wrote:[...]
Carlos E.R. <robin_listas@es.invalid> wrote:
I have not seen where to force a sync.
Dragging down the 'home' ('Today') screen of the Fitbit app, like you >>> described in another response.
I have a stone-age version of the app (don't ask), so it may not be
the same for you, but my app also has an alternative manual sync:
Home/Today page -> Your avatar at the top left -> 'Account' screen ->
tap on your device -> your device screen -> Sync -> Sync Now.
Yes, I have both. But it is a data sync, not time sync.
I would expect it to be both, i.e. a data sync and a time sync.
If it's not a time sync, then how *is* the time synced? The time *is* synced from phone to Fitbit, because when you manually select the
timezone in the Fitbit app, the change is propagated to the Fitbit.
Well, the second method says now last sync was 14 hours ago and is not
refreshing, even though I used the first method a minute ago.
Yes, as I said (for my Charge 5), syncing seems to be awkward and unreliable. :-(
Maybe I need a phone reboot. Each day, I notice my phone has more
difficulty connecting to my car (Android Auto thing), till one day I
have to reboot my phone or it will not connect at all. Maybe the same
happens with the watch.
One day, recently, the watch would not sync data at all. I had to delete
the watch from the phone, and add it again. As a benefit, it offered me
I think it was 60 days of the Pro mode, but I said no. It would be
cheating, and anyway, Pro mode is good but not worth the money they ask.
Still waiting for the phone to restart. Ah, now.
Well, the watch is now 3 seconds off.
Now the second mode of sync on Fitbit app works, says synced 9 minutes
ago. I syc with first method, and second method says "just now".
Improvement.
Trying with watch restart.
Two seconds off.
This is ridiculous.
Perhaps you can post your problems to the Fitbit forum(s). (I used
them in the past, but that was still pre-Google.)
If it's any consolation, my Charge 5 has problems with the 'Health Metrics'. 'Breathing rate' and 'Heart rate variability' frequently give--
"No data in the past 24 hours". And 'Resting heart rate' sometimes is
way too low.
[...]
AJL <noemail@none.com> wrote:
On 10/31/25 2:52 AM, Arno Welzel wrote:
Frank Slootweg, 2025-10-29 17:07:
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit
charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only >>>>>> syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
I would consider it *bad* if a watch is always 5-6 seconds off when it
connects via Bluetooth to a smartphone and could easily adjust it's time >>> then.
My Casio ABL100 is syncing its time 4 times a day with my smartphone and >>> it is always accurate within around 0.2 seconds.
[...]
Bottom line: It's a watch.
Yes - and a watch should show the exact time and not 5-6 seconds off.
Even cheap digital watches are able to do this.
Wow. Complaining over being a few seconds off?? I guess I must have had a
tough youth then. My windup watch was a minute off a day. The horror!! But >> the good part was I got my exercise when I had to wind it. And gosh I often >> had to (gasp) reset it. How did I ever survive?? You kids today just don't >> know how good you have it... ;)
You're missing the point. A watch in 2025 should be able to be accurate to within a second and not drift within 24 hrs. Especially one so technologically advanced as a smartwatch.
That it is drifting is sloppy design and lack of attention to detail.
A half decent analogue watch is better than that.
AJL <noemail@none.com> wrote:
On 10/31/25 2:52 AM, Arno Welzel wrote:i one so
Frank Slootweg, 2025-10-29 17:07:
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit
charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only >>>>>> syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
I would consider it *bad* if a watch is always 5-6 seconds off when it
connects via Bluetooth to a smartphone and could easily adjust it's time >>> then.
My Casio ABL100 is syncing its time 4 times a day with my smartphone and >>> it is always accurate within around 0.2 seconds.
[...]
Bottom line: It's a watch.
Yes - and a watch should show the exact time and not 5-6 seconds off.
Even cheap digital watches are able to do this.
Wow. Complaining over being a few seconds off?? I guess I must have had a
tough youth then. My windup watch was a minute off a day. The horror!! But >> the good part was I got my exercise when I had to wind it. And gosh I often >> had to (gasp) reset it. How did I ever survive?? You kids today just don't >> know how good you have it... ;)
technologically advanced as a smartwatch.
That it is drifting is sloppy design and lack of attention to detail.
A half decent analogue watch is better than that.
On 10/31/25 2:19 PM, Chris wrote:
AJL <noemail@none.com> wrote:
On 10/31/25 2:52 AM, Arno Welzel wrote:i one so
Frank Slootweg, 2025-10-29 17:07:
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit
charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only >>>>>>> syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
I would consider it *bad* if a watch is always 5-6 seconds off when it >>>> connects via Bluetooth to a smartphone and could easily adjust it's time >>>> then.
My Casio ABL100 is syncing its time 4 times a day with my smartphone and >>>> it is always accurate within around 0.2 seconds.
[...]
Bottom line: It's a watch.
Yes - and a watch should show the exact time and not 5-6 seconds off.
Even cheap digital watches are able to do this.
Wow. Complaining over being a few seconds off?? I guess I must have had a >>> tough youth then. My windup watch was a minute off a day. The horror!! But >>> the good part was I got my exercise when I had to wind it. And gosh I often >>> had to (gasp) reset it. How did I ever survive?? You kids today just don't >>> know how good you have it... ;)
technologically advanced as a smartwatch.
That it is drifting is sloppy design and lack of attention to detail.
A half decent analogue watch is better than that.
You're missing MY point. How does a few seconds accuracy on a watch make any difference in normal non-geek folks everyday life. It doesn't.
On 10/31/25 2:52 AM, Arno Welzel wrote:[...]
Yes - and a watch should show the exact time and not 5-6 seconds off.
Even cheap digital watches are able to do this.
Wow. Complaining over being a few seconds off?? I guess I must have had a
tough youth then. My windup watch was a minute off a day. The horror!! But
the good part was I got my exercise when I had to wind it. And gosh I often
had to (gasp) reset it. How did I ever survive?? You kids today just don't
know how good you have it... ;)
A standalone watch with a quartz crystal can deviate up to 4 seconds a
day, I think. But a watch with digital radio communications with another device should be totally in sync, because that is what we pay for. I'm talking as an electronics engineer.
You're missing MY point. How does a few seconds accuracy on a watch make any
difference in normal non-geek folks everyday life. It doesn't. But then my
current battery powered watch has mechanical hands on it and hasn't needed
to be reset since I bought it ($6 US Amazon) so maybe it's as accurate
as yours. Never know...
On 2025-10-31 22:19, Chris wrote:
AJL <noemail@none.com> wrote:
On 10/31/25 2:52 AM, Arno Welzel wrote:
Frank Slootweg, 2025-10-29 17:07:
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-28 19:35, Frank Slootweg wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
Hi,
I just noticed that there is a 6 seconds delay on my smart watch (Fitbit
charge 6) compared to my phone (Lenovo G52).
Do you mean in the displayed time?
Yes.
That would be normal, because the Fitbit has its own clock. It only >>>>>>> syncs once in a while with your phone.
5 seconds delay is not acceptable.
Well, my Fitbit Charge 5 is off (late) by 3 to 4 seconds, probably
closer to 4. So I think 5 to 6 seconds is not that bad.
I would consider it *bad* if a watch is always 5-6 seconds off when it >>>> connects via Bluetooth to a smartphone and could easily adjust it's time >>>> then.
My Casio ABL100 is syncing its time 4 times a day with my smartphone and >>>> it is always accurate within around 0.2 seconds.
[...]
Bottom line: It's a watch.
Yes - and a watch should show the exact time and not 5-6 seconds off.
Even cheap digital watches are able to do this.
Wow. Complaining over being a few seconds off?? I guess I must have had a >>> tough youth then. My windup watch was a minute off a day. The horror!! But >>> the good part was I got my exercise when I had to wind it. And gosh I often >>> had to (gasp) reset it. How did I ever survive?? You kids today just don't >>> know how good you have it... ;)
You're missing the point. A watch in 2025 should be able to be accurate to >> within a second and not drift within 24 hrs. Especially one so
technologically advanced as a smartwatch.
Not only 2025, but a watch that is constantly communicating via radio
with the smartphone. Surely sending timestamping packets should be trivial.
A standalone watch with a quartz crystal can deviate up to 4 seconds a
day, I think.
But a watch with digital radio communications with another
device should be totally in sync, because that is what we pay for. I'm talking as an electronics engineer.
That it is drifting is sloppy design and lack of attention to detail.
Yes.
A half decent analogue watch is better than that.
Well, it kept the same offset for days. It is not drifting, which means
the sync works badly, but there is some syncing going on so that the
watch doesn't deviate further.
AJL wrote:
You're missing MY point. How does a few seconds accuracy on a watch make any >> difference in normal non-geek folks everyday life. It doesn't.
I got your point. I agree it doesn't make a practical difference.
It does matter, however. As the expectation is that a watch is 100%
accurate.
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-10-31 22:19, Chris wrote:
Well, it kept the same offset for days. It is not drifting, which means
the sync works badly, but there is some syncing going on so that the
watch doesn't deviate further.
I thought you said it improved after a reboot. That sounds like drifting to me.
On 10/31/25 11:35 PM, Chris wrote:
AJL wrote:
You're missing MY point. How does a few seconds accuracy on a watch
make any
difference in normal non-geek folks everyday life. It doesn't.
I got your point. I agree it doesn't make a practical difference.
It does matter, however. As the expectation is that a watch is 100%
accurate.
NO watch is 100% accurate. If you go out enough decimal places it will be
off compared to a current standard.
Then of course it depends on your
relative velocity compared to which standard you choose to compare it to.
All impractical for most normal folks as we now apparently agree.
But to keep this sometimes dead newsgroup alive I appreciate the
discussion.
And I might add that the time on my phone lockscreen is always right... ;)
On 2025-11-01 17:51, AJL wrote:
On 10/31/25 11:35 PM, Chris wrote:
AJL wrote:
You're missing MY point. How does a few seconds accuracy on a watch
make any
difference in normal non-geek folks everyday life. It doesn't.
I got your point. I agree it doesn't make a practical difference.
It does matter, however. As the expectation is that a watch is 100%
accurate.
NO watch is 100% accurate. If you go out enough decimal places it will be
off compared to a current standard.
The expectation for networked watches is 100% accuracy.
It is different
if they are stand alone. Sure, a few seconds off true has no importance
in most of real life. But it means that there is something wrong in the >watch.
Then of course it depends on your
relative velocity compared to which standard you choose to compare it to.
All impractical for most normal folks as we now apparently agree.
But to keep this sometimes dead newsgroup alive I appreciate the
discussion.
And I might add that the time on my phone lockscreen is always right... ;) >>
On 11/1/25 12:23 PM, Carlos E.R. wrote:
On 2025-11-01 17:51, AJL wrote:
On 10/31/25 11:35 PM, Chris wrote:
AJL wrote:
You're missing MY point. How does a few seconds accuracy on a watch >>>>> make any
difference in normal non-geek folks everyday life. It doesn't.
I got your point. I agree it doesn't make a practical difference.
It does matter, however. As the expectation is that a watch is 100%
accurate.
NO watch is 100% accurate. If you go out enough decimal places it
will be
off compared to a current standard.
The expectation for networked watches is 100% accuracy.
I guess what you really mean then is that all timepieces on a network must agree to the second with the network base time. That's different from 100% accuracy with "real" time.
It is different if they are stand alone. Sure, a few seconds off true
has no importance in most of real life. But it means that there is
something wrong in the watch.
Dunno but don't think I would worry over a few seconds. Wait. I can't. My watch doesn't have a second hand... 8-O
On 2025-11-01 21:16, AJL wrote:
On 11/1/25 12:23 PM, Carlos E.R. wrote:
On 2025-11-01 17:51, AJL wrote:
On 10/31/25 11:35 PM, Chris wrote:
AJL wrote:
You're missing MY point. How does a few seconds accuracy on a watch >>>>>> make any
difference in normal non-geek folks everyday life. It doesn't.
I got your point. I agree it doesn't make a practical difference.
It does matter, however. As the expectation is that a watch is 100%
accurate.
NO watch is 100% accurate. If you go out enough decimal places it
will be
off compared to a current standard.
The expectation for networked watches is 100% accuracy.
I guess what you really mean then is that all timepieces on a network must >> agree to the second with the network base time. That's different from 100% >> accuracy with "real" time.
Yes. Absolutely. My phone is actually off by half a second (this
instant), and some times more.
It is different if they are stand alone. Sure, a few seconds off true
has no importance in most of real life. But it means that there is
something wrong in the watch.
Dunno but don't think I would worry over a few seconds. Wait. I can't. My
watch doesn't have a second hand... 8-O
The worry is that they have the technology to do it. If they don't, >something is wrong. I'd like to know what is the cause.
It is not that I worry by a few seconds.
On 11/1/25 1:57 PM, Carlos E.R. wrote:
On 2025-11-01 21:16, AJL wrote:
On 11/1/25 12:23 PM, Carlos E.R. wrote:
On 2025-11-01 17:51, AJL wrote:
On 10/31/25 11:35 PM, Chris wrote:
AJL wrote:
You're missing MY point. How does a few seconds accuracy on a
watch make any
difference in normal non-geek folks everyday life. It doesn't.
I got your point. I agree it doesn't make a practical difference.
It does matter, however. As the expectation is that a watch is 100% >>>>>> accurate.
NO watch is 100% accurate. If you go out enough decimal places it
will be
off compared to a current standard.
The expectation for networked watches is 100% accuracy.
I guess what you really mean then is that all timepieces on a network
must
agree to the second with the network base time. That's different from
100%
accuracy with "real" time.
Yes. Absolutely. My phone is actually off by half a second (this
instant), and some times more.
It is different if they are stand alone. Sure, a few seconds off
true has no importance in most of real life. But it means that there
is something wrong in the watch.
Dunno but don't think I would worry over a few seconds. Wait. I
can't. My
watch doesn't have a second hand... 8-O
The worry is that they have the technology to do it. If they don't,
something is wrong. I'd like to know what is the cause.
It is not that I worry by a few seconds.
It sounds to me like you have too much TIME on your hands.
Sorry, couldn't resist...
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,075 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 90:35:26 |
| Calls: | 13,798 |
| Calls today: | 1 |
| Files: | 186,989 |
| D/L today: |
5,332 files (1,536M bytes) |
| Messages: | 2,438,212 |