-
@BobMiles Also nothing for me. Seems to be backend initiated. Who really knows?
-
@Tim4c ahhh, checking… Is enabled
It seems to be a FW bug, or something not very well explained
Suunto: Race, S9Peak, Spartan Sport Wrist
Garmin: FR745, Edge 530
SA topics:- Guides - https://forum.suunto.com/tags/guides
-
@suzzlo You can try a soft reset
-
Improvements to this should be coming in an update.
-
I’m also in the same scenario, since the last update I have never seen the summary
-
Same for me
-
There is word that the notification sound/vibration does not fire so that is probably why people missed it.
Next Sunday, 18:00 just check the watch, the best I can advice for now
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@Dimitrios-Kanellopoulos I will try to check this sunday, but before last FW update, the phone vibrates with the summary
-
@Dimitrios-Kanellopoulos I don’t think so - I was looking at my watch at 17:59 and waited for it to show up at 1800… There was no notification
It would be nice to revisit that notification anyways, why not add it to the notifications list? -
It’s only Sunday at 18:00
-
@Mi_chael I know. i am talking about sunday
That’s what worries me! -
Could you simulate Sunday 18:00 by manually setting the watch?
-
@Darko-Vršič Well probably, yes. Bit since it’s just around the corner I’ll wait until tomorrow 1800. Or has anyone else tried already?
-
@BobMiles and everyone else. se tan alarm 17:59 sunday and you will see it.
-
@Brad_Olwin nothing! There’s no notification, it’s quite a bug.
-
@BobMiles just for the sake of documenting this, I’ve just seen it now (didn’t feel the vibration though…) on my S9, lastest fw
-
I also had no vibration or tones
-
I have watched the clock turn 1800 and there was no notification. SSWB.
Maybe I’ll try a restart, if it’s only me… -
@BobMiles it does not per say come at 18:00 sharp. but if till now you did not get it then it’s a bug.
We did had encountered this in previous test version so it looks like it did not completely go away
-
@Dimitrios-Kanellopoulos Hmmm is there anything I can do?
