From: robin_listas@es.invalid
On 2025-10-30 15:11, Frank Slootweg wrote:
> Carlos E.R. wrote:
>> On 2025-10-29 17:07, Frank Slootweg wrote:
>>> Carlos E.R. wrote:
>>>> On 2025-10-28 19:35, Frank Slootweg wrote:
>>>>> 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).
>>>>>
>>>>> 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.
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.
>
> 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.
>>
>>>
>>> [...]
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
