GCM update

Mine syncs and if forced to sync, doesn't delete alarms created in the watch. Can anybody confirm?

Just tried on my Galaxy S7 Edge after performing the GCM update. When I did a force synch it wouldn't over ride the watch alarm settings and I was quite excited for a while thinking the problem had been fixed but 30 mins later when it has synced by itself it did over ride my watch alarm settings. So for me the problem still exists, and I need to ensure I set my alarms etc on GCM and not on the F5 :(

Mine syncs and if forced to sync, doesn't delete alarms created in the watch. Can anybody confirm?

I did a fair bit of testing this morning and I can confirm that your alarms are no longer affected unless you make a change to the alarms in connect. Once you do that it will reset the alarms on your watch to match the alarms in connect. They've also put into the app the ability to modify the tone/vibration for your alarms.

Just confirmed it again, I made no changes in GCM and I toggled one of my set alarms on my watch from on to off and did no forced sync's or even opened GCM to be sure and just let the synch happen on it's own accord which occurred around 30mins later and the alarm which I had toggled to off had been turned back on again. This is on Android. I guess each user will need to confirm his or her own case scenarios I guess but from my perspective this issue still isn't resolved.

Stupid question time but is this with the latest app update?

Just confirmed it again, I made no changes in GCM and I toggled one of my set alarms on my watch from on to off and did no forced sync's or even opened GCM to be sure and just let the synch happen on it's own accord which occurred around 30mins later and the alarm which I had toggled to off had been turned back on again. This is on Android. I guess each user will need to confirm his or her own case scenarios I guess but from my perspective this issue still isn't resolved.

Same with the iOS-version, though Forerunner 935. What a disgrace.

Same question as I asked Vince142 - have you updated the app to v3.19?
I'm pretty sceptical that it's been fixed 100%, but I ran through all the ways that I could over-write the watch alarms that used to wipe them out and my alarms stayed on the watch fixed this time round.
We'll see if it holds up but so far so good...

Yes, latest version from yesterday evening. First thing was that I checked alarms. Created one on my 935 and one on GCM. Performed a sync and my alarm on the 935 was gone. Very bad.

Yes, latest version from yesterday evening. First thing was that I checked alarms. Created one on my 935 and one on GCM. Performed a sync and my alarm on the 935 was gone. Very bad.

Ah - in my testing that is exactly what I did as well. The update doesn't include 2-way syncing so the moment you make a change to the alarms in Connect it will still over-write all the alarms on your watch.
Which isn't ideal but it is better than what was happening before.

What this update has changed is that if you create an alarm on the watch then as long as you don't change alarms in Connect your watch alarm will persist even if you make changes to other watch settings in Connect.
As soon as you add/change/delete an alarm in Connect your watch alarms will be reset to whatever alarms are in Connect.

Does that make sense? Basically you can either set alarms on the watch or set them in Connect.
This isn't perfect, but it's better behavior than before when the watch would always reset to the Connect alarms no matter what.