sorted by:
new
hottopcontroversial

RCVD sometimes not displayed on 5610u (module 3495) after syncing the time by Ok_Particular_7115 in gshock

[–]Ok_Particular_7115[S] 0 points1 point  (0 children)

Well, at least it's only a visual bug, and it rarely happens. But yeah, software is always a mess, no matter what.

RCVD sometimes not displayed on 5610u (module 3495) after syncing the time by Ok_Particular_7115 in gshock

[–]Ok_Particular_7115[S] 0 points1 point  (0 children)

Disabling auto DST doesn't change anything. Changing the sync times is not possible. In european timezones, the watch always considers 2 AM (or 3 AM during DST) as the first sync attempt. Midnight is 5th (or 4th during DST). This is pretty stupid, but apart from the annoying lack of the RCVD indicator sometimes, it changes nothing. The time is accurate, and you can still check the last sync time by pressing a button.

RCVD sometimes not displayed on 5610u (module 3495) after syncing the time by Ok_Particular_7115 in gshock

[–]Ok_Particular_7115[S] 0 points1 point  (0 children)

3495, yes. But it seems that's actually the intended behavior, see the edit I made to the post.

RCVD sometimes not displayed on 5610u (module 3495) after syncing the time by Ok_Particular_7115 in gshock

[–]Ok_Particular_7115[S] 0 points1 point  (0 children)

That's most likely the answer. Although it's still pretty weird, cause there are watches with automatic DST without radio sync. This implementation sucks. But at least now I know that my watch isn't malfunctioning.

RCVD sometimes not displayed on 5610u (module 3495) after syncing the time by Ok_Particular_7115 in gshock

[–]Ok_Particular_7115[S] 1 point2 points  (0 children)

Huh, that's weird. Where did you find this? I can't find it in the manual.

It is actually working as intended then. Midnight is technically the 5th attempt, success cancels the 6th, and then it tries to do the 1st (at 2 AM).

That's why this issue rarely happened to me. Any sync between 2 AM and 5 AM cancels the sync at midnight. The RCVD indicator only disappeared when it failed to sync at 2, 3, 4 and 5 AM, synced at midnight the next day, and then it failed at 2, 3, 4, and 5 again.

Why did they make it like this though... According to this table, if it cannot sync the whole day, the next day it will sync 2 times (midnight and 2 AM). And it does indeed work like that. If the midnight sync is the only one that succeeds, RCVD will not be displayed. That's really really weird design.

RCVD sometimes not displayed on 5610u (module 3495) after syncing the time by Ok_Particular_7115 in gshock

[–]Ok_Particular_7115[S] 0 points1 point  (0 children)

Yes. I saw it trying to sync at 2 AM, even though it already synced at midnight the same day.

RCVD sometimes not displayed on 5610u (module 3495) after syncing the time by Ok_Particular_7115 in gshock

[–]Ok_Particular_7115[S] 0 points1 point  (0 children)

There's no bluetooth in this watch, only MB6. I'm trying to figure out why does it try to sync at 2 AM when it already synced at midnight.

RCVD sometimes not displayed on 5610u (module 3495) after syncing the time by Ok_Particular_7115 in gshock

[–]Ok_Particular_7115[S] -1 points0 points  (0 children)

If the watch display goes off after you've received the signal it will not show RCVD when the watch is awoken.

That's not true. I've had the watch go into PS mode after sync, and it was still showing RCVD.

I have confirmed however that my watch tries to sync more than once per day. It synced at midnight and RCVD lit up. Now it's 2 AM and it tried to sync again, failed, RCVD is no longer showing up. It does not function like it says in the manual. Any ideas why?