Under Review
over 1 year ago

Receiving a (phone-)notification puts the watch face in a permanent low power mode with an update interval of 1 second

The issue has been observed on Epix2 and MARQ Gen2 devices with recent firmware.

This bug potentially wasts battery life.

See the following videos for evidence of the issue:
https://photos.app.goo.gl/3mC9UhDpQFa3zKwLA
After considering the display brightness I assume that the watch is in low power mode but I'm not 100% sure.

The videos show my watch faces running the burn-in protection toggling pixels in 1 second intervals rather than 1 minute invervals.
As a workaround I will change to toggling pixels by checking System.getClockTime().min % 2.

In one of the reported cases the user had the watch face stuck in this state permanently and was only able to escape this state by switching to another watch face back and forth.

Parents
  • Of course I'm aware of the alpha/beta programs and with my previous device I was enrolled in the beta.
    Initially I thought you have seen this particular issue mentioned in the alpha/beta forums.
    Since I do not own an Epix2 I can't verify if the latest alpha/beta still has this issue.
    That is why I keep this report here for now and I'm hoping somebody from Garmin will pick it up.

    The issue has been reproduce by the two users who kindly provided the recordings with the latest official firmware V10.44.

Comment
  • Of course I'm aware of the alpha/beta programs and with my previous device I was enrolled in the beta.
    Initially I thought you have seen this particular issue mentioned in the alpha/beta forums.
    Since I do not own an Epix2 I can't verify if the latest alpha/beta still has this issue.
    That is why I keep this report here for now and I'm hoping somebody from Garmin will pick it up.

    The issue has been reproduce by the two users who kindly provided the recordings with the latest official firmware V10.44.

Children
No Data