Open maxz opened 10 months ago
Any updates on this?
Not really. So far it has not happened again but I also have not used the stopwatch since flashing a newer version.
I experienced this again today, but I did not use any special faces.
The only thing special I did this time was deactivate the alarm some time yesterday but I reactivated it before I took off the watch for the night.
There seems to be an undesired condition which prevents the watch from entering its low energy mode.
The only "unusual" thing I did yesterday was using the stopwatch. I measured something and stopped at exactly 10 minutes. After using it I reset it to 0 (pressing alarm once to stop it and then pressing light to reset it.) and changed back to the default face. This morning when I woke up the watch was still in its normal mode. When I switched to the stopwatch face again, started it, stopped it and reset it again, the watch properly entered the LE mode after 1 hour.
This occurred with an image based on commit
63d6bc6aa0ddf4cc1ce1918ef7650852a25e581b
.My used faces are
Additionally I used the chime
SIGNAL_TUNE_ZELDA_SECRET
.I will now flash my watch with an image based on commit
63d6bc6aa0ddf4cc1ce1918ef7650852a25e581b
, but wanted to document this before so that it will be clear that it's not due to the fix from #325.After flashing the new firmware image I will use the stopwatch more often and try to provoke this issue to see under which specific conditions it happens. Maybe someone else encountered this too and has observations.