Ticket Created
over 5 years ago

WERETECH-8716

Bug when you set backlight Not during activity Gesture OFF, before 23h59 high power is OK after 00h00 Hight power is no ore operationnal

Hi

On F5X , F5 Plus, F6X  and probably with all F5 series, F5 plus series F6 series, MArq series, 935, 945 , I detect a bug when the watch switch from 23h59 to 00h00 

High power mode is no more operational.

For testing

Set time to manual

Set backlight

not during activity

Gesture OFF

Set time to 23h59.

When you turn the wrist your watch enter in high power mode and onExitSleep is called , after 10 sec onEnterSleep function is called . All is good

Just  after 00:00 when you turn the wrist onExitSleep function is no more called.  

On my watches face i make some actions when the user turn the wrist. new page or new functions

With this settings no more possibility to turn the wrist.

If you set Gesture ON or gesture after Sunset  all is good.

The bug is only when the watch switch from 2359 to 0000

  • I tried the gesture after midnight and it didn't work. But then I realized that my sleep time is set to 0:00-9:00, so this can be either because of midnight or because of the sleep time, so I changed the sleep time to 0:30, and tested again at 0:31 and the gesture worked. So I can confirm that indeed midnight is the problem.

  • Do I understand it well that a ticket was created, but this issue has NOT been fixed by Garmin? Otherwise the status of the bug report would be different, wouldnt it?

  • Moreover I can confirm that beside the midnight effect there is other bug related to OnExitSleep of Fenix 5+. After a couple of hours of inactivity like 2-3 hours, meaning that neither keys have been pushed nor wrist turn happened, OnExitSleep does NOT work, so wrist turn cannot activate it. Anyone can double check it.

  • I see that the state changed to Ticket created. What does it mean in practice? Is it an official approval that the bug webt to Garmin’s developer team to deal with and there is a substantial chance for a fix?

    Or does it purely mean that somebody as a 4-eyes principle player confirmed the existence of the bug and nothing more?

  • I am just a user discovered the midnight bug and not a developer, but since it seems that Fenix 3 HR is free from this bug therefore let me highlight the note from its latest software update:

    ”Changes made from version 5.00 to 5.40:

    •  an intermittent issue where the device might crash around midnight.