@Jaxxdu
Yeah, I didn’t have the issue for quite a while, and it doesn’t happen very often for me — but it’s still a bit annoying.
Looking back, it almost feels like it tends to show up once after a firmware update.
Normally I don’t restart my watch at all, and it runs fine for months. Today the sensors came back to life simply by toggling the energy-saving mode on and off.
When I compare it to other devices that need frequent reboots to behave properly, the watch is actually quite robust.
On the other hand, maybe the issue pops up more often because of restarts — who knows.
Not sure how often it happens for others, but it seems to affect the Race S as well.