-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not entering LE mode under certain conditions #355
Comments
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. |
I use another firmware with other faces but encounter the same issue. My firmware is similar to the default one, except:
This means @maxz and I have in common the simple_clock_face, preferences_face and set_time_face. They all are included in the default firmware also. @maxz: You mentioned "alarm" in your last posting, does that mean you also run a face like wake_face as well? May be I should also mention that low energy used to work for me and my firmware but stopped a few days/weeks ago without having me to change habits or usage noticeably. |
No, only the mentioned faces, @drtrigon. I probably meant the hourly chime. |
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.
The text was updated successfully, but these errors were encountered: