Well, you need to have the background service running to receive notifications. It’s the app that manage the notifications, not the phone itself.
If you previously used MC the service was running but without showing any icon.
If you check the app watch settings (watch icon - 3 dots) you’ll se an option “enable/disable mobile notification”
Regarding HR on watchface , that’s not possible (yet)
Apologies => I just copied this comment into another thread (Running lap times not matching watch), which seems to be even more fitting in the description.
As I don’t want to add another thread and have not found a better one:
I find it is a more than a little bit annoying, that there is (the last three runs exactly) 10 seconds difference in the lap-time of the first kilometer between the watch (SSWHR) and the app (the app is faster by 10 seconds), all other kilometers differ only slightly and only sometimes (mostly a maximum of 1-2 seconds).
Running distance is between 10,x and 13,x kilometers.
The overall distance and time (etc) is identical.
@Dimitrios-Kanellopoulos Incidentally, it happened to a friend today after upgrading firmware to the latest (SSS).
Could not pair with MC. Only thing that worked was the airplane mode.
One more trick on our toolset.
@kolyany4 if it had to overlay others yes.
I also do not use linear in my apps when one stream only is available. Its based to timestamps so I don’t see a bug. But aligning timestamps when 1 and more charts are available should have a liner scale.
FYI you can export the fit file from sytava or Movescount and load it to my app to detect any issues.
App is quantified-self.io
Really really annoying that they do not appear. So even for very very simple analysis like that (time, length, pace and heart rate in each chunk of training) one must still rely on Movescount.
Same problem with SSU 2.5.18 and SA 3.59.5. For example on my last two outdoor cycling moves, the asc and dsc in the watch were reported correctly and SA reported the asc completely wrong and the dsc was the same as in watch.
I noticed something else regarding altitude … while downhill skiing, the watch sometimes failed to record about 200 m of altitude at a time on consecutive runs. It was clearly visible in the graph.
This is the downhill ski move:
Asc and dsc should be the same (approx 8300 m vertical as reported by the ski-data keycard) as I started and stopped the watch in the valley.